Data Processing Agreement
Preamble
This Data Processing Agreement ("DPA") is the agreement between the Client and FreySoft Poland Spółka z ograniczoną odpowiedzialnością ("FreySoft Poland Sp. z o.o.", "Company", "OliApp", "we", "us", or "our"), registered address ul. Domaniewska 45, 02-672 Warszawa, Poland, governing the processing of personal data that the Client provides to the Company in connection with the services the Company provides to the Client (the "Services") via https://app.oliapp.co (the "Site") and the OliApp mobile application (the "App"), each a "Party" and together the "Parties."
Unless otherwise defined in this DPA, capitalised terms have the meanings set out in the Terms of Use between the Parties (the "Agreement"). This DPA remains in force until termination or expiration of the Agreement and all Personal Data has been returned or deleted in accordance with §5.6 hereof.
1Definitions
Standard Contractual Clauses (SCC) — the Standard Contractual Clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679, approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, currently at eur-lex.europa.eu/eli/dec_impl/2021/914/oj.
EU-U.S. Data Privacy Framework (DPF) — the framework found to provide an adequate level of protection by European Commission Implementing Decision (EU) 2023/1795 of 10 July 2023, covering transfers to organisations in the United States certified under it.
General Data Protection Regulation (GDPR) — Regulation (EU) 2016/679.
Personal Data — any information relating to an identified or identifiable natural person.
Data Subject — the identified or identifiable person to whom Personal Data relates.
Candidate Data — Personal Data that the Client provides to the Company in connection with the Services, with respect to which OliApp is a data processor and the Client is a data controller.
Other Data Protection Laws and Regulations — all laws and regulations, including those of the EU, EEA and their member states, the United States and its states, applicable to processing Personal Data, other than the GDPR.
Sub-processor — any entity providing processing services to the Company in furtherance of the Client's processing and on the Client's behalf.
Public Authority — a government agency or law enforcement authority, including judicial authorities.
Supervisory Authority — an independent public authority responsible for monitoring the application of data protection legislation.
2Roles and Responsibilities
2.1 Roles under GDPR
If GDPR applies to your processing of Candidate Data, you acknowledge and agree that, with regard to Candidate Data, you are a controller and we are a processor (as defined by the GDPR) acting on your behalf, as further described in the Standard Contractual Clauses agreed under this DPA (the "Clauses") and the Appendix with its Annexes.
2.2 Application of SCCs
Where OliApp is a processor and data importer of Personal Data and the Client is a controller and data exporter in respect of Personal Data transferred in accordance with Article 46(2) GDPR, the Parties shall comply with Addendum I (Standard Contractual Clauses, Controller-to-Processor) and the Appendix with its Annexes.
3Instructions
The Parties agree that this DPA constitutes complete and final documented instructions regarding the Company's processing of Candidate Data on the Client's behalf (the "Instructions"). Any additional or alternate instructions must be consistent with the terms and conditions of this DPA.
4Your (Client's) Obligations
Within the scope of this DPA, the Client is solely responsible for complying with all requirements that apply to it under the GDPR and Other Data Protection Laws and Regulations. This mirrors the Customer obligations already set out in Terms of Use §4.4. The Client represents and warrants that it is solely responsible for:
the accuracy, quality, integrity, confidentiality, and security of collected Candidate Data;
complying with all transparency, lawfulness, fairness, and other GDPR requirements for the collection and use of the data, including establishing and maintaining a procedure for Data Subjects to exercise their rights, providing the Company only with lawfully and validly obtained data that is relevant and proportionate to its uses, and ensuring compliance with this DPA by the Client's own personnel or any third party accessing Candidate Data on its behalf;
ensuring its Instructions to the Company comply with the GDPR and Other Data Protection Laws and Regulations, including data minimisation, purpose limitation, and storage limitation; and
complying with all applicable laws in respect of any Instructions it issues to the Company.
5Our (Company's) Obligations
5.1 General Obligations
With regard to processing Personal Data, the Company shall:
process Candidate Data only to provide the Services, using appropriate technical and organisational security measures, and in compliance with the Client's instructions subject to §3 and §4 of this DPA;
inform the Client if the Company cannot comply with its obligations under this DPA, in which case the Client may terminate the Agreement or take other reasonable action, including suspending processing;
inform the Client if, in the Company's opinion, an Instruction may violate the GDPR or Other Data Protection Laws and Regulations;
follow the Client's instructions regarding the collection of Candidate Data, including notice and choice, where the Company obtains Candidate Data from Data Subjects on the Client's behalf; and
take reasonable steps to ensure any employee or contractor authorized to access Candidate Data on the Client's behalf complies with the Agreement and this DPA.
5.2 Notices to the Client
Upon becoming aware, we will inform you of any legally binding request for disclosure of Candidate Data by a Public Authority, unless prohibited by law from doing so — for instance, to preserve the confidentiality of a Public Authority investigation. We will inform you if we become aware of any notice, inquiry, or investigation by a Supervisory Authority regarding the processing of Candidate Data under this DPA.
5.3 Security Measures
We will implement and maintain appropriate technical and organisational measures to protect Candidate Data from personal data breaches ("Security Incidents"), in accordance with the standards in Annex II. Security measures are subject to technical progress, so we may modify or update Annex II at our sole discretion, provided the update does not materially degrade the security measures offered at the time of signing.
5.4 Security Incident
Upon becoming aware of a Security Incident, the Company shall: (i) notify you within 48 hours of confirming the incident affects your Candidate Data; (ii) provide timely information relating to the Security Incident as it becomes known or is reasonably requested; and (iii) promptly take reasonable steps to contain and investigate the Security Incident so that you can notify competent authorities and/or affected Data Subjects. An initial notification may be preliminary and updated as more information becomes available. Our notification of or response to a Security Incident is not an acknowledgement of fault or liability regarding it.
5.5 Confidentiality
The Company will not access, use, or disclose to any third party any Candidate Data, except as necessary to maintain or provide the Services, comply with contractual and legal obligations, or comply with a binding order of a public body (such as a subpoena or court order). We will ensure that any employee or contractor authorized to access Candidate Data on your behalf is subject to appropriate confidentiality obligations, including after the end of their employment or engagement.
5.6 Return or Deletion of Candidate Data
The Company shall, and shall cause any Sub-processors to, at the Client's choice, return all Candidate Data and copies to the Client or securely destroy them and demonstrate that it has done so, unless the GDPR or Other Data Protection Laws and Regulations prevent this. Text passed to Vertex AI may be retained by Google for a limited period to detect abuse, and cached for up to 24 hours, under the terms agreed with Google Cloud Poland Sp. z o.o. as a Sub-processor (Annex III), and is deleted when those periods end. Text that the Client's user sent under their own AI provider key (§8) is held by that provider under the terms of the provider account the key belongs to and is outside this obligation; the Company holds no copy of it beyond the Candidate Data stored in the Platform. See Privacy Policy §14 and §17 for the technical mechanics of exporting and deleting data across the system.
5.7 Reasonable Assistance
The Company will provide reasonable assistance regarding: (i) any Data Subject request for access, rectification, erasure, restriction, portability, blocking, or deletion of Candidate Data we process on the Client's behalf — if a Data Subject sends such a request directly to us, §7 of this DPA applies; (ii) investigating a Security Incident and communicating required notifications under §5.4; and (iii) preparing data protection impact assessments and, where necessary, consulting the Supervisory Authority under Articles 35 and 36 GDPR.
6Audit and Certification
If a Supervisory Authority requires an audit of the facilities from which the Company processes Candidate Data, the Client will cooperate and is responsible for all related costs and fees, including the Company's reasonable time.
The Client may audit the Company's technical and organisational measures no more than once every 12 months, on at least 30 days' written notice, at the Client's expense. This right is satisfied by the Company providing a completed security questionnaire or a relevant third-party certification, at the Company's option, in place of an on-site audit.
7Data Subject Requests
If a Data Subject contacts us to exercise their rights under the GDPR and Other Data Protection Laws and Regulations (in particular, access, rectification, or blocking of Candidate Data), we will use reasonable efforts to forward the request to you. If we are legally required to respond ourselves, we will immediately notify you and provide a copy of the request, unless legally prohibited from doing so.
8Sub-processors and Third-Party Processors
General authorisation. You grant us general written authorisation to engage third-party sub-processors to help deliver the Services. The current list is in Annex III and is published at oliapp.co/subprocessors.
Operational tools. Support chat (Crisp) and product analytics (PostHog) process account-level telemetry and user communications, and in respect of that data we act as an independent controller. They do not process unmasked or identifiable Candidate Data that you manage; in session recordings all text, input values, images and file previews are masked at source. These tools are part of how the software is delivered and cannot be switched off for an individual account.
Notice of change. We maintain the sub-processor list at the address above. Where we appoint a new sub-processor to process Candidate Data, we update the list and give you reasonable notice, by email or in-platform announcement, before that sub-processor begins processing. Subscribing to notifications on that page is your own responsibility.
Objection. If you have reasonable grounds to object to a new sub-processor on data-protection grounds, tell us in writing. If we cannot agree an alternative technical arrangement, your sole and exclusive remedy is to terminate the affected Services or subscription without penalty, before that sub-processor begins processing.
The Slack Integration is an example of this. Where you connect the Slack Integration, Candidate Data moves into a Slack workspace that your organisation controls and contracts for. That transfer happens on your instruction, to a provider you selected; the provider is your processor, not ours, and it is not a Sub-processor within the meaning of this DPA. The same applies to any other integration you choose to connect, and to the provider — OpenAI or Google — whose API key your user enters for the AI features that run on it (Privacy Policy §11.1). That provider is your processor under the terms of the provider account the key belongs to; the Company does not contract with it, and the next paragraph does not apply to it.
You acknowledge that, in providing some Services, the Company may — on your instructions — transfer Candidate Data to and interact with third-party data processors. Where this occurs, the Company is responsible for entering into separate contractual arrangements binding those processors to GDPR-equivalent obligations. Such third-party processors are not Sub-processors within the meaning of this DPA.
9Transfers of Candidate Data
The Parties agree to process Candidate Data protected by the GDPR in compliance with the Standard Contractual Clauses approved by European Commission decision 2021/914 of 4 June 2021, to provide adequate safeguards for international transfers as specified in the Addendum and Appendix to this DPA.
An onward transfer from the Company to a Sub-processor in the United States that is certified under the DPF relies on the DPF. This is the case for Google LLC, whose engineers can reach data held on Google Cloud for third-line support. AI Search and Resume Breakdown run on Vertex AI within the European Union and involve no transfer of their own, except an AI Search request that carries an AI provider key supplied by the Client's user. Features that run on an AI provider key supplied by the Client's user send text to that provider on the Client's instruction under §8; that provider is not a Sub-processor. The mechanism relied on for each Sub-processor is named on the Sub-processors page and in the Privacy Policy.
10Liability
Each Party's total liability to the other under this DPA is subject to the limitation of liability set out in Terms of Use §7.3. Neither Party is liable to the other for indirect, consequential, or incidental damages, or lost profits, arising from this DPA.
11Relationship to the Agreement
This DPA forms part of, and is governed by the same law and dispute-resolution terms as, the Agreement (Terms of Use §8, Applicable Law: Poland). It remains in force for as long as the Agreement remains in force, and until all Candidate Data has been returned or deleted in accordance with §5.6.
Addendum I — Standard Contractual Clauses (Controller–Processor)
SECTION I
Clause 1. Purpose and Scope
For the purposes of the Clauses: (a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 for the transfer of personal data to a third country. (b) The Parties: (i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies ("entity/ies") transferring the personal data, as listed in Annex I.A (each a "data exporter"), and (ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (each a "data importer"), have agreed to these standard contractual clauses ("Clauses"). (c) These Clauses apply to the transfer of personal data specified in Annex I.B. (d) The Appendix, containing the Annexes referred to herein, forms an integral part of these Clauses.
Clause 2. Effect and Invariability of the Clauses
(a) These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, under Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, for controller-to-processor and processor-to-processor transfers, standard contractual clauses under Article 28(7), provided they are not modified except to select the appropriate Module(s) or add or update Appendix information. This does not prevent the Parties from including these Clauses in a wider contract or adding other clauses or safeguards, provided they do not contradict these Clauses or prejudice data subjects' fundamental rights. (b) These Clauses are without prejudice to obligations to which the data exporter is subject under Regulation (EU) 2016/679.
Clause 3. Third-Party Beneficiaries
(a) Data subjects may invoke and enforce these Clauses as third-party beneficiaries against the data exporter and/or data importer, with the following exceptions: (i) Clauses 1, 2, 3, 6, 7; (ii) Clauses 8.1(b), 8.9(a), (c), (d), (e); (iii) Clause 9(a), (c), (d), (e); (iv) Clause 12(a), (d), (f); (v) Clause 13; (vi) Clause 15.1(c), (d), (e); (vii) Clause 16(e); (viii) Clause 18(a), (b). (b) Paragraph (a) is without prejudice to data subjects' rights under Regulation (EU) 2016/679.
Clause 4. Interpretation
(a) Terms defined in Regulation (EU) 2016/679 have the same meaning here. (b) These Clauses are read and interpreted in light of that Regulation. (c) These Clauses are not interpreted in a way that conflicts with rights and obligations under that Regulation.
Clause 5. Hierarchy
In the event of a contradiction between these Clauses and related agreements between the Parties, existing now or entered into later, these Clauses prevail.
Clause 6. Description of the Transfer(s)
The details of the transfer(s), including categories of personal data transferred and the purpose(s), are specified in Annex I.B.
Clause 7. Docking Clause
(a) An entity that is not a Party may, with the Parties' agreement, accede at any time, as data exporter or data importer, by completing the Appendix and signing Annex I.A. (b) Once it has done so, the acceding entity becomes a Party with the rights and obligations of its designated role. (c) The acceding entity has no rights or obligations arising from the period before it became a Party.
SECTION II – OBLIGATIONS OF THE PARTIES
Clause 8. Data Protection Safeguards
The data exporter warrants it has used reasonable efforts to determine that the data importer can, through appropriate technical and organisational measures, satisfy its obligations under these Clauses.
8.1 Instructions
(a) The data importer shall process personal data only on the data exporter's documented instructions, given throughout the contract. (b) The data importer shall immediately inform the data exporter if unable to follow those instructions.
8.2 Purpose Limitation
The data importer shall process personal data only for the specific purpose(s) of the transfer set out in Annex I.B, unless further instructed by the data exporter.
8.3 Transparency
On request, the data exporter shall make a copy of these Clauses, including the completed Appendix, available to the data subject free of charge. To protect business secrets or confidential information, including Annex II measures and personal data, the data exporter may redact part of the Appendix before sharing, but shall provide a meaningful summary where the data subject would otherwise be unable to understand its content or exercise their rights. This Clause is without prejudice to the data exporter's obligations under Articles 13 and 14 of Regulation (EU) 2016/679.
8.4 Accuracy
If the data importer becomes aware that personal data it received is inaccurate or outdated, it shall inform the data exporter without undue delay and cooperate to erase or rectify it.
8.5 Duration of Processing and Erasure or Return of Data
Processing shall only take place for the duration specified in Annex I.B. Afterward, the data importer shall, at the data exporter's choice, delete all personal data processed on its behalf and certify this, or return it and delete existing copies. Until deleted or returned, the data importer shall continue to ensure compliance with these Clauses. Where local law prohibits return or deletion, the data importer warrants continued compliance and processing limited to what that local law requires, without prejudice to Clause 14, including the data importer's Clause 14(e) notification duty.
8.6 Security of Processing
(a) The data importer, and the data exporter during transmission, shall implement appropriate technical and organisational measures to secure the data, including against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access ("personal data breach"), considering the state of the art, implementation costs, and the nature, scope, context, purpose, and risks of processing — including encryption or pseudonymisation where appropriate. In complying, the data importer shall implement at least the measures in Annex II, and carry out regular checks that they remain adequate. (b) The data importer shall grant personnel access to personal data only to the extent strictly necessary, and ensure such persons are bound by confidentiality. (c) In the event of a personal data breach, the data importer shall take appropriate measures to address it, including mitigating adverse effects, and notify the data exporter without undue delay, with available details and further information as it becomes available. (d) The data importer shall cooperate with and assist the data exporter to enable compliance with Regulation (EU) 2016/679, including notifying the competent supervisory authority and affected data subjects.
8.7 Sensitive Data
Where the transfer involves special-category data (racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic or biometric data, health, sex life or sexual orientation, or criminal-conviction data), the data importer shall apply the specific restrictions or safeguards described in Annex I.B.
8.8 Onward Transfers
The data importer shall only disclose personal data to a third party on the data exporter's documented instructions. Disclosure to a third party located outside the EU is permitted only if that party is or agrees to be bound by these Clauses under the appropriate Module, or if: (i) the onward transfer is to a country with an adequacy decision under Article 45 covering it; (ii) the third party otherwise ensures appropriate safeguards under Articles 46 or 47; (iii) the transfer is necessary to establish, exercise, or defend legal claims in specific proceedings; or (iv) it is necessary to protect the vital interests of the data subject or another person. Any onward transfer remains subject to all other safeguards under these Clauses, particularly purpose limitation.
8.9 Documentation and Compliance
(a) The data importer shall promptly and adequately deal with the data exporter's enquiries about processing under these Clauses. (b) The Parties shall be able to demonstrate compliance; the data importer shall keep appropriate documentation of processing activities carried out on the data exporter's behalf. (c) The data importer shall make available all information necessary to demonstrate compliance and, on request, allow and contribute to audits at reasonable intervals or where there are indications of non-compliance; relevant certifications may be taken into account. (d) The data exporter may conduct the audit itself or mandate an independent auditor; audits may include inspections of premises, with reasonable notice where appropriate. (e) The Parties shall make this information, including audit results, available to the competent supervisory authority on request.
Clause 9. Use of Sub-Processors
(a) GENERAL WRITTEN AUTHORISATION. The data importer has the data exporter's general authorisation to engage sub-processors from an agreed list. It shall specifically inform the data exporter in writing of any intended addition or replacement of sub-processors at least 30 days in advance, giving the data exporter sufficient time to object before engagement, and shall provide the information necessary to exercise that right.
(b) Where the data importer engages a sub-processor for specific processing activities on the data exporter's behalf, it shall do so under a written contract imposing substantially the same data protection obligations as bind the data importer under these Clauses, including third-party beneficiary rights for data subjects; complying with this Clause fulfils the data importer's obligations under Clause 8.8. The data importer shall ensure the sub-processor complies with the obligations that bind the data importer. (c) On request, the data importer shall provide a copy of the sub-processor agreement and any amendments, redacted as necessary to protect business secrets or confidential information. (d) The data importer remains fully responsible to the data exporter for the sub-processor's performance, and shall notify the data exporter of any failure by the sub-processor to fulfil its obligations. (e) The data importer shall agree a third-party beneficiary clause with the sub-processor so that, if the data importer has factually disappeared, ceased to exist in law, or become insolvent, the data exporter may terminate the sub-processor contract and instruct the sub-processor to erase or return the data.
Clause 10. Data Subject Rights
(a) The data importer shall promptly notify the data exporter of any data subject request received, and shall not respond itself unless authorised by the data exporter. (b) The data importer shall assist the data exporter in fulfilling its obligations to respond to such requests, with the appropriate technical and organisational measures set out in Annex II. (c) In fulfilling (a) and (b), the data importer shall comply with the data exporter's instructions.
Clause 11. Redress
(a) The data importer shall inform data subjects, transparently and accessibly, of a contact point for complaints, and deal with complaints promptly; data subjects may also lodge a complaint with an independent dispute-resolution body at no cost, and are not required to use it or follow a particular sequence. (b) In a dispute between a data subject and a Party over compliance, that Party shall use best efforts to resolve it amicably and keep the other Party informed. (c) Where a data subject invokes a third-party beneficiary right under Clause 3, the data importer shall accept the data subject's decision to lodge a complaint with the competent supervisory authority or refer the dispute to the competent courts under Clause 18. (d) The data subject may be represented by a not-for-profit body under Article 80(1) of Regulation (EU) 2016/679. (e) The data importer shall abide by a decision that is binding under applicable EU or Member State law. (f) The data subject's choice does not prejudice their substantive and procedural rights to other remedies.
Clause 12. Liability
(a) Each Party is liable to the other for damages it causes by breaching these Clauses. (b) The data importer is liable to the data subject, who is entitled to compensation, for material or non-material damage the data importer or its sub-processor causes by breaching third-party beneficiary rights under these Clauses. (c) Notwithstanding (b), the data exporter is liable to the data subject for damage the data exporter or the data importer (or its sub-processor) causes by such a breach, without prejudice to the data exporter's or, where it is a processor, the controller's liability under Regulation (EU) 2016/679 or 2018/1725. (d) If the data exporter is held liable under (c) for damage caused by the data importer, it may claim back the corresponding share from the data importer. (e) Where more than one Party is responsible, all responsible Parties are jointly and severally liable, and the data subject may bring an action against any of them. (f) A Party held liable under (e) may claim back the corresponding share from the other Party/ies. (g) The data importer may not invoke a sub-processor's conduct to avoid its own liability.
Clause 13. Supervision
(a) The supervisory authority of the Member State in which the relevant data subjects are located (in connection with the offering of goods or services to them, or the monitoring of their behaviour), as indicated in Annex I.C, is the competent supervisory authority. (b) The data importer agrees to submit to that authority's jurisdiction and cooperate in any procedure aimed at ensuring compliance, including responding to enquiries, submitting to audits, complying with remedial and compensatory measures, and confirming in writing that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES
Clause 14. Local Laws and Practices Affecting Compliance
(a) The Parties warrant they have no reason to believe that laws or practices in the third country of destination prevent the data importer from fulfilling its obligations, on the understanding that laws respecting the essence of fundamental rights and not exceeding what is necessary and proportionate under Article 23(1) of Regulation (EU) 2016/679 do not contradict these Clauses. (b) In giving that warranty, the Parties have taken account of: (i) the specific circumstances of the transfer; (ii) the third country's laws and practices relevant to those circumstances; and (iii) any relevant contractual, technical, or organisational safeguards supplementing these Clauses. (c) The data importer warrants it has made best efforts to provide relevant information for this assessment and will continue to cooperate. (d) The Parties agree to document the assessment and make it available to the competent supervisory authority on request. (e) The data importer shall promptly notify the data exporter if it has reason to believe it is or has become subject to laws or practices not in line with (a). (f) Following such notification, or if the data exporter otherwise has reason to believe the data importer can no longer comply, the data exporter shall identify appropriate measures and shall suspend the transfer if no appropriate safeguards can be ensured, or if instructed by the competent supervisory authority, with a right to terminate the contract as it concerns processing under these Clauses.
Clause 15. Obligations in Case of Access by Public Authorities
15.1 Notification. (a) The data importer shall notify the data exporter and, where possible, the data subject promptly if it receives a legally binding disclosure request from a public authority, or becomes aware of direct access by a public authority, including available details. (b) If prohibited from notifying, the data importer shall use best efforts to obtain a waiver of the prohibition and document those efforts. (c) Where permissible, the data importer shall periodically provide the data exporter with relevant information on requests received. (d) The data importer shall preserve this information for the contract's duration and make it available to the competent supervisory authority on request. (e) This is without prejudice to the data importer's Clause 14(e) and Clause 16 obligations.
15.2 Review of Legality and Data Minimisation. (a) The data importer shall review the legality of a disclosure request and challenge it where there are reasonable grounds to consider it unlawful, seeking interim measures and not disclosing data until required under applicable procedural rules. (b) The data importer shall document its legal assessment and any challenge and, where permissible, make it available to the data exporter and the competent supervisory authority on request. (c) The data importer shall provide the minimum information permissible when responding to a disclosure request.
SECTION IV – FINAL PROVISIONS
Clause 16. Non-Compliance with the Clauses and Termination
(a) The data importer shall promptly inform the data exporter if unable to comply, for any reason. (b) Where the data importer is in breach or unable to comply, the data exporter shall suspend the transfer until compliance is restored or the contract is terminated, without prejudice to Clause 14(f). (c) The data exporter may terminate the contract, as it concerns processing under these Clauses, where: (i) it has suspended the transfer under (b) and compliance is not restored within a reasonable time and in any event within one month; (ii) the data importer is in substantial or persistent breach; or (iii) the data importer fails to comply with a binding decision of a competent court or supervisory authority, and shall inform the competent supervisory authority accordingly. (d) Data transferred before termination shall, at the data exporter's choice, be returned or deleted in its entirety, with certification, and the data importer shall continue to ensure compliance until then; where local law prohibits return or deletion, the data importer shall continue to ensure compliance and limit processing accordingly. (e) Either Party may revoke its agreement to be bound where the European Commission adopts an adequacy decision covering the transfer, or Regulation (EU) 2016/679 becomes part of the destination country's legal framework.
Clause 17. Governing Law
These Clauses are governed by the law of an EU Member State that allows for third-party beneficiary rights. The Parties agree this is the law of Poland.
Clause 18. Choice of Forum and Jurisdiction
(a) Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State. (b) The Parties agree these are the courts of Poland. (c) A data subject may also bring proceedings against the data exporter and/or data importer before the courts of the Member State of their habitual residence. (d) The Parties agree to submit to the jurisdiction of such courts.
Appendix
Annex I.A — List of Parties
Data exporter
Name: "You", "Client."
Address; contact person's name, position, and contact details: provided to the Company via the Site and/or App.
Activities relevant to the data transferred: collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, alignment or combination, restriction, erasure or destruction.
Signature and date: by entering into the Agreement, the data exporter is deemed to have signed these Clauses, including their Annexes, as of the Agreement's effective date.
Role: controller.
Data importer
Name: FreySoft Poland Spółka z ograniczoną odpowiedzialnością (FreySoft Poland Sp. z o.o.)
Address: ul. Domaniewska 45, 02-672 Warszawa, Poland (KRS 0000864848, NIP 5213910266)
Contact person's name, position, and contact details: privacy@oliapp.co
Activities relevant to the data transferred: collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, alignment or combination, restriction, erasure or destruction.
Signature and date: by entering into the Agreement, the data importer is deemed to have signed these Clauses, including their Annexes, as of the Agreement's effective date.
Role: processor.
Annex I.B — Description of Transfer
1. Categories of data subjects: Candidates.
2. Categories of personal data transferred:
- identification and contact data of Candidates (name, contact details);
- professional history and qualifications, including education and employment information, as contained in CVs and application materials;
- fields extracted from CV text, and fields inferred from it where not stated explicitly (for example industry or duration of experience), which are marked as inferred and can be corrected;
- application content submitted by a Candidate through a Job Ads page, including any referral-pool consent flag;
- the per-Candidate Referral Pool participation flag and its state;
- factual summaries of Candidate conversations, where the Client's user has enabled message synchronization (the underlying message text is deleted once the summary is generated);
- identifiers used to associate a Candidate's activity across supported third-party platforms with one person;
- Candidate status history and related records of recruiter activity in respect of a Candidate;
- masked recordings of Platform screens on which Candidate Data is displayed, generated by the session-replay function described in Annex III. All text, input values, images and file previews are masked at source, and console output and network payloads are not captured, so a recording carries the structure of a session rather than its content. It is listed here because the recording is nevertheless generated from screens showing Candidate Data and is held by a sub-processor;
- any Candidate Data a Client's user chooses to include in a support conversation with the Company through the live-chat function.
3. Sensitive data transferred and safeguards: The Services are not designed or intended for the processing of special categories of personal data within the meaning of Article 9 GDPR, and the Client undertakes not to submit such data to the Platform (see Terms of Use §4.4). The Client likewise undertakes not to submit national identification numbers, passwords, or security credentials.
The Parties acknowledge that free-text fields — in particular notes, comments, and summaries of Candidate conversations generated where message synchronization is enabled — may incidentally contain information falling within Article 9. The Company does not seek, request, index, or use such information, applies the measures in Annex II to it as to all other Candidate Data, and will delete it on the Client's instruction. The Client remains responsible for establishing a lawful basis under Article 9 for any such data it causes to be submitted.
4. Frequency of transfer: Continuous.
4a. Interfaces through which processing occurs: The Platform at app.oliapp.co, the browser extension, the Slack Integration where the Client has connected it, and the mobile application once released. The Slack Integration transmits Candidate Data into a Slack workspace controlled by the Client, on the Client's instruction, as described in §8. Where the Client's user has entered their own AI provider key, the AI features that run on it transmit text to that provider in the same way (§8).
5. Nature of processing: Collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, alignment or combination, restriction, erasure or destruction.
6. Purpose(s) of transfer: Performance of the Services by the data importer for the data exporter under the Agreement.
7. Retention period: Candidate Data is retained for as long as the Client instructs, and in any event no longer than the term of this DPA; on termination it is returned or deleted in accordance with §5.6. The Client determines retention periods for Candidate Data as controller. Text passed to Vertex AI may be retained by Google for a limited period to detect abuse, and cached for up to 24 hours, under the terms agreed with Google Cloud Poland Sp. z o.o. as a Sub-processor (Annex III).
(a) Active data. Candidate Data is retained for the term of the Agreement, unless the Client deletes it earlier using the Platform's own controls. (b) Deletion backstop after termination. On termination or expiry of the Agreement, or on the Client's written request, the Company deletes or returns all Candidate Data within thirty (30) days; text passed to Vertex AI is deleted by Google when the abuse-monitoring and cache periods described in item 7 end; text sent under a user's own AI provider key is outside this item, as set out in §5.6. (c) Backups. Where data persists in automated encrypted backups and disaster-recovery archives, those residual copies are overwritten and purged under the Company's automated backup retention policy — currently thirty (30) days from the date of the backup — and in any event no later than ninety (90) days after termination. (d) Statutory retention. The Company may retain specific records beyond these periods only to the extent required by Union or Member State law — tax, accounting and statutory audit obligations — and deletes them immediately afterwards.
8. For transfers to sub-processors: Subject matter: performance of services. Nature: as in item 5 above. Duration: for the duration of the service agreement between the processor and sub-processor.
Annex I.C — Competent Supervisory Authority
Per Clause 13, the competent supervisory authority is the Urząd Ochrony Danych Osobowych (UODO) — Personal Data Protection Office, Republic of Poland.
Annex II — Technical and Organisational Measures
Description of the technical and organisational measures implemented by the data importer to ensure an appropriate level of security, given the nature, scope, context, and purpose of processing and the risks to data subjects:
The data importer maintains appropriate organisational and technical security measures — including with respect to personnel, facilities, hardware and software, storage and networks, access controls, monitoring and logging, vulnerability and breach detection, incident response, and encryption of Candidate Data in transit and at rest — to protect against unauthorised or accidental access, loss, alteration, disclosure, or destruction of Candidate Data.
The data importer implements measures to ensure the sufficiency of security, privacy, and confidentiality safeguards of all OliApp personnel with respect to Candidate Data, and is liable for any failure by such personnel to meet this DPA's terms.
The data importer takes reasonable steps to confirm that all OliApp employees and contractors protect the security, privacy, and confidentiality of Candidate Data consistent with this DPA.
The data importer has implemented measures to protect the confidentiality and integrity of personal data during transfers.
The data importer is committed to preserving the confidentiality, integrity, availability, and resilience of personal data throughout processing, and to protecting it against loss and destruction through appropriate internal information-security policies and procedures.
Technical and organisational measures to enable the (sub-)processor to assist the controller and, for processor-to-sub-processor transfers, the data exporter.
Concretely, as at the date of this Agreement:
- Encryption at rest: AES-256 applied by the underlying Google Cloud infrastructure to compute disks, object storage and database backups. A second layer is applied at application level (AES-256-CBC) to integration API keys, Slack installation data, the support-chat token, Candidate data aggregates, the audit trail of operations on Candidate Data, conversation texts and summaries, and CV upload-link secrets.
- Encryption in transit: public endpoints are served over TLS 1.2 or higher, with no fallback to earlier versions, and plain HTTP is redirected to HTTPS. The identity provider requires SSL for external requests. Services inside the private network are reachable only by the specific services that need them, enforced by firewall rules; internal parsing services are not exposed to the internet.
- Access to production: limited to five named members of staff, with differentiated rights — full administration, server and database access, and log-read access respectively. Server access runs through an identity-aware tunnel tied to a corporate Google account; no SSH port is exposed to the internet. Multi-factor authentication is enforced at organisation level on the cloud console and on source control.
- Deployment: runs through workload identity federation; the continuous-integration system holds no long-lived cloud credentials.
- Logging: application, access, administrative and sign-in events are logged. Personal data and tokens are redacted at the logging layer before logs leave the application. Retention is 7 days on the host, 30 days in the cloud logging store, 400 days for cloud administrative-activity records, and 365 days for an error-level archive held in
europe-central2. - Monitoring and alerting: alerting rules are maintained as code and cover service availability, host resources, database connections, server errors, missing telemetry and missed backups, routed to an on-call channel with a written runbook.
- Backup: databases are backed up daily to object storage in
europe-central2, separate from the production host, retained for 30 days, with a seven-day period during which an object cannot be deleted and a seven-day soft-delete window. An alert fires if no successful backup has been uploaded within 26 hours. - Vulnerability management: container images and repositories are scanned for known vulnerabilities and committed secrets on pull requests that change dependencies or container definitions, and on a recurring schedule; the backend's dependencies are audited on every pull request. Accepted-findings baselines can only shrink.
Annex III — List of Sub-Processors
The controller has authorised the use of the following sub-processors:
| Sub-processor | Address | Contact | Description of Processing |
|---|---|---|---|
| HubSpot Inc. | 25 First Street, 2nd Floor, Cambridge, MA 02141, USA | Nicholas Knoop, privacy@securys.co.uk | Managing relationships with users |
| PostHog, Inc. — data stored in the EU region (Frankfurt) | 2261 Market Street #4008, San Francisco, CA 94114, USA | privacy@posthog.com | Product analytics about users of the Platform and the browser extension, and masked session replay of Platform screens. Receives internal user identifiers — not names or email addresses — feature-usage counts, and an approximate location derived from the browser's IP address. Candidate Data is excluded from events, masked at source in recordings, and stripped from logs. Replay retention 30 days |
| Crisp IM SAS (France) | see the Sub-processors page | see the Sub-processors page | Live chat support on the Site and in the Platform. Receives the user's name and email and the content of support conversations, which may include Candidate Data the user chooses to paste into the chat. Erased at Crisp when the user's account is purged |
| Canny, Inc. — 800 N King Street, Suite 304 1121, Wilmington, DE 19801, USA — privacy@canny.io | see the Sub-processors page | see the Sub-processors page | Collecting user feedback |
| Google LLC — 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA | see the Sub-processors page | see the Sub-processors page | Site usage analytics |
Google Cloud Poland Sp. z o.o. (Vertex AI — requests are processed within EU member states through the eu endpoint; Google may keep prompts for a limited period to detect abuse and may cache inputs and outputs for up to 24 hours in the same region; not used to train the models) | see the Sub-processors page | see the Sub-processors page | AI Search, Resume Breakdown |
| Google Cloud Poland Sp. z o.o. (Cloud Storage) | see the Sub-processors page | see the Sub-processors page | Storing CVs and templates |
| Google Cloud Poland Sp. z o.o. (Compute Engine, Cloud Run) | see the Sub-processors page | see the Sub-processors page | Infrastructure hosting |
| Stripe Payments Europe, Limited | see the Sub-processors page | see the Sub-processors page | Billing |
| Google Ireland Limited; Microsoft Ireland Operations Limited | see the Sub-processors page | see the Sub-processors page | Calendar scheduling, if applicable |