← Back to the app

Data Processing Agreement

version 1.0 · In force since

1. Parties and conclusion of the agreement

The agreement is concluded between:

  • the Customer using Boardeon — as the controller of personal data (the "Controller"),
  • JG INVEST prosta spółka akcyjna, with its registered office in Oświęcim, ul. Jana Matejki 2, 32-600 Oświęcim, KRS 0000915798, NIP 5492463888 — as the processor (the "Processor", "we").

This agreement forms part of the Terms of Service and is concluded when they are accepted. It meets the requirements of Article 28(3) of Regulation (EU) 2016/679 (the "GDPR"). Capitalised terms have the meaning given to them in the Terms of Service or in the GDPR.

2. Subject matter, nature and purpose of processing

The Controller entrusts us with processing the personal data contained in Customer Content — data that the Customer and its Users enter into Boardeon or upload in documents.

We process it solely to provide the service described in the Terms of Service. Processing comprises: storage, structuring, searching, analysis, passing fragments to AI model providers in order to generate responses, creating reports and notifications, making backups, and erasure.

Processing lasts for the term of the agreement to use Boardeon and until the data is deleted in accordance with section 10.

3. Types of data and categories of data subjects

The Controller decides what data enters Boardeon. Typically, these are:

  • categories of data subjects — the Controller's employees and associates, its clients, business partners, suppliers, contact persons and other people mentioned in documents and notes,
  • types of data — full names, job titles, contact details, data on cooperation and transactions, on remuneration and team costs, as well as other data contained in content entered by the Controller.

Boardeon is not intended for processing special categories of data (Article 9 GDPR) or data relating to criminal convictions (Article 10 GDPR). The Controller should not enter such data; if it does, it is responsible for ensuring that a legal basis exists.

4. Our obligations

We undertake to:

  1. process the data only on documented instructions from the Controller. The instructions are: the Terms of Service, this agreement, the configuration of the Organisation and the actions of Users in Boardeon. If Union or Member State law requires us to carry out other processing, we will inform the Controller before it begins, unless that law prohibits this,
  2. inform the Controller without delay if, in our opinion, an instruction infringes data protection law,
  3. allow access to the data only to authorised persons who are bound by confidentiality, to the extent necessary to provide the service,
  4. apply the security measures required by Article 32 GDPR, described in Annex 1,
  5. assist the Controller — as far as possible and taking into account the nature of the processing — in giving effect to the rights of data subjects and in complying with the obligations under Articles 32–36 GDPR,
  6. maintain the record of categories of processing activities referred to in Article 30(2) GDPR,
  7. not use the data for our own purposes, including training AI models.

5. Sub-processing

The Controller gives us general authorisation to engage sub-processors. Their current list is in Annex 2.

We will inform the Controller of any intended addition or replacement of a sub-processor by email and in this document at least 14 days in advance. During that time the Controller may raise a justified objection. If we do not find a solution, the Controller may terminate the agreement with immediate effect and receive a refund of the fee for the unused, paid-for period.

We impose on sub-processors data protection obligations no less stringent than those in this agreement. We are liable to the Controller for their actions as for our own.

6. Transfers of data outside the EEA

We transfer data outside the European Economic Area only where Chapter V GDPR provides for it — on the basis of an adequacy decision (including the EU–US Data Privacy Framework) or standard contractual clauses approved by the European Commission, with supplementary safeguards where needed.

7. Personal data breaches

We will notify the Controller of a breach affecting the data entrusted by the Controller without undue delay, and no later than 48 hours after becoming aware of it, at the email address of the Organisation owner.

The notification contains the information required by Article 33(3) GDPR, to the extent known to us; we provide any missing information without delay once we obtain it. We take action to limit the effects of the breach and assist the Controller in notifying it to the supervisory authority and to the data subjects.

8. Data subjects' rights

If a data subject sends a request directly to us, we will forward it to the Controller without undue delay and will not respond to it ourselves, unless the Controller asks us to. The Controller can handle most requests — access, rectification, erasure — itself in Boardeon; with the others, we will help on a request sent to privacy@boardeon.com.

9. Audits

On request, we will make available to the Controller the information needed to demonstrate that we comply with the obligations under Article 28 GDPR — in the first place in the form of written answers and documentation.

If that is not sufficient, the Controller may carry out an audit itself or through an independent auditor bound by confidentiality — after giving us at least 14 days' notice, no more than once a year (unless a personal data breach has occurred or a supervisory authority requires it), during business hours and without compromising the security of other customers' data. The Controller bears the costs of the audit.

10. End of processing

After the agreement to use Boardeon is terminated, we delete the Controller's data within 30 days. During that time we will, on request, provide a copy of it in a machine-readable format. Encrypted backups expire after a further 30 days at the latest.

We retain data for longer only where Union or Member State law requires it — solely to the extent and for the period that law requires.

11. Liability

The parties' liability for breach of this agreement is subject to the rules and limitations set out in the Terms of Service, to the extent permitted by law. This does not limit liability towards data subjects under Article 82 GDPR.

12. Final provisions

In matters of personal data protection, the provisions of this agreement take precedence over the Terms of Service. The agreement is governed by Polish law. We make it available in Polish, English and Spanish; in the event of any discrepancy, the Polish version prevails.

Annex 1. Technical and organisational measures

  • Customer isolation — each Organisation's data is separated at database level; every table enforces row-level security, including for the table owner.
  • Access control — roles in the Organisation (owner, administrator, member, viewer), checked on the server side before every operation that changes data or runs AI. Administrative access to infrastructure is restricted to authorised persons.
  • Encryption — TLS in transit, encryption of data at rest on the infrastructure provider's side, customers' API keys encrypted with the AES-256-GCM algorithm using a key bound to the Organisation, with support for key rotation.
  • Authentication — passwords stored only as cryptographic hashes, sessions with limited validity, optional sign-in with a Google account.
  • Data minimisation in AI — only the fragments needed for a specific request are sent to the model provider; providers do not use them for training.
  • Abuse protection — limits on the number of requests and on the AI budget; IP addresses in counters stored only as irreversible hashes.
  • Backups — daily, encrypted database backups that expire after 30 days at the latest.
  • Secure development — review of changes before deployment, automated data isolation tests and scanning of the repository for exposed secrets on every change, separation of environments.
  • Location — database and files in a European Union region (Ireland).
  • Incident response — logging of security events, the notification procedure described in section 7.

Annex 2. Sub-processors

EntityTaskProcessing locationBasis for transfer outside the EEA
Supabase, Inc.Database, authentication, file storageEU (Ireland)Standard contractual clauses (support access)
Vercel Inc.Application hostingEU (primary region), global edge networkData Privacy Framework, standard contractual clauses
OpenRouter, Inc.Routing requests to AI modelsUSAStandard contractual clauses
Model providers selected for the given feature, currently including OpenAI and GoogleGenerating AI responsesUSA and other countriesData Privacy Framework or standard contractual clauses
OpenAI (OpenAI Ireland Ltd and OpenAI, L.L.C.)Indexing documents for searchEU and USAData Privacy Framework, standard contractual clauses
Twilio Ireland Limited (SendGrid)Sending email notificationsEU and USAData Privacy Framework, standard contractual clauses

If the Controller sets up notifications via Telegram, the content of the notifications is sent to Telegram on the Controller's explicit instruction. Telegram is not our sub-processor — the Controller uses it on its own terms.

If the Controller connects its own OpenRouter key, its Organisation's requests are handled by OpenRouter under an agreement concluded directly with the Controller.