Privacy Policy

    Last updated: 2026-10-05

    We explain what data we collect, how we use it, and your rights.

    Data we collect

    Account information (name, email, company), platform usage and diagnostics, the CV and contact details you upload as a candidate or recruiter, and the content a recruiter chooses to publish on their public portfolio.

    How we use data

    To provide and improve the service, communicate updates and ensure security.

    CVs and AI processing

    Candidate CVs in a search

    When you apply to a recruiter's search or join their talent base, the file is stored in Hilancer with access limited to that recruiter, their team, and you. We process the CV's text with the Google Gemini API to prefill the application form and your candidate record. We use Gemini on a paid plan whose terms don't allow Google to use that content to train its models, and Hilancer doesn't use your CV to train its own models either.

    Recruiter portfolio

    A recruiter can build a public page from their own CV. If they do it from the public form without an account, the CV is read in their browser and only the text — with emails and phone numbers removed — is sent to Gemini to draft the page; the file never leaves their device and is never stored by Hilancer. If they upload the CV from inside the app, the file is sent to Gemini to draft the page and then discarded: it is not stored. The draft is only saved when the recruiter saves or publishes it.

    Public page

    Everything shown on a portfolio is published voluntarily by the recruiter and is public: it can be indexed by search engines and shared freely. The recruiter can unpublish it at any time from the app, and their email and phone number are never shown. Visitors can write to the recruiter through a contact form: the message, along with the sender's name, email and company, is emailed to the recruiter, and Hilancer only keeps delivery logs. The form uses Cloudflare Turnstile to block bots; for that, Cloudflare may process the visitor's IP address and browser signals.

    Your rights

    You can access, correct or request deletion of your data, subject to legal requirements.

    Sending data to AI assistants connected by the recruiter (MCP)

    If a recruiter connects a third-party AI Assistant (for example, Anthropic's Claude) to their account through our MCP integration, the data that recruiter can see on the platform — including candidates' personal data, such as name, email, phone number, CV-derived information, recruitment process notes, and application status — may be transmitted to that AI Assistant's provider so it can answer the recruiter's questions or carry out the actions the recruiter asks of it.

    Under the recruiter's own account

    This transmission only happens when the recruiter themselves activates the integration, at their instruction, and only within the scope of what that recruiter can already see and do in Hilancer. It takes place under the recruiter's own account and responsibility with the AI Assistant's provider: Hilancer does not sell this data and does not send it on its own initiative, it acts as the data's originating platform but does not control what that provider does with the information once received. This transmission is subject to the AI Assistant provider's own privacy policy.

    Recruiter responsibility over their candidates' data

    As the controller of their candidates' data, the recruiter is responsible for having an appropriate legal basis for that data to be accessed through an AI Assistant they choose to connect. If you applied to a position or left your CV in the database of a recruiter using this integration, your data may have been accessed this way; you can exercise your rights of access, rectification, or deletion in the usual way described in this policy.

    Activity log and revocation

    We keep a technical log of every query and action executed through this integration (user, connected application, tool used, affected resource when it is an action, outcome, duration, and date), without the content of the data queried or of the responses, for audit, security, and service-improvement purposes. The recruiter can revoke the AI Assistant's access at any time from Settings → Integrations, or by removing the connection from the AI Assistant itself.

    Google integrations

    What we access

    When you connect your Google account, Hilancer accesses your calendar to check your availability (busy/free time slots) and to create interview events on your calendar. We request only the minimum scopes needed for this: reading free/busy information and creating or editing events.

    What we do not do

    We do not read the content or details of your existing events, and we do not copy or store your calendar on our servers.

    How we store this data

    We only store your Google access tokens, encrypted at rest and transmitted over encrypted connections (TLS). We do not share Google user data with third parties, except infrastructure providers strictly necessary to operate the service.

    Google Sign-In and Google Drive

    Hilancer also offers Google Sign-In (openid, email, profile), used exclusively to authenticate you and create your account, and a Google Drive picker using the narrow drive.file scope: Hilancer can only access the specific files you explicitly select (for example, a CV or a contact spreadsheet you choose to import) and never browses any other content in your Drive.

    Artificial intelligence and Google user data

    Hilancer's AI features are powered exclusively by the Google Gemini API (a third-party AI service operated by Google). We do not use any other AI provider. Google Calendar and Google Sign-In data are never transmitted to any AI or machine-learning model. The only Google-API data ever processed by AI are the files you explicitly select in the Google Drive picker, solely to fulfill the import you requested, under API terms that prohibit the use of your data to train AI models. No data obtained through Google APIs is ever used — by Hilancer or by any provider on our behalf — to develop, improve, or train generalized AI or machine-learning models. The use and transfer of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

    Limited Use

    Hilancer's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

    Read the Google API Services User Data Policy

    How to revoke access

    You can disconnect your Google account from within Hilancer at any time, or revoke access directly from your Google account settings.

    Manage your Google account permissions

    Security

    We apply reasonable technical and organizational measures to protect your information.

    Providers

    We use the following providers to operate Hilancer, each processing data on our behalf and under their own terms:

    • Supabase: database, file storage (such as CVs) and authentication.
    • Google: Gemini API for AI features, and Google Sign-In, Calendar and Drive when you choose to connect them.
    • Cloudflare: platform hosting and bot protection (Turnstile) on public forms.
    • Resend: delivery of the platform's transactional emails (confirmations, notifications, invitations).