You should know what Sendet remembers in your browser and why.
We use cookies to keep you signed in and remember access to password-protected pages. We also use browser storage for display preferences, subscription reminders, and information that helps us understand how people find Sendet.
01
Cookies used on Sendet
These cookies are stored for the Sendet website. Supabase, our authentication provider, helps manage the sign-in cookies.
Access to a private page
so_access_<page>
When it’s created
When you enter a page’s password or follow a valid access link from an update email.
What it does
Remembers that this browser has access to that page, so you don’t have to enter the password every time. It contains an access token, not the password itself.
When it expires
Password entry sets 7 days. Email access links initially set 30 days. Each page visit resets the expiry to 7 days from that visit.
Access to a password-protected Village
so_village_password_<page>
When it’s created
When you enter the password for a public page’s Village, or enter the family page password for a private page.
What it does
Remembers password access to that Village. It contains an access token, not the password itself. A changed password can invalidate that access sooner.
When it expires
7 days from password entry. Entering the password again starts a new 7-day period.
Your Village reservations
so_village_guest_<page>
When it’s created
When you reserve a Village task without signing in, manage a saved guest reservation, or follow a valid guest reservation-management link from an email.
What it does
Recognizes your guest reservations so you can manage them from this browser. It contains a guest identifier and access token, not your name or email. It does not replace the current Village password or invitation requirements.
When it expires
365 days from when it is set. Creating or managing a guest reservation, or following a valid management link, may set it again and restart that period.
Your return page after sign-in
auth_next
When it’s created
When you start signing in, including signing in to comment.
What it does
Remembers which Sendet page to return you to after sign-in.
When it expires
10 minutes, or earlier when sign-in completes.
Your account session
sb-<project>-auth-token
When it’s created
When you sign in to a Sendet account.
What it does
Stores authentication information so Sendet can recognize your account and maintain your session.
When it expires
Set with a 400-day cookie lifetime, which may restart when authentication information is refreshed. Signing out clears it from this browser. Your login can become invalid before the cookie expires.
Sign-in verification
sb-…-auth-token-code-verifier
When it’s created
When you start a sign-in flow that uses a browser verification step.
What it does
Helps connect the sign-in request with the browser that started it. Related names ending in -code-verifier may track pending sign-in attempts.
When it expires
Normally removed as the sign-in flow is processed. Leftover cookies can retain the authentication library’s 400-day expiry unless cleared sooner.
<page> identifies a Sendet page; <project> identifies our authentication service. Some authentication cookies are split into smaller pieces with numbered endings such as .0 and .1. Those pieces serve the same purpose and follow the same expiry rules.
These durations describe the expiry Sendet requests. Your browser may clear storage sooner. Cookie expiry and the validity of an authentication session are separate things.
02
Other information stored in your browser
Browser storage is different from cookies, but it can still remember information between visits. We include it here for completeness. The first three items use local storage; “How you found Sendet” uses tab session storage.
Light or dark mode
theme
When it’s created
When you switch between light and dark mode.
What it does
Remembers your display preference.
When it expires
No automatic expiry. Remains until replaced or cleared by you or your browser.
Which updates are new
so_last_visit_<page>
When it’s created
Shortly after you open a Sendet page, unless we detect a supported browser privacy signal.
What it does
Stores the time of your visit so we can mark later updates as “New.”
When it expires
No automatic expiry. Updated on later visits, or removed when browser storage is cleared.
Your subscription reminder
subscribed:<page>
When it’s created
After a subscription is successfully submitted from this browser.
What it does
Remembers that the subscription form was completed and displays a subscription reminder. It stores a yes/no marker, not the subscriber’s name or email.
When it expires
No automatic expiry. Remains until browser storage is cleared.
How you found Sendet
sendet_marketing_attribution
When it’s created
When a visit includes campaign information in its link or an external referring website, unless we detect a supported browser privacy signal.
What it does
Remembers campaign labels, the referring website’s hostname, and the landing page during that tab session. We include this information with analytics events to understand how people find and use Sendet.
When it expires
The tab session, normally ending when the tab is closed. Browser session restoration may preserve it.
The subscription marker is a browser reminder. Clearing it does not unsubscribe anyone, and it may remain after someone unsubscribes through an email link.
03
Analytics without cookies
We use Vercel Web Analytics to understand visits and interactions with Sendet. The analytics service does not use cookies, although our campaign attribution feature uses the tab storage described above. Read Vercel’s analytics privacy explanation.
Sendet also records page and update view counts without creating a separate tracking cookie.
Your browser’s privacy signals
When we detect Global Privacy Control or Do Not Track, we skip analytics, campaign attribution collection, view counting, and the last-visit feature used for “New” badges. Cookies needed for sign-in and page access still work, as do theme and subscription reminders.
04
Cookies during checkout
When you continue to Stripe checkout, Stripe may use its own cookies and browser storage to process payments, maintain checkout, and help prevent fraud. Common examples include:
Other websites linked from a Sendet page may also use their own cookies when you visit them.
05
Clearing cookies and storage
You can remove Sendet’s cookies and browser storage through your browser’s site-data settings.
Clearing cookies may sign you out or require you to enter a page password again. Clearing browser storage may reset your theme, subscription reminder, and “New” badges.
Clearing browser data does not delete your account, posts, payment records, or email subscriptions. Our Privacy Policy explains those records and your deletion options.
Something you’d like us to explain?
If you have a question about something you see in your browser, contact admin@sendet.app.