Legal
Privacy Policy
Erika Platform · the control shift company s.r.o.
This Privacy Policy explains how the control shift company s.r.o., with its registered seat at Italská 2581/67, Vinohrady, 120 00 Praha 2, Czech Republic, Identification No. (IČO) 29997992, registered with the Municipal Court in Prague (Městský soud v Praze) under file No. C 455609 (the “Company”, “Control Shift”, “we”, “us”), Processes Personal Data in connection with the Erika applicant tracking and recruitment platform (the “Platform”), our website, and related services.
1. Who We Are and Our Roles
1.1 Control Shift provides the Erika Platform to employers and recruiters (our “Customers”) to help them source, attract, screen, and manage job candidates.
1.2 Our role under the GDPR depends on the data in question:
- Controller — for Personal Data we determine the purposes and means of, such as the data of our Customers’ account administrators and users, website visitors, prospects, billing contacts, and support requesters.
- Processor — for Personal Data of job candidates and other recruitment data that our Customers upload to or generate within the Platform. Here, the Customer (employer) is the Controller and we Process such data only on the Customer’s instructions, governed by a Data Processing Agreement (DPA). See Section 5.
1.3 Where this policy refers to data for which we are Processor, the Customer’s own privacy notice to candidates governs the lawful basis and primary information obligations; this policy and the DPA describe how we handle that data on the Customer’s behalf.
1.4 Erika AI Job Assistant (talent network). Separately, we operate a free AI assistant that helps job-seekers find work and, with their consent, keeps their profile and lets them apply to employers with matching roles. For that activity we act as Controller, and the candidate-facing Erika — Terms of Use & Privacy Notice for Candidates sets out the details, the consents, and the candidate’s rights. Candidates who apply to an employer are received by that employer as an independent Controller.
2. Scope of This Policy
2.1 This policy applies to the Platform, our website, and related communications. It does not apply to third-party websites or services we link to, which have their own privacy policies.
2.2 The candidate-facing WhatsApp/messaging experience is described in the Erika — Terms of Use & Privacy Notice for Candidates (including its WhatsApp messaging addendum); this policy covers AI voice screening conducted by telephone as part of the Platform.
3. Personal Data We Process
3.1 Customer account and user data (we are Controller). Name, business email, phone, job title, organisation, role/permissions, authentication identifiers, preferences, and login/usage metadata.
3.2 Billing data (we are Controller). Billing contact details, plan and credit history, invoices, and transaction metadata. Card data is handled by our payment processor; we do not store full card numbers.
3.3 Support and communications (we are Controller). Correspondence, support tickets, and related content.
3.4 Website and product usage (we are Controller). Device and browser data, IP address, pages viewed, in-product events, and (where enabled) session-replay data, collected via analytics tools (see Sections 7 and 8).
3.5 Candidate and recruitment data (we are Processor). Data our Customers upload or generate about candidates — e.g. name, contact details, CVs and attachments, application and pipeline status, notes, ratings, tags, consent records, voice-screening recordings/transcripts, and AI-generated summaries. The categories are determined by the Customer as Controller. See Section 5.
3.6 Special category data. We do not seek special category data (Article 9 GDPR). Customers are instructed not to upload such data except where strictly necessary, lawful, and configured for that purpose; they remain responsible for its lawful Processing.
4. Purposes and Legal Bases (Where We Are Controller)
| Purpose | Personal Data | Legal basis |
|---|---|---|
| Providing and administering accounts and the Platform | Account and user data | Performance of a contract (Art. 6(1)(b)); legitimate interests (Art. 6(1)(f)) |
| Billing, payments, and accounting | Billing data | Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) |
| Support and service communications | Support and communications data | Contract; legitimate interests (Art. 6(1)(f)) |
| Security, fraud prevention, abuse detection | Usage and account data | Legitimate interests; legal obligation |
| Product analytics and improvement | Usage data (where possible, aggregated/de-identified) | Legitimate interests; consent for non-essential cookies (Art. 6(1)(a)) |
| Marketing to business prospects/customers | Contact data | Consent and/or legitimate interests, subject to opt-out |
| Compliance with legal obligations and defence of claims | As relevant | Legal obligation; legitimate interests |
4.1 Where we rely on legitimate interests, we balance those interests against your rights and freedoms; you may object as described in Section 12. Where we rely on consent, you may withdraw it at any time without affecting prior Processing.
5. Candidate Data — Control Shift as Processor
5.1 For candidate and recruitment data, the Customer (employer) is the Controller and determines the purposes, legal bases, retention, and notices. Control Shift acts as Processor and Processes such data only on the Customer’s documented instructions to provide the Platform, in accordance with a DPA that meets Article 28 GDPR.
5.2 If you are a candidate and wish to exercise your rights or have questions about how your data is used in a recruitment process, please contact the relevant employer (Controller) directly. We will assist that employer in responding to your request as required by the DPA.
5.3 The Platform provides Controllers with tooling for consent management, configurable retention, anonymisation, erasure, and data export to support their GDPR obligations. Configuration and use of these tools are the Controller’s responsibility.
5.4 We engage the Subprocessors listed in Section 16 to Process candidate data on the Customer’s behalf, under the conditions in Section 8.
6. AI Features and Automated Processing
6.1 The Platform includes AI features (e.g. an AI assistant and agents, AI sourcing and creative generation of images and videos, candidate summaries, and AI voice screening). These features use the AI Subprocessors listed in Section 16.
6.2 No solely automated decisions with legal/significant effect by us. We do not use AI to make decisions producing legal or similarly significant effects on candidates. The Platform generates outputs (e.g. summaries, suggestions); all hiring decisions are made by the Customer with meaningful human involvement. Responsibilities relating to Article 22 GDPR and the EU AI Act rest with the Customer as Controller and deployer.
6.3 Model training. We do not use candidate Personal Data or other Customer Personal Data to train generally-available AI models for third parties. Our AI Subprocessors are engaged under terms that, where offered, exclude use of submitted data to train their general models; details are summarised in the DPA.
6.4 AI Output may be inaccurate or incomplete; it is provided to assist, not replace, human judgement.
7. Cookies and Analytics
7.1 We use strictly necessary cookies to operate the Platform (e.g. authentication and security) and, subject to consent where required, analytics and session-replay technologies to understand and improve usage.
7.2 You can manage non-essential cookies via our cookie banner/settings and your browser controls. Further detail is provided in the cookie settings available via the cookie banner on our website.
8. Sharing and Subprocessors
8.1 We share Personal Data only as needed to provide the Services and as described here: with Subprocessors (Section 16) under written contracts imposing GDPR-compliant obligations; with professional advisers, auditors, and authorities where required by law; and in connection with a merger, acquisition, or reorganisation, subject to this policy.
8.2 We do not sell Personal Data.
8.3 Each Subprocessor is bound by data-protection terms no less protective than those required by Article 28 GDPR. We remain responsible for our Subprocessors’ Processing on our behalf. We give Customers notice of changes to candidate-data Subprocessors and an opportunity to object, as set out in the DPA.
9. International Transfers
9.1 We host the Platform’s primary infrastructure in the European Union. Some Subprocessors (notably certain AI model and communications providers) are located outside the European Economic Area (EEA), including in the United States.
9.2 Where Personal Data is transferred outside the EEA, we rely on an appropriate transfer mechanism under Chapter V GDPR, such as an adequacy decision, the EU–US Data Privacy Framework (where the recipient is certified), and/or the European Commission’s Standard Contractual Clauses (SCCs) together with supplementary measures as appropriate. The transfer mechanism applicable to each Subprocessor is indicated in Section 16 or available on request.
10. Retention
10.1 Where we are Controller, we retain Personal Data only as long as necessary for the purposes in Section 4, including: account data for the duration of the relationship plus a reasonable period thereafter; billing and accounting records for the period required by law (e.g. tax/accounting statutes in the Czech Republic); and support data for as long as needed to handle the matter and defend claims.
10.2 Where we are Processor, candidate data is retained according to the Customer’s configured retention policy and instructions, and is returned or deleted on termination as set out in the DPA, except where retention is required by law.
11. Security
11.1 We implement appropriate technical and organisational measures to protect Personal Data, including encryption in transit, access controls and least-privilege, tenant data isolation, authentication, logging and monitoring, and supplier due diligence. No system is completely secure; we work to continually improve our safeguards.
11.2 We will notify affected Controllers without undue delay after becoming aware of a Personal Data breach affecting their data, and will notify supervisory authorities and individuals where we are required to do so by law.
12. Your Rights
12.1 Subject to applicable law, you have the right to: access your Personal Data; rectification of inaccurate data; erasure (“right to be forgotten”); restriction of Processing; data portability; objection to Processing based on legitimate interests or direct marketing; and to withdraw consent at any time. You also have the right not to be subject to a decision based solely on automated Processing producing legal or similarly significant effects (Article 22 GDPR).
12.2 To exercise rights regarding data for which we are Controller, contact us using Section 15. To exercise rights regarding candidate/recruitment data, contact the relevant employer (Controller); we will assist them as Processor.
12.3 We respond within the timeframes required by the GDPR (generally one month, extendable as permitted). There is no fee unless your request is manifestly unfounded or excessive.
13. Children
13.1 The Platform is a business tool not directed to children and not intended for the Processing of children’s data. Customers must not use the Platform to Process data of individuals below the minimum working age in the relevant jurisdiction other than as lawfully permitted.
14. Changes to This Policy
14.1 We may update this policy from time to time. We will post the updated version with a new effective date and, for material changes, provide additional notice where appropriate.
15. Contact and Complaints
15.1 Controller / contact: the control shift company s.r.o., Italská 2581/67, Vinohrady, 120 00 Praha 2, Czech Republic, email support@erikawork.com.
15.2 Supervisory authority. If you are in the EEA, you may lodge a complaint with a supervisory authority, in particular the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.cz) or the authority in your country of residence or work.
16. Subprocessor List
16.1 The following table lists the Subprocessors we currently engage to provide the Platform. We keep it up to date; the version published here is the one in force.
| Subprocessor | Service / purpose | Data categories | Region | Transfer safeguard (if outside EEA) |
|---|---|---|---|---|
| Google Cloud Platform (Google Ireland Ltd / Google LLC) | Cloud hosting, compute, database, and file storage (primary infrastructure) | All Platform data | EU (europe-west1) | SCCs / DPF as applicable |
| Google Firebase (Google) | User authentication and sign-in, including Sign in with Google | Account/user identifiers, authentication data | EU / US | SCCs / DPF |
| Google Gemini API / Vertex AI (Google) | AI assistant and agents, AI processing of job and candidate data, AI video and image generation, analysis of generated videos | Prompts, chat content, relevant Customer Data and candidate data, generation inputs | EU / US / global | SCCs / DPF |
| Google Workspace APIs (Google) | Calendar, email, and Google Sheets features for users who connect their Google account (Section 17) | Calendar events, emails, candidate data the user chooses to send or export | EU / US | SCCs / DPF |
| Microsoft (Microsoft Ireland Operations Ltd) | Sign in with Microsoft; calendar and email features for users who connect their Microsoft account (Section 17) | Account identifiers, calendar events, emails | EU / US | SCCs / DPF |
| OpenAI | AI text processing (classification, translation, candidate qualification, screening review), AI image generation, and real-time voice for telephone screening | Prompts, job and candidate data, call audio, generation inputs | US | SCCs |
| Anthropic, PBC | AI web search, backup AI text processing, and AI tools our team uses to support Customers and check the quality of the service | Search queries, prompts, Customer Data relevant to the task | US | SCCs |
| OpenRouter, Inc. | Access to AI video generation models | Scripts, prompts, and generation inputs (e.g. reference images) | US | SCCs |
| ElevenLabs | Speech-to-text for video captions | Audio of generated videos | US | SCCs |
| Twilio (Twilio Ireland Ltd / Twilio Inc.) | Telephone lines, calls, and SMS for telephone screening | Phone numbers, call audio and metadata, SMS content | EU / US | SCCs / DPF |
| Meta Platforms (Meta Platforms Ireland Ltd) | Recruitment advertising, lead forms, and candidate messaging on Meta channels (Facebook, Instagram, Messenger, WhatsApp) | Campaign data; lead/application data; messages | EU / US | SCCs / DPF |
| TikTok | Recruitment advertising and conversion measurement | Campaign data; for applicants who arrive from a TikTok ad: hashed email and phone, IP address, browser data | EU / outside EEA | SCCs |
| Telegram | Recruitment advertising on Telegram and candidate messaging via Telegram | Campaign data; messages and Telegram identifiers of candidates who contact us there | EU / outside EEA | Art. 49(1)(b) GDPR (messaging the candidate chooses to start) |
| Stripe (Stripe Payments Europe Ltd / Stripe, Inc.) | Payment processing and billing | Billing contact and transaction data | EU / US | SCCs / DPF |
| Resend | Transactional, notification, and candidate email delivery, and inbound email handling | Email addresses and message content | US | SCCs |
| PostHog | Product analytics and session replay | Usage events, device/usage metadata | EU (EU ingest) | EU hosting |
16.2 A change to this list (addition or replacement of a candidate-data Subprocessor) is notified to Customers with an opportunity to object as set out in the DPA.
17. Connected Accounts (Google & Microsoft) and Google API Limited Use
17.1 What this feature does. A Customer user (recruiter) may optionally connect their own Google or Microsoft account so that Erika can, acting only on that user’s instruction and with a manual approval on anything that reaches a candidate, read their calendar availability, create and manage interview events (whereupon Google or Microsoft emails the invitation to the candidate), and send candidate emails from the user’s own mailbox. Connecting an account is optional, is done per user, and can be disconnected at any time (clause 17.8).
17.2 Access we request from Google, and why. We request only the minimum permissions needed for the features above. Google presents these as individual, per-permission checkboxes, so a user may grant some and decline others; Erika then enables only the features for which access was granted.
| Permission (OAuth scope) | Why Erika requests it |
|---|---|
openid, email, profile | Identify the connected Google account (its email address and basic profile) so the correct mailbox and calendar are used. |
calendar.freebusy | Read only your free/busy status to propose interview times. It does not reveal the details of your events. |
calendar.events.owned | Create and manage the interview events that Erika schedules on your behalf, including the video-meeting link; Google then emails the invitation to the candidate. |
gmail.send | Send the candidate emails you compose and approve, from your own address. This is a send-only permission: Erika cannot read, search, or delete messages in your mailbox. |
17.3 Microsoft equivalents. For a connected Microsoft account we request User.Read (identify the account), Calendars.ReadWrite (availability and interview events), and Mail.Send (send approved candidate emails). Microsoft’s Mail.Send is likewise send-only.
17.4 How we handle this data. Access and refresh tokens for a connected account are encrypted at rest and are used solely to perform the actions you initiate inside the Platform. Every action that reaches a candidate (an email or a calendar invitation) requires a manual approval by you; availability reads happen automatically only to propose times. So that the assistant can follow up on a candidate’s reply, outbound candidate emails may carry a Reply-To routing address operated by us; we do not otherwise access the contents of your mailbox. We do not use this access for advertising, and we do not sell this data.
17.5 Google API Services Limited Use. Erika’s use of information received from Google APIs, including Google Workspace APIs (Gmail and Google Calendar), complies with the Google API Services User Data Policy, including its Limited Use requirements:
Erika’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.
17.6 In particular, information obtained through Google Workspace APIs is used and transferred only to provide or improve the user-facing features described above; is not transferred to others except as necessary to provide those features, to comply with applicable law, or as part of a merger or acquisition; is not used for serving advertisements; and is not read by any human except with your explicit consent (for example when you request support), where necessary for security or to investigate abuse, or where required by law.
17.7 No AI or ML model training on Workspace data. We do not use data obtained through Google Workspace APIs (Gmail or Google Calendar) to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning (AI/ML) models. Where an AI feature acts on this data (for example, drafting an email that you then review and approve), it does so only to deliver the specific feature you requested, and under provider terms that exclude the training of their general models on submitted data.
17.8 Disconnecting and revoking access. You can disconnect a linked account at any time in the Platform (Settings, then Connected accounts). You can also revoke Erika’s access directly from your Google Account permissions page, or, for Microsoft, from your Microsoft account. On disconnection or revocation we stop using the account and delete the stored access and refresh tokens; interview events already created and emails already sent remain in your own Google or Microsoft account and in the recipients’ mailboxes.