This Cookie Policy explains how Testtament ("we", "us", or "our") uses cookies and similar browser storage technologies in the Testtament web app. Read it alongside our Privacy Policy, which explains how we handle personal information.
It also explains the consent preferences and optional analytics used on the Testtament landing website. The website's consent controls apply to that website; they do not change sign-in or remembered login storage in the Testtament app.
How we use them
We use browser storage to maintain authenticated sessions, protect sign-in flows, recognise signed-in users across Testtament pages, remember your last sign-in method, and maintain continuity when you start or retry a monitoring run.
Cookies set by Testtament
| Cookie | Purpose and information stored | Duration |
|---|---|---|
wos_session | Keeps you signed in. Stores session information, including an authentication token and account details. It cannot be read by ordinary browser JavaScript. | Up to 7 days; removed when you sign out. |
testtament_oauth | Protects the sign-in or signup flow by linking the authentication response to your browser. Stores a temporary identifier, return destination, and, where relevant, invitation or signup context. | Up to 10 minutes; removed when the callback processes it. |
tt_signed_in | Lets Testtament pages recognise that your browser is signed in and show the appropriate sign-in or dashboard links. Stores a simple signed-in indicator. In production, it is shared across testtament.com subdomains. | Up to 7 days; removed when you sign out. |
testtament_last_auth | Remembers your last sign-in method and, where supplied, email address, together with a timestamp, to help you sign in again. | Up to 30 days from the latest write. Signing out does not automatically remove it. |
Cookie durations can restart when a cookie is set again. Your browser may remove cookies earlier.
Other browser storage
| Storage item | Purpose | Duration |
|---|---|---|
testtament_last_auth — local storage | Stores the last sign-in method, email address where supplied, and timestamp. It can restore the remembered login information after the corresponding cookie expires. | No automatic expiry in the current app; remains until cleared or overwritten. |
testtament:initial-poll — session storage | Stores client and monitoring-run identifiers and a timestamp to maintain continuity during onboarding or a retry. | Normally the tab's session. Removed when consumed; records older than 6 hours are rejected and removed when read. |
Older versions of the app also stored pinned-client preferences locally. The current app reads existing preferences to transfer them to your account and removes the local copy after a successful transfer.
Services provided by others
Testtament uses WorkOS for authentication, offers Google sign-in, and uses Dodo Payments for hosted checkout and billing services. When you visit those providers' pages, they may use their own cookies or similar technologies. Their notices explain those uses and the choices available to you.
Website preferences and analytics
The landing website stores your choice in testtament_cookie_consent in local storage. It records whether you allow analytics, a preference version, and the time you saved your choice. We treat the choice as valid for 180 days from the latest save, after which we ask again. You can clear it through your browser's site-data settings.
Optional Vercel Analytics measures visits and navigation on the landing website. We load it only after you choose Accept all or enable Analytics and save your preferences. Rejecting optional analytics leaves it off.
Your choices
Use the website's banner to Accept all, Reject all optional analytics, or select Customize and choose whether to allow Analytics. You can reopen Cookie settings in the footer at any time to change or withdraw your choice. Withdrawing analytics consent reloads the website to stop the already-loaded analytics runtime. Storage that remembers your consent choice remains enabled.
You can use your browser settings to block cookies, delete existing cookies, and clear local or session storage. Blocking authentication cookies may prevent you from signing in or using authenticated features.
To remove remembered sign-in information completely, clear both the testtament_last_auth cookie and the app's local storage. Signing out alone does not clear that preference. If you also use the Testtament website, you may need to clear site data for both the app and the website.
Changes to this policy
We may update this policy when our use of cookies or browser storage changes. We will publish the revised policy with an updated date.
Contact us
For questions about cookies or your personal information, contact Testtament at team@testtament.com.