Data processing agreement
This agreement under GDPR article 28 is part of the Terms. The business that owns the workspace is the controller; SynchroShift is the processor.
Draft for lawyer review. This text describes what SynchroShift does today and may change after review.
Version 2026-11-08 ·
1. Subject and duration
SynchroShift processes personal data only to provide the scheduling service described in the Terms, for as long as the workspace exists and for up to 30 days after the owner deletes it.
2. Data subjects and data
Data subjects: the controller's staff, managers and owners. Personal data and retention are listed below. Special categories of data are not intended to be processed; sick leave is recorded only as dates and an optional note.
| Data | Purpose | Kept for |
|---|---|---|
| Your account: email address, name, profile photo, password (stored only as a hash by Supabase Auth), sign-in times, optional two-step sign-in | Signing in and showing who you are | Until the account is deleted |
| Workspace setup: name, shops, departments, job titles, contracts, break rules, templates, opening hours, staffing needs, branding and logo, plan and invoice details, terms acceptance | Running the workspace as the owner set it up | Until the workspace is deleted (30 days after the owner asks) |
| Team members: name, email, phone, role, shop, contract, hourly rate, birth date (only to apply the rules for staff under 18), notes, availability and preferences | Planning shifts within the rules and paying the right hours | While the person is on the team; the owner can erase a person (names and contact details are removed, hours totals stay) |
| Shifts, schedule versions, worked hours and their confirmation, shift swaps and comments, tasks | The schedule itself and payroll | Worked hours: kept until a legal retention period is set (lawyer review pending). Other schedule data: until the workspace is deleted |
| Requests: holiday, unavailability and sick leave (only the dates and an optional note, never a diagnosis), and the manager's decision | Planning around absence | Until the workspace is deleted or the person is erased |
| Announcements and in-app notifications | Telling the team about changes | Notifications: 90 days. Announcements: until the workspace is deleted |
| Activity log (who changed what and when) and the Undo copies of deleted shifts | Security, finding mistakes and undoing them | Activity log: 2 years. Undo copies: 90 days |
| Booking connections (secrets stored as hashes or in a vault), copies of bookings (time, title, staff reference), calendar feed links | Showing bookings next to the schedule and calendar feeds | Booking copies: 30 days after the booking ends. Feed links: until revoked or expired |
| AI use: a counter per question (who, when). Questions and schedule context go to Google Gemini only when someone asks; names are replaced with placeholders first. We do not store the questions | The AI assistant and fair-use limits | Counters: 13 months |
| Email delivery log, unsubscribe and suppression lists, invitation send log | Sending account and team emails and stopping abuse | Delivery log: 90 days. Invitation log: 30 days. Suppression list: until removed |
| Platform records: memberships, permissions, plans, activation events (sign-up source, first schedule published), support access log, retention settings, data-fix log, request counts for abuse limits (the address is stored only as a hash) | Running the service, measuring sign-ups without cookies, accountability for support access | Until the workspace is deleted; support access log: 2 years |
| Contact form: name, email, company, phone (optional), team size and message | Answering you | Kept in our mailbox for up to 12 months, then deleted |
3. Processor obligations
- Process data only on the controller's documented instructions, which are the Terms, this agreement and the settings the controller chooses in the app.
- Ensure that people with access are bound by confidentiality.
- Apply the security measures in section 5.
- Help the controller answer data subjects' requests: owners can export a person's data, correct it and erase a person.
- Help the controller with security, breach notification and impact assessments, taking into account the information available to us.
- Tell the controller without undue delay, and where possible within 48 hours, after becoming aware of a personal data breach.
- At the end of the service, delete the data (30 days after the owner deletes the workspace) unless law requires storage. The owner can export everything before.
- Make available the information needed to show compliance and allow audits, at the controller's cost and with reasonable notice.
4. Sub-processors
The controller gives general authorisation to use the sub-processors below. We tell workspace owners by email at least 30 days before adding or replacing one, and the owner can object. Each sub-processor is bound by equivalent data protection terms. Transfers outside the EU rely on the mechanism shown.
| Service | Purpose | Where | Transfer basis |
|---|---|---|---|
| Supabase | Database, sign-in, file storage and scheduled jobs | EU (Ireland) | No transfer: data stays in the EU |
| Cloudflare | Hosting the web app and bot protection (Turnstile) on sign-in and sign-up | Global network, company in the USA | EU-US Data Privacy Framework and standard contractual clauses |
| Resend | Sending account and team emails | USA | Standard contractual clauses |
| Google (Gemini API) | Answering AI assistant questions, only when someone asks, with names replaced | USA | EU-US Data Privacy Framework and standard contractual clauses |
| Google Fonts | Loading the typefaces of the web app; your browser sends its IP address to Google when it loads them. We are moving to fonts served from our own site | USA | EU-US Data Privacy Framework |
5. Security measures
- Hosting of the database, sign-in and files in the EU (Ireland).
- Each workspace's data separated by database row-level security; permissions per person and, optionally, per shop.
- Connection secrets stored as hashes or in an encrypted vault; secrets are shown once.
- Encryption in transit (HTTPS) and at rest by the hosting provider.
- Activity log of important changes, kept 2 years; logged and time-limited support access.
- Two-step sign-in available; owners and admins are asked to switch it on.
- Retention jobs that delete expired data automatically (see the table above).
6. Contact
Questions about this agreement: s.golee@icloud.com.
