Skip to content

Privacy policy ​

Effective date: October 14, 2026

Otto is a sales and project-tracking application for manufacturers' representatives and their teams. It is operated by Dyce ("Dyce", "we", "us"). This policy covers the Otto web app at workspace.ottokap.app, this documentation site at docs.ottokap.app, and the Google and Microsoft mailbox connections Otto offers.

Otto is sold to businesses. Each customer has a workspace, and the customer's administrators decide who joins it and which mailboxes are connected. For the business data in a workspace, we act on that customer's instructions: the customer controls that data and we process it on its behalf. For the account information described below, we decide how it is used. Customers can request a data processing agreement by contacting us.

What we collect ​

Account information ​

You sign in through WorkOS, our sign-in provider. From that sign-in we keep your email address, your name, your profile picture link (if your identity provider supplies one), and when you were last active. We also keep which workspaces you belong to and your role in each.

We never see or store your Otto sign-in password.

Mailbox data (Gmail and Microsoft 365) ​

When you connect your inbox, you approve access on Google's or Microsoft's own consent screen. Otto never asks for or stores your mailbox password.

Permissions requested.

ProviderPermissionsWhat they are used for
Gmailgmail.readonlyRead your messages and their attachments
Gmailgmail.sendSend email you write or approve in Otto, and email under rules your workspace admin turns on (see Sending email)
Microsoft 365Mail.Read, User.Read, offline_accessRead your messages, confirm your mailbox address, and stay connected without asking you to sign in again
Microsoft 365Mail.SendSend email, as above
Microsoft 365Mail.ReadWriteTwo uses only. (1) To send email with more than 3 MB of attachments: Microsoft requires these to be built as a draft first. Otto creates the draft, attaches the files, sends it, and deletes it if sending fails. (2) Mail filing, only for a mailbox whose person has turned it on (it is off by default): Otto moves mail out of the Inbox into that mailbox's own folders by the person's rules (read mail only, unless a rule says otherwise), and creates a folder when the person asks for one. Filing never deletes email, and every move can be undone. Otto does not use this permission to change, move or delete any other email.

Otto does not request access to contacts, calendars, files or anything outside mail. When a company connects mailboxes for its whole organization instead of one person at a time, the permissions are granted by that company's administrator and are listed in Security & data handling.

Which messages Otto reads. Otto reads every mail folder (Gmail: every label) except Drafts, Spam/Junk, Trash/Deleted Items and Gmail chats. When you first connect, it reads back 12 months of history, then keeps up with new mail as it arrives.

What Otto stores for each message. Otto stores message metadata: sender, recipients, subject, sent and received times, thread and message identifiers, direction (sent or received), and the names, types and sizes of attachments. It also keeps a list of the addresses each connected mailbox has sent mail to, so it can tell known correspondents from strangers.

Mail filing (only when you turn it on). If you turn on Mail filing for a mailbox, Otto looks once at the mail already in that mailbox's folders and keeps only a count of messages per folder for each sender address and sender domain, so it can suggest filing rules. It keeps nothing else from that look: no subjects, bodies, recipients or names. Those counts are deleted when filing is turned off. Otto also keeps your filing rules and a record of each move it makes (which message, from which folder to which, and by which rule) so the move can be shown to you and undone.

What Otto does not store. Otto does not store the body of your email. When you open a message in Otto, the body is fetched from Google or Microsoft at that moment, shown to you, and discarded. Bodies are not written to our database, file storage, logs or caches.

Attachments. When Otto classifies a message as sales-related (for example a purchase order, quote or invoice), it saves a copy of the business documents attached to it so they can be read and turned into records. Other attachments are saved only if someone in your workspace chooses to save them.

Short excerpts. A few features keep a short piece of text the AI read out of an email: a one-sentence reason for a classification, a summary line for a follow-up you promised, or the sentence a quote line was read from. Each is capped at 280 characters.

Business data you enter ​

Your workspace holds the CRM and project records your team creates or imports: accounts, contacts, deals, quotes, purchase orders, invoices, shipments, notes, follow-ups and files you upload.

Project and specification data ​

For workspaces that use it, construction project, specification, bidder and product data comes from Dyce's project-data service, which gathers it from industry sources. Specification documents your team uploads to Otto are sent to that service to be read and matched to your products, and the results come back into your workspace. The service receives project and product records and the documents you upload; it does not receive mailbox data.

Messages to the in-app assistant ​

If you use Otto's assistant, we keep your conversation with it. If the assistant opens an email body to answer you, that body is not saved with the conversation, but the assistant's reply, which may summarize it, is.

Usage and technical data ​

  • Audit log. Significant actions (sign-ins, permission changes, mailbox connections, record deletions and similar) with who did them, when, and the IP address and browser user agent they came from.
  • Application logs. Request and error logs used to run and secure the service. We do not write email bodies to logs.
  • Notification devices. If you turn on phone or browser notifications, the device's push address and browser type.
  • Cookies. One sign-in session cookie and one cookie that remembers your selected workspace. We do not use advertising or analytics cookies, and we do not run third-party advertising or tracking in the app or this site.
  • Fonts. The app and this site load fonts from Google Fonts, so Google receives your IP address when a page loads.

How we use it ​

We use this data only to run Otto for your workspace:

  • Logging email activity. Otto files each message against the right account, contact, deal or project so your team can see the history of a customer relationship.
  • Suggestions. An AI model reads incoming messages and proposes actions: link or create a contact or account, start a deal, draft a purchase order, save a document, track a follow-up you promised. A person accepts or rejects each suggestion. If a workspace admin switches the inbox to automatic mode, Otto applies the low-risk kinds of suggestion on its own. Automatic mode never sends email.
  • Reading documents. Saved attachments and uploaded documents are read (text recognition plus an AI model) to fill in purchase orders, invoices, quotes and specifications for a person to review.
  • Drafting replies. Otto can draft follow-ups and replies. Drafts are saved for you to review and edit before you send them.
  • Showing history to your team. Inside your workspace, a colleague looking at a shared account or contact can see that an email exchange happened: date, subject, direction, the other party, and which mailbox it was in. They cannot open the message, its body or its attachments unless they are a member of that mailbox.
  • Security, support and fixing problems.

Sending email ​

Otto sends email from your mailbox in two ways:

  1. When you send it. You write or review an email in Otto and press send.
  2. Under automatic-send rules your workspace admin turns on. By default Otto sends nothing on its own; every automated email waits as a draft for a person to review. A workspace admin can switch on automatic sending for specific kinds of email: project-milestone notices to customers, follow-up emails from the workspace's playbook rules, and substitution requests for project specifications. When an admin does, Otto sends those emails without a review step, from the mailbox of the record's owner or a default sender the admin chooses. Each automatic send is recorded and visible to the workspace.

Otto does not add tracking pixels or link tracking to the email it sends.

AI processing ​

Otto's AI features run on Amazon Bedrock (Anthropic Claude models by default) in Amazon Web Services' United States regions. Amazon processes the request and returns the result; Bedrock's own request logging is turned off for Otto, and AWS's terms say Bedrock does not use customer content to train its models.

A workspace can instead ask us to use OpenAI or Google Gemini models for its AI features, using an API key that the workspace supplies. In that case, the content those features process, including email text, goes to that provider under the workspace's own agreement with it. This happens only when the workspace asks for it.

Neither Dyce nor any provider we use trains AI models on your data. In particular, Otto does not use data received from Google APIs to develop, improve or train generalized AI or machine-learning models.

Google API Services: Limited Use ​

Otto's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain words, for data Otto receives from your Gmail account:

  1. We use it only to provide the features you see in Otto, as described in this policy: logging your email activity, suggestions, document reading, drafting replies and sending the email you or your workspace's rules send.
  2. We do not transfer it to anyone else, except as needed to provide those features (for example, to the service providers listed below), to keep Otto secure, to comply with the law, or as part of a merger, acquisition or sale of assets, after giving you notice.
  3. No person at Dyce reads it, unless you give us permission for a specific message (for example, while helping you with a support request), it is necessary for security purposes such as investigating abuse, it is needed to comply with the law, or it has been aggregated and anonymized for internal operations.
  4. We never use it for advertising, including personalized ads, retargeting or interest-based ads, and we never sell it.

Where data is stored and how it is protected ​

  • Location. Otto's database, files and logs are in Amazon Web Services, us-east-1 (Northern Virginia, United States). Production runs in its own AWS account, separate from development and testing.
  • Encryption in transit. All connections to Otto use HTTPS.
  • Encryption at rest. The database, file storage and backups are encrypted at rest.
  • Mailbox tokens. The refresh token Google or Microsoft issues when you connect a mailbox is encrypted with AES-256-GCM before it is saved, using a key held separately from the database. Short-lived access tokens are kept in memory only.
  • Separation between customers. Every workspace's data is separated in the database by row-level security: the database itself refuses to return one workspace's rows to another.
  • Separation between mailboxes. Inside a workspace, a connected mailbox's messages can be opened only by that mailbox's members.

Who we share data with ​

We do not sell personal data. We share it only with the service providers that run parts of Otto for us, and only for that purpose:

ProviderWhat it does for Otto
Amazon Web ServicesHosting, database, file storage, AI models (Amazon Bedrock), document text recognition (Amazon Textract), message queues
WorkOSSign-in and account authentication
CloudflareDNS, network security and traffic routing for ottokap.app; hosting of this documentation site
GoogleGmail and Google Cloud Pub/Sub for mailboxes you connect; Google Workspace, which delivers Otto's own system email (such as invitations); Google Fonts
MicrosoftMicrosoft Graph for Microsoft 365 mailboxes you connect
Browser push services (Apple, Google, Mozilla)Deliver notifications you turn on; the contents are encrypted
OpenAI or Google GeminiOnly for a workspace that has chosen one of them, as described under AI processing

We may also disclose data when the law requires it, to protect the security of Otto or its users, or as part of a merger, acquisition or sale of assets, in which case we will tell you before your data becomes subject to a different privacy policy.

How long we keep data ​

DataHow long
Email bodiesNot stored
Email metadata (sender, recipients, subject, times, attachment names)While the workspace exists, until the mailbox is deleted from Otto, or until the person is erased (see below)
Saved attachments and documents7 years from when Otto received them by default. Documents attached to an invoice, vendor quote or reviewed purchase order are kept as long as that record. A workspace can ask for a different period (at least 1 year).
Assistant conversations90 days after the last message
Provider change notifications (the "new mail arrived" signals from Google and Microsoft)90 days in the database, then 12 months in an encrypted archive, then deleted
Mailbox sync records90 days
Audit log7 years by default; a workspace can shorten this to as little as 1 year
Application logs1 year
CRM, project and other business records your team creates, including drafts and email Otto sentWhile the workspace exists, unless your team deletes them
Database backups14 days
Copies of deleted filesUp to 90 days

Disconnecting and deleting ​

Disconnect a mailbox. You can disconnect your own mailbox in Otto under Integrations at any time, and workspace admins can disconnect any mailbox in their workspace. Disconnecting immediately stops Otto from reading the inbox and deletes the stored token. It does not change anything in your mailbox. It does not by itself delete the metadata and documents already in Otto; a workspace admin can delete the mailbox from Otto to remove its stored message history, or you can ask us to delete it (see Contact us).

Revoke access at Google or Microsoft. Disconnecting in Otto does not withdraw the permission you gave at the provider. To do that as well:

  • Google: go to myaccount.google.com/connections, select Otto, and remove its access. A Google Workspace administrator can also remove it under Admin console → Security → Access and data control → API controls.
  • Microsoft: go to myapps.microsoft.com, open the app permissions, and remove Otto. A Microsoft 365 administrator can remove it under Entra ID → Enterprise applications.

After you revoke access, Otto can no longer read or send email for that mailbox.

Delete a person's data. A workspace admin can ask us to erase a person (for example, a customer contact) from a workspace. Erasure deletes their contact record and documents and scrubs their name and address from email records, and is logged without keeping the erased details.

Delete a workspace. When a customer closes its workspace, we delete the workspace and everything in it, including stored files, within 30 days.

Your rights ​

Depending on where you live, you may have the right to see the personal data we hold about you, correct it, delete it, receive a copy, or object to how it is used. Because Otto is run for businesses, many requests are best made to the company that runs your workspace; we will help them answer. You can also contact us directly. We will respond within 30 days.

We will not treat you differently for exercising these rights.

Children ​

Otto is a business tool and is not directed to anyone under 16. We do not knowingly collect personal data from children.

Changes to this policy ​

If we change this policy, we will update the effective date at the top. If the change is significant, we will notify workspace administrators by email or in the app before it takes effect.

Contact us ​

Questions, requests and complaints about privacy:

Dyce Email: hello@ottokap.app

Questions this guide doesn’t answer — contact Otto support. · Privacy policy