Privacy Policy

Last updated: November 1, 2026

This page explains what data Interpret handles, why, and how to ask for information, correction or deletion.

1. Who we are

Interpret (interpret.events) provides AI simultaneous translation for events. Attendees hear and read the translation on their own phones. The service is operated by Gabriel Silva Costa Consultoria em Tecnologia da Informação Ltda., Brazilian company registration (CNPJ) 41.697.730/0001-70, Av. Roberto Silveira, 136, apto. 302, Icaraí, Niterói/RJ, CEP 24230-165, Brazil. For any privacy matter, including reaching our data protection officer, write to [email protected].

We are the controller of website data, demo requests, accounts and billing. For event content (audio, transcripts, questions and attendee data), the organizer is the controller and Interpret processes the data on their behalf, as a processor.

2. Data we handle

• Demo request. Name, email, WhatsApp, organization and the event details you enter in the form. When visit measurement is on, the request also keeps where the visit came from: campaign codes (UTM), the referring page, the approximate country and the device category.
• Organizer account. Dashboard login data and the events, rooms and sessions created.
• Event content. Stage audio is sent for real-time processing. When caption alignment is on, Interpret keeps the original audio temporarily to generate timestamps. In sessions where the organizer turns on recording, stage audio (and, if chosen, the translation voices) is stored as MP3 in their account until deleted or until the retention period ends. Transcripts and summaries can be stored, shown for a limited time or turned off, according to the session policy.
• Attendee. Some events ask for a name, email and a temporary code sent by email to grant access. In the others, the browser keeps an anonymous identifier to remember the chosen language and count the audience. If an attendee sends a question, the text may be saved in the session according to the chosen policy.
• Billing. Name or company name, tax ID, email, billing address, the accepted proposal and payment history. Card details are entered directly into Asaas or Paddle; Interpret never receives or stores them.
• Technical data. IP address and access logs, used for security and to limit abuse.

3. Why we use it and on what legal basis

• Answering your request and preparing the demo and proposal: steps taken at your request before entering into a contract.
• Delivering translation, captions and summaries during the event and keeping the organizer account: performance of a contract.
• Billing, issuing tax invoices and keeping accounting records: performance of a contract and compliance with a legal obligation.
• Keeping the service secure, preventing fraud and fixing bugs: legitimate interest.
• Measuring landing page visits and campaigns: legitimate interest, turned off by Do Not Track and Global Privacy Control (section 10).

4. Organizer controls

The organizer sets access, display, retention and export per organization, event or session. In a session with no local retention, Interpret blocks storing content and the features that depend on it. This control applies to Interpret; it does not confirm retention, use or deletion at external providers.

5. Who we share it with

We do not sell data. To deliver speech recognition, translation and voice, the service sends event audio and text to OpenAI. When caption alignment is on, it also sends the original audio and text to ElevenLabs to generate timestamps. We also use hosting providers, and the page loads fonts from Google Fonts. When the app fails in the browser, a technical error report (browser type, page without parameters and the error stack, with no name, email, cookies or typed input) goes to Sentry so we can fix it. To understand landing page use we use PostHog, and to measure campaigns, Google Ads and OpenAI Ads (see section 10). These providers handle data under their own terms and settings.

For billing, payments in Brazil go through Asaas. Orders from outside Brazil are sold by Paddle.com, which acts as Merchant of Record and receives the data needed to process the payment, issue the invoice and meet tax obligations, under the Paddle privacy policy. We may share data with accountants and lawyers under confidentiality, and with authorities when required by law or court order.

6. International transfers

OpenAI, ElevenLabs, Sentry, PostHog, Google and Paddle may process data outside Brazil, including in the United States and the European Union. These transfers follow Brazil’s data protection law (LGPD), using the providers’ contractual clauses and the safeguards the law provides.

7. How long we keep it

The session policy decides whether transcripts and summaries stay available, for how long, or whether they are not stored locally at all. Legacy sessions may have no automatic deadline. Deleting a session or event starts removing its content from Interpret, but does not confirm immediate deletion from backups or of data already processed by external providers. Billing records and tax invoices are kept for the period required by tax law, usually five years. Demo requests that do not lead to a purchase are deleted when you ask.

8. Your rights

You can ask for confirmation that we process your data, access, correction, anonymization, portability, deletion, information about who we share it with, and withdrawal of consent where consent is the basis. If you are in the European Economic Area or the United Kingdom, you may also object to or restrict processing. Write to [email protected]. If you attended an event, include the event name and, where relevant, the email you used to join; requests about event content may be passed to the organizer. We reply within 15 days. You can also complain to Brazil’s National Data Protection Authority (ANPD) or to the data protection authority where you live.

9. Security

Traffic is encrypted with HTTPS, the dashboard requires login and the website form only accepts submissions: no visitor can read other people’s requests. Access to data is limited to those who need it to run the service.

10. Cookies

We use a session cookie for organizer login. When an event requires email access, another temporary cookie keeps the attendee’s access. The browser’s local storage keeps attendee preferences. Advertising cookies exist only on the landing page, through the Google Ads tag and the OpenAI Ads pixel described below. On the landing page, the blog and the testimonial pages, a random identifier in local storage, valid for 90 days, lets us count visitors and measure clicks, requests and testimonials received (without the testimonial’s content). Without that storage, each visit may be counted separately. We record campaign codes and device category, approximate country and city, without storing full URLs, IPs or form content in analytics. Do not include personal data in UTM codes. Do Not Track and Global Privacy Control signals turn this collection off. The metrics dashboard is restricted to Interpret and shows aggregated data and the sequence of visits and actions of each identifier, without a name until a contact request is sent. The team may tag an identifier (for example, someone who got to a meeting); the tag is deleted when its last visit expires. A daily cleanup removes visits and analytics events older than 93 days. When you send the form, the visit’s origin (UTM, page, country and device) is copied into the contact request; when the visit expires, the request loses the link to it and keeps only that copy. Country and city are estimated locally from the IP, which is discarded after the lookup in the geographic database; this estimate does not reveal your address and may be unavailable or inaccurate.

On the landing page we also use PostHog, a product analytics tool, to see how the page is browsed: page views, clicks, scrolling, interaction with the videos and the demo, form steps (without what was typed), page performance and session recordings with every form field masked. PostHog keeps a random identifier in the browser’s local storage, does not receive name, email or phone, is set to discard the IP address and may process data outside Brazil. Do Not Track and Global Privacy Control also turn this collection off.

On the landing page, the Google Ads tag measures whether someone who arrived from a Google ad requested contact through the form or clicked WhatsApp. Google may set advertising cookies in the browser to link the ad click to that action, and receives the page visited, the conversion type and technical browser data such as the IP address. The tag does not read what was typed in the form. Google handles this data under its own policy and may process it outside Brazil. Do Not Track and Global Privacy Control also turn the tag off.

On the landing page, the OpenAI Ads pixel measures whether someone who arrived from an ad in ChatGPT requested contact through the form or clicked WhatsApp. It sets the __oppref (30 days) and __obref (365 days) cookies to link the ad click to that action and sends OpenAI the page visited, the conversion type and technical browser data such as the IP address. When the page has an email or phone number filled in, the pixel may send them in encrypted (hashed) form, never as readable text, to make that link. It also sends, hashed, the random visitor identifier from our landing page measurement. OpenAI handles this data under its own policy and may process it outside Brazil. Do Not Track and Global Privacy Control also turn the pixel off.

When you send the landing page form, our server also tells Google Ads and OpenAI Ads about the contact request, so it counts even when the browser blocks the tag or the pixel. It sends the email and phone number in encrypted (hashed) form, never as readable text (to OpenAI Ads, also the hashed random visitor identifier), the ad click identifier, the page, the time and technical browser data such as the IP address. Name, organization, message and event details are not sent. Until the form is sent, the click identifier (gclid, gbraid, wbraid or oppref) stays in the browser's local storage for up to 90 days. Do Not Track and Global Privacy Control also turn this off.

This product includes GeoLite Data created by MaxMind, available from MaxMind.

11. Changes to this policy

When this policy changes, the date at the top of the page changes too.