Privacy policy
How Reload Tech Inc. handles information when you visit or use Firedrill.
Effective November 18, 2026 · Version 2026-11-18.
Who we are and what this covers
Firedrill is a product and brand of Reload Tech Inc. (“Reload,” “we,” or “us”). This policy covers our website, account and business relationships, and managed simulation service, including its web application, remote MCP server, API, CLI, and SDK clients.
Reload is responsible for information used for our own purposes, including accounts, customer relationships, website and product measurement, security, and support. For personal information an organization places in customer content, we generally act on its instructions. That organization’s policies and administrators also govern your access. Direct requests about its content to that organization; we can help route them.
Information we handle
Synthetic data is not automatically anonymous. Real personal information in a fixture, repository, prompt, tool call, or capture may become stored test material. Browser video and traces are not automatically redacted and can contain page content, cookies, network bodies, or secrets. Review the content and capture options you enable.
Your agent usually runs in your repository, local process, or CI. Firedrill receives the inputs, outputs, measurements, events, and files that you or your authorized client submit to it; it does not automatically collect everything in your local repository, browser, or external accounts. An explicitly configured integration can provide additional selected content.
Run and account records are saved in our managed database. Uploaded evidence and other supported files are stored in Google Cloud Storage with related identifiers and metadata in the database. They remain subject to access controls and applicable retention or deletion rules. Private content is not automatically published or contributed to a community catalog.
Creating an account does not require a payment card. Applicable subscriptions, included credits, top-ups, discounts and sponsored grants are shown before you accept a paid arrangement. Billing records can include purchased and consumed credits, payment status and provider references. We do not receive full payment-card details from hosted checkout. Records required by an agreement or by law may be retained.
| Category | Examples and sources |
|---|---|
| Account and organization | Name, email, authentication identifiers, organization and project membership, roles, invitations, authorized client connections, preferences, and records of accepted terms and privacy-policy versions from you, your administrator, or an identity provider. |
| Projects and integrations | Repository identifiers and authorized repository content, build sources, tool packages, configurations, integration permissions, and designated credentials. |
| Simulations and evidence | Synthetic records, datasets, scenarios, tool-call inputs and outputs, state changes, events, checks, run outputs, rubric criteria, assessments, comparisons, snapshots, reports, and audit records. Browser or computer-use runs may include screenshots, video, and traces that your runner submits. |
| AI features | Selected instructions, scenario descriptions, candidate scenarios, scoring rubrics, relevant run outputs and evidence, provider responses, and evaluation records used for requested AI-assisted assessment or recommendations. |
| Support | Name, email, messages, attachments you provide, delivery records, derived contact identifiers, abuse-prevention records, and relevant campaign context. |
| Customer relationships and emails | Verified business contact and organization details, memberships, aggregate product activity, and relevant activity dates used for customer support and CRM. Communications you request can also involve delivery, bounce, complaint, unsubscribe, or suppression records. |
| Website and technical activity | Page and interaction events, browser/device information, network and security logs, IP addresses handled by infrastructure or measurement providers, and permitted cookie, campaign, or advertising identifiers. |
Why we use information
Where European or UK data protection law applies, grounds depend on the activity: performing a contract, legitimate interests in operating and protecting our business and assisting customers, legal obligations, and consent for optional analytics and advertising. You can withdraw consent or object to processing based on legitimate interests. Necessary account information may be required to deliver a requested service; optional measurement is not.
Simulations and assessments concern software behavior. They are not designed to make decisions about a person’s employment, credit, health, or other legal or similarly significant interests. A simulation result is not a substitute for the safeguards those decisions require.
- Provide accounts, authorized coding-agent connections and integrations, simulation environments, runs, evidence, comparisons, and requested AI-assisted features.
- Understand resource use, operate shared capacity, apply the credit terms you accept, and maintain service and business records. An estimate or reserved maximum is distinct from actual credit consumption.
- Answer questions, deliver operational notices, diagnose failures, and maintain the service.
- Manage customer relationships and provide support using account and aggregate activity metadata. Optional promotional communications require any consent required by applicable law and must respect unsubscribe and suppression choices.
- Protect accounts and infrastructure, prevent abuse, investigate incidents, and meet legal obligations.
- With the applicable choices, understand website use and measure advertising campaigns.
Who receives information
Providers receive information relevant to their roles. A provider listed here is not necessarily enabled for every visit or account. Website measurement providers do not receive world records merely because their integration exists on the marketing site.
- Organization members and administrators see information allowed by their roles. Recipients you share or export content with receive that content.
- We may disclose information to professional advisers, in response to lawful requests, to protect rights and safety, or in a business transaction with appropriate protections.
- External links and third-party services have their own policies. Footer social links do not embed those platforms’ tracking widgets.
| Provider or recipient | Role |
|---|---|
| Google Cloud and Firebase | Website and application infrastructure, databases, storage, jobs, and operational logging. |
| WorkOS | Account authentication and organization identity flows. |
| GitHub | Authorized repository source access, integration, and configured repository automation. |
| Attio | Customer relationship management using verified contact and organization details, memberships, activity dates, and aggregate product-usage counts—not raw Tool records, source code, prompts, run outputs, or evidence contents. |
| Resend | Configured service email delivery, including recipient details, email contents and links, delivery receipts, and bounce or complaint handling. A configured provider does not mean optional marketing sequences are enabled. |
| Slack | Internal service or customer-relationship notifications when configured, using relevant account or operational metadata rather than simulation contents. |
| Jev (Typesafe) and configured AI evaluator providers | Requested AI-assisted assessments or scenario recommendations using selected instructions, criteria, run outputs, and relevant evidence. Your independently operated agent may use other providers under your own arrangements. |
| Intercom | Requested chat, contact messages, and support handling when configured. |
| Calendly | Meeting scheduling on the enterprise booking page, including availability, contact details you submit, and booking confirmations. |
| PostHog and Google Analytics | Optional website usage measurement with analytics permission, including PostHog session replay of this website with form inputs masked. PostHog also provides consented product analytics associated with your verified account email in the application, where session replay is disabled. |
| Google Ads, Meta, Reddit, LinkedIn, and X | Optional website campaign and conversion measurement when the provider is configured and advertising permission is given. An absent tracking identifier leaves that provider disabled. |
AI assessment and simulation history
When you request AI-assisted assessment or recommendations, selected scenario context, rubrics, recorded outputs, and relevant evidence may be transmitted to the configured evaluator. Assessment results, provider responses needed to interpret them, and submitted evidence can remain in project history. Ending a run, disconnecting MCP, or cleaning up a temporary workspace does not by itself delete that history.
Your existing agent and its model remain under your control. Information it sends to its own provider follows your arrangements with that provider. Retention and training settings are not the same for every provider or account. Ask about applicable arrangements before submitting content that needs particular contractual protections.
Analytics, advertising, and contact requests
Optional analytics and marketing start off. Allow either, both, or neither. The Analytics choice covers website and Firedrill product analytics, including visits, usage and signup sources. On this website it also allows PostHog page view, click and session replay measurement; form inputs are masked and the contact form is never recorded. Advertising providers can use identifiers and browsing activity across sites, which can count as sharing for cross-context advertising under some laws. Decline marketing in Cookie settings or enable Global Privacy Control, which keeps marketing off on this website.
With permission, first and latest campaign details are used for up to 90 days. When Analytics is allowed and no Do Not Track or Global Privacy Control signal is present, public account-entry links can carry limited campaign labels and a referring hostname to Firedrill's application. Advertising click IDs require both Analytics and Marketing permission. The handoff excludes credentials, account identity, arbitrary query values and page contents; it is not proof of identity or access. The application validates these hints and binds them to its original browser authorization request before associating them with a verified account. Campaign parameters are not added to authenticated or signed app links. You can change product analytics in the application's settings. A requested contact message can include campaign labels from your current visit even with optional tracking off; advertising IDs are excluded without marketing permission.
After a contact request is confirmed delivered, analytics permission allows us to associate your submitted name and email with your PostHog visitor profile. Submitted names, email addresses, and messages are not included in Google Analytics or advertising event properties. Contact form contents are excluded from automatic interaction capture. Providers can still receive technical identifiers described above.
If product analytics is allowed, we associate allowlisted navigation and product-usage events with your verified email. Private prompts, source, reports, tool contents, request bodies, headers, console output and screen recordings are not collected by this analytics integration. Deliberately captured simulation evidence is separate from analytics and follows the execution permissions and retention settings you authorize.
You can change product analytics in the application's settings independently of website marketing. The application honors Do Not Track and Global Privacy Control by leaving optional collection off. Choices do not automatically carry between browsers or devices.
Opening chat loads Intercom to provide the conversation you request. An email entered in the contact form does not authenticate you or give access to earlier account conversations. Sending a message is not consent to unrelated promotional email.
Opening the enterprise booking page loads Calendly to show available meeting times. Booking details are submitted directly to Calendly and shared with the meeting host. Calendly provides its own privacy notice and cookie choices in the scheduler. Firedrill does not prefill the scheduler with contact-form details or forward booking details to website analytics.
Use Cookie settings on the Firedrill website to change your choices.
Customer email choices
Creating an account, joining an organization, authorizing a coding agent, or contacting support does not by itself subscribe you to optional promotional emails. CRM synchronization is separate from marketing enrollment. Website cookie and advertising choices do not constitute email-marketing permission.
If we send optional promotional emails, you can use their unsubscribe or preference link, or contact support@firedrill.run. Unsubscribing does not stop necessary account, security, invitation, or requested service notices. Delivery and suppression records can be kept to avoid duplicate or unwanted emails and respect applicable requirements.
How long information stays
Retention depends on purpose, your organization’s settings and agreement, operational needs, and legal requirements. We consider whether an account is active, whether content supports a referenced build or run, support and dispute needs, security investigations, and statutory recordkeeping. There is no single retention period for all information.
Evidence follows its applicable retention policy. Deleting an evidence bundle does not necessarily delete run metadata, account records, authoring history, or exported copies. Referenced builds may remain. Backups, logs, and legally required records can outlast a live record and follow separate schedules.
Website consent choices are valid for 180 days; campaign records for 90 days; conversion-deduplication records for up to 90 days after their latest update. Local storage does not expire itself: the site checks these limits before use. Contact delivery and abuse-prevention storage is configured for asynchronous seven-day lifecycle deletion. Support conversations have separate retention.
Request deletion or applicable retention information at privacy@firedrill.run. Where available, organization settings also provide retention, export, or deletion controls. We assess requests, verify identity where appropriate, and explain lawful exceptions. Logging out, revoking a client connection, or disconnecting an integration does not itself erase all information.
Security and international processing
Access controls, scoped credentials, encryption in transit, and infrastructure protections are intended to protect information. No service guarantees absolute security. Limit permissions and keep secrets out of test content. Report suspected exposure without including a live secret.
Reload and its providers may process information in the United States and other countries where they operate. Infrastructure location alone does not guarantee every identity, support, model, or measurement provider processes information only there. Where a transfer requires safeguards, the applicable arrangement must meet those requirements. Ask us about the safeguards and their availability for review, and confirm any required residency or transfer commitment before using the affected feature.
Your choices and rights
Depending on your location and the processing, you may have rights to access, correct, delete, or obtain a portable copy of information; restrict or object to processing; withdraw consent; and opt out of sale, sharing, or targeted advertising. We will not discriminate against you for exercising applicable rights.
Email privacy@firedrill.run with the associated email or organization and your request. Do not send passwords or identity documents unless we explain a necessary secure verification process. An authorized agent may act with appropriate authority. Other requests may require verification or coordination with the organization controlling the content. Website cookie choices require no account.
You may object to direct marketing and withdraw optional permission at any time. Withdrawal affects future processing, not past lawful processing. Ask us to review a declined request, or complain to your competent regulator, including your local EU supervisory authority or the UK Information Commissioner where applicable.
Use Cookie settings on the Firedrill website to change your choices.
Children and updates
Firedrill is a developer and business service for adults, not directed to children. Do not create an account if you are under 18. Contact us if you believe a child’s information has been provided improperly.
Each published policy identifies its effective date. We may revise it as our practices change and will provide notice of material changes and obtain consent where required. Accepting the Terms of Use or acknowledging this policy is separate from optional analytics, advertising, or email-marketing consent. Reload Tech Inc. is responsible for this policy; Firedrill is the product name.