Security and privacy
Team Continue holds what people tell it about their work. That only works if people trust it — so the rules are simple and strict.
What we don't touch
- No mailbox, calendar or file access. We never connect to Microsoft 365, Google Workspace or your file shares. Team Continue only knows what someone says in their interview.
- No passwords. The interview asks where a login lives (“in the vault, under Vendor portal”), never the password itself. If someone types one anyway, it's removed before the handover is built.
- No scoring of people. Interviews and check-ins are never rated. Managers see handovers, not transcripts.
Who sees what
- The person approves first. A handover is private until its owner has reviewed and approved it.
- Access per team. Only the colleagues and managers the owner's team allows can read or ask a handover.
- Every question is logged. The owner sees which questions were asked in their return brief.
Where data lives
- EU hosting. Data is stored with Supabase in Frankfurt, Germany, with row-level security: one company can never read another's data.
- Encrypted in transit (TLS) and at rest.
- AI processing runs through Anthropic's Claude API under commercial terms. Your interviews are not used to train AI models.
How long we keep it
- Holiday and sick-leave handovers expire 7 days after the person returns, unless the owner keeps them.
- Exit handovers stay until your company deletes them.
- Delete anything, any time. Owners can delete their own handovers; admins can delete everything for the company.
GDPR and works councils
A processor agreement is included in every plan. Because Team Continue is not a monitoring tool — it doesn't watch work, only records what people choose to share — introducing it is usually a short conversation with a works council. We provide a one-page summary for that conversation on request.
security@teamcontinue.com for questionnaires, the processor agreement or our list of subprocessors.