Privacy Policy
Last updated October 14, 2026
We collect only what we need to run Ferrete, we never sell it, and we never use your code to train AI models. This policy explains what we collect, why, who helps us process it, and the choices and rights you have.
The short version
- Your code is yours. Specs, requirements, code and evidence you put into Ferrete belong to you and your company. We process them only to provide the service.
- No AI training. We never use customer content to train or fine-tune AI models, and our AI providers are contractually barred from doing so.
- No selling, no ad tracking. We don't sell personal data, share it for targeted advertising, or use advertising or analytics cookies.
- You're in control. You can download your personal data and delete your account yourself, in Settings → Account.
- Questions? Email akeem@ferrete.ai. We reply within 30 days, usually much sooner.
Who we are and what this covers
Ferrete ("Ferrete", "we", "us") makes tools that generate, verify and deliver firmware: the website at ferrete.ai, the Ferrete Cloud web app and API, the Forge command-line tool, the Ferrete Edge on-device library and the Ferrete extension for Visual Studio Code (together, the "Services").
This policy covers personal data we decide how to use (as a "controller"): visitors to our website, people who contact us, and the people who sign in to the Services.
When a company uses the Services, the content its team puts in, and the personal data inside that content, is processed on that company's behalf. For that data we act as a "processor" (or "service provider") under our Terms of Service and, where applicable, a data processing agreement with the customer. The customer's own privacy notice applies to it, and requests about it go to the customer first; we'll help them answer.
Software you run yourself, such as Forge on your computer, Ferrete Edge on your devices or the Visual Studio Code extension, sends nothing to us unless you connect it to Ferrete Cloud.
What we collect
| Category | What it includes | Where it comes from |
|---|---|---|
| Account and profile | Name, work email, company, job title, password (stored only as a salted hash), two-factor settings, single sign-on identifiers, terms acceptance | You, or your company's identity provider |
| Customer content | Specs, approved requirements, source code, generated code, reference files, build logs, evidence reports, release packages and notes | You and your team |
| Device and fleet data | Device identifiers, firmware versions, update state, uptime and health counters reported by your devices | Your gateways and devices |
| AI usage | Which feature was used, the model, token counts and cost. The prompts and replies themselves only if your workspace turns on AI transcripts | The Services |
| Usage and technical data | IP address, browser and device type, pages and features used, timestamps, sign-in and security events, audit log entries | Collected automatically when you use the Services |
| Billing | Billing contact, plan, invoices and payment status. Card details go straight to Stripe; we never see or store full card numbers | You and Stripe |
| Communications | Messages from our contact form, emails, support requests and notes from calls | You |
| Private page access | The work email you enter to open our private pages, the one-time code (stored only as a hash), and when and from which IP address you opened them | You |
We don't ask for sensitive personal data such as health, biometric or financial account information, and you shouldn't put it in specs or code. If your firmware handles such data, keep real records out of the Services and use test values instead.
How we use it, and why
We use personal data only for the purposes below. If you are in the European Economic Area, the United Kingdom or Switzerland, the second column is the legal basis we rely on.
| Purpose | Legal basis |
|---|---|
| Provide the Services: accounts, builds, proofs, evidence reports, releases and fleet updates | Performing our contract with you or your company |
| Run the AI features you choose to use, by sending the relevant spec, requirements and code to an AI provider | Performing our contract |
| Send service emails: sign-in codes, invitations, approval requests, alerts, billing notices and changes to these terms | Performing our contract |
| Keep the Services secure: prevent fraud and abuse, enforce rate limits, keep audit logs, investigate incidents | Our legitimate interest in a secure service; legal obligations |
| Bill and keep financial records | Performing our contract; legal obligations such as tax law |
| Improve the Services using aggregated, de-identified statistics, such as how often proofs succeed. Never your content itself | Our legitimate interest in improving the product |
| Answer inquiries, arrange demos and, if you opt in, send product news | Our legitimate interest in replying to business contacts; your consent where the law requires it |
| Comply with the law and enforce our terms | Legal obligations; our legitimate interest in protecting our rights |
Where we rely on legitimate interests, we have weighed them against your rights and expectations. You can object at any time; see Your rights.
Your code is not training data
We never use customer content to train, fine-tune or otherwise improve AI models: not ours and not anyone else's. Our AI providers are contractually prohibited from training on it, and we use zero-data-retention terms where the provider offers them.
If your workspace connects its own AI account (Anthropic, Amazon Bedrock or Google Vertex AI), requests go to that provider under your company's own agreement with it, and that agreement governs how the provider handles them.
How the AI features handle your data
- AI runs only when someone in your workspace uses an AI feature, such as drafting requirements, generating or repairing code, explaining a failed check or proposing a change.
- For each request we send only what the task needs: the spec, the approved requirements, the code being written or repaired, the checker's results and the most relevant excerpts of your project's reference files.
- By default requests go to Anthropic. Your workspace can switch to its own Anthropic, Amazon Bedrock or Google Vertex AI account in Settings → AI provider.
- We record which feature was used, the model and the token count, for billing and your usage reports. We keep the prompts and replies themselves only if an admin turns on AI transcripts, and then for 30 days.
- Every piece of AI-generated code is checked by independent tools and reviewed by people in your team before it's used. AI doesn't make decisions about you.
Who we share it with
We don't sell personal data, and we don't "share" it for cross-context behavioral advertising, as California law defines those terms. We disclose it only as follows.
Service providers (sub-processors) that run parts of the Services for us, under written contracts that limit them to providing those services and require them to protect the data:
| Type of provider | What they do for us | Data involved | Location |
|---|---|---|---|
| Cloud infrastructure | Hosting, storage, build workers, backups and key management | All data held in Ferrete Cloud | United States; EU on request for Enterprise |
| AI model provider | Drafting requirements, generating and repairing code | The content sent with each AI request | United States |
| Payment processor (Stripe) | Payments and invoicing | Billing contact and payment details | United States |
| Website hosting | Serving this website and the contact form | Website requests and contact-form messages | United States |
| Email and support tools | Email and customer support | Correspondence with you | United States |
The named list of our sub-processors is on our Sub-processors page for customers and design partners, and anyone can request it at akeem@ferrete.ai. If your workspace connects its own AI account (Amazon Bedrock, Google Vertex AI or Anthropic), that provider processes your AI requests under your company's agreement with it. We give customers at least 30 days' notice before adding a new sub-processor, and customers may object.
Within your workspace. Owners and admins of your workspace can see its members, their roles and activity, and its audit log.
Integrations you turn on, such as Slack, webhooks, your single sign-on provider or your CI system, receive the data you configure them to receive.
For legal reasons: when required by law, court order or other valid legal process, or to protect the rights, property or safety of our users, the public or Ferrete. Where allowed, we tell the affected customer first so it can respond.
Business transfers: as part of a merger, acquisition or sale of assets, subject to this policy, with notice to you.
With your consent, or at your direction.
Cookies and similar technology
The Ferrete Cloud app uses two cookies, both strictly necessary: one keeps you signed in (fr_session) and one protects forms against cross-site attacks (fr_csrf). Neither is used for tracking.
Our website sets no cookies. When you open our private pages with a one-time code, your browser keeps a key in its local storage for 7 days so you don't need a new code on every page. Clear your browser's site data to remove it.
We use no advertising or third-party analytics cookies, so there is nothing to opt out of. We also honor Global Privacy Control signals.
How long we keep it
| Data | How long |
|---|---|
| Account and profile | While your account is active. Deleting your account erases it right away from active systems, and from backups within 90 days |
| Customer content | Until you delete it or close the workspace. A deleted workspace has a 30-day grace period, then is removed from active systems within 30 days and from backups within 90 days |
| Build logs | As set by your workspace: 30, 90 or 365 days, or for the life of the workspace |
| Evidence reports and approvals | For the life of the workspace, because they are your compliance record |
| AI transcripts | 30 days, and only if your workspace turns them on |
| Security and audit logs | For the life of the workspace. They keep the names of people who took actions, even after those people delete their accounts, so each workspace keeps an accurate record |
| Billing and tax records | As long as tax and accounting law requires, usually 7 years |
| Contact-form messages and sales correspondence | Up to 24 months after our last contact |
| Private page access log | 24 months. One-time codes expire after 10 minutes |
Your rights
Depending on where you live, you may have the right to:
- know what personal data we hold about you and get a copy of it;
- correct data that is wrong or incomplete;
- have your data deleted;
- receive your data in a portable format;
- object to processing based on our legitimate interests, including direct marketing;
- restrict how we process your data;
- withdraw consent you've given, without affecting earlier processing; and
- complain to your data protection authority. We'd appreciate the chance to help first.
How to use them. Download your personal data and delete your account yourself in Settings → Account, or email akeem@ferrete.ai. We'll confirm your identity, usually by email, before acting, and respond within 30 days (45 days where US state law allows, with notice if we need longer). You can use an authorized agent; we'll ask them for proof that you authorized them. If we decline a request, you can appeal by replying to our decision, and we'll answer the appeal within 45 days.
Content in a customer's workspace. If your data is part of a workspace your employer controls, we'll pass your request to that company and help it respond.
California and other US states. In the last 12 months we collected the categories of personal information listed in What we collect, for the purposes in How we use it, from the sources listed there. We disclosed them only to the recipients in Who we share it with. We don't sell or share personal information, we don't collect sensitive personal information beyond the sign-in credentials you choose, and we won't treat you differently for using your rights.
International transfers
We are based in the United States, and we and our sub-processors process data there. When we transfer personal data from the European Economic Area, the United Kingdom or Switzerland, we use the European Commission's Standard Contractual Clauses, with the UK Addendum and Swiss amendments, or another lawful transfer mechanism. Contact us for a copy. EU data residency is planned for Enterprise customers.
How we protect it
- Encryption in transit (TLS) and at rest, including stored secrets such as single sign-on settings and AI provider credentials.
- Each customer's builds run in separate, short-lived workers.
- Passwords are stored only as salted hashes; two-factor authentication and single sign-on are available, and workspaces can require them.
- Firmware signing keys stay with you. Ferrete only checks signatures and never holds your private key.
- Our staff tools never show customer specs or code, require two-factor authentication, and record every action in an append-only log.
- Backups are encrypted and checked after they're written.
No system is perfectly secure. If a breach affects your personal data, we'll notify affected customers without undue delay, and you where the law requires. To report a vulnerability, email akeem@ferrete.ai.
Children
The Services are professional tools for businesses and aren't directed at children. We don't knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, email akeem@ferrete.ai and we'll delete it.
Changes and contact
We'll post any update here with a new date. For material changes, we'll email account owners at least 30 days before they take effect.
Questions, requests or complaints: akeem@ferrete.ai, Ferrete, United States. Customers who need a data processing agreement can ask the same address.
Questions about this page? Email akeem@ferrete.ai.