Cookie Policy
How we use cookies and similar technologies to keep the product working.
We use cookies and similar storage to remember locale, keep sessions, protect forms, and understand how the marketing site is used. This policy explains what we store, why, and how you can control it.
This document is sample content for a starter project. Update the table below to match the cookies your deployment actually sets, including any analytics or advertising tags you add.
Cookies are small files stored by your browser. We also use related technologies such as local storage, session storage, and short-lived tokens. In this policy, “cookies” covers those technologies unless we say otherwise.
Why we use cookies
- Keep you signed in and restore a session after a refresh.
- Remember locale and theme so the interface stays consistent across visits.
- Protect sign-in, registration, and contact forms from automated abuse.
- Measure aggregate traffic on marketing pages when analytics is enabled.
- Store a record of cookie choices if you add a consent banner.
We do not use cookies to sell personal information. Details about personal data sit in the privacy policy.
Essential cookies
Authentication and security cookies are required for signed-in features and bot protection. The product cannot work correctly without them. These cookies are typically first-party, set on our domain, and last for the session or a limited number of days.
Examples of essential storage:
- Session identifier used by the auth library to recognize a signed-in user.
- CSRF or bot-challenge tokens on forms.
- A short-lived locale cookie so the first paint matches your language.
You can still block these in the browser, but sign-in, account settings, and locale detection may fail.
Preferences
Locale and theme preferences may be stored in cookies or local storage so the interface stays consistent across visits. Preference cookies are first-party. They do not track you across other websites.
If you clear site data, the product falls back to defaults until you choose a locale or theme again.
Analytics and performance
If you enable web analytics in this starter, a first-party or provider cookie may record page views, referrers, and coarse device information. That data is used to understand which marketing pages are useful, not to build an advertising profile.
Analytics cookies are not required for the core product. If you add a consent banner, they should load only after consent in regions that require it.
We do not currently set advertising or social-media tracking cookies in the default starter. If you add those tags later, list them here and obtain consent where required.
Cookie categories
| Category | Purpose | Typical duration | Required | | -------------- | --------------------------------- | ---------------------- | ----------------------- | | Authentication | Keep you signed in | Session to a few weeks | Yes | | Security | Bot protection and form integrity | Minutes to a day | Yes | | Preferences | Locale, theme, cookie choices | Up to one year | No, but the UI degrades | | Analytics | Aggregate traffic measurement | Up to one year | No |
Exact names and lifetimes depend on the libraries you enable. Review your browser's site-data panel after a local sign-in to confirm what is actually stored.
Third-party cookies
Some optional integrations set cookies on their own domains:
- Identity providers during OAuth sign-in.
- Payment processors on checkout pages.
- Email or support widgets if you embed them.
- Analytics vendors if you connect a third-party script.
Those cookies are governed by the third party's policy. We only load them when the related feature is in use.
Managing cookies
You can control cookies in several ways:
- Use your browser settings to block, delete, or time-limit cookies for this site.
- Use private browsing, which usually drops cookies when the window closes.
- Sign out to invalidate the current session cookie.
- Clear local storage from developer tools if a preference is stuck.
If you block cookies, sign-in and locale detection may stop working. Essential cookies will be set again the next time you visit unless you keep the block in place.
On mobile devices, cookie controls live in the browser or WebView settings, not in the operating system's general privacy screen.
Most browsers let you delete cookies for a single site. After you do that, you will need to sign in and set preferences again.
Do Not Track and Global Privacy Control
Browsers may send Do Not Track or Global Privacy Control signals. If we add a consent or analytics layer that honors those signals, we will describe the behavior here. Until then, treat browser cookie settings as the reliable control.
Changes to this policy
We may update this policy when we add or remove cookies, change providers, or the law changes. The updated version will be posted on this page. If a change is material, we will try to notify account holders by email or an in-product notice.
Contact
Questions about cookies can be sent through the contact page. Related documents: privacy policy and terms and conditions.
Build without boundaries
Join thousands of founders who've eliminated setup complexity and deployed globally with TurboEdge. Start building today - build your SaaS faster than ever.
Start building