Cookies policy
The cookies, browser storage, and privacy choices used by Firedrill.
Effective November 18, 2026 · Version 2026-11-18.
Cookies and similar technologies
Reload Tech Inc. uses these technologies to operate Firedrill and, with your choices, measure website use and advertising. Cookies are browser files sent with matching requests. Local storage keeps values on a website’s origin; session storage lasts for a tab session. Pixels and SDKs can send events without creating a visible cookie.
Choices do not automatically apply to another browser or device. The Analytics choice explicitly covers this website and Firedrill product analytics. With permission, a limited signup handoff associates campaign information with your verified account. Advertising identifiers also require the Marketing choice. You can change product analytics in the application's settings. On this website, the Analytics choice also allows PostHog session replay, with form inputs masked; session replay in the application is disabled. Necessary account cookies are not advertising permission.
Use Cookie settings on the Firedrill website to change your choices.
What you can choose
Rejecting optional tracking does not prevent browsing or sending a contact request. Providers run only when configured and when their conditions are met. Not every listed provider is active on every visit.
| Category | Purpose and control |
|---|---|
| Essential | Remember your choices, support secure sign-in and application context, and deliver communications you request. Does not depend on optional tracking permission. |
| Analytics | Configured PostHog and Google Analytics measurement of visits and interactions, including PostHog page views, clicks and session replay of this website. Replay masks form inputs and never records the contact form or booking calendar. Off until you opt in. |
| Marketing | Configured Google Ads, Meta, Reddit, LinkedIn, and X website campaign and conversion measurement. Off until you opt in; kept off by Global Privacy Control. Providers without a configured identifier stay disabled. |
| Requested support | Intercom Messenger loads when you ask to open chat and can use storage to maintain that conversation. |
| Meeting scheduling | Calendly loads on the enterprise booking page to display availability and handle bookings. Its scheduler provides separate cookie settings; Firedrill’s analytics choices do not set Calendly’s choices. |
Website storage we control
Local storage does not expire itself. These periods describe when Firedrill stops using records and checks for cleanup, not automatic deletion in an unopened browser. Withdrawing all optional permission removes our attribution and conversion records. The consent record remains to respect your choice.
The contact form keeps its current message and retry information in page memory, not persistent browser storage. Server-side delivery and abuse-prevention records are described in the Privacy Policy.
| Name and type | Purpose | Period of use |
|---|---|---|
| firedrill:consent:v3 · local storage | Essential record of analytics and marketing choices. | 180 days from your choice. |
| firedrill:attribution:v1 · local storage | First/latest campaigns with optional permission. Click IDs require marketing permission. | Up to 90 days per campaign record. |
| fd_acquisition_v1 · first-party cookie | First and latest non-direct campaign labels, referring origin, and known public landing page, shared across firedrill.run subdomains for signup attribution. Requires website analytics permission; not created under Do Not Track or Global Privacy Control. Contains no account identity, advertising click IDs, or sign-in credentials. | Up to 90 days per visit record; removed when website analytics permission is withdrawn. |
| firedrill:conversions:v1 · local storage | Up to 100 random submission IDs to prevent duplicate measurement. | Up to 90 days after the latest update. |
Application cookies and preferences
Necessary cookies support sign-in, browser authorization, invitation confirmation, and protection against unauthorized requests. The application uses Secure, HttpOnly, host-scoped authentication cookies. Session expiry or revocation may end access sooner than a cookie's lifetime. The Analytics choice on the website explicitly covers website and Firedrill product analytics; you can change product analytics in the application's settings. Session replay in the application is disabled.
| Name | Purpose | Lifetime |
|---|---|---|
| firedrill-product-analytics-consent-v1 · local storage | Record of an analytics choice, including a refusal. This does not enable session replay. | 180 days from your choice. |
| __Host-fd_portal_flow_<flow> · cookie | Bind a WorkOS sign-in flow to the browser that started it. | 10 minutes. |
| __Host-fd_portal_invitation_<context> · cookie | Bind an invitation confirmation to the browser that opened it. | 5 minutes. |
| __Host-fd_portal · cookie | Authenticate the application session. | Up to 7 days; authorization may expire or be revoked sooner. |
| __Host-fd_portal_csrf · cookie | Protect deliberate application actions against cross-site request forgery. | Up to 7 days; refreshed by the application. |
| __Host-fd_ui · cookie | Access a selected synthetic Tool interface. | Until the selected interface session expires or access is revoked. |
| firedrill-theme · local storage | Remember application theme. | Until cleared. |
| Application action-recovery records · session storage | Remember pending Tool setups, selected options, and deliberate requests so an uncertain response can be recovered without blindly repeating an action. Records are scoped to the signed-in user and selected organization or project. | Tab session, or until the relevant record is cleared or completed by the application. |
Provider technologies
These are conditional examples, not a claim that every cookie is set. Names and lifetimes depend on account settings, browser limits, and provider changes. Local storage may remain until cleared. WorkOS and other authorized identity providers also control necessary cookies on their own sign-in and browser-authorization domains.
| Provider | Examples and duration |
|---|---|
| PostHog | ph_<project_token>_posthog analytics storage is used only with permission. Browser and configured provider limits apply; local storage has no built-in expiry. With permission, website session replay uses this storage to group the recording of a visit. |
| Google Analytics / Ads | Analytics _ga and _ga_<container-id>: default 2 years, subject to browser limits. Advertising _gcl_*: typically 90 days. |
| Meta | Pixel events and identifiers such as _fbp or _fbc when marketing is allowed. See provider policy for current storage and duration. |
| Pixel and attribution identifiers when marketing is allowed. Duration depends on provider configuration; see its notice. | |
| Examples include li_fat_id and lms_ads: 30 days; li_sugr: 90 days; bcookie: 1 year; lidc: 24 hours. Which apply depends on provider behavior. | |
| X | Configured website pixel events and campaign identifiers, including twclid, only when marketing is allowed. Provider storage and duration depend on its configuration and current policy. |
| Intercom | Requested support: session cookie up to 1 week; device identifier up to 270 days, refreshed with activity. Messenger local storage can persist until cleared. |
- PostHog storage
- Google cookie information
- Google Analytics cookie lifetimes
- Meta cookies policy
- Reddit business cookies notice
- LinkedIn cookie table
- X cookies information
- Intercom Messenger storage
Change or withdraw your choices
Essential only refuses optional tracking. Accept all allows both categories. Choose settings lets you select them separately. Cookie settings in the footer reopens your choices. Scrolling, closing a dialog, or continuing to browse is not consent.
Withdrawal stops future optional processing through our website integrations. The page reloads when needed to stop provider listeners. This does not undo events already sent or remove every vendor cookie. Use browser site-data controls and provider privacy tools to clear remaining identifiers or request deletion.
Global Privacy Control keeps marketing off. Global Privacy Control and Do Not Track also prevent the shared signup-attribution cookie. Clearing browser data may cause the site to ask again. If your browser cannot save a choice, we apply it for the visit and tell you. Essential-only fallback behavior prevents a reload from silently restoring optional permission.
Use Cookie settings on the Firedrill website to change your choices.
Questions and updates
Reload Tech Inc. is responsible for this policy. Email privacy@firedrill.run with questions. We will update the policy when technologies or purposes materially change and seek a new choice where required.