Cookie policy
This translation is provided for convenience. In case of discrepancy, the French version prevails.
Last updated: 11 November 2026
What we set
ABEERY sets only the following cookies, all in its own name, on its own domain (or on a customer's custom domain, for that customer's public pages):
| Purpose | Cookie | What it is for | Where | Duration |
|---|---|---|---|---|
| Session | sb-…-auth-token (sometimes split into .0, .1…) | keeping you signed in; carries the session token | application, a coach's student portal | 400 days, renewed each time the session is refreshed; erased when you sign out |
| Session | sb-…-auth-token-code-verifier | securing sign-up and password reset | account creation, forgotten password | 400 days at most; erased once the operation is complete |
| Return and security | abeery_connection_return | bringing you back to the right screen after connecting a network; erased once used | application | 20 minutes |
| Return and security | intake_connection_return | the same role, during setup | application | 15 minutes |
| Return and security | abeery-recovery | allowing the password change after the link received by email; erased once the password has been changed | password reset | 15 minutes |
| Preferences | abeery_ui_locale | remembering the interface language | application | 12 months |
| Preferences | abeery-space | remembering the active Workspace, for a person who belongs to several Workspaces | application | 12 months |
| Visit matching | abeery_vid | on a customer's tracked links and "My links" page, only if that customer has turned on visit matching (off by default): a randomly drawn token that links a visit to a form filled in later | tracked links, "My links" | 30 days, not renewed |
Session, return and preference cookies are strictly necessary: they cannot be turned off without preventing use of the service. This also applies to the active Workspace cookie, without which a person who belongs to several Workspaces could not stay in the one they chose.
The visit matching token is set only when the customer has turned this setting on; without it, no cookie is set and the click is counted without a token.
No data is kept in the browser's local storage (localStorage).
On ABEERY's own website (home page, pricing, demo, customer journey, frequently asked questions, blog), no cookie is set. The demo request form keeps the first name and email entered in the tab's memory (sessionStorage) until the tab is closed, to display the confirmation page.
Course students
A student who signs in to a coach's course portal uses the same session cookie as the application. Videos are played in the player of our video host, Bunny, shown from its own domain (player.mediadelivery.net); their thumbnails also come from its servers. This player may set its own cookies or use the browser's storage, under Bunny's rules; ABEERY neither chooses nor reads them. The same applies to a free preview lesson on a course's public page.
Payment
Paying for a subscription, an offer or a course takes place on Stripe's page, to which you are redirected. Stripe applies its own cookies there, on its own domain. No Stripe script is loaded on ABEERY's pages.
What we do not set
ABEERY uses no advertising cookie and no third-party tracker for targeting purposes, and sells no browsing data. Fonts are served by ABEERY; no page loads any resource from Google. A YouTube video placed on "My links" is shown by its thumbnail, copied to our servers: YouTube is contacted only if the visitor clicks.
Audience measurement on public pages
The public pages created by our customers (website, booking page, forms) may include audience measurement. On these pages, it is carried out without cookies: a randomly drawn visit identifier lives in the tab's memory (sessionStorage) and disappears when the tab is closed, and only that identifier, the traffic source and the pages viewed are kept. The same method applies to the measurement script a customer can place on their own website; it does not create an identifier when the browser asks not to be tracked (Do Not Track, Global Privacy Control).
Tracked links and "My links" pages set a cookie only if the customer has turned on visit matching: this is the token described above.
When a customer turns on named attribution — that is, linking a visit to an identified contact — it is up to that customer to inform its visitors and obtain their consent. This option is off by default.
Your choices
You can set your browser at any time to refuse cookies or to warn you about them. Refusing strictly necessary cookies will prevent you from signing in to your Workspace or to the course portal.