Privacy policy
Last updated 31 October 2026
Highers helps companies hire salespeople. This page explains what personal data we hold, why, and what you can ask us to do with it. Highers B.V. (Poortland 66, 1046 BD Amsterdam, the Netherlands, KvK 42186560) is the controller of this data. Contact: thomas@highers.co.
Clients: when you sign in and use the app
If you sign in with Google or Microsoft, we receive your email address and your name from them. We use these to create and identify your account. We do not receive your password and we do not access your mailbox, contacts or files. A cookie keeps you signed in; it is required for the app to work and is not used for tracking or advertising.
Information you give us about your company and roles (the brief, your feedback on candidates) is used to run your search. When your company accepts our Client Terms we keep a record of the acceptance: who accepted, for which company, when, from which IP address and browser, and which version. We keep it as evidence of the contract.
Clients: when you connect your calendar
A company admin can connect a Google Calendar or a Microsoft Outlook calendar so candidates are offered real interview times. Connecting is optional, and the connection belongs to your company account. What we do with it:
- We read when your primary calendar is busy or free, and the calendar's timezone, to work out open slots inside the hours you set. We do not read the titles, descriptions or attendees of your other events, and we do not keep them.
- When a candidate confirms a time, we create one interview event on your calendar (title, time, video link, the candidate as guest), and move or delete that same event if the time changes. We only change events we created.
- The open slots we computed are included in the replies we draft to candidates. Our AI providers process them for that purpose only.
- People at Highers do not read your calendar data, except the interviews we created for you, and otherwise only with your permission, to fix a problem you report, for security, or when the law requires it.
- Who receives it: the candidate, as guest of the interview event; our AI providers, who receive only the open slots, process them only to draft the reply and do not use them to train their models; and our hosting provider (Google Cloud). Nobody else.
- How long we keep it: the connection (account email, timezone, encrypted token) until you disconnect, which deletes it at once. The record of each interview we created (its identifier, time, video link and guest) while your company account is open; we delete it when the account is closed, or earlier if you ask us at the address above.
The access we receive from Google or Microsoft (a refresh token) is stored encrypted. We do not sell calendar data, share it for advertising, or use it to train AI models, ours or anyone else's. You can disconnect in the app at any time, which deletes the stored token. You can also revoke access in your Google or Microsoft account settings, which makes the token useless at once. Events we already created stay on your calendar until you remove them.
Highers' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Candidates: where your data comes from
We find people whose professional background fits roles our clients are hiring for. We collect professional information that is publicly available, mainly on LinkedIn and company websites: name, job titles, employers, career history, education, skills, location and profile links. Contact details may come from data providers. We also hold the messages we exchange with you, and anything you tell us or upload (for example a CV, your salary expectations or your availability).
We use this to contact you about roles that may interest you, to assess whether a role fits you, and, if you tell us you are interested, to introduce you to the hiring company. Our legal basis is our legitimate interest in matching people with roles (GDPR art. 6(1)(f)); where you sign up yourself, or ask us to introduce you, it is also to take the steps you ask for (art. 6(1)(b)), and your consent where we ask for it.
We use AI tools to help find, assess and write to candidates. A person at Highers reviews introductions, and hiring decisions are always made by people at the hiring company. You can ask us to explain how we assessed you, or to have a person look at it again.
Visitors to highers.co
When you visit highers.co from the United States, we use RB2B, a website visitor identification service, to learn which company and, where RB2B can match it, which person visited. RB2B sets cookies and matches the visit against its own US data, then sends us the result: for example name, job title, company, LinkedIn profile and the pages viewed. We use it to contact people at companies that may be hiring salespeople. Our legal basis is our legitimate interest in reaching those companies (GDPR art. 6(1)(f)). Visitors from outside the United States are not identified: the RB2B script is not loaded for them. You can object at any time by writing to the address above; we then delete what we received about you and do not contact you.
Who receives the data
- Hiring companies we introduce you to. Each uses your profile only for its hiring, as an independent controller, and must delete it within 6 months if it does not hire you.
- Service providers that process data for us: hosting (Google Cloud, Vercel), AI providers (Anthropic, OpenAI, TypeSafe), messaging and outreach tools (lemlist, Unipile), contact data enrichment (FullEnrich), website visitor identification for US visitors (RB2B) and translation (DeepL).
Some providers are in the United States. Transfers outside the European Economic Area rely on an adequacy decision of the European Commission or on the EU standard contractual clauses. We do not sell personal data or share it for advertising.
How we protect the data
- Encryption in transit: the app and our API are only served over HTTPS (TLS).
- Encryption at rest: our database and servers run on Google Cloud, which encrypts stored data by default. On top of that, the access we receive from Google or Microsoft when you connect a calendar (refresh tokens) is encrypted again by us, with a key kept outside the database, so a copy of the database alone cannot be used to reach your calendar.
- Separation between companies: every row in our database belongs to one company, and the database itself enforces that a company's users can only read their own company's data (row-level security).
- Accounts: clients sign in with Google or Microsoft, so we never hold their password. Our own staff passwords are stored only as argon2 hashes. Sessions use a secure, httpOnly cookie, and we store only a hash of session and API tokens, never the tokens themselves.
- Access by our team: limited to the people who run the service, through individual accounts. Server access uses personal SSH keys.
- Minimum data: for a calendar connection we keep the connected account's email address, its timezone and the encrypted token, and for each interview we create its identifier, time, video link and guest. Busy and free times are read when needed and not stored.
- Incidents: if a breach affects your personal data, we notify you and the competent data protection authority as the law requires.
How long we keep it
Candidate data: as long as it is useful to put you forward for roles, and at most 2 years after our last contact with you, unless you ask us to delete it sooner. Client account data: while the account is open and as long as needed for invoices and claims afterwards. Records of acceptance of our Client Terms: as long as the contract can give rise to a claim.
Your rights
You can ask us to see, correct, export or delete your data, to restrict its use, or object to it at any time, including to any further contact from us. Write to thomas@highers.co; we answer within one month. You can also lodge a complaint with a data protection authority: in the Netherlands, the Autoriteit Persoonsgegevens, or the authority where you live or work.