SESSIOS
TermsPrivacy

Privacy notice

Last updated 11 November 2026

The short version: if you join the waitlist, we keep your email address so we can invite you to the Sessios beta, and, if you arrived through someone’s shared ticket, whose ticket it was. Your source code never reaches us. You can ask us to delete your address at any time, and every email we send carries an unsubscribe link. We count visits with PostHog, hosted in the EU: anonymously and without cookies unless you accept, and in more detail if you do.

Who is responsible

The controller is [LEGAL NAME], [FULL ADDRESS], registered under [SIREN]. For anything on this page, write to hello@sessios.app.

What we hold, and why

The waitlist

The email address you type into the waitlist form, and the date you joined. We use it for one thing: to write to you when your beta invite is ready, and occasionally with news about the beta. The legal basis is your consent, which you give by submitting the form and can withdraw at any time.

Shared tickets and referrals

When you join, you get a ticket with a name on it, taken from the part of your email address before the @ (for example “jane doe” for jane.doe@…). The ticket and its link are shown only to you. If you choose to share it, the name becomes visible to anyone who opens the link or sees its preview; the link never contains your email address.

If someone joins through your shared link, we note on their waitlist entry that your ticket brought them (the name on your ticket and a random identifier), so we can thank and prioritise the people who spread the word. Basis: our legitimate interest in knowing how people find Sessios.

Who is on the site right now

While a page of this site is open and visible, your browser tells our server, every 30 seconds and each time you move to another page, which page it is on. That is all it sends: the page’s path (for example /legal/privacy, without anything after a ? or #) and a random identifier for that browser tab. The identifier is created in your browser, kept in its session storage (not in a cookie), and is gone when you close the tab, so it cannot follow you from one visit to the next or to other sites. A hidden tab sends nothing.

We use it to count how many people are on the site and on which pages, and how many tabs visited today and in the last seven days. We do not store your IP address or your browser’s user agent with it. To stop one address from flooding the counts, a keyed hash of your address (not the address itself) is kept for 24 hours and then deleted. Each visitor record is deleted after 30 days.

If your browser sends a Global Privacy Control or Do Not Track signal, none of this happens: the page sends nothing at all. Basis: our legitimate interest in knowing how many people use the site and which pages they read. Nothing here is used for advertising, combined with other data, or shared.

If you are signed in, the same signal goes with your session instead of a random identifier. Our administrators can then see that your account is on the site, which page you have open, and when your session was last active. Those page records are deleted after 24 hours; the “last active” time is kept with the record of your session.

Analytics, with PostHog

We measure how the site is used with PostHog, on its EU cloud: the data is stored in Frankfurt, Germany. Your browser sends it to this site’s own address (www.sessios.app/ingest), which passes it on to PostHog; no PostHog script is loaded from anywhere else. What is measured depends on your answer to the banner.

Before you answer, or if you decline. Each page you open, the page that sent you here (the referrer) and any campaign tags in the link (utm_source and the like), the buttons and links you click, your browser, operating system, screen size and approximate location (country and city, worked out from your IP address, which PostHog then discards instead of storing). Nothing is stored in your browser: no cookie, no local or session storage. To count unique visitors, PostHog’s servers compute a hash of your IP address and browser with a secret that changes every day, so a visit today cannot be linked to one tomorrow. No recording is made and you are not identified, even when signed in. Basis: our legitimate interest in knowing how many people visit and how they find the site. If you arrived through someone’s shared ticket, the ticket’s code is removed from every address before it is sent.

If you accept. PostHog also keeps a random identifier in a cookie (ph_…_posthog) and in your browser’s local storage, so your visits are linked together; it records your sessions as replays (what the page showed, your mouse movements, clicks and scrolling), builds heatmaps of where people click and how far they scroll, and captures more of what you do on the page. Everything you type into a form is hidden in replays and email addresses are kept out of them. Shared ticket pages are never recorded. On the account page, the admin console, the welcome questions and the page that links the desktop app, only the page view is counted: no replay, no clicks, no heatmap. If you are signed in, your visits are tied to your account: PostHog receives your account’s identifier and email address. Our server also tells PostHog when you finish signing in, answer or skip the welcome questions (the choices, never what you typed under “other”), start a checkout, or link a computer. Basis: your consent.

Your answer is kept in your browser’s local storage (sessios.analytics-consent) and, if you accepted, in a cookie our server can read (__Host-sessios_consent). We ask again after 13 months if you accepted, and after 6 months if you declined. If your browser sends a Global Privacy Control or Do Not Track signal, we go further than declining: PostHog is not loaded at all and nothing is sent to it, not even the anonymous count. You can change your mind at any time, as easily as you answered: , here or at the foot of every page. Withdrawing deletes PostHog’s identifier from your browser and returns to the anonymous count; to have what was already collected erased, write to us.

Abuse protection

When you submit the form, your IP address is used to limit how many signups can come from one place, so nobody can flood the list. It is held only in the server’s memory, for about a minute at most and never beyond a restart, and is not stored with your email address. Our host keeps its own request logs for a short period to run and secure the service. Basis: our legitimate interest in keeping the waitlist free of abuse.

Your account

If you create an account (to use the Sessios desktop app), we hold your email address, a hash of your password if the account was created with one before sign-in moved to GitHub and Google (never the password itself), whether and when you confirmed your address, and the sign-in providers you linked. For each session we keep when it started, the IP address and browser user agent it started from, and when it was last active; for each computer you linked, its name and when it last checked in. If you hold a licence we keep its plan and dates, and if you pay, the Stripe customer and subscription status Stripe reports to us (Stripe holds your card, we never see it). Basis: the contract you enter by creating the account. Our administrators can see all of this, and every change they make to an account is recorded.

Two questions after you sign up

After your first sign-in we ask where you are as a developer (from just starting out to senior, or not a developer at all) and how you found Sessios (a friend, a social network, a search engine, an AI assistant, a shared ticket, or somewhere else, which you may describe in a few words). Answering is optional: you can skip, and we do not ask again. If you answer, we keep your two answers, anything you wrote under “other”, and when you answered; if you skip, only that you skipped and when.

We use them to understand who Sessios is for and which channels bring people to it, mostly as counts across all accounts. Our administrators can also see the answers of a given account. They are stored with your account, never shared, and never used for advertising. Basis: our legitimate interest in knowing who uses Sessios and how they found it. They are erased with your account.

What we do not hold

Your code, your prompts, your agents’ output and your git history stay on your machine: Sessios runs locally and does not send them anywhere. Our analytics are about this website only, never the app. We do not advertise, we do not use the analytics for advertising or share them with anyone else, and we do not sell anything about you to anyone.

Cookies

This site sets no advertising cookie, and none at all for analytics unless you accept them; the presence count above uses no cookie either. If you sign in, it sets two session cookies, __Host-nv_at (lasts about 15 minutes) and __Host-nv_rt (lets the first be renewed, lasts 30 days), which keep you signed in, and for the few minutes a sign-in with GitHub or Google takes, __Host-nv_oauth, which ties that sign-in to your browser. Scripts on the page cannot read them, and the session cookies are deleted when you sign out. They are strictly necessary for the sign-in you asked for and need no consent.

Only if you accept analytics: PostHog’s ph_…_posthog cookie and its local storage entries, which last up to one year, and our __Host-sessios_consent cookie, which remembers that you accepted for 13 months. The banner, and the it comes back with, are how you give or withdraw that consent.

Who else sees it

  • Resend (Resend, Inc., United States) stores the waitlist and sends our emails. It receives your email address.
  • Vercel (Vercel Inc., United States) hosts this site and handles its requests, including your IP address.
  • [API HOST] hosts the accounts service and its database, in [COUNTRY].
  • Stripe (Stripe Payments Europe, Ltd., Ireland) processes payments, if you make one.
  • PostHog (PostHog Inc., United States) runs our analytics, with the data stored in its EU region in Frankfurt, Germany. It receives what the analytics section above describes.

Resend and Vercel move data outside the European Economic Area, and PostHog, whose data stays in the EU, may still be reached by its staff from the United States. Those transfers rely on the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses. Nobody else receives your data, except where the law obliges us to hand it over.

How long

  • Your email address: until you unsubscribe, ask us to delete it, or the beta waitlist closes, whichever comes first.
  • Your IP address: not stored by us; the host’s request logs expire on their own. The keyed hash of it used against abuse of the presence count: 24 hours.
  • Presence: a visitor tab’s record, 30 days; a signed-in session’s page records, 24 hours. The tab’s identifier itself is deleted by your browser when the tab closes.
  • Analytics in PostHog, on its free plan: events, one year; session replays, up to 30 days; then deleted by PostHog. Should we move to a paid plan, where longer periods are possible, we will keep these limits or update this page first. The identifier in your browser: up to one year, or until you withdraw your consent or clear your browser’s data. The daily hash used without consent cannot be linked from one day to the next.
  • Your answers to the two questions after sign-up: as long as your account, and erased with it.
  • Your account: until you delete it from your account page, which erases it; session and device records, [RETENTION].

Your rights

You may ask for access to your data, correct it, have it erased, restrict or object to its processing, receive it in a portable form, and withdraw your consent at any time.

To exercise any of these rights, write to hello@sessios.app. We answer within one month. If our answer does not satisfy you, you may complain to the CNIL — cnil.fr — or to the supervisory authority where you live.

Changes

If we change how any of this works, for example when accounts open with the public release, we will update this page and change the date at the top, and tell you by email before it applies to you.