Privacy Policy

Last updated: 18 November 2026

1Gesture (“we”, “our”, “us”) operates a meeting reminder and impact gesture service. This Privacy Policy explains what data we collect, why we collect it, how we protect it, and the rights you have over it. We are committed to transparency and to handling your data responsibly under the UK GDPR, the EU General Data Protection Regulation (GDPR), and the California Consumer Privacy Act (CCPA).

1. Data We Collect

Account Data

When you create an account via Google or Microsoft OAuth, we receive and store:

Calendar Event Data

With your explicit consent, we read your Google Calendar or Microsoft Outlook Calendar to find your upcoming meetings. We retrieve:

We read your calendar only to find upcoming meetings. We do not currently create, edit, or delete calendar events. To deliver reminders, we send emails on your behalf from your own connected mailbox. See Section 7 for the exact permissions we request and why. We store these details encrypted with each meeting; some guest details are also kept unencrypted (see Section 10).

Email Sending

To deliver meeting reminders, 1Gesture sends emails on your behalf from your own connected Google (Gmail) or Microsoft (Outlook) mailbox, using the send permission you grant at sign-in. These emails go to your meeting attendees or the meeting organiser, and contain the reminder and impact-gesture content you have configured. We do not read your existing emails, and we do not send anything other than the reminders you set up.

Payment & Billing Data

If you buy Gestures, or are on a legacy subscription plan, payments are processed by Stripe. We store billing identifiers (your Stripe customer reference, and for a legacy subscription plan its subscription identifier) and invoice and transaction metadata (amounts, dates, plan). We do not store your full card number: card details are collected and held directly by Stripe as a PCI-DSS compliant payment processor.

Default Gesture & Automatic Donation of Unused Gestures

If you are on a paid plan, an administrator chooses your organisation’s default gesture in Settings. Gestures you buy on the Unlimited plan, including through automatic top-up, expire 12 months from the purchase they came from. On a legacy Starter, Pro or Team plan, each month’s Gestures expire at the end of that billing period, and a Boost expires one month after it is bought. Whatever you have not used when Gestures expire goes to the good cause behind your organisation’s default gesture, on the same basis as a Gesture a guest chooses (see Section 4 of our Terms of Service). Where no default gesture has been set, it goes to a verified cause selected by 1Gesture. We record each automatic donation in our impact ledger (organisation, gesture, cause, amount and date) so that it is auditable and appears in your impact totals and in our reporting to the receiving Gesture Partner. An administrator can change your default gesture at any time in Settings, which changes where Gestures that expire later go. No personal data about your meeting attendees is involved in this processing; the legal basis is the performance of our contract with you (UK GDPR Art. 6(1)(b)).

Uploaded Content

If you upload an organisation logo to brand your reminders, the image file is stored using Vercel Blob storage and served from there.

Team & Organisation Data

If you use 1Gesture as part of a team or multi-user organisation, we store your organisation membership, your role (for example, administrator or member), and any invitations sent or received. Organisation administrators can see the members of their organisation and organisation-level activity and impact.

LinkedIn Waitlist

If you join the waitlist on our LinkedIn page, we collect your name and at least one of your email address or your LinkedIn profile link, plus whether you ticked the box to hear occasional news from us (and, if you did, when you ticked it and the exact wording you agreed to). We record the time you joined. We keep this in our customer records in HubSpot, not in our own database. If you are already in our customer records, for example because we are connected on LinkedIn, we add the waitlist details to that record and do not change the name, email address or profile link already there. We use your LinkedIn profile link to connect with you on LinkedIn, so you can see the experience for yourself.

Attendee Interaction Data

When attendees receive reminder emails sent on your behalf, we collect:

Emails After You Ask for a Gesture

If you ask for a Gesture on one of our advert pages and tick the box to receive occasional emails about 1Gesture, we may send you a small number of follow-up emails. We record that each email was sent and when a button in it is pressed, and we keep that with your request. We do not record whether an email was opened. Every one of these emails has an unsubscribe link.

Product & Usage Analytics (first-party)

We operate our own first-party product analytics, stored in our primary application database (Supabase, United Kingdom). With your consent, analytics also runs in your browser and is sent directly to PostHog (EU Cloud, hosted in the European Union), which acts as a processor for us and is never our system of record; we also forward a server-side copy of our product-analytics events there. Consented analytics can include masked session replays: recordings of how our pages are used in which all text, typing and form entries are hidden before anything leaves your browser. This analytics is never used for advertising. If you have accepted analytics cookies and you sign in to your account, we tell PostHog your account’s internal user number (never your name or email address), so that what you do in your browser and what our server records for your account are held together as one person; when you sign out, the browser starts again under a new number. Deleting your account deletes that record from PostHog too. PostHog uses your IP address once, to work out your approximate country and region (for example, England or California), and then discards it: it is configured not to store your IP address, and it does not record your town, postcode or coordinates. The analytics described in this paragraph and the list below, which use cookies and similar storage, run only after you give consent via our cookie banner, and you can withdraw consent at any time (see your rights in section 5 and our Cookie Policy). The anonymous measurement described further down this section uses no cookies or storage; choosing Essential only switches it off too.

With your consent we also run the HubSpot (USA) tracking code, which records the pages you view on our website. Unlike the analytics above, this one is not anonymous: where you are already one of our contacts (because you hold an account with us, or because we sent you a personal link), we tell HubSpot which contact you are, so that your page views appear on your record and we can see which pages are useful to the people we work with. We do this only for account holders and for people we have sent a personal link to; visits by anyone else are recorded without a name. We do not do this for meeting attendees choosing a Gesture. The HubSpot cookies, and how long they last, are listed in our Cookie Policy.

With your consent we also use Google Analytics (Google, USA) on every page of our website to count visits and see where visitors came from. Before any page address is sent to Google we remove private codes and names from it, and everything after the “?” except campaign tags, so a personal link we sent you never reaches Google. It is used for analytics only; Google’s advertising features are switched off. The Google Analytics cookies, and how long they last, are listed in our Cookie Policy.

Advertising (Meta). If Advertising is on in our cookie banner, we use the Meta Pixel from Meta Platforms (the company behind Facebook and Instagram) to measure whether our adverts work and to show them to people likely to find them useful. Advertising is a separate choice from analytics. It is off until you turn it on, except for visitors in the US outside California, where it is on until you turn it off (see below). Your browser then tells Meta which of our public pages you viewed, with the IP address and browser details every browser sends, and Meta sets cookies that recognise your browser and whether you came from one of our adverts. If you then ask for a Gesture on one of our advert pages, sign up from one of them, or buy a plan, our server tells Meta that a form was sent, a sign-up or a purchase happened, a purchase’s value and currency, your email address (and, for the form or a sign-up, your first name) in a scrambled (hashed) form that Meta can match to its own accounts but cannot read back, and those Meta cookies. Meta can link this to a Facebook or Instagram account you hold and uses it for its own purposes too, under its own privacy policy; for the data the Pixel collects, Meta and 1Gesture are joint controllers. We never use the Meta Pixel inside your signed-in account, on pages reached through a personal link, or for meeting attendees choosing a Gesture. Switching Advertising off stops all of this from that moment. Details are in our Cookie Policy.

Sign-ups and purchases in the US. We tell from the location of your internet connection whether you are in the US, and which state. If you are in the US outside California, the Meta Pixel runs by default, before you make a choice in our cookie banner, and you can switch it off. In California, and if we cannot tell your state, it runs only after you accept Advertising. Wherever you are in the US, when you sign up, when you ask for a Gesture on one of our advert pages, and when you buy a plan, our server tells Meta by default, even if you have not switched Advertising on. It sends that a sign-up, a form submission or a purchase happened, a purchase’s value and currency, your email address, name and account number in a scrambled (hashed) form, your IP address, your approximate location (your state), the type of browser you used, and Meta’s own cookies if the Meta Pixel ran in your browser. Meta can link this to a Facebook or Instagram account you hold and uses it for its own purposes as well as ours, under its own privacy policy. You can stop all of it in three ways: switch Advertising off in our cookie banner, or choose Essential only; turn on Global Privacy Control in your browser; or use our Do Not Sell or Share My Personal Information page. If you are signed in when you use that page, we also remember your opt-out on your account, so it applies whichever browser you buy from. An opt-out always wins, even over an earlier choice to switch Advertising on. Outside the US, nothing changes: the Meta Pixel runs, and we tell Meta about a purchase or an advert-page form submission, only if you have switched Advertising on, and we tell Meta about a sign-up only if you started it from one of our advert pages and have switched Advertising on. More in section 5b.

When enabled with your consent, we collect:

We use this strictly to understand and improve the product. We do not use it for advertising or for automated decisions that produce legal or similarly significant effects about you, and we never place payment-card or sign-in-token data into analytics. We may run non-manipulative A/B experiments (for example, comparing two dashboard layouts) to improve the product; we do not run experiments designed to reduce the funds reaching good causes.

Independently of the consent-based analytics above, and on the basis of our legitimate interest in operating and securing the service, we also record a small set of operational signals that do not require consent: generic, pre-defined diagnostic reason codes when an action fails (for example, that a sign-in was declined or a payment was not authorised), never raw error messages or free text; and email deliverability outcomes for the system emails we send (whether a message was delivered, bounced, or marked as spam), with spam-complaint signals kept only in aggregate and never linked to your account.

We also count visits to our site without cookies and without identifying you. For each arrival we record the page, the site you came from, any campaign tags in the link, and your country. On pages with a video we also record, in the same way, how many seconds of it were played, and whether it was played with sound and to the end. We also count, in the same way, how many visitors choose Accept all and how many choose Essential only. On the page where you choose a Gesture we also count, in the same way, whether a Gesture was selected. On our forms that send you a Gesture we also count, in the same way, whether someone started filling one in, never what was typed. So that the pages of one visit can be counted together, we also record, in the same way, each later page you open on our site during that visit, and our server puts a visit number on these counts. It is a number of the kind described in the next paragraph: our server makes it from your IP address and your browser’s description of itself, using a secret that we replace and delete every day, so it cannot be traced back to you or connected to a visit on any other day. This number is kept only in our own records. It is never stored in your browser or sent to it, never attached to your name, email address, account or a form you send, and never sent to PostHog. We do not make it while your browser sends the Global Privacy Control signal, or for visitors in the places named in the next paragraph where we do not carry out that measurement. After you confirm a Gesture from one of our advert pages, we also record, without cookies, which of the next pages you open and whether you press a sign-in button on it, against the Gesture request you made, so we can see which requests lead to a sign-up. We do not store your IP address or anything in your browser for this, and it happens whether or not you accept analytics cookies. A copy goes to PostHog with nothing in it that could link one visit to another. If the link that brought you here carried campaign tags and you create an account during the same visit, we record those tags against the sign-up, so we can tell which campaigns bring customers. If you accept analytics cookies, we collect more, as described above.

Anonymous measurement of how our website is used. Unless you choose Essential only in our cookie banner, or your browser sends the Global Privacy Control signal, we capture anonymous data about visitors’ journeys through our website, so that we can analyse in aggregate how the site is used and improve it. This covers which pages are viewed and in what order, how long is spent on them and how far they are scrolled, which buttons and links are clicked, how our videos are watched, and the approximate country and region a visit comes from. It does not include recordings of how a page is used, or where on a page visitors click and move the pointer: those are made only if you accept analytics cookies. We do this without cookies: nothing is stored in your browser for it, and nothing stored there is read. So that the pages of one visit can be counted together, our server makes a number from your IP address and your browser’s description of itself, using a secret that we replace and delete every day. For visitors in the European Union and the European Economic Area we use only the first part of your IP address for this, not the whole of it. Your IP address is used for that calculation and is not stored. Once a day’s secret has been deleted, that day’s number cannot be traced back to you, or connected to a visit on any other day, by us or by anyone else. The data is held by PostHog (EU Cloud), which uses your IP address once to work out your approximate country and region and then discards it; it does not record your town, postcode or coordinates. It reaches PostHog through an address on our own website, not through a third-party address in your browser. We do not attach your name, email address or account to it, we do not link it to the analytics you may separately consent to, and we do not collect it inside your signed-in account. We do not carry out this measurement for visitors in Germany, in Quebec, in California, or elsewhere in the United States when we cannot determine the state. We use it to understand how the site performs as a whole, not to follow individual visitors, and never for advertising. We rely on our legitimate interest in understanding and improving our website (UK GDPR Article 6(1)(f)); choosing Essential only switches it off at once in that browser, and you can object at any time by emailing privacy@1gesture.org.

On the same legitimate-interest basis, our own operations team reviews internal usage reports derived from your use of the service (for example, how often meetings included an impact gesture, or how many gestures were funded over a period). In these reports, individual members appear under a pseudonymous label rather than a name or email address, access is restricted to authorised platform operators, and every view of a report is itself logged. These reports are used only to operate and improve the service, never for advertising, and never for automated decisions that produce legal or similarly significant effects about you.

2. Legal Basis for Processing

Under the UK GDPR and EU GDPR, we process your personal data based on the following legal grounds:

Legal Basis GDPR Article Purpose
Consent Art. 6(1)(a) Reading your Google or Microsoft calendar; sending reminder emails on your behalf from your own connected mailbox; and, where you have given consent, non-essential first-party product analytics; where you have switched on advertising cookies, measuring our adverts with Meta; and sending occasional news to people who ticked the box when joining our LinkedIn waitlist
Contract Art. 6(1)(b) Delivering the service you signed up for, processing impact gestures on your behalf, billing for paid plans, and storing your timezone for meeting time display
Legitimate Interest Art. 6(1)(f) Service operation, security, error monitoring, and anonymised analytics to improve the product. Also keeping customer records in our CRM, and emailing account holders about our own services. Telling people who joined our LinkedIn waitlist when it launches, and connecting with them on LinkedIn, which is what they asked us for when they joined. You can tell us to stop at any time and we will stop.
Legal Obligation Art. 6(1)(c) Retaining billing and transaction records to meet tax and accounting obligations

You may withdraw your consent at any time by revoking 1Gesture's access in your Google or Microsoft account settings, by disconnecting your account in 1Gesture. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.

3. Third-Party Data Processors

We share data with the following third-party processors, each under appropriate data processing agreements:

Processor Purpose Data Shared Location
Google (OAuth, Calendar API, Gmail send) Authentication, reading your calendar, and sending your reminders from your Gmail address OAuth tokens, calendar event metadata, reminder email content USA / global
Microsoft (OAuth, Graph API) Authentication, reading your calendar, and sending your reminders from your Outlook address OAuth tokens, calendar event metadata, reminder email content USA / global
Resend System and transactional email delivery (e.g. account, verification, and billing notifications) and fallback sending; also provides Svix-signed deliverability webhooks (delivered, bounced, marked as spam) used only in aggregate Recipient email, email content; deliverability status (aggregate spam-complaint signals are never linked to your account) USA
Stripe Payment processing for paid plans Billing identifiers, invoice/transaction metadata, card data (collected and held by Stripe) USA
Vercel Application hosting (serverless infrastructure) Request data in transit, server logs, IP addresses USA / global
Vercel Blob Storage of uploaded organisation logo images Logo image files USA / global
Supabase Primary application database (PostgreSQL) Stored account, calendar, gesture, team, and billing-metadata records United Kingdom (London, eu-west-2)
Google Cloud (Cloud Key Management Service) Holds the master key that protects the key we use to encrypt meeting details from your calendar An encrypted copy of our data key and logs of our application's key requests. It never receives meeting details or guest details United Kingdom (London, europe-west2)
PostHog (EU Cloud) Secondary product-analytics & backup store (server-side mirror of first-party events); not the system of record. Also holds the anonymous measurement of website use described in section 1 Pseudonymous analytics identifier, coarse device family, page/interaction events, first-touch UTM, approximate country and region (no stored IP, no payment or sign-in data). For anonymous measurement: an anonymous visitor number that changes daily, page/interaction events, approximate country and region, and masked page recordings European Union
Google (Google Analytics) Website analytics, only with your consent: counting page visits and where visitors came from. Advertising features are switched off A random identifier stored in a cookie, the pages you view (with private codes and names removed from the address), the website you came from, your browser and device type, and your approximate location derived from your IP address USA
Cloudflare Content delivery network and security (DDoS protection, WAF) IP addresses (processed transiently for security) Global
Anthropic (Claude API) AI-powered support chat assistant. Your messages are processed by an automated AI model (Claude) to answer FAQ-based questions, with escalation to a human when it cannot confidently answer. The same model also runs the guided questions when you report a bug or suggest an idea. The support-chat messages you type, which may contain any personal data you choose to include (such as your name, email address, or a description of your issue). When you report a bug we also collect basic technical details automatically: the page address without its query string, your browser and screen size, language, time zone, and any recent error messages from the page. USA
HubSpot Support ticketing, our customer records (managing your account, telling you about our own services, and holding our LinkedIn waitlist), and, with your consent, website analytics Your name, email address, support ticket subject and message, and the full support-chat transcript. If your organisation has an account with us, we also hold its name and website domain, its plan, its signup date, its number of seats, its Stripe customer reference, the total it has spent and the total refunded to it, its service usage, and whether you have asked us not to send you marketing. For an organisation on a legacy subscription plan we also hold its subscription status, billing frequency, renewal date, its monthly price, and whether it is set to cancel at the end of the period. If you joined our LinkedIn waitlist, we also hold your LinkedIn profile link, when you joined, and your choice about occasional news. If you consent to analytics cookies, it also holds the pages you viewed on our website, linked to your record where we already hold one USA

We share the limited data described in section 1 under “Advertising (Meta)” and “Sign-ups and purchases in the US” with Meta Platforms (Ireland and USA): if you switch on advertising cookies, or, if you are in the US, when you sign up, send our advert-page form or buy a plan and, outside California, through the Meta Pixel by default, unless you have opted out. Meta uses it for its own purposes as well as ours (for the Pixel, as a joint controller), so it is not our processor and is not listed in the table above. We do not sell your personal data for money. Outside the US, we share nothing with Meta or any other advertiser unless you have switched advertising cookies on.

4. Data Retention

5. Your Rights

Under the UK GDPR and EU GDPR, you have the following rights regarding your personal data:

Please note that the right to erasure does not extend to records we are legally required to keep, in particular billing and transaction records retained to meet tax and accounting obligations (see Section 4).

If you are in the US, including California, section 5b sets out your rights there, including the right to opt out of the sale or sharing of your personal information.

To exercise any of these rights, email privacy@1gesture.org. We will respond within 30 days.

5b. US privacy rights, including California

This section is for people in the US, including California residents under the California Consumer Privacy Act as amended by the California Privacy Rights Act (together, the “CCPA”).

What we share with Meta, and why. When someone in the US signs up, sends our advert-page form or pays for a plan, we give Meta Platforms, Inc. the details below, so we can measure our adverts on Facebook and Instagram and show them to people likely to find them useful. Meta may also use it to show adverts on its own services and elsewhere. Under the CCPA this can count as “sharing” personal information for cross-context behavioural advertising. The categories are:

When the Meta Pixel runs. In the US outside California, it runs by default and you can switch it off. In California, and if we cannot tell your state, it runs only after you accept Advertising in our cookie banner.

We do not sell for money. We never sell your personal information for money. 1Gesture is not meant for anyone under 18 (see section 9), and we do not knowingly sell or share the personal information of anyone under 16.

Your right to opt out of sale or sharing. You can tell us not to sell or share your personal information, in any of three ways:

We honour Global Privacy Control as a valid opt-out request. While your browser sends it, we do not load the Meta Pixel, we do not tell Meta when you sign up, send our advert-page form or buy, and we do not carry out the anonymous measurement of how our website is used described in section 1. An opt-out always wins, even over an earlier choice to switch Advertising on. You can allow it again on the same page; that takes the opt-out off your account but does not switch Advertising on, which only you can do in the cookie banner.

Your other rights. You also have the right to know what personal information we collect, use and share, to have it corrected, and to have it deleted, subject to the records we must keep (see section 4). We will not treat you differently for using any of these rights: opting out never changes your price or the service you get. To use them, email privacy@1gesture.org. We will respond within 30 days.

6. Attendee Privacy

A guest’s Gesture choice is shared with the meeting organiser. The reminder email tells the guest this before they choose. We do not show a guest’s choice to other attendees.

When attendees interact with 1Gesture reminder emails:

By default, when an attendee chooses a gesture from one of your reminder emails, the thank-you page they see displays your aggregate lifetime impact through 1Gesture, for example, “120 plastic bottles removed, 23 school meals provided, 12 days of clean water”. Only summed totals per gesture type are shown; no per-meeting detail, no attendee names, and no information that could identify a specific event is exposed.

Our lawful basis for this processing is legitimate interest under UK GDPR Article 6(1)(f): the disclosure supports recipient-to-sender conversion (a core growth mechanism of 1Gesture) and is proportionate to the limited, aggregate-only data involved. You can object at any time by switching off the toggle in Settings → Branding → Show my running impact; the totals stop appearing on the thank-you page immediately (subject to a short cache propagation window of up to five minutes).

If you would prefer never to have your impact totals appear on recipient thank-you pages, you may keep the toggle off; we will not use that data on the public surface. We may still use it internally for your own dashboard and to compute platform-wide totals.

6b. Cross-recipient referrer parameter (email “?ref=email-seed”)

Reminder emails sent on your behalf may include a link to 1gesture.com tagged with a ?ref=email-seed query parameter. We use this parameter solely to measure recipient-to-sender conversion attributable to that link. The parameter does not encode any recipient or meeting identifier and does not enable us to single out any individual attendee.

These links, and the “Powered by 1Gesture” and invitation links in a Gesture email, may also carry a short code (k=) that stands for the organisation that sent the email. If someone who followed one of those links later fills in a form or signs up, we record which organisation’s email brought them, so we can see how 1Gesture spreads from one organiser to the next. The code is the same for every email that organisation sends; it does not encode any recipient or meeting identifier.

6c. Public organisation impact page

If your organisation is on a paid plan (Unlimited, Pro or Team) and has set a public profile slug, 1Gesture publishes a public web page at /impact/<your-slug> showing your organisation's name and its aggregate impact totals (for example, “120 plastic bottles removed, 23 weeks of school meals”). Only your organisation name and summed totals are shown, never attendee names, email addresses, meeting details, individual choices, or any financial information.

This page is on by default for eligible organisations. You can switch it off at any time using the public impact control in your organisation settings. When it is off, the page returns a “not found” response and your impact data is not queried for the public page at all.

7. OAuth Scopes & Permissions

To provide the service, 1Gesture asks for your permission to access parts of your Google or Microsoft account. You are shown these permissions on the provider's consent screen at sign-in, and you can revoke them at any time. We request the following:

Google

1Gesture's access to, and use of, information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The only Google account data we access is your basic profile and email address (for sign-in), read-only access to your calendar (to find your upcoming meetings), and permission to send email on your behalf via gmail.send (to deliver your reminders from your own Gmail address). We use this data solely to provide and improve these features for you; we do not use it for advertising; we do not transfer it to others except as necessary to provide the service, to comply with applicable law, or in connection with a merger or acquisition; and we do not allow humans to read your Google data except with your affirmative consent for specific messages, where necessary for security or to comply with the law, or where the data has been aggregated and anonymised. We do not request any “restricted” Google API scopes, and we do not read the contents of your Gmail mailbox.

Microsoft

8. Cookies

1Gesture uses a minimal set of essential and functional cookies, plus analytics storage that is set only with your prior consent. That consented set includes cookies set by HubSpot, the system we keep our customer records in, which record the pages you view on our site. Separately, Meta sets cookies used to measure our adverts on Facebook and Instagram, only if Advertising is on: you switch it on, except in the US outside California, where it is on until you switch it off. We use no other advertising cookies, and no other cross-site tracking cookies.

For full details on the cookies we set, their purpose, and duration, see our Cookie Policy.

You can change or withdraw your analytics or advertising cookie choice at any time using the button below; withdrawing is one click on Essential only and takes effect immediately. In the US outside California, Essential only is inside Manage.

9. Children's Privacy

1Gesture is not intended for use by anyone under the age of 18. We do not knowingly collect personal data from individuals under 18. If you believe we have inadvertently collected data from a minor, please contact us immediately at privacy@1gesture.org and we will delete the data promptly.

10. Data Security

We implement appropriate technical and organisational measures to protect your personal data, including:

11. International Data Transfers

Several of our third-party processors operate outside the United Kingdom and the European Economic Area (EEA), in particular Google, Microsoft, Stripe, Resend, Vercel, Anthropic, HubSpot, Google (Google Analytics, only with your consent) and, when Advertising is on, Meta, which process data in the United States, and Cloudflare, which operates globally. Our primary database, hosted by Supabase, is located in the United Kingdom (London / eu-west-2 region), so that data is not transferred outside the UK for storage; for users in the EU/EEA, the UK benefits from a European Commission adequacy decision. Our secondary analytics store, PostHog, is hosted in the European Union (EU Cloud), so first-party product-analytics events forwarded to it remain within the UK/EEA.

Where personal data is transferred outside the UK/EEA, we ensure appropriate safeguards are in place, such as Standard Contractual Clauses (SCCs) approved by the European Commission and the UK International Data Transfer Addendum, or the processor's participation in recognised data protection frameworks (such as the EU-US and UK-US Data Privacy Framework).

Data processing agreements and the corresponding transfer safeguards (Standard Contractual Clauses or the UK International Data Transfer Addendum) are in place with all sub-processors listed in Section 3, including Anthropic (Claude API), which we use for support, and HubSpot, which we use for support and for our customer records.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will notify you via email or a prominent notice within the service. The “Last updated” date at the top of this page reflects the most recent revision.

13. Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, contact us at:

Email: privacy@1gesture.org
Service: 1Gesture Platform Ltd.

If you are not satisfied with our response, you have the right to lodge a complaint with your local data protection authority. In the UK, this is the Information Commissioner's Office (ICO).