Privacy Policy
Last updated: November 2026
1. Who we are
Hiro is a recruitment CRM platform operated by Operanex SRL, Rue de Bordeaux 38, 1060 Brussels, Belgium. This privacy policy explains how we collect, use, and protect information when you visit our marketing website (hiro.ninja) and when you use the Hiro application, including when you connect a Google or Microsoft account (mailbox, calendar or Google Meet) to it.
For the candidate and client data our customers store in the application, our customer is the data controller and Operanex acts as their processor (see our Terms & Conditions). For the data of the people who sign in to Hiro, including the mailboxes they connect, Operanex is the data controller.
2. What data we collect
Contact form submissions
When you submit a demo request or contact form, we collect the information you provide: name, email address, company name, job title, and your message. This data is used solely to respond to your enquiry.
Audience measurement (no consent required)
We use Plausible Analytics, a privacy-friendly analytics tool hosted in the European Union. Plausible does not use cookies, does not store your IP address and does not collect personal data: it only produces aggregate statistics such as page views, referral sources, countries and device types. Because it cannot identify you, it runs for every visitor without asking for consent. Legal basis: our legitimate interest in knowing how our website is used.
Product analytics (with your consent)
If you accept analytics cookies in our consent banner, we load PostHog (PostHog EU cloud, hosted in Germany). PostHog records how you navigate the website: pages viewed, clicks, conversion funnels such as pricing page to trial sign-up, and session recordings that replay your visit. In session recordings, everything you type is masked before it leaves your browser. PostHog assigns you a random identifier, stored in a cookie shared with our application, so that a trial started after a visit can be linked to that visit. It is never loaded if you decline or do not answer the banner. Legal basis: your consent, which you can withdraw at any time (see "Cookies" below).
Advertising tags (with your consent)
If you accept marketing cookies, we load Google Tag Manager, which in turn loads the advertising tags we use to measure conversions and to show you relevant ads on other platforms (retargeting): Google Ads, Microsoft Advertising (UET tag), LinkedIn Insight Tag and Meta Pixel. We run Google Tag Manager with Google Consent Mode v2: all advertising signals default to "denied" and only switch to "granted" once you accept marketing cookies. Google Tag Manager is not even downloaded before you accept analytics or marketing cookies, so no data is sent to Google, Microsoft, LinkedIn or Meta without an opt-in. These providers may transfer data outside the European Economic Area (see "Sub-processors" below). Legal basis: your consent.
3. Google and Microsoft account data (Hiro application)
Hiro users can connect their Google or Microsoft account to the application, in Settings › Email. This is optional, is done by the user through Google's or Microsoft's own consent screen, and can be revoked at any time. Each permission below is only requested when you turn on the feature that needs it: sending email when you connect the account, calendar access when you click "Sync calendar", and Google Meet access when you click "Import Meet transcripts".
What we access and why
- Your email address (Google
userinfo.email, MicrosoftUser.Read) — to identify which mailbox is connected. - Reading messages (Microsoft
Mail.Readonly) — to keep the replies of your candidates and clients next to their record in Hiro. When a new message arrives, we check its sender and recipients. Only messages exchanged with contacts that already exist in your Hiro workspace are retrieved and stored; all other messages are ignored and never stored. Hiro does not request access to read Gmail messages. - Sending messages (Google
gmail.send, MicrosoftMail.Send) — for Gmail, the permission you grant when connecting the mailbox; for Outlook, only if you separately click "Allow sending" in your mailbox settings. Hiro then sends, from your address, the emails you write and confirm in Hiro, and nothing else. This permission does not let Hiro read, modify or delete your messages. - Your calendar (Google
calendar.events, MicrosoftCalendars.ReadWrite) — only if you click "Sync calendar". Hiro adds the interviews you schedule to your calendar, with the guests and video-call link you choose, and updates or cancels them when the interview changes; your calendar provider sends the invitations. Hiro also reads the events of your main calendar, from 30 days ago to six months ahead, so that you can see them next to your interviews in Hiro, and so that an interview you move in your calendar is moved in Hiro too. Hiro never changes or deletes calendar events it did not create. - Google Meet transcripts and settings (Google
meetings.space.readonlyandmeetings.space.settings) — only if you click "Import Meet transcripts". After an interview call held on a Google Meet link that Hiro created for that interview, Hiro reads the transcript of that call and adds it to the candidate. When you tick "Transcribe the call automatically" on an interview, Hiro turns on automatic transcription for that call's Meet space; it is off unless you tick it, and Google Meet tells everyone in the call that it is being transcribed. Hiro does not read your other meetings, recordings or files.
What we store
The OAuth tokens that give access to your mailbox, encrypted at rest. For synced messages with your contacts: sender, recipients, subject, date, a short preview and a copy of the message, so you can read it in Hiro. For emails sent through your mailbox: the recipient, subject, content and delivery status, so the campaign history is complete. This data is only visible to you and to the members of your Hiro workspace who are allowed to see it.
For calendar sync: a copy of the events of your calendar (title, description, location, times, organiser, guests and video-call link) and the link between each interview and its calendar event. Events you did not create in Hiro are only shown to you; the interviews you schedule are visible to your workspace like any other interview. For Meet transcripts: the transcript of each interview call (speaker names, what was said and when, and the link to the transcript document in your Google account), attached to the candidate and visible to the members of your workspace.
What we never do
- We never sell this data or use it for advertising.
- We never transfer it to third parties, except to the sub-processors needed to run Hiro (listed below), to an AI assistant you connect yourself (see below), to comply with the law, or as part of a merger or acquisition with prior notice.
- Humans at Operanex do not read it, unless you ask us to (for example for support), it is necessary for security or abuse investigations, or the law requires it.
- We do not use it to develop, improve or train generalised artificial intelligence or machine learning models.
AI features and AI assistants you connect
Hiro's built-in AI features do not receive the emails, calendar events or transcripts described in this section. If you connect your own AI assistant (such as Claude or ChatGPT) to Hiro in Settings › AI assistants, that assistant can, when you ask it, read your own calendar events in Hiro (title, times, location, guests and video-call link) to answer you; it does not receive Meet transcripts. You choose and authorise that assistant yourself, can disconnect it at any time, and its provider's own terms and privacy policy apply to what it receives.
Google API Services: Limited Use
Hiro's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access and deleting data
In Settings › Email in Hiro, the menu of each connected account lets you turn features off one by one: "Stop syncing calendar" removes the copies of your calendar events from Hiro (the events stay in your own calendar), and "Stop importing transcripts" stops reading Meet transcripts (transcripts already added to candidates stay until you or an admin of your workspace delete them). "Remove" disconnects the account: we then revoke our access with Google or Microsoft, delete the stored tokens and remove the synced messages and calendar copies of that account from the application. You can also revoke access from your Google Account or your Microsoft account. To have every remaining copy deleted, including emails already sent through your mailbox, contact us at the address below; we complete such requests within 30 days.
Legal basis: the performance of our contract with you (providing the features you enable), and our customer's legitimate interest in managing its recruitment communications.
4. Cookies
Our website sets the following first-party cookies on the hiro.ninja domain:
hiro_consent— remembers the choice you made in the consent banner (analytics: yes/no, marketing: yes/no). 12 months. Strictly necessary, no consent required.hiro_attrandhiro_attr_last— the acquisition source of your visit: campaign parameters in the URL (UTM, ad click identifiers), the referring website and the page you landed on. They contain no personal data and are only written once you have accepted analytics cookies. 90 days. If you start a trial or request a demo, this source is attached to your account or request so that we know which channels bring us customers. Legal basis: our legitimate interest in measuring our marketing.- PostHog cookies (
ph_*) — the random visitor identifier and session state described above. Only set after you accept analytics cookies. Up to 12 months. - Advertising cookies set by Google, Microsoft, LinkedIn and Meta through Google Tag Manager, only after you accept marketing cookies. Their names and durations are documented by each provider.
You can change or withdraw your choice at any time via the "Cookie settings" link in the footer of every page. Withdrawing analytics consent stops PostHog and deletes the attribution cookies; withdrawing marketing consent switches all advertising signals back to "denied". Cookies already set by third parties can be removed from your browser settings.
5. How we use your data
- To respond to your demo request or enquiry
- To understand how visitors use our website (via aggregated, anonymous analytics)
- To improve our website content and user experience
- In the application, to provide the features you enable, such as syncing replies from your contacts or sending emails from your connected mailbox (see section 3)
We do not sell, rent, or share your personal data with third parties.
6. Your rights under GDPR
If you are located in the European Economic Area, you have the following rights regarding your personal data:
- Access: request a copy of data we hold about you
- Rectification: request correction of inaccurate data
- Erasure: request deletion of your data
- Portability: request your data in a portable format
- Objection: object to processing of your data
- Restriction: request restricted processing of your data
To exercise any of these rights, please contact us using the details below.
7. Data retention
Contact form submissions are retained for as long as necessary to respond to your enquiry and for legitimate business purposes. Plausible data is stored in aggregate form and cannot be linked to individual visitors. PostHog events and session recordings are kept for a limited period that we are currently confirming with our provider; this policy will be updated with the exact duration.
Account tokens are deleted as soon as you disconnect the account. Copies of calendar events are deleted when you stop syncing the calendar or disconnect the account. Synced and sent emails, and the Meet transcripts added to candidates, are kept while the Hiro account that holds them is active, and are deleted with the rest of the account data when the account is closed (see our Terms & Conditions), or earlier on request; a transcript can also be deleted at any time by the person who imported it or a workspace admin.
8. How we protect your data
We take the following technical and organisational measures to protect personal data, in particular the data received from Google and Microsoft accounts described in section 3, against unauthorised access, alteration, disclosure or destruction:
- Encryption in transit. The website and the Hiro application are only served over HTTPS (TLS), and Hiro calls the Google and Microsoft APIs over TLS.
- Encryption at rest. The OAuth tokens that give access to a connected account are encrypted by the application with AES-256-GCM before they are stored, with a key kept outside the database; they are never sent to your browser. The database and file storage are encrypted at rest by our hosting providers.
- Hosting in the European Union. The application, its database and its files are hosted in Frankfurt, Germany (see "Sub-processors" below).
- Separation between customers. Every request is tied to a signed-in user and limited to that user's workspace; one customer can never see another customer's data. Within a workspace, data from your connected account follows the visibility described in section 3.
- Least privilege. We only request the permissions a feature needs, only when you turn that feature on, and you can turn each one off again (section 3). Access by Operanex staff is limited to the people who run the service, is only used for support you ask for, security or abuse investigations, or legal obligations, and is logged.
- Logging and monitoring. Requests to the application are logged with the user who made them, and key actions are recorded in an activity log, so that unusual access can be detected and investigated.
- Deletion. Tokens are deleted as soon as you disconnect an account, and we revoke our access with Google or Microsoft at the same time (see section 7 for how long other data is kept).
- Incidents. If a personal data breach occurs, we notify the competent supervisory authority and, where required, the people affected, as the GDPR requires.
9. Sub-processors
The following providers process data on our behalf when you use this website or the Hiro application. Providers marked "with consent" only receive data after you accept the matching cookie category.
- Amazon Web Services EMEA SARL — website hosting. Frankfurt, Germany (EU).
- Plausible Insights OÜ — cookieless audience measurement. Company in Estonia, servers in Germany (EU).
- PostHog Inc. (with analytics consent) — product analytics and session recordings. EU cloud hosted in Frankfurt, Germany (EU).
- Google Ireland Limited (with marketing consent) — Google Tag Manager and Google Ads conversion measurement. Ireland (EU); Google may transfer data to the United States under the EU-US Data Privacy Framework.
- Microsoft Ireland Operations Limited (with marketing consent) — Microsoft Advertising (UET tag) conversion measurement and retargeting. Ireland (EU), with possible transfers to the United States under the EU-US Data Privacy Framework.
- LinkedIn Ireland Unlimited Company and Meta Platforms Ireland Limited (with marketing consent) — conversion measurement and retargeting. Ireland (EU), with possible transfers to the United States under the EU-US Data Privacy Framework.
In addition, for the Hiro application:
- Amazon Web Services EMEA SARL — application hosting, file and email storage, and email delivery. Frankfurt, Germany (EU).
- Amazon Web Services EMEA SARL (Amazon Bedrock) — the AI features you choose to use, such as the assistant, CV extraction and imports. The models run inside AWS in the EU (Frankfurt, Germany); your data is not shared with the companies that publish the models and is not used to train them.
- Neon Inc. — managed database hosting, running on Amazon Web Services in Frankfurt, Germany (EU).
- Stripe Payments Europe, Ltd. — subscription billing. Ireland (EU).
- PostHog Inc. — product analytics in the application. EU cloud hosted in Frankfurt, Germany (EU).
- Google Ireland Limited (Google Maps Platform) — address autocomplete and geocoding when you enter an address. Ireland (EU); Google may transfer data to the United States under the EU-US Data Privacy Framework.
- OpenStreetMap Foundation — map tiles shown in the map view, which receives your IP address when the map loads. United Kingdom, covered by an EU adequacy decision.
- Meta Platforms Ireland Limited — only if you connect a WhatsApp Business or Meta Ads account: sending WhatsApp messages, publishing your job ads and reporting their conversions. Ireland (EU), with possible transfers to the United States under the EU-US Data Privacy Framework.
10. Contact
For any questions about this privacy policy or to exercise your data rights, please contact us at privacy@hiro.ninja.