Privacy
Privacy Policy
Theodore is installed on your computer and builds your decks there. This policy says what we hold about you to run your account, what we never receive, and the choices you have.
Last updated: to be confirmed.
Who we are
This policy covers the website theodoreand.ai, your Theodore account, the Theodore plugin and the client that runs on your computer, and the Theodore connector for assistants that run in the cloud.
Theodore& ("Theodore", "we", "us") decides how the personal data described here is used. Our legal name and registered address: to be confirmed.
Questions about this policy or your data: support@theodoreand.ai.
The short version
- Your decks, templates, slide text, images, file names and folder paths stay on your computer. Theodore's servers never receive them.
- We hold what we need to run your account: your email address, the computers you sign in, your licence, the preferences you save, technical bug reports and daily usage counts.
- What you share in a conversation with your assistant goes to that assistant's provider, under your agreement with them. Theodore adds no other recipient.
- We do not sell your data and do not use it for advertising.
- You can see your computers, preferences and reports in your account, export your data and delete your account there.
What we collect
- Account
- Your email address; the name and company you give us, if any; the assistants and the kind of computer you told us about when you asked for access; your plan (Beta) and when your account was created.
- Sign-in
- Your sign-in sessions and the browser each came from. One-time codes are stored only as keyed hashes and expire after minutes. If your account has a password from an earlier version of Theodore, it is stored as a salted hash.
- Computers
- For each computer you sign in: the name you or your computer gives it, its operating system and processor type, the assistant, the Theodore versions and update channel, and when it was last seen. Each computer's credential is stored only as a keyed hash.
- Usage counts
- Per account and per day: how many times the design instructions were fetched, how many reports were filed and how often the licence was renewed. We also keep counts per version and system that are not tied to you.
- Bug reports
- During the beta, when a Theodore command fails, your assistant may send a technical report: a title and description it writes, the command, the error code, the versions and the operating system. The client and our servers remove home-folder paths, email addresses, document file names and long tokens before a report is stored.
- Preferences
- The short notes you ask Theodore to keep (up to 30 of 280 characters), so later decks follow them.
- Messages
- The emails we send you (address, template and delivery status, never the one-time code itself) and anything you write to us.
- Network addresses
- IP addresses are kept only as keyed hashes, to limit request rates and stop abuse.
What we do not receive
Theodore builds, edits and renders decks on your computer. The client that talks to our servers never sends deck content, slide text, images, file names, folder paths, renders, or anything else from your work folders.
The engine that builds your decks connects to the network in three cases only, each started by what your assistant asks for, and each sends only a search text or a URL, never deck content:
- an image search: the search text goes to Wikidata, Wikimedia Commons and the Simple Icons CDN (and DuckDuckGo, when an optional package is installed), and the engine downloads the image it picks;
- a download of an image URL your assistant gives it;
- while it writes a deck, PptxGenJS fetching an image or other media that the deck names by URL.
Images given as files, and the asset packs, never reach the network. None of these goes to Theodore.
The design instructions Theodore follows are sent from our servers to your computer each time they are used. That flow runs from us to you; nothing of your work goes back with it.
Your assistant and its provider
Theodore runs inside an assistant you already use, such as Claude Code or Codex. What you type, attach or share in that conversation, and what the assistant reads from your computer to do the work, is processed by the assistant's provider under your agreement with them. The provider decides how that data is used; it is not our processor and we do not receive it.
Read your assistant provider's terms and privacy policy, and your employer's rules, before you share client material with it.
How we use it, and why
- To create and run your account, sign you in and keep your computers' licences current: this is needed to provide the service you asked for.
- To deliver the design instructions, updates and asset packs, and to apply your preferences: also needed to provide the service.
- To find and fix faults from bug reports, and to keep the service secure, including limiting request rates, detecting scraping of the design instructions and stopping abuse: our legitimate interest in a working, secure product.
- To email you about your access, sign-in codes, security and important changes to the service or these documents: needed to provide the service, or our legitimate interest.
- To meet legal obligations.
We do not use your data for advertising, do not sell it and do not build profiles of you for anyone else.
Who processes it for us
We use a small number of providers who process data on our instructions:
- Cloudflare: hosting of the website and the service, the database and file storage, and Turnstile, which checks the access form for automated abuse.
- Microsoft (Azure Communication Services and Microsoft Graph): sending our emails.
- GitHub: if we track a bug report there, the issue carries the report's technical content and a reference number, never your name, email address or account.
Where these providers process data, and on what legal basis it may leave your country: to be confirmed.
How long we keep it
- Account, computers and preferences: while your account is open. You can remove a computer or a preference at any time.
- Bug reports: kept to fix the faults they describe. When you delete your account, technical bug reports stay with no link to you.
- Daily usage counts: 400 days.
- Sign-in codes: minutes; activation codes for a computer expire after 10 minutes.
- Deleting your account removes your profile, sign-in and sessions, your devices (the computers you signed in, their names included), your preferences, any pending access request and your data exports. Records of the emails we sent you keep only their status and dates. Copies in our database backups expire within 30 days.
- Requests for access that are never approved: to be confirmed.
Your choices and rights
In your account you can see and remove your computers, read every bug report your assistant filed, switch automatic reports off, see and edit your preferences, export your data and delete your account.
Depending on where you live, you may also have the right to ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to complain to your data protection authority. Write to support@theodoreand.ai; we answer within the time the law sets.
Security
Credentials and one-time codes are stored as keyed hashes, and sign-in cookies are limited to our own site. What protects each download (pinned checksums, signed manifests, a published checksum) is described on the security page.
Children
Theodore is a tool for work and is not meant for children. The age below which we do not accept an account: to be confirmed.
Changes to this policy
Theodore is in beta and this policy will change as the product does. We publish every change on this page. How and when account holders are told about a material change: to be confirmed.