Privacy

BuildOS is a thinking environment for people making complex things. It is run by DJ Wayne as a sole proprietorship in Glen Burnie, Maryland. This policy covers the BuildOS website, app, emails, published pages, and related services. "We" means BuildOS.

When you send something from BuildOS to another service, such as a connected AI agent, that service's own policy governs what it does next.

We use your information to run BuildOS for you: organizing your thinking, answering in chat, writing your briefs, syncing your calendar, sending the notifications you chose, handling billing, keeping accounts secure, fixing errors, and understanding which features help.

We don't sell your information. We don't use your workspace content for advertising. We don't train AI models on your content, and we don't let our AI providers train on it (section 4).

Where the law asks for a legal basis, we rely on our contract with you, our legitimate interest in running a secure service, your consent, or a legal obligation, depending on the activity.

When you use an AI feature, BuildOS sends the model what it needs for that request: your message and the relevant parts of your workspace. That can include personal details you wrote.

Zero data retention. Every AI request goes through OpenRouter with two rules we set in code: the model host must offer zero data retention, and it may not collect your data for training. A request that can't be served under those rules fails instead of going elsewhere. This covers chat, the assistant's safety review of changes, daily briefs, search indexing, reading text from images, and Jev, the small model that picks tools and scores email relevance.

Which models. Today these are mainly open-weight DeepSeek models run by independent hosting companies, OpenAI models hosted on Microsoft Azure, Google Gemini on Google Cloud, and TypeSafe's Jev. The lineup changes as models improve. The zero-retention rule doesn't.

The one exception: voice. Dictation (your recorded audio) and spoken briefs (the text of your brief) go to OpenAI audio models, which don't offer zero retention. OpenAI may keep that data for up to 30 days to check for abuse, and it doesn't use it for training. If you'd rather avoid this, type instead of dictating and leave spoken briefs off.

Web research. When the assistant searches the web, the search query goes to Tavily, our search provider. BuildOS fetches pages from our own servers. When a page won't load that way, it asks Tavily to fetch the page's address.

Both are optional, and they are separate connections. Connecting one doesn't connect the other. You can disconnect either one at any time in Settings. When you do, we revoke BuildOS's access at Google and delete the stored credentials.

Gmail is read-only. We ask Google for read-only access and nothing more. BuildOS can't send, draft, delete, archive, label, or mark mail, and it never downloads attachments.

When BuildOS reads your email. Only while working on something you asked for, in a chat or from the Gmail panel in Settings. To answer something like "did anything come in about my book?", BuildOS searches your inbox. Jev scores each email's subject, sender, and preview for relevance, under zero retention. The chat model then reads the relevant emails, also under zero retention, and answers you.

What we keep from your email. No subjects, senders, previews, or message text. We keep short traces:

• the search terms the assistant used, plus message and thread ids, dates, counts, and relevance scores, for 30 days;
• a short memory of which emails were already checked, stored as keyed hashes, for 30 days;
• a log of when Gmail was accessed and whether it worked, for 180 days.

One thing to know: your chat keeps what the assistant told you. If its reply summarizes an email, that reply stays in your chat like any other message, until you delete it.

Google Calendar. Calendar access is read and write, so BuildOS can show your schedule, answer questions about it, and create, move, or delete the events it manages for you. We store the events BuildOS creates, and the links that keep them in sync. For events BuildOS didn't create, we never store descriptions, locations, or attendees. The record of what the assistant looked up keeps only event ids and times, for 30 days. When you run a calendar analysis, we keep only the title and time of the events behind each suggestion, and delete them within 30 days, or sooner if the suggestion is deleted. Events that don't back a suggestion are never stored.

Google's rules. BuildOS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google data only to provide the features you turned on. We don't use it for advertising, don't sell it, and don't use it to train or improve AI models. People don't read it, except with your permission, for security, to comply with the law, or in aggregated and anonymized form for internal operations. Because we don't store your email content, there is nothing for anyone at BuildOS to read later.

You can connect agents such as Claude or ChatGPT through the BuildOS Connector or an agent key. They can reach only the projects and permissions you approve. With write access, they can change your BuildOS content.

• We store agent keys and tokens only as one-way hashes.
• We log each agent action, keeping its inputs and results for 30 days and the record that it happened after that.
• Revoking an agent stops future access. It can't pull back what the agent already received.

If you publish a page, anyone can see, copy, and share it. To count views, we store a one-way hash of the visitor's IP address and browser, plus the referring page, for 90 days. A Do Not Track signal skips the record.

Our emails can include open and click measurement. Optional emails have an unsubscribe link. Account, security, and billing emails still arrive.

BuildOS is a general productivity tool, not a medical records system or a HIPAA-covered service. If you write health, financial, or other sensitive details into your workspace, we handle them like the rest of your content: to run the features you use, and never for advertising.

Delete your account in Settings, or email us. Right away, we:

• sign you out and block sign-in;
• disconnect Gmail and Google Calendar, revoke BuildOS's access at Google, and stop calendar sync;
• cut off any connected AI agents and agent keys;
• stop briefs, notifications, and texts;
• take down pages you published;
• schedule your subscription to cancel.

Within 30 days, we permanently delete your account and everything in it: projects you own, chats, files, voice recordings, briefs, exports, connections, and the records tied to you. We also delete your profile from our analytics provider.

What remains. If you worked in a project someone else owns, your contributions stay so their project isn't broken. Your name is replaced with "Deleted user", though your own words stay as written. We keep consent records, and Stripe keeps billing records as the law requires. Emails we already sent you stay in your inbox and in our sending mailbox. Twilio keeps its own delivery logs. Backups held by our database host roll off on its schedule. If we ever restore one, we delete your data again.

You can see and edit your content in BuildOS at any time. You can download everything you've created as a zip from Settings → Your data. You can delete individual items or your whole account. You can change your analytics and marketing choices in the footer.

Depending on where you live, you may also have the right to know what we hold, correct it, restrict or object to processing, opt out of targeted advertising, and appeal a decision. To use any of these rights, email dj@build-os.com from your account's email address. We may confirm it's you first, and we'll answer within the time the law sets (usually 45 days). To appeal a decision, reply with "Privacy Appeal". We won't treat you differently for using your rights.

We encrypt all traffic in transit. We encrypt Google credentials with AES-256 before storing them, and we store agent keys only as hashes. Database rules limit each account to its own data.

BuildOS is run by its founder. Admin tools open account data only for support, security, or legal reasons. Every time an admin opens or exports another person's chats, it is recorded.

No system is perfectly secure. If a breach affects your information, we'll tell you as the law requires.