Data Processing Agreement
The promise we make to every business about its visitors' and team's data. You accept it when you create an account, and we will sign a copy on request.
Version 2026-10-24 · Last updated 29 October 2026
This agreement is published only in English. It is not translated, and the English text is the only version.
This agreement takes effect on 22 October 2026.
1. Who and what this covers
- "turnda", "we": SKANDAN PTE. LTD. (UEN 202621966R), 60 Paya Lebar Road, #06-28 Paya Lebar Square, Singapore 409051.
- "You", "the business": the business that holds a turnda account.
- The laws this agreement serves: Singapore's Personal Data Protection Act 2012 (PDPA), and, where they apply to your processing, the EU General Data Protection Regulation (GDPR, including its Article 28), the UK GDPR and any other data-protection law that applies to you ("Data Protection Law").
- This agreement covers the personal data of your visitors and of your own team that we handle for you when we provide turnda ("Business Personal Data"). It forms part of the Terms of Service. You accept it when you create your account, and we record the version and date you accepted. A person who takes over the business through the owner hand-over accepts it again for the business, and we record that too. If you need a copy signed by both of us, write to legal@turnda.com and we will sign this same text.
- It does not cover data turnda is itself in charge of (billing, our website, and keeping sign-in and the service secure); our Privacy Policy covers that. Your team's sign-in details are handled for both purposes: for you, so your team can use turnda, and by us, to keep accounts secure.
- If this agreement and the Terms disagree about personal data, this agreement wins. If the standard contractual clauses in Annex 4 apply and disagree with this agreement, the clauses win.
2. Roles
- You are in charge of Business Personal Data (the controller, or in Singapore the organisation responsible). You decide what is collected, why, and how long it is kept.
- We act only on your instructions (the processor, or in Singapore a data intermediary). Your instructions are: this agreement, the Terms, and the settings you choose in turnda. If we think an instruction breaks the law, we will tell you, and we may decline to follow it.
- You are responsible for having a legal basis for what you collect, giving your visitors the notice your law requires (turnda lets you add your own short notice to each location's visitor pages), and the content you and your team type into turnda, including notes and flags.
3. What we process (details in Annex 1)
- Purpose: to run your lines, appointments, lobby screens, messages, reports and the rest of the service, and to fix problems you report.
- Whose data: your visitors, and your own owners, managers and staff.
- What data: the visitor fields you switch on (name, one contact for messages — a WhatsApp number or an email (both, if the visitor gave an email and then turned on WhatsApp) — a mobile number for your staff to call, party size, service, vehicle, a note), the answers to any questions of your own you ask visitors, line and appointment records, notes and flags your staff add, ratings and comments, WhatsApp messages, the mobile number a visitor gives for text updates and the proof that the visitor agreed to them, what your connected systems send in, and your team's names, usernames, sign-in emails and roles, and, if you turn on staff scheduling, their attendance record.
- Your own questions. You can ask visitors questions of your own when they join or book. You decide what to ask and you are responsible for it. The answers are kept with the visit, shown to your staff, and deleted on your visitor-data window.
- Your connected systems. You can connect your own outside systems to turnda. Such a system can add a visitor (with a name and a phone number or email) on its own statement that the visitor agreed to be messaged; you are responsible for that agreement. It receives the visit updates you choose, never a visitor's name, phone number or email from us. The systems you connect, and what you send them, are your choice and your responsibility: they are not our sub-processors.
- Staff attendance. If you turn on staff scheduling, we keep for you, for each team member, the first and last time they used turnda each day, late starts, missed shifts and sign-ins that look unusual, and a one-way marker of each browser they sign in from. You must tell your team that you keep it.
- Sensitive data. turnda does not ask for health, religious, financial or identity-document data. Our setup screens do give examples such as an "allergy" flag or a priority group for "wheelchair users", and at a clinic or a similar business the name of a line or a service can itself reveal health information. A note, a flag or the answer to one of your own questions can hold such data only if your team types it in or your question asks for it. turnda refuses some words in questions as a first safety net, but it does not catch every wording. You must have a legal basis to do so. We treat notes and flags as sensitive: staff-only, never on a public screen, left out of exports, and deleted outright when your visitor-data window ends.
- How long: for as long as you have an account, and then as set out in section 11.
4. Confidentiality
Only the people who run turnda (today its founder) can access Business Personal Data, and only to provide, support or secure the service, or when the law requires it. They are bound to keep it confidential.
5. Security
We keep the measures in Annex 2 in place, and we may improve them. We will not reduce the overall protection they give during your subscription.
6. Retention you control
You set how long visitor details are kept: any value from 24 hours to 1 year, 48 hours by default, counted from the end of each visit (for an appointment, from the booked time). The database refuses a value outside that range. When the window ends, the visitor's name and contact are erased, and notes, flags, comments, answers to your own questions, a connected system's reference for the visit and WhatsApp reply-window records are deleted; anonymous counts remain for your reports. If you shorten the window, it also applies to visits that have already ended. A visit left as called, being served or on hold is closed only after 72 hours untouched, so its clock starts then. The other fixed periods, including the 30 days the WhatsApp message log keeps each message and the number it went to, are listed in Annex 1.
7. Sub-processors
- You give us general permission to use the sub-processors listed at turnda.com/sub-processors (Annex 3 lists them).
- Before we add or replace one, we update that page and email you at least 14 days ahead. If you object on reasonable data-protection grounds, tell us within those 14 days; if we cannot meet your objection, you may close your account before the change, and we will refund the unused part of the period already paid for.
- Every sub-processor is bound by written terms that protect the data at least as well as this agreement. We remain responsible to you for what they do.
8. Helping you with people's requests
- turnda gives you the tools to answer requests yourself: an owner can search for one visitor (the name, the contacts including any earlier contact your staff replaced, and when the visit was made) and erase everything held about that visit in one step, and can export the setup and reports. Every request handled this way is logged for your records, identifying the person only by a one-way fingerprint.
- If a request about your data reaches us directly, we pass it to you within 5 working days and do not answer it ourselves unless you ask us to or the law requires it.
- If you need our help beyond the tools, we give it at no charge for reasonable requests.
Limits we tell you about now:
- Opt-out records survive erasure. If a visitor replied STOP or unsubscribed, a one-way fingerprint of their number or address is kept so we keep honouring it.
- Backups are not reached by an erasure straight away. See section 11.
- A support-report screenshot cannot be searched for one person. Screenshots you attach to a support report are deleted after 30 days; an erasure does not reach them sooner.
9. If personal data is breached
- We will tell you without undue delay, and within 72 hours of becoming aware, of any breach of security that leads to Business Personal Data being lost, destroyed, changed, disclosed or accessed without permission.
- We will tell you what happened, what data and how many people may be affected, the likely consequences, what we have done and will do, and who to contact. If we do not know everything at first, we tell you what we know and follow up.
- We will take reasonable steps to contain it and help you meet your own duties (for example to notify a regulator or the people affected). You decide whether to notify them; we will not notify your visitors or a regulator about your data in your name unless you ask us to or the law requires us to.
10. Assessments, records and audits
- We will give you the information you reasonably need for a data-protection impact assessment or a regulator's enquiry about our processing.
- Audits. Because turnda is run by a very small team, we meet audit requests in writing: we answer your reasonable written questions about our processing and security within 30 days, once a year (or more often after a breach or if a regulator asks). If the law gives you a right to inspect that written answers cannot satisfy, we will agree a remote review with you, at your cost, with 30 days' notice.
- We keep records of our processing as the law requires.
11. When your account ends
- Before you leave, you can export your setup and download your reports at any time. The setup export holds your locations and hours, lines and every line's settings, counters, journeys, services, your own questions, priority groups, screen designs, message wording and the staff-schedule set-up. It never contains visitor or appointment records, your team list, or the keys of connected systems. Individual visit records are not kept long enough to export, by design.
- If you close the account, it can be reversed for 7 days; then Business Personal Data is deleted, and so are the pictures you uploaded and the sign-in records of your owners, managers and staff at our sign-in provider (a person who also belongs to another business on turnda keeps theirs until that business is deleted too). We also delete the business at our payment provider (Stripe), with its billing email and saved cards; Stripe keeps invoices and payments only where the law requires it.
- An account on the Free package is kept while it is used. It is never deleted for not paying. If for 12 months nobody signs in to it, no visitor joins one of its lines, and no appointment is booked (online or at your desk) or checked in, we email the owner twice — 30 days and 7 days before — naming the date, and then delete Business Personal Data and the team's sign-in records as above. One sign-in, one visitor joining, or one appointment booked or checked in, stops this. A paid package that ends moves the business to the Free package.
- You can ask us to delete sooner.
- Backups: we back up nightly and keep 14 daily and 8 weekly copies, and each night's backup is also encrypted by us and copied to a private store at Cloudflare in the European Union, where about 14 nights are kept. An erasure or deletion does not reach a backup; deleted data leaves the backups only as they expire, so it can remain in a backup for about 8 weeks. Backups are private and used only to recover from a disaster. If we restore one, we re-apply every erasure and deletion recorded in our request log since that backup before the service is used again. Because backups are nightly, up to 24 hours of data could be lost in a disaster.
- What we keep after deletion: the items listed in section 8.3 of our Privacy Policy — none of them contains your visitors' names or contact details, except one-way fingerprints in opt-out records and in the mobile-number check.
12. International transfers
- Business Personal Data is stored in the European Union: in Frankfurt, Germany, with an encrypted second copy of our backups at Cloudflare in the EU. Some sub-processors handle it in other countries (Annex 3). turnda itself is a Singapore company.
- Wherever data leaves the country it came from, we make sure it is protected to a standard comparable to the law it came from: through our sub-processors' written terms (including approved standard clauses where required), and through Annex 4 for transfers from you to us.
13. Liability
Each party's liability under this agreement is subject to the limits in the Terms of Service (section 13). A claim under this agreement is covered by the same overall cap as any other claim (Terms section 13.2); it is not added on top of it.
14. Term, law and changes
- This agreement lasts as long as we process Business Personal Data for you.
- It is governed by Singapore law, except where Annex 4 says the standard contractual clauses are governed by another law.
- We may change it with at least 30 days' notice by email and in the app, unless the law requires a change sooner. A change will not reduce the protection of Business Personal Data.
Annex 1 — Details of the processing
| Subject matter | Providing turnda: lines, appointments, lobby screens, visitor messages, reports, support |
|---|---|
| Nature | Collecting, storing, organising, displaying, sending, erasing |
| People | Your visitors; your owners, managers and staff |
| Visitor data | As switched on by you: name; one contact (WhatsApp number or email), and any earlier contact your staff corrected; answers to your own questions; a connected system's own reference for the visit; the messages sent and whether each was delivered, bounced or read; the language the visitor's page was shown in (so messages use it); party size; service; vehicle; visitor's note; line and appointment times and outcome; staff notes and flags; rating and comment; WhatsApp messages in both directions; the mobile number a visitor types for text updates (stored encrypted) and the proof of the visitor's agreement to them; a one-time code fingerprint for a few minutes if you require email confirmation; network address in an abuse counter for at most 15 minutes |
| Team data | Name, sign-in email, optional recovery email, username, PIN fingerprint, role, locations, device names, sign-in sessions, team chat messages, notifications; if staff scheduling is on, the attendance record and a one-way marker of each browser used |
| Sensitive data | Only if your team types it into a note or flag, or a question of yours asks for it |
| Visitor details kept | You choose 24 hours to 1 year after the visit; 48 hours by default. An earlier contact your staff corrected is erased at the same time |
| WhatsApp message log | The contents of each message and the number it went to: 30 days |
| Details typed before opening WhatsApp | 30 minutes |
| Mobile number given for text updates | Stored encrypted; until the visit ends plus 30 days, then wiped |
| Proof that a visitor agreed to text updates | 24 months. It holds the wording seen, the country and the language, and never the number itself |
| Mobile-number check | Before the first text, our messaging provider (Twilio) checks that the number is a mobile; the number is shared with it for that purpose only. We keep the answer as a one-way fingerprint of the number and its line type, with no end date |
| Team chat | 7 days |
| Notifications | Support replies at least 30 days, payments at least 90 days, others on your visitor window |
| Support screenshots and technical details | 30 days; the report itself 1 year after its last message |
| Security log of changes | 1 year |
| Staff attendance record | 1 year |
| Browser marker | 1 year after it was last used; deleted at once when the person is removed |
| Connected-system call log | 7 days, with names, phone numbers, emails and notes blanked |
| Connected-system record of calls already applied | 24 hours |
| Review-request marker | A one-way fingerprint, up to 365 days |
| Opt-out records | Kept (one-way fingerprint only) |
| Backups | About 8 weeks; the encrypted second copy about 14 nights |
Annex 2 — Security measures
- Separation of businesses by the database itself (row-level security forced on every business table, with a database role that cannot bypass it), and an automated check that refuses any new business table without it.
- Encryption in transit everywhere (HTTPS with strict transport security). Stored data is encrypted by our database provider.
- No passwords. Sign-in by email link or Google; staff PINs and recovery codes stored only as one-way fingerprints; sign-in sessions expire. When a team member is removed, their sign-in stops at once and their open browser clears the business data it holds the next time it checks in.
- Least data. Out of the box the join page asks for a name and an email address, the appointment booking page asks for a name, an email address and the service, and the entrance tablet asks nothing; every other visitor field is off unless you switch it on. One contact for messages per visit (an email the visitor gave stays alongside WhatsApp if they turn it on); notes and flags staff-only and never sent to a public screen; a numbers-only lobby screen is never sent names.
- Automatic deletion on the clocks in Annex 1, run every few minutes.
- Security log of every change made in an account, recording the event, not the personal data.
- Scrubbed logs and error reports: contact details and keys removed before anything is written; the error monitor's personal-data collection is switched off.
- Abuse protection: limits on sign-in attempts, code guessing and request floods.
- Backups nightly to private storage that the software checks is private before writing, and a second copy of each, encrypted by us before it leaves (AES-256) and checked after upload, in a private store at a different supplier (Cloudflare, EU).
- Card data never touches turnda; it goes straight to Stripe.
- Access to production limited to the people who run turnda, with keys held outside the code.
Annex 3 — Sub-processors (summary)
The list that governs, with what each company handles and where, is at turnda.com/sub-processors. It names ten companies:
| Company | What it does for turnda | Where |
|---|---|---|
| Supabase | Database, sign-in, file storage and backups | Frankfurt, Germany (EU) |
| Fly.io | Runs the application | Frankfurt, Germany (EU); connections accepted at the location nearest the person |
| Upstash | Background job queue and abuse counters | Frankfurt, Germany (EU) |
| Stripe | Payments and subscriptions | Stripe's own locations, including the United States |
| Meta (WhatsApp Business Platform) | Sends and receives WhatsApp messages on the turnda number | Meta's own locations, including the United States |
| Resend | Sends email to visitors and to business owners and teams | Sends from Ireland (EU); a United States company |
| Twilio | Sends text messages (SMS) and checks that a typed number is a mobile | Twilio's own locations, including the United States |
| Cloudflare | Domain names, routing of email sent to turnda.com addresses, website visit counting (no cookies), and the encrypted second copy of our backups | Cloudflare's global network, including the United States; the backup copy is stored in the EU |
| "Continue with Google" sign-in, and our support mailbox (Gmail) | Google's own locations, including the United States | |
| Sentry | Error reports, with personal-data collection switched off | Germany (EU) |
If this annex and that page ever differ, the page governs.
Annex 4 — Transfers from you to us
turnda is in Singapore and stores data in the European Union. Where the law that applies to you requires an approved mechanism for sending personal data to turnda, the following are incorporated into this agreement by reference and apply automatically, with you as the exporter and turnda as the importer:
| Your data comes from | Mechanism | Choices |
|---|---|---|
| European Economic Area or Switzerland | The EU standard contractual clauses (Commission Implementing Decision (EU) 2021/914) | Module 2 (controller to processor); where you are yourself a processor, Module 3. Clause 7 (docking) applies. Clause 9: option 2, general authorisation, with the notice in section 7 above. Clause 11: the optional wording does not apply. Clause 13: the supervisory authority of the EU country where you are established; if you are not established in the EU, that of the EU country where your representative under Article 27 of the GDPR is established, or, if you need none, that of one of the EU countries where the visitors whose data is transferred are located. Clauses 17 and 18: the law and courts of Ireland. Annexes I–III are filled by Annexes 1–3 of this agreement. For Switzerland, references to the GDPR are read as the Swiss Federal Act on Data Protection, and the Swiss regulator is competent. |
| United Kingdom | The UK International Data Transfer Addendum to the EU clauses, issued by the Information Commissioner | The tables are filled from this agreement; either party may end the addendum as its section 19 allows. |
| Brazil | The standard contractual clauses of Brazil's data protection authority (Resolution CD/ANPD No. 19/2024) | Incorporated in full, unchanged, as that resolution requires. |
| Saudi Arabia | The standard contractual clauses issued by the Saudi Data and AI Authority under the Personal Data Protection Law | Controller-to-processor clauses, incorporated by reference. |
| Anywhere else | This agreement, as a binding contract giving protection comparable to your law | — |
If a mechanism above is replaced by an updated version, the updated version applies from the date it becomes mandatory.
Also see our Terms of Service, Privacy Policy and sub-processor list.