Subprocessors
DRAFT — NOT YET IN EFFECT. This document is a working draft prepared for review by an attorney. It has not been approved, is not legal advice, and does not bind anyone in its current form. Text in square brackets, such as
[LEGAL ENTITY NAME], is a placeholder that still has to be filled in.
A subprocessor is a company we engage that may process personal data contained in Customer Data in order to help us provide Tick Tack Timetrack. This list forms part of our Data Processing Addendum. Every subprocessor is bound by a written agreement that requires it to protect the data and use it only to provide its services to us.
Current subprocessors
| Subprocessor | What it does for us | Data involved | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting of the application (Amazon ECS on AWS Fargate), the database (Amazon RDS for PostgreSQL), file storage for photos and exports (Amazon S3), and application logs (Amazon CloudWatch) | All Customer Data | United States ([AWS REGION]) |
| Amazon Web Services, Inc. | Sending email notifications, invitations, and security alerts (Amazon Simple Email Service) | Recipient name and email address and the content of the message | United States ([AWS REGION]) |
| Amazon Web Services, Inc. | Maps and address search (Amazon Location Service). The user’s browser requests map images directly; our servers send the address text an administrator searches for | Viewer IP address and the map area displayed; address search text. No worker names are sent | United States ([AWS REGION]) |
Used only if enabled
| Subprocessor | When it is used | Data involved | Location |
|---|---|---|---|
| Functional Software, Inc. (Sentry) | If we turn on error monitoring. Reports are sent only when a request fails with a server error or the web app crashes | Error description with secrets, contact details, pay amounts and coordinates removed; request ID, route and status code; company and user identifiers. No request bodies, cookies, or IP addresses | United States [CONFIRM SENTRY DATA REGION] |
| Google LLC | Only if the Customer enables “Sign in with Google” and a user chooses it | Email address and account identifier exchanged during sign-in | United States |
| Microsoft Corporation | Only if the Customer enables “Sign in with Microsoft” and a user chooses it | Email address and account identifier exchanged during sign-in | United States |
| Apple Inc. | Only if the Customer enables “Sign in with Apple” and a user chooses it | Email address, name (on first sign-in) and account identifier exchanged during sign-in | United States |
Single sign-on is not available at launch. These providers will receive data only once the feature is offered and the Customer enables it.
Not subprocessors
- Webhooks and API integrations. When a Customer configures a webhook or connects an integration through our API, we send data to the endpoint the Customer chose. That recipient acts for the Customer, not for us.
- Payroll file exports. Export formats for payroll providers are files the Customer downloads. We do not send data to those providers.
- The marketing website does not load analytics, advertising, or third-party tracking scripts.
Changes to this list
We will publish an updated list, with a new version date, at least
[SUBPROCESSOR NOTICE PERIOD, e.g. 30] days before a new subprocessor starts processing Customer
Data, and email Customers’ administrators who have asked to receive these notices at
[SUBPROCESSOR NOTICE SIGN-UP METHOD]. A Customer may object as described in the DPA. Earlier
versions remain available at /legal/subprocessors/<version>/.
Planned additions that will be announced this way before they start: a payment processor for paid plans after the beta, and providers for text messages and mobile push notifications if those features are launched.