Ridgecrest Works LLC d/b/a BlazeFleet · Privacy policy

Version 1.0

Privacy Policy

This Privacy Policy describes the collection, use, disclosure and retention of personal information by Ridgecrest Works LLC d/b/a BlazeFleet, and the choices and rights available to individuals.

Effective · Last updated

Encrypted transit

Where we forward end-to-end encrypted content, we do not decrypt or retain the payload.

Technical information

Technical information is used for performance and reliability improvements. Customer business content is excluded from technical optimization datasets.

Optional processing

Optional processing requires authorization. Content provided for that purpose is used only for the relevant customer and is not used for shared models.

1. Scope and roles

Ridgecrest Works LLC is a California company doing business as BlazeFleet (“BlazeFleet,” “we,” “us” and “our”). This Policy applies to our website, applications, accounts and services. Our services are intended for individuals aged 18 or older and are currently offered in the United States, Canada and United Kingdom. We do not knowingly collect children's personal information.

We act as controller for personal information processed for our own business purposes, including account administration, billing, support and the technical improvement described in this Policy. When processing organization-controlled information on a customer's behalf, we act under its instructions and applicable service and data-processing agreements. Those arrangements do not limit our independent legal obligations.

Where UK law applies, our legal bases are, as applicable: performance of a contract with the individual; legitimate interests in managing organizational accounts and providing proportionate security and technical improvement; consent where required for optional activities; and compliance with legal obligations. An employer's contract does not constitute an individual's consent. Use of the services does not constitute consent to all processing.

2. Information collected and purposes

We collect information directly from individuals, from their organizations and supporting service providers, and through use of the services.

Categories, processing purposes, recipients and retention.
CategoryExamplesPurpose and recipientsRetention
Contact and accountName, work email, organization, sign-in details and permissionsProvide access, administer accounts and communicate; relevant staff and contracted providersRelationship duration and necessary business records
Applications and supportCompany, industry, fleet-size range, hardware choices and messagesReview applications, reply, resolve issues and keep contact records; relevant staff and delivery and contact-management providersFollow-up or resolution, then necessary records. Application and contact records: up to 24 months after our last contact
Technical informationDevice characteristics, software versions, resource use, timing and technical errorsOperation, reliability and compatibility; internal teams and infrastructure providersTechnical telemetry: six months maximum, or a shorter agreed period
Security and administrationIP addresses, access records, permissions and security eventsProtect services, manage access and investigate incidents; authorized staff and infrastructure providersAs needed for protection, investigations and legal obligations
Usage and billingAccount-linked activity, request and token totals, invoices and payment statusQuotas, billing, reconciliation and disputes; relevant staff and payment providersOperational usage may remain for 13 months; financial records separately
Customer contentPrompts, responses, files and codeOnly the requested service or separately authorized purpose; access depends on that purposeNo payload retention in encrypted transit; other authorized handling follows its agreed terms

3. Customer content

We do not use routine customer prompts, outputs, files or code to train, fine-tune or evaluate our own models. Content intentionally submitted for support is used solely to resolve the relevant issue and is not used for model training or evaluation.

Support submissions should contain only information necessary to address the request. Unnecessary sensitive information and credentials should not be included.

4. Organization accounts and third-party services

An organization may control its users' access, configuration, activity records and retention. Customer-selected systems, integrations and copies are governed by the organization's controls and the relevant providers' terms. The encrypted-transit restriction in Section 3 does not govern their storage practices.

Where a customer authorizes another AI provider to receive content, that provider's privacy terms and retention practices apply to its processing. Such authorization does not permit BlazeFleet to reuse the content independently. Requests concerning organization-controlled information should be directed to the organization's administrator. We remain responsible for requests concerning our own processing.

5. Technical information and service improvement

We process technical information to operate and secure the services and to improve performance, reliability and compatibility. We minimize collection, remove personal information from technical analysis and exclude customer business content. Deidentified technical information is used internally for technical optimization and not for semantic analysis of customer content.

Operational records are not necessarily anonymous. Access, administration, usage and security records may identify accounts, devices or individuals. Removal of a name alone does not constitute anonymization. We maintain deidentified information in that form, apply safeguards against reidentification and do not attempt reidentification. Technical telemetry is not sold or used for advertising.

Technical telemetry, including performance records from which personal information has been removed, is retained for no more than six months. We comply with shorter retention periods agreed with the customer's organization. This limit applies to copies held by us and our processors, including recovery copies. Customer-controlled exports are subject to the customer's retention policies.

6. Optional processing

A customer may authorize additional processing, including customer-specific AI development or analysis. An authorized representative must affirmatively approve the information, purpose, access and retention before processing begins. Ordinary use of the services does not constitute authorization. Customers must have authority to provide the information, and we remain responsible for our independent obligations. Organizational authorization does not replace an individual's consent where required by law.

Information provided for an authorized purpose is used exclusively for the relevant customer. It is not reused across customers or for our own general models. Withdrawal of authorization stops future optional processing. The agreed terms describe the treatment of completed work and necessary legal records without limiting applicable withdrawal or deletion rights. Withdrawal does not reverse processing already completed.

7. Retention

The six-month technical-telemetry limit is separate from ordinary business records. Account-linked usage needed for billing, quotas, reconciliation or disputes may remain for 13 months. Account, financial, security and support records may remain as necessary for the relationship, legal obligations, documented disputes or legal holds.

Where no fixed retention period applies, we consider the processing purpose, sensitivity, contractual obligations, applicable legal requirements and whether a less detailed record would suffice. We delete or deidentify information when retention is no longer justified. Recovery copies expire under their backup schedules; deleted information is not restored for routine processing.

Aggregated or deidentified business metrics, such as daily client totals, device-type totals and request volumes, may be retained longer for internal planning. Such metrics must not reasonably identify an individual or disclose a particular customer's business activity. We apply safeguards against reidentification and do not attempt reidentification. Identified financial and support records are maintained separately.

8. Service providers and disclosures

Our selected primary providers are Google Cloud Platform for infrastructure, Stripe for payments and PostHog for product analytics. Primary service locations are in the United States; providers' operations may involve other countries. Providers receive information necessary to perform their functions, subject to applicable contractual protections. Payment providers may also act independently for fraud prevention and legal compliance. PostHog collection is limited to an explicit event allowlist; autocapture and session replay are disabled.

Cloudflare provides website hosting and application storage. When configured, Resend processes application information for email notifications and contact management. Contact records may include the submitted name, email, company, industry, fleet size, hardware details and message. A stored application, email notification and contact record are separate copies and may have different retention periods.

We may disclose information to comply with legal requirements, protect rights and security, or carry out a business transaction subject to appropriate protections. Information processed abroad may be subject to lawful access by foreign courts or authorities. Where international-transfer rules apply, transfers must have a legally valid basis and the required safeguards. Information about applicable safeguards, and a copy where available, may be requested using the contact details below. We do not claim Data Privacy Framework certification.

9. Privacy choices and rights

Essential storage is used for security, service operation and recording privacy preferences. Optional website analytics is disabled unless the individual consents. Consent may be changed through Analytics preferences in the footer. Withdrawal stops new optional events and clears unsent events; it does not erase records already received.

This website sends selected, consented page and form events to Google Analytics, which may set analytics cookies. These events exclude form contents, email addresses, company and fleet details, raw query strings and referrers. Submission of an application does not constitute a subscription to marketing emails or change existing marketing preferences.

We do not sell personal information or share it for cross-context behavioral advertising. This restriction applies regardless of whether a Global Privacy Control signal is received. We do not currently respond to browser Do Not Track signals.

Depending on applicable law, you may request access, correction, deletion or portability, restrict or object to processing, or withdraw consent. UK users can complain to the Information Commissioner's Office. Canadians may challenge accuracy or compliance and contact the Office of the Privacy Commissioner of Canada. Where the CCPA applies, Californians also have rights to know, correct, delete, limit certain sensitive-information uses, opt out of sale or sharing, and receive equal treatment for exercising rights. See the California privacy rights guide.

Right to object. Where UK law applies, individuals may object to processing based on legitimate interests on grounds relating to their particular situation. We assess the request and cease processing unless a lawful exception permits it to continue.

Requests may be submitted to privacy@blazefleet.ai. Reasonable verification of identity or an authorized agent's authority may be required; creation of a new account is not required. We assist with directing organization-controlled requests to the responsible organization, explain applicable exceptions and respond within legally required periods.

10. Security and policy changes

We use reasonable technical and organizational safeguards, including encrypted transport, access controls and permissions appropriate to the information. Authorized staff and providers receive access needed for their work. Encryption does not make information unreadable to an authorized recipient, and no system guarantees absolute security.

We notify affected customers, individuals or authorities of security incidents where required by law. We identify revisions to this Policy by updating its version and last-updated date. Material changes take effect on the stated effective date, with advance notice and consent where required by applicable law.

11. Contact information

Privacy questions, requests and complaints may be submitted to:

privacy@blazefleet.ai
Ridgecrest Works LLC d/b/a BlazeFleet
220 Montgomery St, Suite 810
San Francisco, CA 94104
United States

A small choice about data.

Optional analytics helps us understand whether this page is useful. Your name, email and message never enter analytics.

If you allow it, selected page and form events go to Google Analytics.

About your data