Cookie notice
Last updated . Version 2026-09-11.
LaunchProof uses cookies for sign-in. It does not run advertising cookies, session replay, or behavioural analytics.
Who uses this information
EXPONENTIAL EDUCATION S.R.L. operates LaunchProof. Our identity, registered address, processing purposes, and your data-protection rights are in the privacy notice. Contact contact@exponentialeducation.ro about browser storage.
Storage used by LaunchProof
Cookies are small values stored in your browser. Authentication cookies keep your session working and protect the sign-in exchange. They are needed when you request sign-in. Reading our public information does not require an account.
| Name | Purpose and trigger | Lifetime |
|---|---|---|
launchproof-session | WorkOS AuthKit session on the LaunchProof host, set during sign-in. Necessary for authenticated access. A deployment using the SDK default name may call it wos-session. | Up to 400 days, renewed during session refresh. Session validity can end earlier; signing out removes the application session. |
wos-auth-verifier-* | Protects a particular WorkOS sign-in attempt. The suffix distinguishes simultaneous attempts. Necessary for the sign-in exchange. | 10 minutes, or removed when the sign-in exchange completes. |
recipe | A saved display-recipe preference from an explicit selection. Current public pages use a fixed design and do not set this cookie. It is not used for tracking. | 365 days after selection, or until you remove it. |
The application session and sign-in verifier are HTTP-only, so application JavaScript cannot read them. Production HTTPS cookies use the Secure attribute. LaunchProof requires its session cookie to be limited to its own host; it is not a shared cookie for every CompanyNerve product. The cookie's storage lifetime is not a promise that the account remains signed in for that long.
The current LaunchProof application does not use localStorage or sessionStorage for analytics, advertising, or report storage. Report files selected for upload are read by the page; they are uploaded when you submit the report, rather than being placed in browser persistent storage.
WorkOS, Google, and Stripe pages
Sign-in takes you to WorkOS AuthKit and, if you choose Google, Google's sign-in service. Those providers can use their own cookies for authentication, security, and preferences on their domains. Consult WorkOS's cookie information and Google's cookie information. Cookies on a provider's own website are separate from the application cookies listed above.
When payment services are available, opening Stripe Checkout or the billing portal takes you to Stripe. Stripe uses cookies and related device information to operate payment pages and prevent fraud. Its cookie policy and cookie settings describe the cookies, lifetimes, and choices for its pages. LaunchProof does not embed Stripe tracking on its public legal pages.
Consent and controls
Strictly necessary storage for a service you explicitly request does not require optional-cookie consent under the applicable ePrivacy rules. The display preference is stored only in response to your selection. We will obtain consent before introducing non-essential tracking where required, with a way to withdraw it. There is currently no LaunchProof advertising or analytics consent to accept or withdraw.
You can inspect, block, or remove cookies in your browser's site-data settings. Signing out ends the application session. Clearing site data removes the saved display preference and may require you to sign in again. Blocking authentication cookies can prevent sign-in. To control provider cookies, use that provider's settings and your browser settings for its domain.
Cookie choices are separate from accepting the terms or placing an order. Changes to browser storage will be reflected in this notice.