This document is published in English only.
The English version is the sole legally binding version of this Privacy Policy.
1.1. Rekruto is operated by Pavel Kravets, operating under the Régimen Simplificado de Confianza (RESICO) tax regime in Mexico.
| Detail | Information |
|---|---|
| Operator | Pavel Kravets |
| Tax ID (RFC) | Available upon request at legal@rekruto.org |
| Country | México |
| Jurisdiction | State of Quintana Roo, México |
| Privacy contact | privacy@rekruto.org |
1.2. For the purposes of the EU General Data Protection Regulation (GDPR), Rekruto acts as a Data Processor with respect to candidate data (processing on behalf of recruiters who are the Data Controllers). With respect to recruiter account data, Rekruto acts as a Data Controller.
1.3. For the purposes of the Mexican Federal Law on Protection of Personal Data (LFPDPPP), Rekruto is the Responsable for recruiter data and Encargado for candidate data processed on behalf of the recruiter.
| Data Category | Specific Data | How Collected |
|---|---|---|
| Registration data | Full name, email address, organization name | Provided by you at registration |
| Payment processing | Subscription plan, billing cycle, invoice history. Rekruto does not collect, process, or store payment card data. All payment transactions are handled directly by Stripe, Inc. as an independent data controller for payment data. Card details are entered exclusively in Stripe's PCI DSS-certified interface and never reach Rekruto's servers. | Subscription metadata from Stripe API (no card data) |
| Team member data | Name, email, and role of team members invited to your organization (multi-seat plans) | Provided by the account owner or the invited team member |
| Google Calendar data (optional) | If you connect your Google Calendar: free/busy status of the calendars you select (no event titles, descriptions, attendees, or other event content), and events created by Rekruto in a dedicated "Rekruto Interviews" calendar within your Google account. OAuth tokens are stored encrypted at the application level. | Via Google OAuth, only after your explicit authorization. Disconnect anytime in Settings or via your Google Account security page |
| Account activity | Login timestamps, IP addresses, user agent, feature usage | Collected automatically |
| Support communications | Email correspondence, support tickets | When you contact us |
| Data Category | Specific Data | How Collected |
|---|---|---|
| Identity & contact | Name, email, phone, postal address | Submitted by candidates via application forms created by the recruiter |
| Professional data | CV/resume content: education, work history, skills, certifications, languages | Uploaded by candidates or by the recruiter |
| Other CV content | Where a candidate has included them in their CV, the extraction tools may also record fields such as date of birth, gender, nationality, citizenship and marital status. Each of these is recorded only where the candidate has stated it in the document; none of them is inferred. Whether they are extracted at all is controlled by the recruiter in organization settings. | Extracted from the CV supplied by the candidate or the recruiter |
| Application data | Application form responses, cover letters, portfolio links | Submitted by candidates |
| Interview scheduling | Selected interview slot, timezone, language preference, and contact details submitted when booking an interview via a scheduling link | Submitted by candidates via public booking pages |
| Sharing with interview participants | Where you schedule an interview and choose to attach them, the candidate's files — including the CV — are sent by email to the participants you invite, who may be outside your organization | Sent on your instruction when you schedule the interview |
| Candidate notifications | Delivery records and content of notification emails (e.g., application status or rejection notices) | Generated when the recruiter instructs the platform to send a notification |
| Consent records | Consent type (primary/extended), timestamp, IP, user agent, geo-country, consent template version | Recorded automatically upon consent |
Important: Rekruto processes candidate data on behalf of the recruiter (Data Controller). We do not determine the purposes or means of processing candidate data. The recruiter is responsible for the lawfulness of data collection and for providing candidates with appropriate privacy notices.
| Data Category | Specific Data | How Collected |
|---|---|---|
| Identity | Nickname or name, email (if provided by recruiter) | Provided by the recruiter when inviting reviewers |
| Activity | IP address, comments, feedback on candidates | Collected when hiring managers interact with shared links |
| Data | Purpose | Legal Basis |
|---|---|---|
| IP address | Security, fraud prevention, geolocation (country-level). Geolocation is resolved locally on our servers using an on-premise GeoLite2 database — IP addresses are not disclosed to any third party for this purpose | Legitimate interest |
| User agent (browser, OS) | Service compatibility, debugging | Legitimate interest |
| Cookies (session, auth) | Authentication, session management | Strictly necessary (no consent required) |
| Bot-protection token (Cloudflare Turnstile) | Abuse and bot prevention on registration and public booking pages | Legitimate interest |
If you use the client management features, you may record details of individuals who represent your clients and counterparties: name, business email, phone, messaging and professional-network handles, job title and functional role.
This data reaches the Service in one of two ways: you enter it directly, or you accept it from a document you have uploaded, where our extraction tools have identified it. Nothing is recorded without your action.
Rekruto processes this data solely on your instruction and does not contact these individuals. Any communication addressed to them is sent by you, from your organization's identity. You are the Controller for this data.
The Service allows you to upload documents relating to your clients and to record commercial and billing details. This covers the documents you choose to upload and their contents, including details of your own and your counterparties' legal entities — registered names, addresses, tax and registration numbers and bank details — commercial terms, and details of individuals named in those documents.
Where you request it, an uploaded document may be sent in full to the AI sub-processors listed in Section 6 for text recognition and extraction of structured fields. You decide which documents to upload and which extracted values to keep.
The Service offers an optional browser extension that lets you save a professional profile you are viewing into your candidate database. Where you use it, we record the professional information visible on that page — name, headline, location, the profile summary the person has written about themselves, work history, education and skills — together with the source address and the time of capture.
Rekruto does not decide on what basis you may do this, does not record a basis on your behalf, and does not contact these candidates. Where the law that applies to you or to the candidate requires you to inform a person whose data you obtained from another source, that obligation is yours.
| Purpose | Data Used | Legal Basis (GDPR) | Legal Basis (LFPDPPP) |
|---|---|---|---|
| Provide the Service | Registration data, candidate data (as Processor) | Contract performance (Art. 6(1)(b)) | Contractual relationship (Art. 10, 12) |
| Billing and payments | Subscription metadata (plan, cycle, invoices). Card data processed exclusively by Stripe as independent controller | Contract performance (Art. 6(1)(b)) | Contractual relationship |
| Technical support | Account data, support communications | Contract performance / Legitimate interest (Art. 6(1)(f)) | Contractual relationship |
| Security and fraud prevention | IP, user agent, authentication logs | Legitimate interest (Art. 6(1)(f)) | Legitimate interest |
| AI-assisted data extraction | CV/resume content, job descriptions, and documents you upload under Section 2.6 | Contract performance (recruiter's instruction as Controller) | Contractual relationship (Encargado acting on instructions) |
| AI-assisted drafting (interview kits, pre-screening questions, outreach and notification email drafts) | CV/resume and vacancy content | Contract performance (recruiter's instruction as Controller) | Contractual relationship (Encargado acting on instructions) |
| Candidate notifications and interview scheduling (on the recruiter's instruction) | Candidate contact details, booking data, notification content | Contract performance (recruiter's instruction as Controller) | Contractual relationship (Encargado acting on instructions) |
| Legal compliance | Invoices, consent logs, security logs | Legal obligation (Art. 6(1)(c)) | Legal obligation (CFF Art. 30) |
3.2. We do not use your data for: advertising, selling to third parties, training AI models, or any purpose not listed above. Rekruto itself does not subject you or candidates to automated decision-making with legal or similarly significant effects. The Service includes optional, recruiter-configured matching and filtering tools (see Section 5.3); these operate exclusively under the recruiter's control, and the recruiter (as Data Controller) decides whether and how to use them.
3.3. Data Verification. We do not independently verify personal data provided by users. As a Data Processor, we rely on you (the Data Controller) to ensure the accuracy, completeness, and lawfulness of all personal data you collect and input into the Service. You are solely responsible for verifying that you have a valid legal basis for processing all candidate data.
We rely on the following legal bases depending on the category of data and the purpose of processing:
5.1. Rekruto uses AI (large language models) solely to assist recruiters with:
5.2. AI is not used for:
5.3. Deterministic matching tools (not AI). The Service includes optional rule-based tools — a match indicator and knockout filters — that compare structured candidate fields against vacancy requirements using only criteria explicitly configured by the recruiter. These tools are deterministic: they involve no machine learning and no inference, their criteria are fully transparent to the recruiter, and they never exclude a candidate on the basis of incomplete data (a missing field means the rule is skipped, never failed). Their output is advisory only and never triggers any automatic action toward a candidate. The recruiter (Data Controller) decides whether and how to use these tools and is solely responsible for the lawfulness of the configured criteria and of any decisions made with their help, including compliance with GDPR Art. 22 and any applicable automated employment decision regulations.
5.4. AI processing is performed by the third-party providers listed in Section 6. Depending on the feature you use, the content sent to them may include CV and application content, job descriptions, and documents you upload under Section 2.6, which may be sent in full.
Which provider performs which task may change within the list in Section 6; adding a provider to that list follows the sub-processor notification procedure in the DPA. Our providers do not use this content to train their models. Retention is set out in Section 8.
5.5. All AI outputs (extracted data and generated drafts) are provisional and may contain errors. Human review by the recruiter is required before relying on or sending any AI output.
5.6. AI Act Classification. Rekruto's AI functionality is limited to data extraction, structuring, and drafting assistance under full human control. The Service does not use AI for candidate scoring, ranking, profiling, automated decision-making, or any decisions with legal or similarly significant effects on individuals. Based on this scope, the AI processing performed by Rekruto is classified as minimal risk under the EU AI Act (Regulation (EU) 2024/1689). The deterministic matching tools described in Section 5.3 operate on rules defined solely by the recruiter, without machine learning or inference, and therefore do not constitute AI systems within the meaning of the EU AI Act (cf. Recital 12). If the recruiter combines Rekruto data or outputs with any external AI or automated decision system, the recruiter is solely responsible for the regulatory classification and compliance of that downstream use. All AI outputs are provisional and require human review by the recruiter before any action is taken.
We use the following third-party service providers (sub-processors) to operate the Service:
| Sub-processor | Purpose | Location | Data Processed |
|---|---|---|---|
| Supabase | Database, auth, storage | EU (Frankfurt) | All platform data |
| OpenAI | AI text recognition and extraction from CVs, job descriptions and uploaded documents | USA | CV content, job descriptions, uploaded documents |
| Anthropic | AI-assisted extraction and drafting | USA | CV content, job descriptions |
| Mistral | AI text recognition and extraction from CVs, job descriptions and uploaded documents | EU (France) | CV content, job descriptions, uploaded documents |
| Stripe | Payment processing (independent controller for card data) | USA | Card data collected directly by Stripe — never passes through Rekruto. Rekruto receives only subscription metadata (plan, status, invoice IDs) |
| Resend | Email delivery (platform notifications and candidate-facing emails sent on the recruiter's instruction) | USA | Email addresses, notification content |
| Cloudflare | CDN, security, bot protection (Turnstile) | Global | IP, request metadata |
| Google LLC | Calendar integration (optional, per-user opt-in); website analytics on our public and registration pages | USA / Global | Calendar: free/busy status of selected calendars and interview events created by Rekruto. Analytics: IP address and page interaction data, collected only where you have accepted analytics cookies |
We require all sub-processors to maintain appropriate data protection standards. Changes to sub-processors are communicated in accordance with the DPA (Annex A of the Beta Terms of Service).
Rekruto's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically: we access only the free/busy status of the calendars you select and a Rekruto-created calendar; we use this data solely to display your availability and to create the interview events you schedule; we do not transfer Google user data to third parties except as necessary to provide this feature, comply with applicable law, or as part of a merger or acquisition with prior notice; we do not use Google user data for advertising; and we do not allow humans to read this data unless you give explicit permission, it is necessary for security or legal compliance, or the data is aggregated and anonymized. Free/busy responses are not stored in our database (short-lived cache only).
7.1. Rekruto's primary data storage is located in the European Union (Supabase, Frankfurt, Germany).
7.2. Data may be transferred to the following locations for specific purposes:
| Destination | Purpose | Transfer Mechanism |
|---|---|---|
| USA (OpenAI, Anthropic) | AI processing | SCCs / EU-US DPF |
| USA (Stripe) | Payment processing | SCCs / EU-US DPF |
| USA (Resend) | Email delivery | SCCs |
| Global (Cloudflare) | CDN, security | SCCs |
| USA (Google) | Optional calendar integration; website analytics (subject to your cookie consent) | SCCs / EU-US DPF |
7.3. For Mexican data subjects: Transfer of your personal data outside of Mexico requires your explicit consent under LFPDPPP Article 36. This consent is obtained separately through the Cross-Border Data Transfer Consent at registration. Without this consent, use of the Service is not possible, as data is physically stored in the EU.
7.4. For international transfers we rely on appropriate safeguards, including Standard Contractual Clauses (SCCs) with our sub-processors, as required by GDPR Chapter V.
Retention periods for candidate data are set by the recruiter (Data Controller) in their consent templates, measured in months. We do not determine retention periods for candidate data, and we do not enforce them: expiry of a retention period does not, by itself, remove a candidate from the Service. The consent log shows which consents have passed their retention period, so that the recruiter can act on them.
Once the recruiter deletes or blocks a candidate, the removal continues on its own in two phases: a block phase, lasting until the end date the recruiter sets (30 days by default), during which the data is excluded from active use and the action is reversible; and then irreversible in-place anonymization — all fields identifying the candidate are permanently removed. The retained record contains only anonymized, non-identifying data, which is no longer personal data.
| Data Category | Retention Period | Legal Basis |
|---|---|---|
| Account data (recruiter) | Active account + 30 days after deletion | Contract performance |
| Inactive trial accounts (no subscription) | 30 days after trial ends + 14-day final notice before deletion | Terms of Service §7.7 |
| Inactive lapsed paid accounts | 6 months of inactivity after subscription ends + 14-day final notice before deletion | Terms of Service §7.7 |
| Our invoices to you (subscription billing) | 5 years after tax declaration | CFF Art. 30 (fiscal records) |
| Payment card data | Never collected or stored by Rekruto. Processed exclusively by Stripe as independent controller | N/A — outside Rekruto's scope |
| Client records, contact persons and counterparties | For as long as you keep them. Deleting a client starts a 30-day recovery window, after which the client record itself is anonymized; contact persons and counterparty records are kept until you delete them | Contract performance |
| Uploaded documents and their analysis results | For as long as you keep them. Deleting a document starts a 30-day recovery window, after which the file and its analysis are deleted | Contract performance |
| Invoices you issue to your clients | For as long as you keep them; we do not delete them automatically. Retaining them for tax or accounting purposes is your responsibility | Contract performance |
| Platform consent logs (ToS, PP acceptance) | 5 years after account deletion | Código de Comercio Art. 1043 |
| Document versions (ToS, PP, DPA) | Permanent | Accountability (GDPR Art. 5(2)) |
| Candidate consent logs | 3 years after hard delete, with the candidate identifier removed | Audit trail, GDPR Art. 7(1) |
| Authentication and security logs (sign-in attempts, step-up verification, security events) | While the account is active and for as long as needed to investigate account security and abuse | Security (legitimate interest) |
| Platform audit log (actions performed in the Service) | While the account is active | Security, accountability (legitimate interest) |
| Access logs for public pages (IP, approximate location, user agent) | Blocked attempts: 12 months. Other access records, where enabled: 90 days | Security (legitimate interest) |
| Records of a security incident | For as long as needed to investigate, remediate and account for the incident | Legal compliance, evidence |
| Support correspondence | For as long as needed to handle your request and any follow-up | Service quality |
| Legal correspondence | 5 years | Código de Comercio Art. 1043 |
| Google OAuth tokens | Until you disconnect the integration or delete your account, whichever comes first; revoked tokens are deleted immediately | Contract performance |
| Browser extension sessions | Until revoked or expired | Contract performance |
| AI usage records (provider, time, volume — used for quotas and billing analytics) | While the account is active | Contract performance, legitimate interest |
Certain data must be retained regardless of your deletion request due to legal obligations:
If you are located in the EU/EEA, you have the following rights:
Response time: within 30 days of receiving your request.
If you are located in Mexico, you have the following rights (derechos ARCO):
Response time: within 20 business days of receiving your request (LFPDPPP Art. 32).
Contact us at privacy@rekruto.org with your request. Please include:
We may request identity verification before processing your request.
Recruiters can exercise access and portability for candidate, vacancy and consent data at any time without contacting us, using the self-service Data Export. For data outside that scope, write to privacy@rekruto.org; we will assist as set out in Annex A of the Terms.
Important: If you are a job candidate, a contact person recorded by one of our customers, or anyone else whose data is processed through Rekruto on a customer's behalf, your primary point of contact for exercising your data rights (access, rectification, erasure, portability, restriction, objection) is the organization that collected your data (the Data Controller). Rekruto acts as a Data Processor and does not have a direct relationship with these individuals. The Data Controller is responsible for responding to your requests using the self-service tools provided by the platform. If you are unable to reach the Data Controller, you may contact us at privacy@rekruto.org and we will redirect your request to the appropriate Data Controller.
9.5.1. California Residents (CCPA/CPRA). If you are a California resident, you have the following additional rights under the California Consumer Privacy Act (Cal. Civ. Code §1798.100 et seq.), as amended by the California Privacy Rights Act:
To exercise your California rights, contact us at privacy@rekruto.org. We will respond within 45 days of receiving a verifiable request. You may designate an authorized agent to make a request on your behalf.
9.5.2. Brazilian Residents (LGPD). If you are a resident of Brazil, you have the following rights under the Lei Geral de Proteção de Dados (Law No. 13.709/2018):
To exercise your LGPD rights, contact us at privacy@rekruto.org. We will respond within 15 days of receiving your request.
Rekruto does not sell your personal information. We do not sell, rent, or trade personal information to third parties for monetary or other valuable consideration, as defined under the CCPA/CPRA (Cal. Civ. Code §1798.140(ad)).
Rekruto does not share your personal information for cross-context behavioral advertising. We do not share personal information with third parties for the purpose of cross-context behavioral advertising as defined under the CPRA (Cal. Civ. Code §1798.140(ah)).
We only disclose personal information to our service providers and sub-processors for the business purposes described in this Privacy Policy and the Beta Terms of Service.
| Cookie / Technology | Type | Purpose | Consent Required |
|---|---|---|---|
| Session cookie | Strictly necessary | Authentication, session management | No |
| Auth token (JWT) | Strictly necessary | User authentication | No |
| Trusted-device cookie | Strictly necessary | Remembering a device you have confirmed, so that additional verification is not requested on every sign-in. Expires after the period set for your organization (30 days by default) | No |
| Language preference | Strictly necessary | Showing pages in the language you selected | No |
| Bot protection (Cloudflare Turnstile) | Strictly necessary | Abuse prevention on registration and public pages | No |
| Google Analytics (_ga) | Analytics | Measuring how our public and registration pages are used. Set only if you accept analytics cookies | Yes |
We do not use advertising cookies, social media tracking pixels, or third-party marketing trackers.
You may also disable cookies in your browser settings, although this may affect Service functionality.
We implement appropriate technical and organizational measures to protect your data, including:
While we strive to protect your data, no method of electronic storage or transmission is 100% secure. We cannot guarantee absolute security, especially during the Beta period.
12.1. We may update this Privacy Policy from time to time to reflect changes in our practices, the Service, or applicable law.
12.2. When we publish a material change, we notify you by email to the address associated with your account and by an in-app notice on your next sign-in. The updated version applies from the date it is published, which is shown on the document.
12.3. Your continued use of the Service after the updated Privacy Policy takes effect constitutes your acceptance of the changes. If you do not agree, you should stop using the Service and delete your account.
12.4. The effective date and version number displayed on this document are managed by the platform and always reflect the most recent published version.
| Purpose | Contact |
|---|---|
| Data protection, DSAR/ARCO requests, consent | privacy@rekruto.org |
| Legal inquiries, disputes | legal@rekruto.org |
| Abuse reports, platform misuse | abuse@rekruto.org |
| Technical support, account, billing | support@rekruto.org |
| General inquiries, partnerships | hello@rekruto.org |
If you believe we have not adequately addressed your data protection concerns, you have the right to lodge a complaint with a supervisory authority: