1. Who we are
Frazer AI LLC, a Florida limited liability company at 1221 Brickell Ave, Ste 900, Miami, FL 33131 (“Frazer”, “we”, “us”), provides the Frazer platform and the website frazer.ai. For the personal data this policy describes, Frazer is the controller: we decide why and how it is processed.
To reach us about privacy, write to privacy@frazer.ai. We have not appointed a data protection officer, because the law does not require one for the processing we do; the people who read privacy@ are responsible for privacy at Frazer.
2. What this policy covers, and what it does not
It covers personal data about:
- visitors to frazer.ai, its docs and its other pages, and to our status page at frazerstatus.com;
- people who write to us: through the sign-up queue at
/start, the contact form at/contact, or any of our email addresses; - account holders: people with a Frazer account, as members of an organization or on their own, and billing contacts;
- people who report a vulnerability, abuse or a copyright claim to us.
It does not cover the data customers put into Frazer: code, files, databases, model prompts and outputs, mail they send, workloads and the personal data inside them. For that data the customer is the controller, Frazer processes it only on the customer’s instructions, and the Data Processing Addendum applies. If you are, for example, a recipient of mail a customer sent through Frazer Mail, or a user of an application a customer runs on Frazer, please contact that customer first; we will help them answer you.
It also does not cover servers customers bring to Frazer, which run in the customer’s own site or provider account.
3. The website
3.1 No cookies, no trackers
frazer.ai sets no cookies. It loads no analytics, advertising or social-media scripts, no third-party fonts and no embedded content from other sites. Its security policy allows scripts from frazer.ai only. We do not use tracking pixels, fingerprinting or session recording.
3.2 One setting in your browser, on docs pages
Some docs pages show code samples in tabs, for example the same task in the console, the CLI and the API. When you pick a tab, your browser saves which one you picked in its local storage, under a key named after the set of tabs, so the next page shows the same tab. It is saved only after you pick a tab, it never leaves your browser, and it is not used to identify you. You can clear it in your browser’s settings at any time. Because it only does what you asked for, it needs no consent banner.
3.3 Server logs
Our website host receives the requests your browser sends, as every web server does: your IP address, the page asked for, the time, your browser’s user agent and the referring page. The host keeps these logs for a short time to run and protect the site. We use them only to keep the site working and secure, never to build a profile of you.
3.4 Machine-readable copies
Every page has a Markdown copy at its address plus .md, and llms.txt lists them. Fetching them works like any other request, under the same logs.
4. Our forms
4.1 What the forms collect
- Sign-up queue (
/start): your work email, name and company, and, if you choose, your role, the products you want to run first, where they will run, how many servers you run today, your cloud spend per month as a range, and a message. - Contact form (
/contact): your work email, name and topic, your message, and, if you choose, your company, your role and the ranges above.
4.2 How a form submission travels
- Your browser sends the form to a function on our website host.
- The function checks it and sends it by email to our team’s mailbox at our mail host. It keeps no copy.
- The function’s log records a reference number, which form it was, the topic, and whether delivery worked. It never records what you typed.
- To stop abuse, the function counts requests per IP address in memory for ten minutes and refuses a sender who sends too many. The count is not written anywhere.
If nothing can deliver your submission, the page offers to open an email to support@frazer.ai with what you typed, so you can send it yourself.
4.3 What we use it for
To read your request, reply to you, and set Frazer up with you if you go ahead. We do not add you to a mailing list, we do not use the data for advertising, and we never sell it.
5. When you email us
When you write to support@, security@, abuse@, privacy@ or legal@frazer.ai, we receive your address, your message and anything you attach, and we use them to handle what you asked. Our mail host stores the mailboxes.
6. When you have an account
| Data | Examples | Why we use it |
|---|---|---|
| Account | Name, email address, your sign-in method, second factors, profile | To create your account and let you sign in |
| Sessions and security | IP address, device and browser, approximate location from the IP address, sign-in times | To protect your account. A sign-in from a new device sends you an email with these facts |
| Organizations and roles | Which organizations and projects you belong to, your roles and approvals | To enforce who may do what |
| Audit log | Changes you, your agents or Frazer staff made, with time and reason | So your organization can see who did what |
| Billing | Legal name, billing address, tax IDs, billing contacts, invoices, usage | To bill, collect tax and keep accounting records. Card details go to our payment processor and never reach our systems |
| Support | Your cases and messages, and any access you grant our staff | To help you, and to record every staff action in your audit log |
| Email activity | Which emails we sent you and whether they arrived, for 30 days | So you can see what we sent and why |
| Public profile | What you choose to show on a public profile; facts computed from your public repositories and contributions, shown by default and each one hideable; facts from an organization’s private work only under that organization’s insight policy and your own opt-in. Insights come only from records on Frazer’s servers, never from telemetry in your tools, and members are told 14 days before an organization turns on any per-person view | Public content is visible to anyone |
| App and extension diagnostics | Crash reports and usage counts that do not identify you | To fix and improve the Frazer app and editor extensions. Your organization can turn this off, the extensions follow your editor’s telemetry setting, and session content is never included |
We send required emails about your account, security, billing and legal notices, which you cannot turn off while you have an account. Product news is opt-in: we send it only if you ask for it, and every optional email has a one-click unsubscribe. Our emails carry no tracking pixels and no rewritten links.
7. AI, and what we never do with your content
- We do not use what you put into Frazer, your inputs to agents and models, or their outputs, to train or improve AI models, ours or anyone else’s. The AI Terms say this in contract form.
- We do not sell personal data, and we do not “share” it for cross-context behavioral advertising, as California law defines those words.
- We do not make decisions about you that have legal or similarly significant effects by automated means alone. Automated checks do stop abuse, for example a mail stream with a high complaint rate pauses, a cryptocurrency miner is stopped, and a form submission that looks like spam is dropped. A person reviews any appeal.
8. Why we may process it: legal bases
Where the EU or UK GDPR applies, we rely on:
- contract: to provide your account and the services you use, and to bill you;
- steps before a contract: to answer a sign-up request and onboard you;
- legitimate interests: to answer people who write to us, to keep frazer.ai and Frazer secure, to prevent abuse and fraud, and to improve our products using information that does not identify you. We have weighed these interests against your rights, and you can object (section 12);
- consent: for product news by email, which you can withdraw at any time;
- legal obligation: to keep tax and accounting records and to answer lawful requests.
9. Who receives personal data
- Sub-processors, companies that process personal data for us under contract. They are listed, with what they do and where, on the sub-processors page. We add a company there before it processes personal data for us.
- Model providers you choose. When you send a request through a model route that names a provider, that provider receives the request. Routes paid through Frazer use providers that do not train on inputs, under our contract with them; with your own key, your agreement with the provider applies.
- Other users, for what you make public: a public profile, public repositories and models, and contributions to public projects.
- Your organization. If you use Frazer as a member of an organization, its owners and admins can see your membership, your roles and the audit log of your actions in it.
- Professional advisers, such as lawyers, accountants and auditors, under a duty of confidentiality.
- Authorities, when the law requires it. Our law-enforcement guidelines explain what we ask for and when we tell you.
- A buyer or successor, if Frazer is merged, acquired or sells its assets. The data stays protected as this policy says, and we tell you before it moves to a new policy.
10. Where it is stored, and international transfers
Frazer and its systems are in the United States. The data locations page says where each kind of data is stored. If you are outside the United States, your data is processed in the United States, whose laws differ from yours. Where the EU or UK GDPR or Swiss law requires it for data a customer sends us, the Standard Contractual Clauses in the Data Processing Addendum apply, and we require the same protection from our sub-processors.
11. How long we keep it
| Data | How long |
|---|---|
| Website host logs | A short period set by the host, to run and protect the site |
| Form submissions you sent us | While we are in touch, then 12 months after our last exchange, unless you become a customer |
| Email you sent us | While the matter is open, then up to 2 years. Abuse reports and our records of them: 2 years |
| Vulnerability reports | As long as they matter for security. We delete your contact details on request |
| Account and profile | While you have the account. After you delete it, 30 days, so a mistake can be undone, then it is deleted |
| Audit log entries | 400 days. After you delete your account, entries keep a pseudonym instead of your name |
| Billing records | As long as tax and accounting law requires |
| Email activity | 30 days |
| Backups | Encrypted, and removed on their schedule. Data deleted from the live system is not restored from them |
12. Your rights
Depending on where you live, you can ask us to:
- tell you what personal data we have about you and give you a copy, also in a machine-readable form;
- correct it;
- delete it;
- restrict how we use it, or object to a use based on legitimate interests;
- stop sending you product news (one click, in any such email);
- withdraw a consent you gave.
You also have the right not to be treated differently for using these rights. California residents have the rights to know, delete and correct, and to opt out of sale and sharing; we do neither, and we honor a Global Privacy Control signal as such a request anyway.
How to ask. Account holders can export and delete their data in the console. Anyone can write to privacy@frazer.ai. We may ask you to confirm the request from the email address we know, so we do not hand your data to someone else. Someone you authorize may ask for you, with proof of the authorization. We answer within 30 days, and tell you if we need longer, which the law allows in some cases. If we decline, we say why, and you can ask us to reconsider by replying to that answer.
Complaints. You can complain to the data protection authority where you live or work. We would like the chance to fix it first, so please write to us.
13. Security
We protect personal data with encryption in transit and at rest, short-lived credentials, separation between customers and between projects, hardware keys for staff, and encrypted copies off the primary site. Our staff reach customer data only with the customer’s consent on a support case or a recorded emergency reason, and every such action appears in the customer’s audit log within a minute. If a breach affects your personal data, we tell you and the authorities as the law requires. The security page describes more.
14. Children
Frazer is not for children. You must be at least 16 to have an account, and our website and forms are not directed at children under 16. If we learn we have personal data of a child under 16, we delete it. Please tell us at privacy@frazer.ai.
15. California notice at collection
In the last 12 months, and going forward, Frazer collects these categories of personal information, for the purposes and periods described above: identifiers (name, email address, IP address, account IDs); professional information (company and role); commercial information (orders, invoices, usage); internet activity (requests to our website, sign-ins, actions in the console and API); approximate location derived from an IP address; and account sign-in credentials, which are sensitive personal information under California law and which we use only to let you sign in. We collect them from you, from your organization when it invites you, and automatically when you use our website and services. We disclose them to the recipients in section 9 for business purposes. We do not sell or share them, and we have no actual knowledge of selling or sharing personal information of anyone under 16.
16. Changes to this policy
When we change this policy in a way that matters to you, we post the new version on the legal page and email account holders 30 days before it takes effect. Every earlier version stays online, with what changed.
17. Contact
Privacy questions and requests: privacy@frazer.ai. Other legal notices: legal@frazer.ai. By mail: Frazer AI LLC, Attn: Privacy, 1221 Brickell Ave, Ste 900, Miami, FL 33131.