Privacy Policy
Last updated: 6 August 2026
1. Who is responsible for your data
SyncHire is a service operated by GetPro, a French société par actions simplifiée (SAS) registered with the Paris Trade and Companies Register under number 812 105 138, with its registered office at 41 rue Faidherbe, 75011 Paris, France. GetPro is the data controller for the personal data described below. For any question about this policy or your data, contact us at privacy@synchire.app.
2. What SyncHire does, in one sentence
SyncHire helps recruiters schedule interviews by showing candidates only the times when the hiring manager is genuinely free, read live from their calendar. Understanding what we do is understanding what data we handle — and, above all, what we don't.
3. The data we process
- Recruiters (users). First and last name, email, password (stored encrypted, never in clear text), scheduling preferences, and the organisation you belong to.
- Organisations. Your company name.
- Hiring managers. First and last name, email, company, and their calendar connection status.
- Candidates. First and last name entered by the recruiter; email and phone number that the candidate provides themselves when booking.
- Calendar data. Free/busy periods read live from connected calendars to compute availability. We do not store these periods; they are used only to render a page, then discarded.
- Created events. When a candidate books, we create an event in the recruiter's calendar (title, time, participants, Google Meet link).
- Billing data. For organisations subscribed to the Pro plan: the organisation name, billing identity, subscription status and invoice history. Card details are entered directly with our payment provider and never touch our servers.
- Technical incident data. When a page fails, we keep — for as long as it takes to fix the fault — the error message, the page address, and the identifiers of the account and organisation concerned along with their plan (free or Pro). Your email address is not included (see section 7).
4. Calendar access — our commitment
SyncHire only reads free/busy: never event details, and never writes to a hiring manager's calendar. Access is revocable at any time.
In practice, for a hiring manager, we know when they are busy — never with whom, on what, or why. The connection is made through Google or Microsoft OAuth with read-only access, which we use solely to compute availability (free/busy) — we never read event details. A hiring manager can remove this access at any time from their own Google or Microsoft account, without telling us.
For the recruiter, access is broader: it lets us create the interview event in their own calendar (they are the organiser) and generate the video link (Google Meet or Microsoft Teams).
5. Purposes and legal bases (GDPR)
We process this data to: create and manage your account, compute availability, create interview events, send service emails (confirmations, password resets, invitations, notifications), and manage subscriptions and billing. The legal bases are performance of the contract with your organisation and our legitimate interest in providing a reliable scheduling service. Billing additionally rests on our legal obligation to retain accounting records, and technical fault monitoring on our legitimate interest in keeping the service reliable and secure. Connecting a calendar relies on consent, which can be withdrawn at any time.
6. Google user data (Limited Use)
SyncHire's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically: we use Google calendar data only to provide the user-facing scheduling feature; we do not sell it; we do not use it for any advertising purpose; and no human reads it, except with your consent, for security purposes, to comply with the law, or where strictly necessary for support.
We share Google user data only with Nylas (EU region), which operates the technical connection to the Google Calendar API on our behalf, and with our hosting provider Hetzner (Germany) strictly insofar as it passes through our servers — and with no other third party. In particular, it is never sent to the payment, error-monitoring or artificial-intelligence providers listed in section 7. We never sell Google user data, never share it with advertisers or data brokers, and never transfer or disclose it except to these processors or where required by law.
7. Processors and hosting
We rely on a small number of contractually-bound providers, each for a specific reason:
- Hetzner (Germany) — hosting of our servers and database.
- Nylas (EU region) — technical connectivity to Google and Microsoft calendars; Nylas, not us, holds the calendar access tokens.
- Google and Microsoft — sign-in to your SyncHire account and calendar data, when you choose those providers.
- Resend — sending service emails (booking confirmations, invitations, notifications, password resets).
- Stripe — payment and billing for the Pro plan: organisation name, billing identity and invoice history. Card details are entered directly with Stripe and never touch our servers. No candidate, hiring-manager or calendar data is sent to Stripe.
- Sentry (EU region) — technical monitoring: when a page fails, we are sent the error message, the page address, and the identifiers of the account and organisation concerned along with their plan (free or Pro), for as long as it takes to fix the fault. Neither your email address, nor the contents of the page, nor any calendar data is included. These reports are erased after ninety days.
- Anthropic (United States) — only when a recruiter clicks "Translate" in their settings: the text of their message template is then sent to the Claude API to draft a translation. This call happens only at their explicit request, never automatically, and covers that text alone — no candidate, hiring-manager or calendar data is ever sent to it.
- Plausible (European Union) — audience measurement for our public site and sign-up pages, without cookies and without individual identifiers.
Some providers may process data outside the European Union; where that happens, such transfers are covered by appropriate safeguards (the European Commission's Standard Contractual Clauses).
8. How we protect your data
All communication with SyncHire, and between SyncHire and our providers, is encrypted in transit (HTTPS/TLS). The OAuth tokens that grant calendar access are stored by Nylas in the European Union and never touch our servers — our application holds only opaque identifiers. Account passwords are stored as salted hashes (bcrypt), never in clear text, and application secrets are kept encrypted. Free/busy calendar data is processed in memory to render a page and never written to our database. Access to production systems is restricted to authorised personnel, data is hosted in the European Union (Germany), and each organisation's data is isolated from every other's.
9. Retention
We keep your account data for as long as your account is active. Free/busy periods are not retained. Hiring manager and candidate data are kept for as long as useful to your recruiting activity, then deleted on request. When an account is closed, associated data is deleted or anonymised. Two exceptions exist, for distinct reasons: invoices and accounting records are kept for ten years, as French law requires; technical incident reports are automatically erased after ninety days.
10. Your rights
Under the GDPR, you have the right to access, rectify, erase, restrict, port and object to the processing of your data, as well as the right to withdraw consent (for example by disconnecting a calendar). To exercise them, write to privacy@synchire.app. You may also lodge a complaint with the French data-protection authority, the CNIL (www.cnil.fr).
11. Cookies
SyncHire uses only strictly necessary cookies, chiefly to keep you signed in. We use no advertising cookies, no tracking for targeting purposes, and we never resell data. Audience measurement on our public site and sign-up pages (Plausible, hosted in the European Union) works without cookies and without individual identifiers — which is why you are never asked for a consent banner.
12. Changes
We may update this policy. For any significant change, we will inform users. The date at the top shows the last update.