Skip to content

Legal

Privacy Policy

This policy describes the personal data we process in Forlead – about the people who use the Service and about the entrepreneurs whose data comes from public registers – why we process it and what rights you have.

Last updated:

Controller

The controller of the personal data described in this policy is Aeris Studio sp. z o.o., the company that runs the Forlead service (formerly Aeris; the “Service”, “we”). The exception is the data we process on behalf of the organizations that use the Service – their controller is the organization concerned (see “Company data from registers”). We have not appointed a data protection officer. For anything about personal data, write to kontakt@forlead.pl.

The company’s registry details:

Company name
Aeris Studio sp. z o.o.
Tax ID (NIP)
PL9182194574
KRS
0001260263
REGON
545483350
Share capital
PLN 5,000
Registered office
Majdan Stary 58, 23-414 Majdan Stary, Poland
Registry court
District Court Lublin-Wschód in Lublin, seated in Świdnik, 6th Commercial Division of the National Court Register

What we process and why

We process only the data we need to run the Service. Each kind of data is listed with its purpose and legal basis.

  • Account: your name or another name you give us, your e-mail address, a hash of your password (never the password itself) and whether the address has been confirmed. Links to confirm the address and to set a new password are sent by e-mail; they are valid for 24 hours and for one hour respectively. Purpose: creating and running the account. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Signing in with Google (if you use it): Google gives us your e-mail address, the name and ID of your Google account, the address of your profile picture (we neither download nor display the picture) and the tokens issued at sign-in. Signing in gives us no access to your mail. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Sessions and security: IP address, browser and device information (user agent), when each session was created and last used, and counters of sign-in and sign-up attempts. Purpose: keeping you signed in, the list of active devices in the account settings and protection against abuse. Legal basis: our legitimate interest in keeping the Service secure (Article 6(1)(f) GDPR).
  • Organization and team: the organization’s name and address in the Service, your role (“Owner”, “Admin” or “Member”), the chosen PKD codes and scoring criteria, company statuses and rejection reasons, your alert setting and invitations – the invitee’s e-mail address, their role and who invited them. Purpose: the team’s shared work in the Service. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Sending mailbox (if you connect one): the mailbox address and, depending on how it is connected, a Google token with a single permission – sending messages (gmail.send) – or the SMTP server address, port, login and password. We store the token and the password encrypted (AES-256-GCM). We read nothing from your mailbox: no replies, no bounces, no other messages. When you disconnect the mailbox we delete the access data, and for Google we also ask for the access to be revoked. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Calendar (if you connect Google Calendar or generate a subscription address): the meetings and follow-ups you plan in the Service on a company – kind, time, title, note, who runs them and who planned them. With Google Calendar connected – the address and identifier of the Google account and a token with a single permission: creating our own secondary calendars and writing to them (calendar.app.created), stored encrypted (AES-256-GCM). Forlead creates a side calendar “Forlead · organization name” in your Google account and writes copies of the entries to it: the title with the company name, the time and a link to the company in the Service, and the note only if you switch that on. We read nothing from your calendar – neither the main one nor any other. The subscription address (ICS) is a random token of which we store only a hash; whoever knows the address can read that calendar, which is why you can replace it at any time. When you disconnect we delete the access data and the side calendar. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Niche wizard (if you use it): the content of your answers in the conversation with the assistant – a description of what you sell and to whom – is passed to Anthropic Ireland, Limited (Ireland) as a processor, which answers them with a language model and stores them in the US; they are not used to train models, and Anthropic deletes them within 30 days – unless its automated safety systems flag the conversation as violating its usage policy (it then keeps the content for up to 2 years and the classification scores for up to 7 years) or the law requires longer. We pass no company data from the catalog and nothing from your account, and of the organization’s settings only the list of tracked PKD codes, saying which of them the morning e-mail covers and which are switched off, and the number of free alert seats; do not put personal data in your answers – the conversation does not need it, and we automatically replace only e-mail addresses and long numbers. We do not store the conversation. With the organization we keep the assistant’s latest proposal, even one that was never applied: PKD codes with the suggested product, scoring preset, regions and cities, excluded legal forms, and the short summary and reasons the assistant wrote, along with who started the conversation and usage counters. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Sender profile and messages to companies: the organization details shown in the letter’s footer (name, tax identification number (NIP), address, contact e-mail, website) and, for every message, the recipient, subject, body, footer, time sent, the address it left from and the person who sent it. Purpose: preparing and sending messages and keeping the record of contact that prevents writing to the same company again for 90 days. Legal basis: performance of a contract (Article 6(1)(b) GDPR). We process the recipients’ data on behalf of the organization that sends the messages – it is their controller (see “Company data from registers”).
  • New-company alerts: if your organization has priority codes and you have alerts switched on, we e-mail you the new companies under those codes every morning. You can switch alerts off on the “PKD codes” screen. Legal basis: performance of a contract (Article 6(1)(b) GDPR).
  • Payments: the customer ID in Stripe, the plan, the subscription status and period. You enter your card details directly with Stripe and they never reach our servers; Stripe also keeps the payment history and billing documents, which we show on the “Billing” screen. Legal basis: performance of a contract (Article 6(1)(b) GDPR) and tax and accounting obligations (Article 6(1)(c) GDPR).
  • Messages to us: your e-mail address and the correspondence when you write to kontakt@forlead.pl, complaints included. Legal basis: performance of a contract (Article 6(1)(b) GDPR) or our legitimate interest in answering messages (Article 6(1)(f) GDPR).
  • Analytics and marketing (only with consent): information about visits to the Service’s public pages collected by Google Analytics 4 and Meta Pixel – details in the Cookie Policy. Legal basis: your consent (Article 6(1)(a) GDPR).
  • Claims: the data needed to establish, pursue or defend claims related to the Service. Legal basis: our legitimate interest (Article 6(1)(f) GDPR).

Providing data is voluntary, but without the account data you cannot create an account, and without the mailbox data you cannot send messages. We make no decisions about you based solely on automated processing that would produce legal effects or similarly significantly affect you.

Company data from registers

The Service shows its customers companies from public registers: companies from the National Court Register (KRS) and sole proprietorships from the Central Register and Information on Economic Activity (CEIDG). An entrepreneur entered in CEIDG is a natural person, so their data is personal data, and we are its controller. This part of the policy contains the information required by Article 14 GDPR for the people whose data comes from the registers.

We do not send this information individually to every person whose data comes from the registers: we rely on the exemption in Article 14(5)(b) GDPR, because notifying each of them individually would involve a disproportionate effort. Instead, we take other measures to protect your rights: we make this information publicly available in this policy, every message a customer of the Service sends to a company ends with a footer carrying the Article 14 GDPR notice, and you can object to the processing at any time (described below).

What data, and where from:

  • from CEIDG (dane.biznes.gov.pl): the entrepreneur’s business name, which by law contains their first and last name, the first and last name separately, tax identification number (NIP), REGON, the business address, PKD codes, the start date and status of the business, and the e-mail address, phone number and website – if the entrepreneur published them in CEIDG; we store the entry whole, as CEIDG provides it, and so also the other data it contains, among them the correspondence address, additional places of business, the address for electronic delivery, the dates the business was suspended and resumed, citizenship and information on the marital property regime;
  • from KRS (api-krs.ms.gov.pl): the company’s extract as the register publishes it, including data of the people who hold positions in it, such as board members and commercial proxies; the register publishes their names masked, but the extract’s descriptive fields may contain personal data, PESEL numbers (the Polish national identification number) included – we store the extract whole, and when displaying it we leave out every field in which we recognise a PESEL number;
  • from the Public Procurement Bulletin (ezamowienia.gov.pl) and the list of European Funds 2021–2027 projects (dane.gov.pl): won tenders and grants assigned to KRS companies;
  • from the Public Procurement Bulletin and the Baza Konkurencyjności (bazakonkurencyjnosci.funduszeeuropejskie.gov.pl): open procurement notices – we store the buyer’s name and tax identification number (NIP) only when the buyer is a company or an institution; from the GUNB register (wyszukiwarka.gunb.gov.pl): building permits granted to companies and institutions. We do not store the name or NIP of a buyer or investor who is a natural person.

Purpose: showing our customers – entrepreneurs looking for business partners – new companies in their industries, scoring how well these companies fit with a 0–100 score and showing the events that justify contact. Legal basis: the legitimate interest of ours and of our customers in establishing B2B cooperation with companies whose data is public (Article 6(1)(f) GDPR).

Recipients: organizations with an active subscription to the Service whose industries the company matches, and our providers listed below. The 0–100 score is calculated automatically from the facts in the register and the criteria the customer sets. It is not a decision about you: whether to write is always decided by a person.

We limit the data to what is necessary. We do not show customers a separate field with the CEIDG entrepreneur’s name. Of the KRS extract, we show only the number of board members and their positions, and the list of shareholders as the register publishes it: for natural persons, the name as masked by the register (the first letter and the length) and the number and value of their shares. We show only the contact details the company itself gave the register.

We refresh KRS companies every night: using the daily list of entries the register publishes, we download again the extracts of the companies the court has made a new entry for, and we mark a company struck off the register as closed. A CEIDG entry is saved once – usually in the days the business starts – and is not refreshed afterwards, so the Service does not show later changes in CEIDG, the closure of the business included. We keep the data from the registers for as long as we run the Service, also after a company has closed.

When a customer of the Service writes to your company, they do so from their own mailbox and in their own name. The controller of the data in that correspondence is their organization, and Aeris Studio processes it on that organization’s behalf as a processor. Every such message ends with a fixed Article 14 GDPR notice: who the controller is and how to contact them, the purpose and legal basis of the contact, the categories and source of the data, the recipients and your rights. The sender cannot remove or change it.

If you do not want further messages, use the unsubscribe link in the footer of the letter or reply “no” to the sender. The link works on its own: it stops further letters from that organization at once, whatever status it gave your business in the Service. The sender also marks a company that declined as rejected. The organization can prepare another message to the same company 90 days later at the earliest.

Messages that the Service’s customers send to companies are also subject to Article 398 of the Polish Electronic Communications Law, which prohibits directing commercial information to an e-mail address without the recipient’s prior consent – also when the recipient is a company. The sender of such a message, and the controller of the data in that correspondence, is the Service’s customer, and the customer is responsible for sending it lawfully. Aeris Studio sends no messages to companies from the registers in its own name and reads no replies – they reach only the sender’s mailbox. Instead of replying to the sender, you can write to us at kontakt@forlead.pl and tell us who wrote to you: we will pass your refusal on to them and mark your business as rejected in their organization in the Service. The competent authority for personal data is the President of the Personal Data Protection Office (UODO), and for commercial information sent by electronic means, the President of the Office of Electronic Communications (UKE, uke.gov.pl).

You can object to being contacted at any time (Article 21 GDPR). Every message sent through the Service carries an unsubscribe link in its footer: following it records the objection against that sender at once, with no sign-in and no reply, and the entry stays in that organization’s register of objections – from then on nobody there will send you another message through the Service. On the same page you can opt out, in one click, of messages from every organization using the Service. An objection against the catalogue itself – against our showing your business to the Service’s customers and sending it in the new-company alerts – goes to kontakt@forlead.pl and we act on it by hand.

Recipients

We do not sell data. We pass it to providers who help us run the Service as processors – they process the data on our behalf and only on our instructions:

  • Cloudflare – hosting of the Service and network infrastructure;
  • Neon – the database;
  • Resend – sending system e-mails: address confirmations, password reset links, invitations and new-company alerts;
  • GitHub – the servers on which the nightly registry import and the alerts run;
  • Stripe – processing payments, subscriptions and billing documents;
  • Anthropic – the assistant’s answers in the niche wizard, only when you use it;
  • Google – Google Analytics 4, only after you consent to analytics cookies.

Authorised people at Aeris Studio also have access to data in the Service, as far as needed to operate it and help its users. The other members of your organization see your name, e-mail address, role and who sent a message to a company.

Separate controllers

These parties receive data as separate controllers and process it in their own name, on their own terms:

  • Google – signing in with Google, sending through Gmail and copies of entries in Google Calendar, only if you use them;
  • the provider of your mailbox – the messages you send to companies leave through it;
  • the provider of your calendar – if you subscribe to the Service's ICS address in it, it fetches and keeps it on its own terms;
  • Meta Platforms Ireland Limited – only after you consent to marketing cookies. For the collection of data by Meta Pixel and its transmission to Meta, we and Meta are joint controllers, and after that Meta processes the data as a separate controller. The split of responsibilities between us is set out in Meta’s Controller Addendum: https://www.facebook.com/legal/controller_addendum; you can exercise your rights against each of us;
  • Stripe – for its own legal obligations, such as fraud prevention and anti-money-laundering checks;
  • public authorities and courts – when the law requires it.

Transfers outside the EEA

Some providers – Cloudflare, Neon, Resend, Stripe, Anthropic, GitHub, Google and Meta – are based in the United States or use subcontractors outside the European Economic Area. Data goes there only with the safeguards of Chapter V GDPR: on the basis of the European Commission’s adequacy decision (the EU-US Data Privacy Framework) for providers that take part in it, or of the standard contractual clauses adopted by the Commission (Article 46(2)(c) GDPR).

You can obtain a copy of these safeguards by writing to kontakt@forlead.pl.

Retention

We keep data as long as it is needed for the purpose we collected it for:

  • account – until it is deleted; we delete it at your request sent to kontakt@forlead.pl;
  • session – expires after 30 days without use or when you sign out; we delete the session record (IP address and browser information) when you sign out or end the session in the account settings, and keep the record of a session that expired at most until the account is deleted;
  • organization data, including company statuses, the sender profile, invitations and messages to companies – until the organization is deleted, which deletes them with it;
  • mailbox access data – until the mailbox is disconnected;
  • billing documents – 5 years from the end of the calendar year in which the tax payment deadline passed;
  • correspondence with us – as long as needed to deal with the matter, then until the limitation period for claims expires;
  • technical server logs – no longer than 12 months;
  • data in Google Analytics 4 – no longer than 14 months; cookies – for the periods given in the Cookie Policy;
  • company data from registers – as described in “Company data from registers”.

Your rights

On the terms set out in the GDPR, you have the right to:

  • access your data and receive a copy (Article 15),
  • rectify your data (Article 16),
  • erase your data (Article 17),
  • restrict processing (Article 18),
  • port the data processed on the basis of a contract or consent (Article 20),
  • object to processing based on legitimate interest (Article 21),
  • withdraw consent at any time – without affecting the lawfulness of processing before the withdrawal.

To exercise them, write to kontakt@forlead.pl. We will reply without undue delay and within one month at the latest; we may ask for information that confirms the request comes from the person the data concerns.

You also have the right to lodge a complaint with the President of the Personal Data Protection Office (UODO; ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl).

Security

We protect data with technical and organisational measures suited to the risk. Among other things:

  • connections to the Service are encrypted (HTTPS);
  • we store passwords only as a cryptographic hash, and the Google token and the SMTP mailbox password encrypted (AES-256-GCM);
  • when you sign up, change or set a new password, we check whether it appeared in known breaches: only the first 5 characters of the password’s SHA-1 hash go to the Have I Been Pwned service, and the password itself never leaves our server;
  • the number of sign-in and sign-up attempts is limited, and you can end a session on another device in the account settings;
  • only authorised people have access to data, and changes made by the Service’s support staff are recorded in a log.

Cookies

The Service uses cookies and similar technologies. The necessary ones always work, while Google Analytics 4 and Meta Pixel run only after you consent. The Cookie Policy lists the files, their purpose, how long they are kept and how to change your consent.

Changes to this policy

We update this policy when the Service, our providers or the law change. The current version is always on this page, and the date of the last change is shown at the top. We will tell account holders about material changes by e-mail.

Contact

For anything about personal data, write to kontakt@forlead.pl or to the registered office of Aeris Studio sp. z o.o. given at the start of this policy.