Skip to content
NewThe generated home ended todayRead more

Legal

Privacy Policy

Last updated: · Version 2026-11-13

This policy explains what personal data we collect when you use Syntext, why we collect it, who we share it with, and your rights.

1. Who we are

Syntext is provided by Bytangle Ltd, a company registered in England and Wales (company number 17287853), whose registered office is at 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. In this policy, “we”, “us” and “our” mean Bytangle Ltd.

This policy covers syntext.dev, the Syntext dashboard at app.syntext.dev, our API at api.syntext.dev, the CLI, SDKs and integrations, and the doc sites our customers publish with Syntext.

We are registered with the UK Information Commissioner’s Office (ICO) under number C2028690. We are not required to appoint a Data Protection Officer. For any privacy question, contact us at [email protected].

If EU law requires us to appoint a representative in the European Union, we will do so and list them here. Until then, people in the EU can contact us directly at [email protected].

2. Our role: controller and processor

We are the controller for data about our customers and the people who use their accounts: account details, billing, use of the dashboard, support conversations and marketing. We decide how that data is used.

We are a processor for the content customers put into Syntext and for data about the readers of their doc sites. The customer who runs the doc site is the controller. We use that data only to provide the service, on the customer’s instructions and under our Data Processing Addendum.

There is one narrow exception. We act as controller for security and abuse logs (for example, IP addresses in access and request logs) that we keep to protect the service and its users.

If you read a doc site built with Syntext and want to use your data protection rights, contact the organisation that runs the site. We will help them respond.

3. Data we collect about customers, and why

DataWhy we use itLawful basis
Name, email address, password (stored only as a hash), profile pictureTo create your account and sign you inContract
GitHub username, GitHub access tokens, and the repositories you connectTo sign you in with GitHub and build your docs from your repositoriesContract
Your content: docs, configuration, API specifications, themes and build logsTo build, host, search and publish your docsContract
Sign-in sessions: IP address, browser or CLI details, time last usedTo keep accounts secure and show you where you are signed inLegitimate interests (security)
Workspace audit log, including the IP address of each actionSo workspace owners can review activity, and to investigate security issuesLegitimate interests (security)
How you use the dashboard: when you were last active and which features you have set upTo understand and improve the productLegitimate interests (product analytics)
Service emails: verification, password reset, invitations, alerts and notices about your accountTo run your account and tell you about changes that affect itContract; legitimate interests
Support conversations by email or in-app chatTo answer your questions and fix problemsLegitimate interests
Marketing emails: product news and tipsTo tell you about SyntextConsent, or our legitimate interests where the soft opt-in applies (section 12)
Billing: name, email, workspace name, Stripe customer ID and invoicesTo take paymentContract
Billing recordsTo meet our tax and accounting dutiesLegal obligation

Stripe collects your card details directly. We never see or store them. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

4. Data about doc-site readers

When someone reads a doc site built with Syntext, we process the following on behalf of the site owner:

  • Analytics: pages viewed and in what order, time on page, referring site, country, browser, operating system, device type and user agent. These are linked to a random visitor ID stored in the reader’s browser. We do not store IP addresses with analytics.
  • Searches: what readers search for and which result they open.
  • Assistant conversations: questions, answers, sources cited, ratings and conversation titles. Readers can rename and delete their own conversations. If a reader shares a conversation, anyone with the link can read it.
  • Assistant memory: short facts the assistant takes from a reader’s conversations, such as the programming language they use, so later answers fit them better. Memory is on by default. Readers can see what is remembered, delete single facts or all of them, and turn memory off.
  • Feedback: ratings of pages and sections, and any comment a reader writes.
  • Support requests: if a reader asks for their conversation to be passed to the site’s support team, their email address and the summary they approve.
  • Protected sites: for sites that need a password or sign-in, the page requested, how access was granted, and the reader’s IP address.

The site owner decides whether the assistant, and so its memory, is available on their site. In the UK and EU, the site owner is responsible for telling readers about this processing and for having a lawful basis for it.

5. AI features

Syntext uses OpenAI, through its API, as a subprocessor for these features:

  • Search and the docs assistant. We convert doc content into embeddings so the assistant can find relevant passages. When a reader asks a question, we send OpenAI the question, recent messages in the conversation, any assistant memory, and the relevant passages from the docs. This applies on doc sites, in the embeddable widget, and in Slack, Discord and MCP connections the customer turns on.
  • Writing tools. The editor assistant and translation send the content you are working on to OpenAI.

Under OpenAI’s API terms, OpenAI does not use data sent through its API to train its models. We do not use customer content or reader conversations to train AI models either.

AI answers are generated automatically and can be wrong. Answers on a doc site are based on that site’s docs but are not checked by a person before they are shown.

6. Cookies and browser storage

syntext.dev sets no cookies and uses no analytics or advertising trackers. The dashboard uses cookies to keep you signed in and, for signed-in users, Intercom cookies for support chat. Doc sites use cookies for protected sites and browser storage for the assistant, preferences and analytics.

For UK readers, doc-site analytics rely on the exemption for statistical purposes in the Privacy and Electronic Communications Regulations, as amended by the Data (Use and Access) Act 2025. Site owners whose readers are in the EU are responsible for getting consent where EU law requires it. We will offer site owners a mode in which no persistent visitor ID is stored.

We ask for consent before setting any cookie that is not needed to provide the service you asked for. Full details, including each cookie’s name and how long it lasts, are in our Cookie Policy.

7. Who we share data with

We use these providers (subprocessors) to run Syntext. Each receives only the data it needs for its task.

ProviderWhat it does for usData involvedLocation
RailwayHosting for our API, dashboard, website, database and job queueAll data we storeUnited States
CloudflareContent delivery, doc-site serving (Workers), file storage (R2) and custom domainsDoc-site requests (including IP addresses), built sites, profile picturesGlobal
OpenAIAI search, the docs assistant, writing tools and translation, through its APIDoc content, reader questions and conversations, assistant memoryUnited States
MeilisearchSearch for doc sitesDoc content—
ResendSending emailEmail addresses and message contentUnited States
StripePayments and invoicesBilling name, email, workspace name, payment detailsUnited States and Ireland
GitHubSign-in with GitHub and repository integrationGitHub identity and the contents of repositories you connectUnited States
IntercomIn-app support chat in the dashboard (signed-in users only)Name, email, workspace, messages you sendUnited States

We give customers 30 days’ notice of a new subprocessor, by email or in our changelog, as set out in the Data Processing Addendum.

Integrations you turn on. If you connect Slack, Discord, outbound webhooks, or an AI client such as Claude or ChatGPT through our MCP connector, we send data to that service because you asked us to. Those services are not our subprocessors, and their own terms and privacy policies apply.

We also share data when the law requires it, to protect our rights or the safety of others, or with a buyer if our business is sold. We do not sell personal data.

8. International transfers

We are based in the UK, but several of our providers process data in the United States and other countries. When personal data leaves the UK or the European Economic Area, we protect it with the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, and with the EU Standard Contractual Clauses for data covered by EU law.

To get a copy of these safeguards, email [email protected].

9. How long we keep data

DataHow long we keep it
Account dataFor as long as your account is open, then up to 30 days after you delete it
Sign-in sessions90 days
Workspace audit logsStarter plan: 7 days. Pro plan: 1 year. Enterprise: as agreed. The Free plan has no audit log.
Content in a deleted workspace or project30 days after deletion
Doc-site reader analytics13 months
Assistant conversations12 months, or until the reader deletes them
Backups35 days, on a rolling basis
Support messages2 years
Billing records6 years, as UK law requires

After these periods we delete the data or make it anonymous. When you delete your account, we remove your name, email, profile picture, password and GitHub connection. We keep an anonymous record in its place so that content you created for a workspace stays with that workspace.

10. Security

We protect personal data with these measures:

  • all traffic is encrypted in transit with TLS;
  • our hosting and storage providers encrypt data at rest;
  • passwords are stored only as salted hashes, and sign-in, verification and reset tokens only as hashes;
  • each customer’s data is kept separate, and access to production systems is limited to staff who need it;
  • actions in each workspace are recorded in an audit log.

No system is completely secure. If a breach puts your personal data at risk, we will tell you and the ICO as the law requires.

11. Your rights

Under UK data protection law, and EU law where it applies, you have the right to:

  • get a copy of the personal data we hold about you;
  • receive your data in a portable, machine-readable format;
  • have inaccurate data corrected;
  • have your data deleted;
  • object to our use of your data, or ask us to restrict it;
  • withdraw your consent at any time, where we rely on consent.

How to use them. You can delete your account yourself in the dashboard under account settings. If you are the only owner of a workspace, transfer ownership or delete the workspace first. For anything else, including a copy or export of your data, email [email protected]. We will respond within one month (30 days). We may ask you to confirm your identity first.

Doc-site readers should contact the organisation that runs the site, which controls their data. Readers can also view, delete and turn off assistant memory, and delete their conversations, in the assistant itself.

If you are unhappy with how we have handled your data, you can complain to the ICO (see section 16).

12. Marketing emails

We send marketing emails, such as product news and tips, only if you have agreed to receive them. If you are an existing customer, we may send you emails about similar Syntext products and features where the law allows this without separate consent; you can opt out when you sign up and at any time after.

Every marketing email includes an unsubscribe link. You can also change your email preferences in the dashboard. Unsubscribing does not stop service emails, such as password resets, security notices and billing messages, which we need to send to run your account.

13. California residents

If you live in California, the California Consumer Privacy Act gives you the right to know what personal information we collect, use and disclose, and to ask us to delete or correct it. We do not sell personal information, and we do not share it for cross-context behavioural advertising. We will not treat you differently for using these rights. To use them, email [email protected].

14. Children

Syntext is for businesses and professionals. You must be at least 16 to create an account. We do not knowingly collect personal data from children under 16. If you believe a child has given us personal data, contact us and we will delete it.

15. Changes to this policy

We will update this page when our practices change, and change the date at the top. If a change is significant, we will tell account holders by email or in the dashboard at least 30 days before it takes effect.

16. Contact and complaints

Email [email protected], or write to Bytangle Ltd, 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.

Please contact us first if you have a concern, so we can try to resolve it. You also have the right to complain to the Information Commissioner’s Office, the UK data protection regulator, at ico.org.uk/make-a-complaint or by phone on 0303 123 1113. If you are in the EU, you can also complain to the data protection authority in your country.