Privacy Policy

1. Who We Are

LangRelay is operated by Chris Jayden, an Eenmanszaak (sole proprietorship) registered in the Netherlands.

Chris Jayden is the data controller for the personal data described in this policy, except for the data about visitors of our customers' websites described in section 2.7, which we process as a processor on our customers' behalf. We are subject to Regulation (EU) 2016/679 (the General Data Protection Regulation, "GDPR").

2. What Data We Collect

2.1 Account Data

When you create an account we collect your email address and the name you give us. We store no password: you sign in with a link we email you, or with Google. If you sign in with Google, we receive your name, email address and profile picture from Google, with the identifier of your Google account, and we keep them with your account. We also keep, in encrypted form, the access and refresh tokens Google issues for the sign-in; we do not use them to read anything from your Google account. All of this is kept until your account is deleted. Google decides what it does with your sign-in under its own privacy policy.

2.2 Billing Data

Billing is run by Autumn(useautumn.com), which keeps track of your plan and usage and passes payments to Stripe. Autumn receives your organisation's ID, your name and your email address. We store your subscription plan and billing status. We do not store full card numbers or raw payment details. Those remain with Stripe under their own privacy policy and PCI DSS compliance.

2.3 Website & Translation Data

When you connect a website to LangRelay, our crawler visits the pages you specify to extract text content for translation. It reads only what a visitor who is not logged in can see. The extracted text and its translations are stored in our database.

When your website is served through LangRelay's proxy, every request to it passes through our servers at Cloudflare on its way to your server, and your server's response passes back the same way. We translate the pages your visitors ask for in another language, including pages shown to logged-in visitors, and pass everything else through unchanged. We keep nothing from these requests beyond the Site analytics in section 2.7. A translated page that your server sent to a visitor who was not logged in may be kept for a short time in Cloudflare's cache, so the next visitor gets it faster; a page sent to a logged-in visitor never is.

Messages you send to Relay, LangRelay's assistant, in the dashboard or by email, are stored with your Site's conversation, as are Relay's answers and a copy of the emails it sends you. Screenshots you share with it, and the text read from them, are stored apart from the conversation. How the AI models that translate and answer receive this data is described in section 2.8.

2.4 Usage & Analytics Data

We keep internal usage metrics (e.g. number of translated words) for billing. These stay in our own database.

We also record how you use the LangRelay dashboard, to see where people get stuck and to improve the product: steps such as signing up, creating an organisation or a site, approving a translation and publishing a page, and which kinds of dashboard page you open. When you sign up through a link on this website, we also record which link it was and the campaign tags it carried (such as utm_source); nothing else about your visit is passed on. Each event is tied to a pseudonymous identifier (your account ID) and your organisation's ID, never to your name or email address. It carries codes and counts only, never your website's content, its addresses or your translations. We send these events to OpenPanel(openpanel.dev), which hosts them in the EU. The dashboard stores nothing on your device for this: no analytics script, cookie or local storage.

While you are signed in to the dashboard, we also usePostHog(posthog.com) to see what went wrong when something does and to improve the product. PostHog is operated by PostHog, Inc. and we use its EU cloud, which hosts the data in Frankfurt, Germany. PostHog receives a recording of your session on the dashboard (the pages you open, your clicks and scrolling, and the layout of what you see), the technical errors the dashboard raises, the requests the dashboard makes to our servers (their name, how long they took and whether they succeeded), and, for each model call that Relay or our reviewer makes, which model answered, how many tokens it used, what it cost and how long it took. Each of these is tied to your account ID and your organisation's ID, never to your name or email address. The recording masks everything you type and blocks every part of the screen that shows your content: your translations and their source text, your pages' text, your glossary and your conversations with Relay. We never send the content of your website, its addresses, your translations or what you and Relay write to each other to PostHog. The dashboard stores nothing on your device for this: PostHog's identifiers live in the page's memory, so reloading the page starts a new session.

On this website (langrelay.com), PostHog counts page views and the campaign tags a link carried, without cookies, without recording your visit, without reading anything you type and without building a profile of you. It stores nothing on your device and does not keep your IP address.

You can object to this at any time by emailingsupport@langrelay.com, and we will stop recording your usage. What we count about the visitors of websites that use LangRelay is described in section 2.7, and PostHog plays no part in it.

2.5 Communication Data

We use Cloudflare Email Service (Cloudflare, Inc.) to send transactional emails (e.g. sign-in links, account verification, billing receipts). Your email address is shared with Cloudflare for this purpose. You can unsubscribe from marketing emails at any time via the unsubscribe link in each email; transactional emails cannot be opted out of while your account is active.

When you sign up, we share your name and email address withBento(bentonow.com), which sends your welcome email and, later, emails that help you get started. Bento receives only your name, your email address, your account ID and the fact that you signed up, never your usage events. Onboarding emails beyond the welcome email carry an unsubscribe link.

When you reply to an email from Relay, the reply is received by Cloudflare's Email Routing and passed to Relay in your Site's conversation. We keep the text of a reply we accept, including any part of the earlier message you quoted or forwarded, so Relay can read it. We keep a one-way code computed from the sender's address, never the address itself or the subject. A reply we cannot match to one of our emails is dropped, and its text is not kept. Replies are kept with your account and deleted with it (section 6).

2.6 Technical Logs

Our servers and our hosting provider, Cloudflare, may log IP addresses, request timestamps, and error traces for security, debugging, and abuse prevention. These logs are retained for up to 30 days.

2.7 Visitors of Our Customers' Websites (Site Analytics)

When a website uses LangRelay, we count its page views, as LangRelay serves a page or as LangRelay's script on the page reports the view, so that our customer can see how many people visit, from where, on what kind of device, and in which language. For this data our customer, the website's owner, is the controller and we are their processor: we process it only on their instructions and to provide this feature, as our Data Processing Agreement sets out.

Page views. For each page view we keep:

• the page's path, without its query string;
• the visitor's language as the website names it, and whether the page was shown in that language;
• the referring website's host name only (for examplegoogle.com), never the page or search that led there;
• the country, as our hosting provider Cloudflare reports it;
• the type of device, browser and operating system (for example "mobile", "Safari", "iOS"), never the full browser identification;
• a daily visitor hash and whether the view started a visit or ended after one page.

The daily visitor hash is a one-way code computed from the visitor's IP address, their browser's identification and the website, using a random key that changes every day (UTC). Each day's key is created at random, not derived from anything, and is deleted automatically about a day after its day ends. After that, nobody, LangRelay included, can work out a past day's hash from an IP address, and the hash alone links nothing from one day to the next (a shop's logged-in customers are the one exception, below). The IP address and the browser identification are used only to compute the hash and the device, browser and system types above; they are never stored.

We set no cookies and store nothing on the visitor's device for this. A visitor whose browser sends a Global Privacy Control signal (Sec-GPC) or a Do Not Track signal (DNT) is not counted. Known crawlers and automated clients are not counted either.

Each website owner can switch Site analytics off in the LangRelay dashboard. While it is off, nothing is counted; what was counted before stays available to them.

Revenue (on by default for a WooCommerce shop; its owner can turn it off).A WooCommerce shop connected through our WordPress plugin has revenue tracking on by default, and its owner can turn it off in the LangRelay dashboard. If the owner has switched Site analytics off when our plugin first reports WooCommerce, revenue tracking stays off until they turn it on. Any other website has it only if its owner turns it on. Revenue tracking has its own switch, and switching Site analytics off also stops it until Site analytics is back on. While it is on, the shop sends us, from its own server, facts about its orders: the order's number in the shop, its total, its currency, whether it was paid, refunded (and by how much) or cancelled, when, and the language the shop was in at checkout. We use this to show the shop its revenue per language. With an order the shop may also pass on the IP address and browser identification of the checkout request; we use them only to compute that day's visitor hash for the order, as for a page view, and never store them. The order's visitor hash is removed 90 days after the order; the order keeps its language. We receive no name, email address, postal address, phone number or customer number of the buyer; the order of a logged-in buyer may carry a pseudonymous profile key instead, as described next. When the owner turns revenue tracking off, or switches Site analytics off, we keep no new orders; orders already received are kept as section 6 describes.

Logged-in customers (only where the shop's owner turns on customer linking; never on by default).A shop whose owner turns on customer linking may give each customer who is logged in to the shop a pseudonymous profile key. The shop's own server computes the key from the customer's account in the shop and a secret we hand the shop; it is never computed from an email address, and it does not name the customer. The key is sent with that customer's page views of the shop and with their orders, and we store it with them: on page views for three months, and on orders for as long as the order is kept (section 6). Unlike the daily visitor hash, the key links that customer's visits across days, so that the shop can see which pages its customers came in on before they ordered. We delete a customer's key from their orders when the shop asks us to, for example when the customer asks the shop to erase their data; page views that carry it run out their three months. We receive no name, email address or customer number with it, and we keep no other facts about the customer.

2.8 AI Processing

To translate your website and to answer you, we send the website text being translated, your messages to Relay and the screenshots you share with it to AI models, through Vercel's AI Gateway. We use models made by Google, OpenAI, Anthropic and TypeSafe AI. The gateway may serve the same model from one of the cloud platforms that host it, such as Google Cloud (Vertex AI), Amazon Web Services (Amazon Bedrock) or Microsoft Azure. The model provider receives this data only to produce the answer.

We use the gateway with zero data retention turned on. Vercel does not keep the prompts or the answers, and sends our requests only to providers that have agreed with Vercel not to keep them or train their models on them. A provider may still keep a request for a short time where its terms require it to check for misuse. SeeVercel's zero data retention terms.

2.9 Support and Operations

To run LangRelay and to help you, LangRelay's staff can see the status of your account: your email address and name, how you sign in and when you last did, the organisations you belong to and their members, your plan and AI credits, and for each of your Sites its address, its languages, how it is delivered, and whether its pages are live, waiting for you or still being translated, listed by their web address. Staff never see the text of your website or its translations, your conversations with Relay, or the emails you exchange with it. They cannot sign in as you. To help you, for example when you ask for help or when your Site is stuck, staff can re-crawl your Site, retry translations that failed, re-run its delivery check, and approve and publish pages that are waiting. Each of these is recorded in your Site's history with who did it and why. Each time staff open your account, your organisation or one of your Sites, that look is recorded in its history.

Staff may use an AI assistant to read this status, for example to find which Sites need attention today. When they do, the account details above are sent to Anthropic, the provider of that assistant (Claude), only to answer staff's question. These requests do not pass through Vercel's AI Gateway, so the zero data retention in section 2.8 does not apply to them: Anthropic keeps them for up to 30 days and does not use them to train its models.

3. Legal Basis for Processing (GDPR)

4. Data Sharing & Third Parties

We do not sell your personal data. We share it only with the following sub-processors, under their data processing terms:

• Cloudflare, Inc.(USA): hosts the LangRelay API, dashboard, Relay (with its conversations), this website and LangRelay's proxy; receives replies to our email (Email Routing, section 2.5); and stores Site analytics (section 2.7). Covered by Standard Contractual Clauses.
• Neon, Inc.(USA): database hosting in Frankfurt, Germany, including the orders of section 2.7. Covered by Standard Contractual Clauses.
• Vercel Inc.(USA): AI Gateway, which passes translation and Relay requests to the AI model providers below, with zero data retention (section 2.8). Covered by Standard Contractual Clauses.
• AI model providers(mainly USA), reached through Vercel's AI Gateway: Google, OpenAI, Anthropic and TypeSafe AI, whose models we use, and the cloud platforms that may serve the same models, Google Cloud, Amazon Web Services and Microsoft Azure. They receive the website text being translated, your messages to Relay and the screenshots you share with it, only to produce the answer, under agreements with Vercel not to keep it or train on it (section 2.8). For support and operations, Anthropic, the provider of the AI assistant LangRelay's staff use, also receives the account details in section 2.9, outside the gateway.
• Rebase, Inc., trading as Autumn(USA): subscription and usage billing (section 2.2). Receives your organisation's ID, your name and your email address.
• Stripe Inc.(USA): payment processing. Covered by Standard Contractual Clauses and certified under EU-US Data Privacy Framework.
• Cloudflare, Inc.(USA): transactional email delivery through Cloudflare Email Service (section 2.5).
• OpenPanel AB(Sweden): product analytics (section 2.4). Data hosted in the EU (Germany).
• PostHog, Inc.(USA): product analytics, session recordings, error reports and model call metrics for the dashboard, and page views on this website (section 2.4). Data hosted in PostHog's EU cloud in Frankfurt, Germany; transfers are covered by the safeguards in PostHog's Data Processing Agreement.
• Backpack Internet Pty Ltd, trading as Bento(Australia): welcome and onboarding email (section 2.5). Data hosted in the United States; transfers are covered by the safeguards in Bento's Data Processing Agreement.

We may disclose personal data if required to do so by law or in response to valid legal process from Dutch or EU authorities.

5. International Data Transfers

Some of our sub-processors are based outside the European Economic Area (EEA), primarily in the United States and, for Bento, Australia. PostHog stores its data in the EU but is a US company, so its staff may access it from the United States under the same safeguards. An AI model provider may answer a request from a data centre outside the EEA. Where personal data is transferred outside the EEA, we ensure adequate safeguards are in place, such as Standard Contractual Clauses (SCCs) approved by the European Commission, or reliance on the EU-US Data Privacy Framework where applicable.

6. Data Retention

• Account data:Retained for the duration of your account. Upon account deletion, your personal data is deleted or anonymised within 30 days, unless we are required to retain it by law (e.g. tax records, up to 7 years under Dutch law).
• Google sign-in:Your Google account's identifier, name, email address and picture, and the encrypted access and refresh tokens, are kept until your account is deleted, and then deleted with your other account data.
• Replies to Relay's email (section 2.5):Kept with your account, and deleted with it within the 30 days above.
• Relay conversation history (sections 2.3 and 2.5):The messages you send to Relay, the replies you email to it, Relay's answers and our copy of the emails it sends are kept in your Site's conversation, with a title taken from the first message. A conversation of yours, and any conversation that holds a reply you emailed, is deleted with its title and our copy of its emails when your account is deleted: at our next hourly clean-up, and in any case within the 30 days above. The screenshots you shared with Relay, and the text read from them, are deleted the same way. A Site's conversations, emails and screenshots are deleted once the Site is deleted and its 30-day restore period has passed.
• PostHog (section 2.4):Session recordings are kept for 30 days and other events for up to 12 months, and are deleted on request.
• Translation data:Deleted within 30 days of Site deletion or account deletion.
• Server logs: Retained for up to 30 days.
• Site analytics page views (section 2.7):Each page view, with its daily visitor hash, is deleted automatically by Cloudflare three months after it was counted. Each day's random key is deleted about a day after its day ends. Daily totals per website, which hold no visitor hash, may be kept for as long as the website is a LangRelay Site; they are deleted once the Site is deleted and its 30-day restore period has passed.
• Orders (section 2.7):Kept for as long as the website is a LangRelay Site, and deleted once the Site is deleted and its 30-day restore period has passed. An order's visitor hash, where the shop passed on the checkout request, is removed 90 days after the order; the order keeps its language.
• Profile keys of logged-in customers (section 2.7):On page views, deleted automatically by Cloudflare three months after the view was counted. On orders, kept as long as the order, and deleted from the customer's orders when the shop asks us to.
• Billing records:Retained for 7 years as required by Dutch tax law (Belastingdienst).

7. Your Rights Under GDPR

As a data subject under the GDPR, you have the following rights. To exercise any of them, contact us atsupport@langrelay.com.

• Right of access (Art. 15):You can request a copy of the personal data we hold about you.
• Right to rectification (Art. 16):You can ask us to correct inaccurate or incomplete data.
• Right to erasure (Art. 17):You can ask us to delete your personal data, subject to legal retention obligations.
• Right to restriction (Art. 18):You can ask us to restrict processing of your data in certain circumstances.
• Right to data portability (Art. 20):You can request your account data in a machine-readable format.
• Right to object (Art. 21):You can object to processing based on legitimate interests, including direct marketing.
• Right to withdraw consent:Where processing is based on consent, you may withdraw it at any time without affecting prior processing.

We will respond to requests within 30 days. If you are unsatisfied with our response, you have the right to lodge a complaint with the Dutch supervisory authority:

8. Cookies

LangRelay uses only strictly necessary session cookies for authentication. We do not use tracking or advertising cookies, and product analytics, including PostHog (section 2.4), stores nothing on your device. You do not need to accept any cookie banner to use this service. Site analytics (section 2.7) sets no cookie and stores nothing on the devices of the visitors of our customers' websites.

9. Security

We implement appropriate technical and organisational measures to protect your personal data against unauthorised access, loss, or disclosure. These include HTTPS encryption in transit, single-use sign-in links in place of passwords, and access controls on our infrastructure. However, no method of transmission over the internet is 100% secure.

10. Children

LangRelay is not directed at persons under 18 years of age. We do not knowingly collect personal data from minors. If you believe a minor has provided us with personal data, please contact us and we will delete it promptly.

11. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify registered users by email and update the "Last updated" date at the top of this page. Continued use of the service after the effective date of changes constitutes acceptance of the updated policy.

12. Contact

For any privacy-related questions or to exercise your rights, contact us at:
support@langrelay.com