We use a small number of third parties to run useful hr. Each one is a sub-processor under our Data Processing Agreement.
We give you at least 30 days’ notice before we add or replace anyone on this list, and you may object on data protection grounds.
Current sub-processors
| Provider | What they do | Where they process | Entity |
|---|---|---|---|
| Google Cloud / Firebase | Hosting, database, backend functions, sign-in (Firebase Authentication), app attestation (App Check with reCAPTCHA Enterprise) | Belgium (europe-west1) for stored data; sign-in in the United States; hosting and app attestation on Google’s global network | Google Cloud EMEA Limited |
| Postmark (ActiveCampaign) | Transactional email: sign-in links, and notifications when a review or an announcement launches | United States | ActiveCampaign, LLC |
Where your data lives
Your employee data is stored in Belgium (Google Cloud, europe-west1). It is not stored in the United States.
Two things do reach the United States:
- Sign-in. Firebase Authentication, which lets your users sign in, runs only from Google’s US data centres. It holds each user’s email address, the name and photo from Google sign-in, sign-in events including IP addresses, and the ids and permissions that let them into a workspace. It holds none of their review, rating or objective data.
- Email. When we send a sign-in link or a notification, the recipient’s name and email address pass through Postmark.
Both transfers rely on the UK Extension to the EU–US Data Privacy Framework where the recipient is certified, or on the UK International Data Transfer Addendum to the Standard Contractual Clauses.
What we deliberately do not use
- We do not use an advertising network inside the application.
- We do not use session replay or heatmap tools.
- We do not sell data to anyone, for any purpose.
- We do not use your data to train models that serve other customers.
Changes
| Date | Change |
|---|---|
| 4 November 2026 | Initial list published |