Security & data handling

OperatorIQ runs inside Microsoft Excel as an Office add-in. Your working models stay in your own Excel files, on your own machines and storage - they are not migrated into a proprietary platform.

What OperatorIQ stores on its servers, only when you use the corresponding feature:

• Versioned model snapshots - the assumptions, outputs, and the decision note (“the why”) you commit, with the cell values and formulas of the sheet you commit from.
• The workbook vault - each time you commit a version, the add-in also stores a copy of the whole workbook file for that version, up to 20 MB, so you can reopen it later. The file stays until you delete it or close your account.
• Datasets you explicitly upload - detail tabs you choose to store, deletable from your account at any time.
• Connected financial data - when you connect QuickBooks or Square, the synced financials used for your analysis.
• Account and billing basics - handled by Clerk (auth) and Stripe (payments); OperatorIQ never stores full card numbers.
• Agent sessions - when you use the Excel agent, a copy of the workbook’s cell values and formulas and the full conversation with the agent are kept on our servers for six hours after your last message, then deleted automatically.
• Agent build log - one entry per finished agent request, kept for 30 days, with the request’s status, model, cost and, for requests that fail, short progress notes.

• QuickBooks and Square connect through each provider’s official OAuth. OperatorIQ never sees or stores your password - only an access token you can revoke at any time, from our side or the provider’s.
• OAuth tokens are encrypted at rest with AES-256-GCM (an Intuit security requirement we apply across providers).
• OperatorIQ reads your financials to build your analysis and never writes to your books. This is enforced in code, not just policy: the only write-capable endpoint is hard-gated to an internal allowlist, so no customer account can reach it regardless of any configuration.
• You can disconnect any integration at any time from your account.

• Models the agent builds are checked by a deterministic verification gate when they are staged in your workbook. A build that fails the check is undone at once. A build that passes stays highlighted with Apply and Undo.
• Written answers are composed by the AI model from cells it reads and results our calculation tools return. Before you see an answer, any amount of 100 or more, or any dollar amount, that does not appear in your workbook or in a tool result is sent back to the model once to correct or remove. Percentages and other numbers under 100 are not checked this way, and the check confirms that a figure exists in the workbook, not that it is the right one.
• When the workbook cannot answer a question, the agent is instructed to say what is missing rather than guess.
• The Excel agent runs on Anthropic’s Claude models: Claude Opus for building, and Claude Sonnet and Claude Haiku for answering and checking. Anthropic is the only AI provider for the Excel agent, and Anthropic does not use API data to train models. In the web portal, Ask Thalen also sends your question to Voyage AI to search our industry benchmark database, and spoken replies are generated by ElevenLabs.
• We do not use customer data to train AI models. OperatorIQ is building its own model: it does not answer your questions, and it is not trained on customer workbooks or conversations. Since October 15, 2026, our code sends nothing from customer accounts to the machine our own model trains on.

• Hosted in the United States. Data is encrypted in transit (HTTPS/TLS), and OAuth tokens are encrypted at rest as described above.
• Authentication is handled by Clerk; sessions and API access are token-based. Password handling never touches OperatorIQ servers.
• A small set of subprocessors operates the platform (hosting, database, auth, billing, email, AI). The complete list, with what each handles, is maintained in our Privacy Policy - we give at least 14 days notice before material changes.

• Every model change is versioned with who made it, what changed, when, and why - a real audit trail, available in-product and writable into the workbook.
• Team history is kept for team accounts. Team accounts are not open yet. Team accounts scope models to your organization: shared version history and one current version of each model.

• Datasets you upload are deletable from your account at any time. Disconnecting an integration stops the data flow immediately.
• Cancelling a subscription does not delete your data. Closing your account deletes the personal data we hold in our databases, file storage, session stores and mailing lists, including agent sessions, build log entries and any training records still on our servers. If a store cannot be reached or refuses the delete, the request reports which ones still hold data and can be sent again. Closing your account does not delete: your sign-in account with our login provider, so you can come back to where you were; waitlist or contact form entries never tied to your login; service provider logs (Anthropic, Vercel, Cloudflare, Stripe, Voyage AI, ElevenLabs); mailing-list and email delivery logs (Mailchimp, Resend); copies held by the services you connected (QuickBooks, Square, Xero, Plaid, Motive, John Deere, Microsoft); Excel data owned by your organization; chat history saved inside your Excel files; copies of workbooks or files on your own computer; files the add-in saved to your own SharePoint, and the permission you granted in Microsoft, which you remove in My Apps. Excel files stay until you remove one, or until you close your account. Some cached data from your connected accounts may remain in our cache after closing; ask us and we will remove it.
• Excel agent sessions, including the workbook copy and conversation, are kept for six hours after your last message. The Excel agent build log is kept for 30 days. The account audit log holds the most recent 1,000 entries until you close your account.
• For a data export or deletion request, email help@myoperatoriq.com.

OperatorIQ is a young company and does not yet hold formal certifications such as SOC 2. We would rather tell you that plainly than imply otherwise. What we offer instead: this page, a subprocessor list that stays current, and direct answers. We complete security questionnaires for prospective customers.

If you believe you have found a security issue, email help@myoperatoriq.com with “Security report” in the subject. We read every report and will respond promptly. Please do not test against accounts or data you do not own.