Privacy Policy
This policy explains how {{OWNER_LEGAL_ENTITY}} handles personal data when people visit its websites, start a trial, subscribe to its services, or have their data processed through the platform by a customer. It sets out the two roles the company plays, the legal bases it relies on, how long data is kept, how it is shared and transferred, and how to exercise data rights or complain.
Who this policy covers and which version applies
The policy applies to visitors to the company websites, free-trial sign-ups, subscribers, and anyone whose personal data is processed through the platform. It states that personal data is never sold to third parties and that processing follows the EU GDPR, UK GDPR, Swiss nFADP, CCPA/CPRA and other applicable data protection laws.
The current edition is Version {{OWNER_POLICY_VERSION}}, described as the {{OWNER_POLICY_EDITION}} Edition and aligned with the Data Privacy Framework. The last-updated date shown is {{OWNER_POLICY_LAST_UPDATED}}. The policy says material changes are announced by email and by a prominent website notice at least {{OWNER_AMENDMENT_NOTICE_PERIOD}} before they take effect, consistent with the amendment process in the Data Processing Agreement (Section 12.5). Questions and rights requests go to {{OWNER_SUPPORT_EMAIL}}.
Data Privacy Framework adherence
{{OWNER_DPF_CERTIFICATION_STATUS}}
Where this policy conflicts with the DPF Principles, the Principles govern. Current listing status can be checked at the official Data Privacy Framework site. The company's DPF commitments are subject to the investigatory and enforcement powers of the U.S. Federal Trade Commission. The policy notes that the DPF self-certification does not currently cover human resources data.
Controller and processor: which role applies to you
The company acts in two capacities, and the distinction decides who a person should contact.
As a data controller, it collects and processes data directly from website visitors, prospective customers, trial users and its own subscribers for marketing, account management and service delivery. It determines the purposes and means of that processing and is directly responsible to those individuals.
As a data processor, it handles personal data that customers (who are controllers) upload, import or otherwise submit about their candidates, contacts and clients. That processing follows the customer's instructions under the Data Processing Agreement. Customers are responsible for having a lawful basis to submit the data.
If you are a candidate, contact or end-customer whose data was uploaded by a recruitment agency or employer, that organisation is your controller. Contact it directly to exercise your rights; the company says it will assist customers in responding as required by law.
What data is collected and why
Data provided directly includes contact details (name, email, phone, mailing address), business details (company name, size, industry, job title), account credentials with passwords stored in hashed form, billing details processed through PCI-DSS compliant payment processors, communications such as emails, support tickets, feedback, survey responses and testimonials, and professional profile information such as employment history and qualifications where provided.
Data collected automatically includes device data (device type, operating system, browser, device identifier), log data (IP address, access timestamps, pages visited, referring URLs, clickstream), usage data (features accessed, session duration, interactions), location data (approximate from IP; precise only with device-level consent for mobile apps), and cookie and tracking data.
Customers may upload candidate and contact data including CVs, employment history, contact details, qualifications, and AI-processed outputs such as call summaries, transcripts and candidate assessments. That data is processed strictly on the customer's instructions.
Lawful bases for processing
Under GDPR, each processing activity needs a documented lawful basis. The table below sets out the basis for each purpose where the company acts as controller, plus the processor-role and AI-feature rows. Where legitimate interests are relied on, the company says it has documented a Legitimate Interests Assessment that can be requested. Where consent is relied on, it can be withdrawn at any time without affecting earlier lawful processing, by contacting {{OWNER_SUPPORT_EMAIL}} or using the unsubscribe link in marketing email.
How personal data is used
Service delivery and account management covers running and improving the platform, creating and managing accounts with authentication and access control, payments, billing, invoicing and renewals, transactional communications such as account alerts, security notices and service updates, and support, troubleshooting and dispute resolution.
Marketing and communications, where opted in, covers newsletters, product updates, feature announcements and promotional offers, surveys and feedback requests, personalisation based on usage patterns, and targeted advertising on the company website and third-party platforms with consent where required. Opting out of marketing does not stop service-related messages.
AI features are optional and controller-directed. They include call transcription, note-taking, candidate summaries, job description generation and email drafting. The policy states that customer data is not used to train, fine-tune or improve AI models without explicit prior written consent; that customers retain full ownership of inputs and outputs; that safeguards are maintained with shared responsibility under GDPR Articles 26 and 28; that AI outputs are informational assistance only and decisions based on them are the customer's responsibility; that automated processing with significant effects (Article 22) is disclosed on request with human review available; and that only anonymised or pseudonymised technical usage data is used for service quality, with no personal data used for product improvement without explicit consent.
Sharing, sub-processors and onward transfer
Personal data is not sold. It is shared with sub-processors under written data processing agreements, and customers are notified of changes to the sub-processor list under the DPA. The authoritative list, with processing purposes and countries of establishment, is maintained in Annex III of the Data Processing Agreement. International transfers use an adequacy decision, a recognised data privacy framework, or Standard Contractual Clauses as appropriate.
Legal disclosures may be made to law enforcement, courts or public authorities where required by law or a binding order. Where legally permissible, affected customers are notified before compliance so they can seek remedies, and disclosure is limited to the minimum necessary. In a merger, acquisition, asset sale or restructuring, data may transfer to the acquiring entity with advance email and website notice, and the acquirer is bound by equivalent privacy commitments. Other sharing happens only with explicit prior consent.
Under the DPF Principles, the company remains liable for onward transfers to third-party sub-processors acting on its behalf, unless it proves it is not responsible for the event causing the damage.
International transfers
The company is headquartered in the United States. For transfers from the EEA, UK or Switzerland to the US or other countries, it relies on the EU-U.S. DPF, the UK Extension and the Swiss-U.S. DPF as the primary mechanism. The EU-U.S. DPF rests on the European Commission's Adequacy Decision C(2023) 4745 of 10 July 2023. {{OWNER_DPF_CERTIFICATION_STATUS}}
As a supplementary safeguard, Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module 2: Controller-to-Processor) are in place with sub-processors and customers for EEA-to-US transfers. The SCCs are governed by Irish law, with disputes subject to the courts of Dublin, Ireland, consistent with the DPA. The UK International Data Transfer Addendum applies where UK GDPR governs.
Transfers within the EEA follow GDPR directly; transfers to the UK follow UK GDPR; transfers to countries with an EU adequacy decision rely on that decision; all others use SCCs or another Chapter V mechanism. The policy states that bundled consent is not used as a transfer mechanism for EEA, UK or Swiss data to the US.
Data retention
Data is kept only as long as needed for the purpose it was collected for, or as required by law. The retention table below summarises the key periods. After a period expires, data is securely and permanently deleted following NIST SP800-88 media sanitisation guidance, and deleted customer data cannot be recovered. On written request, a written certification of deletion is provided within 30 days. Controllers using the platform as a processor should read the retention table alongside Section 11 of the Data Processing Agreement when completing their Article 30 records.
Cookies and tracking
Cookies and similar technologies (web beacons, pixels, local storage) are used on the website and in the services. In jurisdictions where the ePrivacy Directive and GDPR require it, including all EEA states and the UK, consent is obtained before non-essential cookies are set, via the cookie consent banner. The cookie table below lists the four categories and their legal bases.
Consent can be managed or withdrawn at any time through the cookie preference centre or browser settings; disabling some cookies may affect functionality. The policy states that the company does not currently respond to browser Do Not Track signals. Advertising networks including Google, Facebook/Meta and LinkedIn may use cookies and web beacons for interest-based advertising; opt-out links for EEA and US users are provided, along with a separate opt-out for RB2B/Retention.com data practices.
Your data protection rights
Rights are available to individuals in the EU/EEA under GDPR, in the UK under UK GDPR, and in Switzerland under the FADP, including access and the right to limit use and disclosure. The statutory basis and sometimes the scope vary by law, as the rights table shows. Valid requests are answered within 30 days or the timeframe required by law, and no fee is charged unless a request is manifestly unfounded or excessive.
The policy notes that UK GDPR mirrors the EU GDPR's articles and numbering, so UK individuals exercise the same rights on the same basis. Swiss FADP rights correspond closely (access, rectification, erasure/destruction and portability under Articles 25–32 FADP; protection from automated individual decisions under Article 21 FADP) but differ in scope: there is no directly equivalent standalone right to restrict processing, and the right to object is narrower than GDPR Article 21.
How to exercise rights and where to complain
To exercise a right, contact {{OWNER_SUPPORT_EMAIL}} with the subject line "Data Rights Request". Identity verification may be requested to protect against unauthorised access. Employees or candidates whose data is processed by a customer should contact that customer, which is the controller.
If unsatisfied with the response or concerned about unlawful processing, a complaint can go to the relevant supervisory authority: the authority of the EU Member State of habitual residence or work (with the Irish Data Protection Commission as lead authority for SCC governing-law matters), the UK Information Commissioner's Office, the Swiss Federal Data Protection and Information Commissioner, or the California Privacy Protection Agency for California residents.
For DPF complaints, the first contact is {{OWNER_SUPPORT_EMAIL}}. If a privacy or data-use concern remains unresolved, the US-based independent dispute resolution provider JAMS is available free of charge. Under certain conditions, binding arbitration before the DPF Panel may also be available.
Security
Technical and organisational measures under GDPR Article 32 include encryption in transit (TLS 1.2 or higher) and at rest, multi-factor authentication for systems holding personal data, role-based and need-to-know access controls, annual independent penetration and vulnerability testing, annual SOC 2 Type II audits with ISO 27001:2022 alignment, continuous application monitoring, physical data centre controls at AWS facilities, annual privacy and security training for personnel with data access, and formal incident response procedures aligned with NIST and EDPB Recommendation 01/2020.
A breach likely to risk rights and freedoms is reported to the relevant supervisory authority within 72 hours of awareness (Article 33) and to affected individuals without undue delay where Article 34 requires it. The policy acknowledges that no internet transmission is completely secure and absolute security cannot be guaranteed.
Children, California rights, mobile apps and Google API data
The services are for adults and professional organisations. The company does not knowingly collect data from children under 13, or under 16 in EEA states that set digital consent at 16 under GDPR Article 8, and does not permit child access without verified parental consent; suspected cases should be reported for prompt deletion.
California residents have additional CCPA/CPRA rights: to know, to delete, to correct, to opt out of sale/sharing (the company does not sell personal information and does not share it for cross-context behavioural advertising without opt-in consent), to limit use of sensitive personal information, and to non-discrimination. California requests are answered within 45 days. The policy states that Global Privacy Control signals are not responded to at this time, a position reviewed on an ongoing basis.
On mobile, the app collects device type, operating system version, device identifier and usage data, may send push notifications that can be disabled at device level, and collects location data only with explicit device-level consent for location-based search, revocable in device settings.
For Google API data, the policy states adherence to the Google API Services User Data Policy including Limited Use requirements: data received through Google APIs is used only to provide the requested feature and is not used for advertising, sold, or used to train AI models.
Third-party links, amendments and contact
The website links to third-party sites and integrates with social platforms including LinkedIn, Facebook and Twitter/X; those platforms' privacy practices are outside the company's responsibility and their policies should be reviewed. Embedded social features such as Like or Share buttons may set cookies and collect IP addresses, subject to cookie consent choices. Community forums and public blogs may be read by others; removal of personal information from public forums can be requested through {{OWNER_SUPPORT_EMAIL}}.
The policy is reviewed periodically. Material changes are announced by email to the registered address at least {{OWNER_AMENDMENT_NOTICE_PERIOD}} ahead, with a prominent website notice, an updated last-updated date, and fresh consent where required. The notice period matches the DPA amendment notification process (Section 12.5); for business customers bound by both documents, the DPA governs processor-role changes while this policy governs controller-role processing and individual rights. DPF-related changes are notified to the U.S. Department of Commerce in advance, and DPA amendments require written agreement by both parties under Section 12.5.
The contact table below maps each query type to the right channel.
| Processing purpose | Type of data | Lawful basis (Art. 6 GDPR) |
|---|---|---|
| Providing the Services and managing your account | Contact, billing, account, usage data | Art. 6(1)(b) — Performance of contract |
| Processing payments and preventing fraud | Billing, payment, device data | Art. 6(1)(b) — Contract; Art. 6(1)(f) — Legitimate interest |
| Responding to support requests | Contact, account, usage data | Art. 6(1)(b) — Contract; Art. 6(1)(f) — Legitimate interest |
| Sending service-related notifications | Contact, account data | Art. 6(1)(b) — Contract; Art. 6(1)(f) — Legitimate interest |
| Sending marketing communications (where opted in) | Contact, usage data | Art. 6(1)(a) — Consent |
| Product analytics and service improvement | Usage, device, log data (pseudonymised) | Art. 6(1)(f) — Legitimate interest |
| Security monitoring and incident response | Log, device, usage data | Art. 6(1)(f) — Legitimate interest |
| Compliance with legal obligations | All relevant categories | Art. 6(1)(c) — Legal obligation |
| Processing on behalf of customers (as data processor) | All customer-submitted personal data | Art. 6(1)(b) — Contract (with controller) |
| AI Feature processing (optional, controller-directed) | As submitted by controller | Art. 6(1)(b) — Contract with controller; inherits lawful basis established by the controller |
This table reflects the policy as published in the {{OWNER_POLICY_EDITION}} Edition, Version {{OWNER_POLICY_VERSION}}. Legal bases can change with law and practice; check the current policy and take legal advice before relying on it.
| Data category | Retention period | Legal basis for retention |
|---|---|---|
| Customer account data (active accounts) | Duration of subscription | Art. 6(1)(b) — contract performance |
| Customer account data (post-termination) | 14 days (export window) | Art. 6(1)(f) — legitimate interest in orderly transition |
| System logs (active log management) | 30 days post-termination | Art. 6(1)(f) — security incident investigation |
| System logs (cold storage archive) | 11 months further (after active log period) | Art. 6(1)(f) — legal compliance and security |
| Billing and financial records | 10 years | Art. 6(1)(c) — legal obligation (tax/accounting law) |
| Marketing opt-in records | Until consent withdrawn + 3 years | Art. 6(1)(a) — consent; Art. 6(1)(f) — dispute resolution |
| Candidate/contact data (processor role) | As instructed by Controller | Per customer DPA instructions |
These periods are the published policy values for the {{OWNER_POLICY_EDITION}} Edition, Version {{OWNER_POLICY_VERSION}}. Controllers using the platform as a processor should read them with Section 11 of the Data Processing Agreement when completing Article 30 records.
| Cookie type | Purpose | Legal basis |
|---|---|---|
| Essential cookies | Required for the platform to function. Include session management, authentication and security tokens. Cannot be disabled without disrupting the Service. | Art. 6(1)(b) — contract; strictly necessary |
| Analytics / insight cookies | Used to understand how users interact with our platform (e.g. Mixpanel, Datadog). Help us improve user experience. Data is pseudonymised where possible. | Art. 6(1)(a) — consent |
| Marketing cookies | Used to deliver targeted advertising and track campaign effectiveness (e.g. Facebook Pixel, LinkedIn Insight Tag). Set only with your consent. | Art. 6(1)(a) — consent |
| Functional cookies | Remember your preferences and settings (e.g. language, timezone). Improve convenience but not essential. | Art. 6(1)(a) — consent |
Cookie names and vendors can change; the cookie preference centre shows the current set. The policy states that browser Do Not Track signals are not currently honoured.
| Right | What it means | How to exercise | Legal basis |
|---|---|---|---|
| Right of Access (Art. 15) | Obtain a copy of your personal data and information about how it is processed. | Email: {{OWNER_SUPPORT_EMAIL}} | Art. 15 GDPR / UK GDPR; Art. 25 FADP |
| Right to Rectification (Art. 16) | Correct inaccurate or incomplete personal data we hold about you. | Email or via account settings | Art. 16 GDPR / UK GDPR; Art. 32(1) FADP |
| Right to Erasure (Art. 17) | Request deletion of your personal data where there is no legitimate reason for continued processing. | Email: {{OWNER_SUPPORT_EMAIL}} | Art. 17 GDPR / UK GDPR; Art. 32(2) FADP (destruction / blocking) |
| Right to Restrict Processing (Art. 18) | Request that we limit how we use your data in certain circumstances. | Email: {{OWNER_SUPPORT_EMAIL}} | Art. 18 GDPR / UK GDPR; closest FADP equivalent is the right to request a prohibition on disclosure (Art. 32(2)(c) FADP) — FADP has no directly equivalent standalone right |
| Right to Data Portability (Art. 20) | Receive your personal data in a structured, machine-readable format. | Email: {{OWNER_SUPPORT_EMAIL}} | Art. 20 GDPR / UK GDPR; Art. 28 FADP |
| Right to Object (Art. 21) | Object to processing based on legitimate interests or for direct marketing purposes. | Email or unsubscribe links | Art. 21 GDPR / UK GDPR; Art. 30(2) FADP (narrower scope — see note below) |
| Right re Automated Decisions (Art. 22) | Not be subject to solely automated decisions that produce significant effects, including profiling. | Email: {{OWNER_SUPPORT_EMAIL}} | Art. 22 GDPR / UK GDPR; Art. 21 FADP |
| Right to Lodge a Complaint (Art. 77) | Complain to a supervisory authority in your country of residence. | Contact your national DPA, UK ICO, or Swiss FDPIC | Art. 77 GDPR / UK GDPR; see Section 10.2 for the Swiss FDPIC reporting channel |
The policy itself notes that the exact statutory citations should be confirmed by legal counsel before final publication. The FADP right to object is narrower than GDPR Article 21 and there is no directly equivalent standalone FADP right to restrict processing.
| Query type | Contact |
|---|---|
| General privacy enquiries | {{OWNER_SUPPORT_EMAIL}} |
| Data rights requests | {{OWNER_SUPPORT_EMAIL}} (subject: "Data Rights Request") |
| Data breach reports | {{OWNER_SUPPORT_EMAIL}} (subject: "Security Incident") |
| DPF complaints (first contact) | {{OWNER_SUPPORT_EMAIL}} |
| DPF independent recourse | JAMS — jamsadr.com/dpf-dispute-resolution |
| Lead supervisory authority (SCC governing law) | Data Protection Commission (DPC) Ireland — dataprotection.ie |
| Company address | {{OWNER_LEGAL_ENTITY}}, {{OWNER_REGISTERED_ADDRESS}} |
| Website | https://rolescrm.com |
The company address and website must be supplied by the owner before publication. Contact channels can change; confirm on the current policy page.
Frequently asked questions
I am a candidate whose CV is in a recruitment agency's CRM. Who do I contact?
The agency or employer that uploaded your data is the data controller for it. Contact that organisation directly to exercise access, correction, erasure or other rights. The platform operator acts as a processor for that data and assists customers in responding to requests as required by law.
Does the platform train AI models on customer or candidate data?
The policy states that personal data and customer data are not used to train, fine-tune or improve AI models without explicit prior written consent. Customers keep full ownership of AI inputs and outputs, and AI outputs are informational assistance only, with decisions resting on the customer.
What happens to account data after a subscription ends?
Customer account data is kept for the duration of the subscription and then for a 14-day export window after termination. System logs are kept for 30 days post-termination, with a further 11 months in cold storage. Billing and financial records are kept for 10 years under tax and accounting law. Deleted customer data cannot be recovered, and a written deletion certificate is provided within 30 days on written request.
How long does a data rights request take?
Valid requests are answered within 30 days or the timeframe required by applicable law, with no fee unless the request is manifestly unfounded or excessive. California requests are answered within 45 days as required by CCPA/CPRA. Identity verification may be requested first.
Can I withdraw cookie consent or opt out of interest-based advertising?
Yes. Consent can be managed or withdrawn through the cookie preference centre or browser settings, though disabling some cookies may affect functionality. For interest-based advertising, EEA users can use youronlinechoices.eu, US users can use optout.aboutads.info, and each advertising platform's privacy settings also offer controls. A separate opt-out exists for RB2B/Retention.com data practices.
What is the difference between a DPF complaint and a supervisory authority complaint?
A DPF complaint starts with the company's support channel and, if unresolved, can go to the US-based independent dispute resolution provider JAMS free of charge, with binding arbitration before the DPF Panel available under certain conditions. A supervisory authority complaint goes to a national data protection authority such as the Irish DPC, UK ICO, Swiss FDPIC or California CPPA and concerns compliance with the relevant data protection law.