Data Processing Addendum
This addendum forms part of the agreement between Tinbit ("we") and the customer ("you") for Tinbit Business and Enterprise. It applies when we process personal data on your behalf. Version 0.9, November 2026. Draft for review: the signed version will be issued with your order.
1. Roles
You are the controller of personal data about your team members that you ask us to process (team membership, roles, training completion, the admin log and shared done/next cards). We are your processor for that data. Each person's own Tinbit account, focus history and progress belong to that person, and we act as their controller under our Terms. That's why your team can't see them.
2. What we process, and why
- Categories of people: your team members and admins.
- Data: names, work emails, roles, team membership, shared cards and replies, training completion (done or not done), admin log entries, and the team's weekly totals, which have no people in them.
- Purpose: to provide Tinbit Teams as described on heytinbit.com/teams and in the Trust Charter.
- Never: per-person activity reports, emotion inference, screenshots, keystrokes or content of apps and pages. The Trust Charter forms part of this addendum.
3. Our commitments
- We process your data only on your documented instructions, including the settings in your team's admin console.
- Everyone with access is bound by confidentiality.
- We help you answer requests from people exercising their rights, and with data protection impact assessments and consultations with works councils or regulators.
- We tell you without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting your data.
- At the end of the service we delete your team's data within 30 days, unless the law requires us to keep it. People's own accounts stay theirs.
- We make the information you need to show compliance available to you, and allow audits once a year with reasonable notice. Enterprise customers can also use our security questionnaire answers.
4. Security
- Encryption in transit (TLS) and at rest. Integration tokens are also encrypted with AES-GCM.
- Passkey sign-in and optional company single sign-on (SAML/OIDC) and SCIM.
- The admin log can't be edited, and every member of the team can read it.
- Totals-only reporting with a 10-person minimum and noise, enforced in code.
- Least-privilege access for our staff, and every access is logged.
5. Subprocessors
| Subprocessor | What for | Where |
|---|---|---|
| Cloudflare, Inc. | Hosting, database, real-time rooms | Global edge; EU region on request (Enterprise) |
| Stripe, Inc. | Billing and invoices | US / EU |
| Resend | Sign-in emails | US |
| WorkOS, Inc. | Single sign-on and directory sync (Enterprise, only if you turn it on) | US |
Slack, Microsoft and Google are only involved when you or your people connect them, and then under your own agreements with them. We give 30 days' notice before adding a subprocessor, and you can object.
6. International transfers
Where data leaves the EEA, UK or Switzerland, the EU Standard Contractual Clauses (module 2, controller to processor) and the UK Addendum apply and are incorporated by reference. Enterprise customers can ask for EU data residency.
7. Order of precedence
If this addendum and the agreement conflict on data protection, this addendum wins. If the Trust Charter gives people more protection than either, the Trust Charter wins.
Need a signed copy, a different version for your legal team, or a security questionnaire? Ask from the teams page.