COOKIE POLICY
Last updated July 17, 2026
This Cookie Policy explains how Fielded Inc. ("Fielded," "we," "us," or "our") uses cookies and similar technologies on https://www.tryfielded.com and the Fielded application (together, the "Services"). It explains what these technologies are, why we use them, and the choices you have.
Read this alongside our Privacy Policy, which explains what personal information we collect and how we handle it, and our Terms of Service.
1. WHAT ARE COOKIES?
Cookies are small text files placed on your device when you visit a website. They are widely used to make websites work, to remember your preferences, and to report information to site owners. Similar technologies — such as browser local storage and session storage — store data in your browser for comparable purposes. Where this policy says "cookies," it covers those technologies too.
Cookies set by the site you are visiting are called first-party cookies. Cookies set by another domain are third-party cookies.
2. HOW WE USE COOKIES
We only use cookies that are strictly necessary to operate the Services. We do not use cookies for advertising, and we do not use analytics, profiling, or cross-site tracking cookies. We do not sell or share cookie data with advertisers, and we do not permit third parties to place advertising cookies through our Services.
Specifically, we use cookies to:
- keep you signed in and maintain the security of your session;
- protect our sign-in endpoints against automated abuse;
- remember that you entered the pre-launch access password, while the Services are in private beta.
Because these cookies are strictly necessary to deliver a service you have asked for, they are exempt from consent requirements under the EU/UK ePrivacy rules, and we therefore do not show a cookie consent banner. If we ever add analytics or marketing cookies, we will update this policy and ask for your consent first where the law requires it.
3. COOKIES WE USE
The table below lists the cookies used across the Services. Exact names may vary slightly as our providers update their software.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
fielded_site_access | Fielded (first party) | Remembers that you entered the pre-launch access password, so the site does not ask again on every page. Contains no personal data. | 30 days |
__session | Clerk (first party) | Holds your signed-in session as an encrypted token. Set only after you sign in. HttpOnly, so scripts cannot read it. | Session / until sign-out |
__client_uat | Clerk (first party) | A timestamp telling the browser whether a signed-in session exists, so pages render the right state. Readable by scripts by design; contains no personal data. | 1 year |
__clerk_db_jwt | Clerk (first party) | Used by Clerk development instances in place of __session. You will not normally encounter this on the live site. | 1 year |
sb-<project>-auth-token | Supabase (first party) | Keeps your session valid against our database while you use the dashboard. Set only after you sign in. | Session, refreshed on use |
__cf_bm, _cfuvid | Cloudflare, via Clerk | Bot detection protecting our sign-in provider's endpoints. Set on Clerk's own domain, not ours. | 30 minutes / session |
We also store a small amount of data in your browser's local storage under the keys
__clerk_environment and clerk_telemetry_throttler. These are used by our sign-in provider to cache configuration and to limit how often diagnostic events are sent. They are not used to track you.4. THIRD-PARTY SERVICES
We rely on a small number of processors to run the Services. Their use of cookies is governed by their own policies:
- Clerk — authentication and session management. Clerk sets the session cookies listed above, and Cloudflare bot-protection cookies on Clerk's own domain. See Clerk's Privacy Policy.
- Supabase — our database and session store. See Supabase's Privacy Policy.
- Stripe — payment processing. Checkout is hosted by Stripe: when you start a subscription you are taken to Stripe's own checkout page, and any cookies Stripe sets are placed there, under Stripe's control, not on our site. See Stripe's Privacy Policy.
- Sentry — error monitoring, so we can diagnose faults. It is configured without session replay and sets no cookies on our site. See Sentry's Privacy Policy.
- Vercel — hosting and content delivery. See Vercel's Privacy Policy.
5. YOUR CHOICES
Because the cookies we use are strictly necessary, there is nothing to opt out of within the Services — but you remain in control of your browser.
Most browsers let you view, delete, and block cookies through their settings. Be aware that blocking or deleting the cookies listed above will prevent you from signing in and will stop the Services from working. Instructions for common browsers:
You can also clear cookies stored by any site via your browser's privacy settings, and most browsers offer a private or incognito mode that discards cookies when you close the window.
6. DO NOT TRACK
Some browsers send a "Do Not Track" (DNT) signal. There is no common industry standard for how to respond to it, and we do not track users across third-party websites, so our behaviour is the same whether or not DNT is enabled.
7. CHANGES TO THIS POLICY
We may update this Cookie Policy from time to time — for example, if we add a new provider or a new category of cookie. When we do, we will revise the "Last updated" date above. Where changes are significant, or where the law requires consent, we will give you notice and ask for your agreement before the change takes effect. Please revisit this page periodically.
8. CONTACT US
If you have questions about our use of cookies, you can reach us at hello@tryfielded.com, or by mail at:
Fielded Inc.
125 Marine Dr
Clarenville, Newfoundland and Labrador A5A 1M6
Canada
125 Marine Dr
Clarenville, Newfoundland and Labrador A5A 1M6
Canada
For questions about personal data more generally, including how to exercise your privacy rights, contact privacy@tryfielded.com or read our Privacy Policy.