Legal
Cookie Policy
Without your consent the Service sets only the files it needs to work. Google Analytics 4 and Meta Pixel load only once you allow them, and only on public pages – never in the app after you sign in.
Last updated:
About this policy
This policy describes the cookies and similar technologies used by the Forlead service (formerly Aeris; the “Service”), run by Aeris Studio sp. z o.o. How we process personal data is described in the Privacy Policy.
What cookies are
Cookies are small text files a website stores in the browser and reads on later visits. Browser storage (localStorage and sessionStorage) works in a similar way: a website can save information there without creating a cookie. This policy covers both.
The Google Analytics and Meta Pixel files are set on the Service’s domain by those companies’ scripts, and Google and Meta read and use them.
Necessary
The Service does not work without these files, so they need no consent and cannot be switched off in the cookie settings. The Service itself sets them:
- forlead.session_token (with the __Secure- prefix over HTTPS) – keeps you signed in; expires after 30 days without use or when you sign out;
- forlead.state – only while signing in with Google, confirms that the sign-in started in this browser; 5 minutes;
- forlead-mailbox-state, forlead-mailbox-verifier, forlead-mailbox-return – only while connecting a Gmail mailbox, they secure that connection; 10 minutes;
- forlead_consent – stores your choice about analytics and marketing cookies and the date of the decision; 365 days.
The Service also sets one file that only makes signing in easier: forlead.last_login_method remembers which method was last used to sign in on this browser (Google or e-mail), so the sign-in page can mark it; 180 days. Signing in works without it, and you can delete it in your browser settings.
In browser storage (localStorage) the Service keeps the chosen theme (theme), the plan picked on the pricing page (forlead.intended-plan) and hashes of the e-mail address and account ID that spare you a second password prompt on the address confirmation page (forlead.email-proof; they stop working after one hour or after 7 days). For as long as the tab is open (sessionStorage) it also keeps what you typed into forms – never passwords – and the state of some screens, such as the address confirmation; this storage is cleared when the tab is closed.
Cloudflare, our hosting provider, may set a technical file that protects the Service from automated traffic (such as __cf_bm, up to 30 minutes).
Analytics
We set these files only after you consent to analytics cookies; before that, the Google Analytics 4 script does not load at all.
Google Analytics 4 shows us how many people visit the Service’s public pages, which pages they read, where they come from (for example, a search engine), what devices they use and roughly where they are. We send page addresses without link tokens and without e-mail addresses, and after a sign-up or sign-in only the event itself, without your e-mail address, name or any other data from the form. According to Google, Google Analytics 4 does not log IP addresses.
- _ga – tells browsers apart; up to 2 years;
- _ga_<ID> – keeps the state of the current visit; up to 2 years.
The provider is Google Ireland Limited. Google’s policy: https://policies.google.com/privacy
Marketing
We set these files only after you consent to marketing cookies; before that, the Meta Pixel script does not load at all.
Meta Pixel tells Meta that a public page of the Service was visited and, after a sign-up, that it was completed. This lets us see whether our ads on Facebook and Instagram lead to sign-ups, and lets Meta show them to people who have visited the Service. Meta may link this information to your Facebook or Instagram account. On pages whose address contains a link token or an e-mail address, the pixel sends nothing.
- _fbp – recognises the browser for Meta’s ads; about 90 days;
- _fbc – stores the click ID when a Meta ad leads to the site; about 90 days.
For the collection of this data and its transmission to Meta, we are a joint controller with Meta Platforms Ireland Limited; after that, Meta processes it as a separate controller, on its own terms: https://www.facebook.com/privacy/policy/. The split of responsibilities between us and Meta is set out in Meta’s Controller Addendum: https://www.facebook.com/legal/controller_addendum
How to change your consent
You can change or withdraw your consent at any time with the “Cookie settings” button on this page and in the footer of the Service’s public pages, the sign-in and sign-up pages included. Withdrawing switches off Google Analytics 4 and Meta Pixel and deletes their _ga, _ga_*, _fbp and _fbc files from this browser. It does not affect the lawfulness of what happened before the withdrawal.
Your choice applies to the browser it was saved in. You can also delete and block cookies in your browser settings:
- Chrome: Settings > Privacy and security
- Firefox: Settings > Privacy & Security
- Safari: Settings > Privacy
- Edge: Settings > Privacy, search, and services
Blocking the necessary files makes signing in impossible. Refusing analytics and marketing cookies limits nothing in the Service.
Changes
We update this policy when the files or tools we use change. The current version is always on this page, and the date of the last change is shown at the top. If we add a tool that needs consent, we will ask for it again.