1. Data controller
The controller of your personal data is JG INVEST prosta spółka akcyjna, with its registered office in Oświęcim, ul. Jana Matejki 2, 32-600 Oświęcim, entered in the register of entrepreneurs of the National Court Register (KRS) under number 0000915798, tax identification number (NIP) 5492463888, statistical number (REGON) 389702924 ("we").
For matters concerning personal data, write to privacy@boardeon.com or by post to our registered office address. We have not appointed a data protection officer — the law does not require us to — so all matters are handled at this address.
2. When we are the controller, and when we act on the Customer's behalf
This policy covers data whose purposes and means of processing we decide on: account, billing, correspondence, security, website and Partner Program data.
It does not cover the data you provide to Stripe as the seller when buying a Subscription Plan (Entrepreneur, Founder or Multi-Founder) — the Seller within the meaning of the Terms of Service. That data is processed by the Seller as a separate controller, under its own privacy policy (section 6).
It is different with personal data that the Customer enters into Boardeon — for example, data of employees, clients or business partners in documents and notes. The Customer is the controller of that data, and we process it solely on the Customer's behalf, under the Data Processing Agreement. If your data reached Boardeon this way, contact the company that entered it first to exercise your rights. We will help that company fulfil them.
3. What data we process and where we get it
- Account data — email address, full name (if you provide it), profile picture, interface language, encrypted authentication data, role in the Organisation. When you sign in with a Google account, we receive your email address, full name and profile picture from Google.
- Invitation data — when someone invites you to their Organisation, they give us your email address.
- Billing data — company name, address, tax identification number (NIP), payment and invoice history for the Enterprise Plan, which we sell directly. We do not see payment card data — it is handled by the payment operator.
- Information about purchases from the Seller — when you buy a Subscription Plan, the Seller passes on to us information about the purchase and the subscription status (Plan, billing period, amount, payment status, trial, cancellation) and the buyer's details from the order needed to link the purchase to the Organisation, for example full name, email address and country. We do not receive the full card number or CVC. We fetch the card brand, its last four digits and expiry date, and the list of invoices from the Seller only when an owner or administrator opens Settings → Plan, to show them there — we do not store them. If you give a reason or comment when cancelling, we pass it to the Seller together with the cancellation.
- Organisation links and trial — which Additional Organisations under the Multi-Founder Plan belong to the same owner as the Main Organisation, and whether the owner has already used a trial. We need this to apply the discount and grant the trial in accordance with the Terms of Service.
- Partner Program — Partner data — if you join the Partner Program (Partner Program Terms): your
refand its earlier versions; the version, date and language of the Partner Program Terms you accepted; the type of Partner (business or private individual), country and payout method; payout details — business name or full name, address, tax identification number (NIP) or VAT number (for a private individual — the data the law requires in the PIT tax information), IBAN and SWIFT code, or the email address of your PayPal or Wise account; and the commissions accrued, payouts, invoices, bills and tax information. We encrypt payout details — they are visible only to the person who handles Program settlements on our side. - Partner Program — data of referred people — when you arrive at Boardeon from a partner link or enter a partner code: the click on the link (a salted hash of the IP address instead of the address itself, the path of the landing page and the time), the fact of the referral and its source (link or code), the attribution of your Organisations to the partner, the payments on which we calculate commission, and a hash of the payment card identifier provided by Stripe, which we use to check for self-referral. We do not receive the card number or any other card data.
- Correspondence — the messages you send us and our replies.
- Notification channels — an email address or Telegram chat ID, if you set up notifications.
- Technical data — server logs (date and time, request address, response code, browser type, IP address), security events. For rate limiting we do not store the IP address, only its irreversible hash.
- Consent records — what you chose in the cookie banner, when, and against which version of the policy, without the IP address.
- Analytics data — only with your consent, via Google Analytics and PostHog, as described in the Cookie Policy.
- Service statistics — key steps in the service recorded on our side, without cookies: account creation and its source (campaign, sign-up method), email confirmation, sign-ins and failed attempts (without the email address), creation of an Organisation, progress through the setup wizard, use of AI features (which feature and with what result — without content), Plan selection and changes, and payments (amount, currency, status). We label them only with the account and Organisation identifiers — without the email address, name or company name.
- Partner referral cookie (
boardeon_ref) — only with your consent, as described in the Cookie Policy. - Google Drive data — only if you connect Boardeon to your Google Drive. Details below.
Google Drive data
The Google Drive integration is optional. You turn it on in Boardeon under Integrations → Google Drive by signing in to Google and choosing files in Google's file picker. We use the Google Drive API only with the drive.file scope. This means Boardeon can access only the files you choose — it cannot see your other files, your folders or the contents of your Drive. Choosing a folder does not give access to the files stored in it.
- What data we receive from Google: the content of the files you choose and their metadata — name, type, size, modification date, the link to the file in Google Drive, and the fact that a file has been changed, moved to the trash, deleted, or that Boardeon has lost access to it. We also receive the email address of the Google account used for the connection, so that you can see which account is connected.
- What we use it for: only to build and keep up to date your Organisation's knowledge base in Boardeon. We split the text of the files into fragments, convert them into vectors and search them when the AI advisor in Boardeon, or an AI agent you have connected to your Organisation, answers a question. We fetch changes to the chosen files automatically. For files that are scans or images, an AI model may read the text — only within your Organisation's AI budget.
- Where we store it: text fragments, vectors and file metadata are stored in your Organisation's database (Supabase, European Union), separated from other Organisations. We do not keep copies of the files themselves. We encrypt the access token and refresh token received from Google with AES-256-GCM and bind them cryptographically to your Organisation.
- Who we share it with: the fragments needed for a specific answer are sent to the language model provider and to the provider of the model that converts text into vectors — under the rules in section 5, to the entities listed in section 6. No one else.
- What we do not do: we do not sell this data and do not use it for advertising, credit-worthiness assessment or lending. We do not use it to create, train or improve artificial intelligence or machine learning models — neither our own nor anyone else's. Our staff do not read its content unless you explicitly agree to it for specific files (for example in a support request), it is necessary for security purposes (for example to investigate abuse), or the law requires it.
- How to delete it: the "Disconnect" button under Integrations → Google Drive immediately deletes the tokens and all fragments that came from Drive. A file that you remove from the list in Boardeon, move to the trash or delete in Google Drive, or to which Boardeon loses access, is removed from the knowledge base at the next synchronisation. You can also revoke access in your Google account settings at myaccount.google.com/connections — we then stop fetching files and delete the fragments once we detect that access has been revoked. Deleting the Organisation deletes all of this data (section 8).
Files from Google Drive are your company's content, just like documents added directly to Boardeon. If they contain other people's personal data, we process it on the Customer's behalf under the Data Processing Agreement (section 2).
Boardeon'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.
4. Purposes, legal bases and retention periods
| Purpose | Legal basis (GDPR) | How long |
|---|---|---|
| Creating and maintaining the account, providing the service | Article 6(1)(b) — contract | Until the account is deleted, then up to 30 days |
| Billing, invoices, accounting | Article 6(1)(c) — legal obligation | 5 years from the end of the year in which the tax payment deadline passed |
| Handling purchases from the Seller: linking the Plan to the Organisation, subscription status, the Multi-Founder discount, the partner discount, eligibility for a trial, refunds and complaints | Article 6(1)(b) — contract | For the term of the agreement, then until claims become time-barred |
| Partner Program: the Partner's participation, accruing commissions and payouts | Article 6(1)(b) — contract | For the duration of participation in the Program, then until claims become time-barred |
| Partner Program: the Partner's invoices, bills and tax information | Article 6(1)(c) — legal obligation | 5 years from the end of the year in which the tax payment deadline passed |
| Partner Program: recording clicks, attributing referrals, detecting self-referrals and other abuse | Article 6(1)(f) — legitimate interest | Clicks — 13 months; attributions and the card identifier hash — for as long as commissions on the given Organisation are being settled, then until claims become time-barred |
| Google Drive connection: tokens, Google account address, metadata of the chosen files | Article 6(1)(b) — contract | Until the integration is disconnected; a file's data — until it is removed from the list or from Drive, or access is lost (next synchronisation) |
| Handling complaints and enquiries | Article 6(1)(b) and (f) | Until the matter is closed, then until claims become time-barred |
| Security, abuse prevention, logs | Article 6(1)(f) — legitimate interest | Up to 30 days, longer only in the event of an incident |
| Protecting sign-up, sign-in and password reset from bots (hCaptcha) | Article 6(1)(f) — legitimate interest | The check takes a moment; data held by hCaptcha under its own rules, at most a few weeks |
| Establishing, pursuing and defending claims | Article 6(1)(f) | Until claims become time-barred |
| Messages about changes to the service and documents | Article 6(1)(b) and (c) | For the term of the agreement |
| Proof of consent to cookies | Article 6(1)(c) in conjunction with Article 7(1) | Up to 3 years after you change your choice |
| Visit statistics (Google Analytics) | Article 6(1)(a) — consent | Until consent is withdrawn; event data 14 months |
| Analytics of behaviour in the service and session recordings (PostHog) | Article 6(1)(a) — consent | Until consent is withdrawn; recordings 30 days, events up to 2 years |
| Service statistics: sign-up funnel, activation, purchases and payments (PostHog, without cookies) | Article 6(1)(f) — legitimate interest | Up to 2 years |
| Newsletter, if you subscribe to it | Article 6(1)(a) — consent | Until consent is withdrawn |
Our legitimate interest is ensuring the security of the service and protection against claims, measuring whether the service works — where sign-ups or purchases fail and which features are used — and, in the Partner Program, settling commissions reliably and preventing abuse such as self-referrals and fictitious accounts. We have weighed it against your rights. You may object — we describe how in section 10.
5. Artificial intelligence — where your data goes
When you use an AI-based feature — the advisor, AI board meetings, strategic analyses, plan commentary, summaries — the fragments of your company's data needed for the response are sent to a language model provider. We route requests through OpenRouter, which passes them to the model selected for the given feature, currently from providers including OpenAI and Google. Document search uses an OpenAI model that converts document text into vectors.
- We send only the data needed for a specific request, not your whole account.
- We choose providers that, under their own terms, do not use data submitted via the API to train models.
- Providers may briefly retain request content to detect abuse, in accordance with their terms.
- Some providers process data outside the European Economic Area — the rules are described in section 7.
If you do not want data to reach a model provider, do not use the AI features. Business Score, the financial calculators, the simulator and the valuation are calculated entirely on our infrastructure. Find out more in the AI Use Policy.
6. Who we share data with
We entrust data to entities that help us provide the service and act on our instructions:
| Entity | Task | Where |
|---|---|---|
| Supabase, Inc. | Database, authentication, file storage | EU (Ireland) |
| Vercel Inc. | Application hosting | EU (primary region) and global edge network |
| OpenRouter, Inc. and the model providers it routes requests to | Generating AI responses | USA and other countries |
| OpenAI (OpenAI Ireland Ltd and OpenAI, L.L.C.) | Indexing documents for search | EU and USA |
| Twilio Ireland Limited (SendGrid) | Sending email | EU and USA |
| Intuition Machines, Inc. (hCaptcha) | Telling people from bots at sign-up, sign-in and password reset — IP address, browser and device data, how the form is used | USA |
| Google Ireland Limited | Google Analytics — only with consent | EU and USA |
| PostHog, Inc. | Product analytics: service statistics and, with consent, behaviour in the service and session recordings | EU (Germany); support access from the USA under standard contractual clauses |
| Stripe Payments Europe, Limited | Payment processing for the Enterprise Plan, which we sell directly | EU and USA |
| Accounting firm | Accounting | Poland |
Some recipients are independent controllers of the data:
- Google — when you sign in with a Google account or connect Boardeon to Google Drive, under Google's privacy policy. We fetch files from Google on your instructions (section 3, "Google Drive data").
- Telegram — when you yourself set up notifications via Telegram; messages then pass through Telegram's servers, including outside the EEA.
- Stripe as the Seller ("Sold through Link" transactions) — when you buy a Subscription Plan, Stripe processes the purchase data — full name, email address, billing address, payment details and VAT number — as a separate controller, under its own privacy policy. You provide this data to the Seller on the order page; we may pass on to it the account email address and the Organisation identifier to link the order to your Organisation. We receive information about the purchase and the subscription status from the Seller (section 3).
- The payment operator — to the extent that the law imposes its own obligations on it, for example anti-money laundering obligations.
- The bank, Wise or PayPal — when we pay out a commission in the Partner Program, we pass on the recipient's details needed for the transfer.
- Public authorities — when the law requires it.
Partners in the Partner Program do not receive the data of the people they referred — they see only aggregate figures: clicks, registrations, customers, paying customers, commissions and payouts.
We do not sell data or share it for advertising purposes.
7. Transfers of data outside the EEA
Some recipients have their registered office or infrastructure outside the European Economic Area, mainly in the USA. We transfer data only with the safeguards required by Chapter V GDPR: to entities certified under the EU–US Data Privacy Framework, or on the basis of standard contractual clauses approved by the European Commission. You can obtain a copy of the safeguards by writing to privacy@boardeon.com.
8. How we protect data
Each Organisation's data is separated at database level: every table enforces row-level security, so one Organisation's queries cannot reach another's data, even if there is a bug in the application. Data is encrypted in transit and at rest. API keys you provide are encrypted with the AES-256-GCM algorithm and cryptographically bound to your Organisation. Only authorised people have access to production data, to the extent necessary to maintain the service.
When an Organisation is deleted, its data disappears from production systems, and encrypted backups expire after 30 days at the latest.
9. Do you have to provide data
Providing an email address is necessary to create an account and conclude the agreement, and billing data is necessary to issue an invoice. The data needed for a purchase from the Seller is set by the Seller on the order page. Payout details are necessary to pay out a commission in the Partner Program. You provide any other data voluntarily. Consent to analytics cookies is voluntary and does not affect access to the service.
10. Your rights
You have the right to:
- access your data and receive a copy of it,
- have inaccurate data rectified,
- have your data erased,
- have processing restricted,
- transfer your data to another controller,
- object to processing based on legitimate interest,
- withdraw consent at any time — without affecting the lawfulness of processing carried out before its withdrawal.
Write to privacy@boardeon.com. We respond without undue delay, and within one month at the latest. We may ask you to confirm your identity if the request did not come from the account email address.
If you believe we are processing your data unlawfully, you may lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warszawa, or with the supervisory authority in the country where you reside or work.
11. Automated decisions
We do not take decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. Boardeon's scores and recommendations concern the company and are information for you, not a decision taken about you.
12. Children
Boardeon is a tool for businesses and is not intended for people under 18. We do not knowingly collect their data.
13. Cookies
We describe cookies, Google Analytics and PostHog in the Cookie Policy.
14. Changes to this policy
We publish every change on this page. We give notice of material changes by email before they take effect. Previous versions remain available.