Legal
Data Processing Addendum
Last updated: · Version 2026-11-13
This addendum sets out how we process personal data on your behalf when you use Syntext, as Article 28 of the UK GDPR requires.
1. About this addendum
This Data Processing Addendum (“DPA”) is between Bytangle Ltd (“we”, the processor) and the customer that has accepted our Terms of Service (“you”, the controller). It forms part of the Terms and applies automatically; you do not need to sign it separately. If the DPA and the Terms conflict on data protection, the DPA takes priority.
“Data Protection Law” means the UK GDPR, the Data Protection Act 2018 and, where they apply to your data, the EU GDPR and the laws of EU member states. Terms such as “personal data”, “processing”, “controller”, “processor” and “personal data breach” have the meanings given in that law.
2. Details of the processing
| Item | Detail |
|---|---|
| Subject matter | Providing the Syntext service: building, hosting, searching and analysing your documentation, and the AI assistant |
| Duration | The term of your agreement with us, plus the deletion period in section 10 |
| Nature and purpose | Storage, hosting, indexing, analytics, AI question answering, email delivery and support, as needed to provide the service |
| Types of personal data | Any personal data in your content; readers’ visitor IDs, page views, device and browser details, country, searches, assistant conversations and memory, feedback, email addresses given in support requests, and IP addresses on protected sites |
| Data subjects | Readers of your doc sites; people named in your content; your users whose data is in your content |
| Special categories | None intended. You must not put special category data into the service. |
3. Our obligations
We will:
- process personal data only on your documented instructions, which are the Terms, this DPA and your use of the service settings, unless the law requires otherwise, in which case we will tell you first if the law allows;
- tell you if we believe an instruction breaks Data Protection Law;
- make sure everyone we authorise to process the data is bound by confidentiality;
- apply the security measures in section 5;
- use subprocessors only as set out in section 6;
- help you, taking into account the nature of the processing, to respond to requests from data subjects (section 9);
- help you meet your obligations on security, breach notification, data protection impact assessments and prior consultation with a regulator;
- delete or return the personal data when the service ends (section 10); and
- make available the information you need to show compliance with this DPA, and allow audits as set out in section 11.
4. Your obligations
You are responsible for the lawfulness of the personal data you give us and of your instructions. In particular, you will tell your readers how their data is used, have a lawful basis for the processing, and get any consent the law requires, including for analytics and the AI assistant on your doc sites.
5. Security
We maintain appropriate technical and organisational measures to protect personal data, including:
- encryption in transit with TLS, and encryption at rest by our hosting and storage providers;
- passwords and sign-in tokens stored only as hashes;
- separation of each customer’s data, and access controls that limit production access to staff who need it;
- audit logging of actions in each workspace;
- backups kept for 35 days on a rolling basis; and
- review of these measures as the service and the risks change.
6. Subprocessors
You give us general authorisation to use subprocessors. Our current subprocessors are:
| Provider | What it does for us | Data involved | Location |
|---|---|---|---|
| Railway | Hosting for our API, dashboard, website, database and job queue | All data we store | United States |
| Cloudflare | Content delivery, doc-site serving (Workers), file storage (R2) and custom domains | Doc-site requests (including IP addresses), built sites, profile pictures | Global |
| OpenAI | AI search, the docs assistant, writing tools and translation, through its API | Doc content, reader questions and conversations, assistant memory | United States |
| Meilisearch | Search for doc sites | Doc content | — |
| Resend | Sending email | Email addresses and message content | United States |
| Stripe | Payments and invoices | Billing name, email, workspace name, payment details | United States and Ireland |
| GitHub | Sign-in with GitHub and repository integration | GitHub identity and the contents of repositories you connect | United States |
| Intercom | In-app support chat in the dashboard (signed-in users only) | Name, email, workspace, messages you send | United States |
- We will give you at least 30 days’ notice before adding or replacing a subprocessor, by updating this list and announcing the change in our changelog or by email.
- You may object on reasonable data protection grounds within that 30 days by emailing [email protected]. We will try to address the objection. If we cannot, you may end the affected part of the service, and we will refund fees paid in advance for the period after it ends.
- We impose data protection terms on each subprocessor that give at least the same protection as this DPA, and we remain responsible to you for their performance.
7. International transfers
We may transfer personal data outside the UK and the European Economic Area, including to subprocessors in the United States. Where we do, we use the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses for data covered by UK law, and the EU Standard Contractual Clauses (Module 2 or Module 3, as applicable) for data covered by EU law. These are incorporated into this DPA by reference, with the details of the processing in section 2 completing their annexes.
8. Personal data breaches
We will tell you without undue delay, and in any case within 72 hours, after becoming aware of a personal data breach affecting your personal data. We will tell you what we know about its nature, likely consequences and the steps taken, and give you further information as it becomes available, so that you can meet your own obligations to notify regulators and data subjects.
9. Requests from data subjects
If we receive a request from one of your readers or other data subjects, we will pass it to you and not respond ourselves, except to tell the person to contact you. We will help you respond, using the tools in the service where possible, such as analytics export, conversation deletion and assistant memory controls.
10. Deletion and return
When your agreement ends, you can export your content for 30 days. After that, we delete the personal data we process for you, unless the law requires us to keep it. Copies in backups are deleted as the backups expire, within 35 days.
11. Audits
We will answer your reasonable written questions about our compliance with this DPA, and provide relevant documentation, such as descriptions of our security measures and our subprocessors’ certifications. This is how audits are carried out in the first instance.
If that information is not enough to show compliance, or a regulator requires it, you may carry out an audit yourself or through an independent auditor bound by confidentiality. You must give us at least 30 days’ notice, you may audit no more than once a year (unless after a breach), and you will bear the costs.
12. Liability
Each party’s liability under this DPA is subject to the limits in section 14 of the Terms of Service.
13. Contact
Questions about this DPA, objections to subprocessors, and audit requests: [email protected], or write to Bytangle Ltd, 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ.