1. What are cookies?
Cookies are small text files a website stores on your device when you visit. They let the site remember information between page loads — for example, that you are signed in. We also use browser local storage for similar purposes; local storage is never transmitted to our servers unless you explicitly trigger an action.
2. The cookies we set
Triforce uses a single first-party cookie. We do not set advertising cookies, third-party tracking cookies, or cross-site profiling cookies.
| Name | Purpose | Type | Duration |
|---|---|---|---|
| triforce_session | Holds your signed authentication token so you remain signed in after visiting us via magic link. Without it you would need to request a new link on every page load. | Strictly necessary · First party · HttpOnly · Secure | 30 days from last activity, or until you sign out |
3. Browser local storage
In addition to the cookie above, we write a small number of keys to your browser’s local storage. Unlike cookies, local storage values are never sent to our servers automatically — they exist only in your browser.
triforce_cookies_dismissed— records that you acknowledged the cookie notice so we don’t show it again.triforce_install_silencedandtriforce_install_snoozed_until— your preference about the “Install” prompt for the progressive web app.- Service-worker cache — offline-capable resources (HTML shell, fonts, critical CSS) stored in the browser cache managed by the service worker. No personal data is cached.
4. Strictly necessary cookies — no consent required
The triforce_sessioncookie falls into the “strictly necessary” category under the EU ePrivacy Directive and equivalent national laws (UK PECR, UAE PDPL, and others). Strictly necessary cookies are those without which the core service cannot function. Because they are essential for you to receive the service you have asked for, they are exempt from prior consent requirements.
We do not use cookies for advertising, audience profiling, cross-site tracking, or any purpose beyond keeping you authenticated.
5. Third-party cookies
Triforce does not embed third-party advertising or analytics scripts that would set their own cookies on your device. Our vendor list (Vercel, Neon, Resend, Twilio, Stripe, Cloudflare R2, Mapbox, Sentry) interact with our servers, not your browser directly, so they do not set cookies in your browser.
The airport autocomplete feature on the request flow calls the Mapbox Geocoding API. Mapbox receives your search query for the purpose of returning results; it does not receive a persistent identifier and does not set a cookie in your browser.
6. How to manage or delete cookies
You can view, block, or delete cookies at any time using your browser’s settings:
- Chrome / Chromium— Settings → Privacy and security → Cookies and other site data.
- Safari (macOS)— Safari → Settings → Privacy.
- Safari (iOS / iPadOS)— Settings → Safari → Advanced → Website Data.
- Firefox— Settings → Privacy & Security → Cookies and Site Data.
- Edge— Settings → Cookies and site permissions.
Deleting the triforce_session cookie will sign you out of the Triforce portal. You can sign back in at any time by requesting a new magic link.
7. Changes to this policy
If we add new cookies or local storage keys, or change the purpose of existing ones, we will update this policy and revise the effective date above. For active account holders, we will notify you by email of any material change. The current version is always available at /cookies.
8. Contact
Questions about this policy or your data:
dispatch@triforce.flights
Triforce Mission Control — 00 800 TRI FORCE
Privacy Policy — Terms of Service