itr8 Privacy Policy
Effective Date: November 5, 2026
This Privacy Policy explains how itr8 ("itr8," "we," "us," or "our") collects, uses, discloses, and retains personal information when you use itr8's websites, browser extensions, mobile applications, APIs, native helper software, and related services (collectively, the "Services").
Contact: privacy@itr8.ai
1. Scope
This Privacy Policy applies to information we collect from or about you when you:
- create or use an itr8 account;
- use the web app, browser extensions, mobile apps, APIs, or native helper;
- connect third-party accounts, API keys, secrets, or integrations;
- submit prompts, files, messages, memories, or other content; or
- interact with us for support, security, or legal matters.
If you use a third-party provider, website, app, or account through itr8, that third party's terms and privacy practices also apply.
2. Information We Collect
A. Account and profile information
We collect information such as:
- your name, email address, and profile information from sign-in providers such as Google and Apple;
- your username and account settings;
- a mobile phone number, if you verify one, and your text messaging choices and opt-outs; and
- records of account creation, authentication, and account status.
B. Content you provide or generate
We collect content you submit to or create through the Services, including:
- prompts, messages, and conversation history;
- files, attachments, images, audio, video, code, documents, artifacts, uploads, and screenshots;
- project data, memories, task lists, notes, commands, settings, and agent configurations; and
- feedback, support requests, and other communications with us.
C. API keys, secrets, and credentials
If you choose to store provider API keys or other secrets in itr8, we collect and store them so the Services can use them on your behalf. Stored provider keys and user secrets are encrypted at rest in our systems.
D. Local device, filesystem, browser, and desktop data
If you install or use the native helper or other tool-enabled features, we may collect or process data from your local environment based on what you enable or direct, including:
- local files and folders;
- screenshots, images, recordings, and window or desktop content;
- browser page content, cookies, and session data when you use browser automation tools;
- clipboard contents, commands, command output, logs, and other local system data; and
- metadata about connected mounts, local sessions, browser tabs, or helper status.
E. Usage, device, technical, and analytics information
We automatically collect certain technical information, such as:
- IP address and approximate location derived from it;
- browser type, device information, operating system, and app version;
- timestamps, access logs, crash data, diagnostics, performance information, and analytics or telemetry data we collect directly or through measurement tools we may implement; and
- information about how you use the Services, features, screens, workflows, and integrations.
F. Cookies and similar technologies
We use cookies, local storage, session storage, SDKs, pixels, and similar technologies for authentication, security, settings, product functionality, analytics, measurement, product improvement, and fraud prevention.
3. How We Use Information
We use personal information to:
- provide, operate, maintain, and secure the Services;
- authenticate users and manage accounts;
- process prompts, files, tool calls, and other requests;
- route requests to third-party model providers, vendors, websites, and services as needed to deliver requested functionality;
- store your settings, projects, memories, and other workspace state;
- debug, monitor, analyze, measure usage, and improve the Services;
- prevent fraud, abuse, misuse, unauthorized access, and security incidents;
- comply with law, enforce our terms, and protect rights, safety, and property; and
- communicate with you about the Services, support, updates, and legal notices.
4. How We Disclose Information
We may disclose personal information in the following circumstances:
A. AI model and feature providers
We may send prompts, files, tool inputs, outputs, and related metadata to third-party providers whose models or services power requested features. These may include model, audio, browser, sandbox, or media providers. Requests to the AI models that run itr8's agents and AI features, including the voice assistant, run on the API keys you supply (in a project someone else owns, the project owner's keys). Other services, such as web search and page reading, browser automation, sandboxes and rendering, may run on provider accounts or keys maintained by itr8, and some of those providers use their own AI models to process what they receive. For information from your Google account, see Section 5A.
B. Service providers and infrastructure vendors
We disclose information to vendors that help us operate the Services, such as providers of authentication, hosting, storage, databases, email, customer support, automation, or security services.
C. At your direction
We disclose information when you instruct the Services to interact with a third party, such as a website, browser session, API, file destination, sandbox, external tool, or connected account.
D. Legal, safety, and enforcement reasons
We may disclose information if we believe doing so is necessary to:
- comply with law, regulation, legal process, or government request;
- enforce our Terms or other policies;
- detect, prevent, or respond to fraud, abuse, security, or technical issues; or
- protect the rights, property, or safety of itr8, our users, or others.
E. Corporate transactions
We may disclose information in connection with a merger, financing, acquisition, bankruptcy, reorganization, sale of assets, or similar transaction.
F. Text messages
If you verify a mobile number or enroll in itr8 Agent Texts, we share your number and the content of verification and program texts with our messaging provider (Twilio) to verify the number, deliver texts and process STOP and HELP requests. We keep text messaging opt-in data and consent separate from the information disclosed for those purposes.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.
All the above categories exclude text messaging originator opt-in data and consent; this information won't be shared with any third parties.
5. Service Improvement, De-Identified Training Use, and Third-Party Processing
We may use content to develop, improve, tune, train, evaluate, and support our models, systems, analytics, and Services—but only after it has been aggregated, anonymized, or otherwise de-identified so that it is not reasonably linkable to you.
Unless we expressly offer and honor a different choice for a particular plan or feature, such as a future paid-plan training opt-out, we may use de-identified content from free-tier or other non-opted-out use for those purposes. If we introduce a plan-level or feature-level opt-out, we will describe it in the applicable terms, settings, or supplemental notice.
This section does not apply to information from your Google account; see Section 5A.
If a third-party provider receives your data because you use its model, API, browser, audio, media, or other service through itr8, that provider may process the data under its own terms, privacy practices, and account settings. If you supply your own API keys, accounts, or credentials, you are responsible for understanding those third-party practices.
5A. Information From Your Google Account
This section applies when you connect a Google account to itr8 as an integration, for example to let itr8's agents send or manage email for you, work with your Google Calendar, Google Drive, Google Docs, Google Sheets, Google Contacts or Google Tasks, or help you administer your Google Workspace's users and groups. It doesn't apply to signing in to itr8 with Google, which is covered in Section 2.A and gives us only your name, email address and profile picture.
itr8's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Workspace API User Data and Developer Policy.
For information from your Google account, this section controls if anything elsewhere in this Privacy Policy or in our Terms of Service says otherwise.
What we access
When you connect a Google account, you choose which Google services to connect, and Google shows you the exact permissions before you agree. Depending on what you choose, itr8 can access:
| Google service | What itr8 can access | What itr8 can do |
|---|---|---|
| Gmail (send only) | Permission to send email from your account. itr8 can't read your inbox | Send email when you, or an agent working for you, asks |
| Gmail (read and manage), only if you choose it | Your email messages, threads and labels | Read and search your email; write drafts and send email; add and remove labels, archive, and move messages to trash. itr8 never permanently deletes email you've received or sent. |
| Google Calendar | Your calendars and events | Read events; create, update and delete events |
| Google Drive (files you pick) | Only the files you open with itr8 or that itr8 creates for you | Read, create and update those files |
| Google Drive (search and read), only if you choose it | All files in your Drive | Find and read any of them. Creating and editing stay limited to files itr8 creates or you open with itr8. |
| Google Docs and Sheets | Your documents and spreadsheets | Read and edit them |
| Google Contacts | Your contacts | Read, create, update and delete contacts |
| Google Tasks | Your task lists and tasks | Read, create, update and delete task lists and tasks |
| Google Workspace admin, only if you choose it and your account is a Workspace admin | The users, user aliases, groups, group aliases, group members and group settings in the Google Workspace you administer, as far as your admin role allows. This includes other people's names, email addresses, account status and group memberships. | Read them when you ask. Create, change, suspend or delete users, aliases, groups and memberships, and change group settings, only after you approve each change in itr8. itr8 never sets or reads passwords chosen by an agent, and never changes admin roles other than making a user a super admin or removing that, which you confirm by typing the address. |
We also receive your Google account's email address, so we can show which account is connected.
We access this information only when you, or an itr8 agent working on your request, asks for it. itr8 doesn't scan your Google account in the background.
How we use it
We use information from your Google account only to provide and improve the features you use it for in itr8, for example:
- an agent answering a question about your calendar or a document;
- sending an email you asked for;
- reading or editing a document or spreadsheet you asked about;
- creating a calendar event or task you asked for;
- an agent summarizing or searching your email when you ask, if you chose Gmail (read and manage);
- finding and reading a Drive file you describe, if you chose Drive (search and read); or
- showing you your Workspace's users and groups, and making a change you asked for and approved, if you chose Google Workspace admin.
We don't use information from your Google account for any other purpose. In particular, we don't use it:
- for advertising, including targeted, personalized or interest-based ads, or retargeting;
- to determine credit-worthiness or for lending;
- to build profiles of you for any purpose unrelated to the features you're using; or
- to develop, improve or train generalized artificial intelligence or machine-learning models. This applies to the raw data and to anything aggregated, anonymized or derived from it. The de-identified training use described in Section 5 does not apply to information from your Google account.
We don't sell information from your Google account.
Who we share it with
We transfer information from your Google account only as needed to provide the features you're using, and only in these cases:
- The AI model provider that runs the agent. itr8 works by sending your request, and the information an agent needs to answer it, to an AI model. When an agent reads your Google data to help you, that data is sent to the provider of the model that runs the agent, using the API key set up to run that project's agents. In a project someone else owns, that is the project owner's key. itr8's helper features that work with a project's content, such as improving a prompt you're writing, describing or answering questions about a file you upload, transcribing speech, or summarizing a long conversation, also run on the project owner's API keys, but each uses a model itr8 chooses for that feature, from Anthropic, OpenAI or Google, which may not be the provider of the model that runs the agent. For example, describing an upload uses Google's Gemini, and improving a prompt uses Gemini first when the owner has a Google API key. The provider receives the data under the agreement between the holder of that key and the provider. That agreement and the key's settings decide whether the provider may store or use the data; itr8 doesn't control them. See "Your AI provider settings" below.
- The voice assistant's model. If you talk with itr8's voice assistant in a project, what you say, and the project content it reads out or looks up for you, is sent to its voice model, OpenAI's realtime model, using the project owner's OpenAI API key, under the agreement between the owner and OpenAI. That content can include information from your Google account. If you share your screen with it, the still images it chooses to look at (one at a time, and only while you're sharing) are sent too.
- Infrastructure providers that host and store itr8 (such as our database, storage and hosting providers), under contracts that require them to protect it.
- The notification email for an agent's question. When an agent in a project that has used information from your Google account asks someone in that project a question, itr8 may send them a notification email with the question, delivered by our email delivery provider. If the question quotes information from your Google account, that email includes it. It goes only to the member the question is addressed to, at their registered email address, and never if they've turned email notifications off. It contains the question's text (shortened if it's long) and a link to the question in itr8, never files or attachments.
- At your direction. If you ask an agent to send information from your Google account somewhere else, such as emailing it, publishing it, or sharing it in a project with other people, we do that because you asked. This includes apps and AI tools you connect to itr8 with your own itr8 API key (for example through itr8's MCP server): they can read your projects, including information from your Google account in them.
- For security and legal reasons: to investigate abuse or a security issue, or to comply with the law. We transfer it as part of a merger, acquisition or sale of assets only after getting your explicit consent.
Which AI models can receive it
Agents in itr8, and its voice assistant, send information from your Google account only to models from Anthropic, OpenAI, Google or xAI, and to Muse Wonder, one model from Meta (no other Meta model can receive it). Models offered through OpenRouter, and custom models you add to itr8, can't receive it. This doesn't limit where you yourself choose to send it (see "At your direction" above). In practice:
- Once an agent has fetched Google data in a project, only those models can run there. itr8 refuses any other model, names it and says how to fix it. An agent on a different model can't fetch Google data at all.
- Once a project has used Google data, it stays limited to those models. That includes the project's subagents, and projects created or duplicated from it.
- Content from such a project can be shared, copied or sent only to other projects that follow the same rule.
- Gemini only on a billed key. itr8 doesn't send information from your Google account to a Google Gemini model unless the project's owner has confirmed that their Gemini API key is on a Google Cloud project with billing enabled. A Gemini key on a Google Cloud project without billing lets Google use what it receives to improve its products, including training, so itr8 won't send Google data to Gemini on that key. Until the owner confirms it, that key isn't used in any project that has used Google data.
Extra protections for your email and Drive files
Email and files can contain text written by other people, including instructions meant to trick an AI agent. So in a project where an agent has read your Gmail or searched your Drive through these options, or looked up your Workspace's users or groups through Google Workspace admin, itr8 asks you before an agent sends email from your Gmail, moves email to trash or spam, sends calendar invitations, shares a Drive file or publishes a feed, and shows you what will be sent and to whom, or which emails would be moved. Nothing is sent or moved until you approve it in itr8.
Extra protections for Workspace administration
If you choose Google Workspace admin, an agent can't change your Workspace on its own. Every change to a user, alias, group, group member or group setting becomes a request you approve in itr8, in every project, showing what will change and for whom. Deleting a user or a group, making someone a super admin or removing that, suspending or renaming an account, opening a group to people outside your organization, sending a group's replies to an outside address, and making an outside address a group owner also ask you to type the affected address. Only the person whose Google connection would make the change can approve it, signed in to itr8. When an agent creates a user for you, itr8 creates a temporary password, shows it only to you after the change is sent (also when Google's answer is unclear, so check the Admin console), and requires a new password at first sign-in. The agent never sees it.
Directory information is information about other people in your organization. itr8 treats it like the rest of the information from your Google account: under the Limited Use rules above, never for advertising, never sold, and never used by itr8 to train AI models. The Gemini billing rule above covers it too.
Your AI provider settings
Each AI provider's terms, and the settings on the API key, decide whether that provider may keep or use what it receives. These settings belong to the key, and whoever holds the key manages them with the provider. For your own keys that's you; in a project someone else owns, ask its owner. Before you connect Google, check them, for example:
- Google (Gemini): an API key on a Google Cloud project without billing uses Google's free tier, where Google may use what you send to improve its products. Check how Google treats your key under your agreement with Google. itr8 requires the key's owner to confirm billing is enabled before Gemini can receive any information from your Google account.
- OpenAI: if your OpenAI organization has opted in to sharing data with OpenAI, OpenAI may use what you send to improve its models. Check your organization's data-sharing setting.
- xAI: we recommend turning on zero data retention for your xAI API key.
- Anthropic: check Anthropic's commercial terms for your account.
- Meta (Muse Wonder): check Meta's Model API terms for your key. Meta designates Muse Wonder a Standard model on its pay-as-you-go Model API, and describes use through a Muse Code subscription as contributing content for training by default, so use a Model API key.
Before you connect Google, itr8 asks you to confirm that you understand where your Google data goes.
Who can see it at itr8
People at itr8 don't read information from your Google account, except:
- with your explicit permission for specific messages, files or data (for example, when you ask support to look at a problem);
- when needed for security, such as investigating a bug or abuse;
- to comply with the law; or
- when the data has been aggregated and anonymized and is used for internal operations, as the Google API Services User Data Policy and the law allow.
Anyone working for or with itr8 who handles this information must follow the same rules.
Where it's stored and how long we keep it
- OAuth credentials. Google gives itr8 access and refresh tokens so it can act for you. We store them encrypted at rest, use them only for your requests, and delete them when you disconnect.
- Information in your projects. When an agent reads something from your Google account, such as an event, a contact or a document, what it read is saved in that project's conversation history so the agent can keep working with it. It can also end up in things the agent creates, such as a reply quoting a calendar event, a document made from a Google Doc, or a project memory. itr8 doesn't copy anything from your Google account that an agent hasn't read for you, except the details it shows you when it asks you to approve something, such as a Drive file's name and owners, an event's title, the date, sender and subject of each email it asks to move to trash, or a Workspace user's or group's current settings that a change would replace, which are saved with that request in the project. If an agent asks to send an email with attachments, copies of those files, including attachments from a Gmail draft, are kept with that request until you approve or decline it, or for at most 7 days. This information is treated like your other project content: you can delete it, and it's retained as described in Section 6.
- Logs. Diagnostic and security logs are kept for limited periods, as described in Section 6. We design them to record that a request happened rather than what your Google data says, and we remove search terms from the web addresses we log.
How to disconnect
You can disconnect a Google account at any time in itr8's integration settings. Disconnecting deletes that connection's stored tokens, and we revoke itr8's access at Google when it's safe to. We don't revoke it when another itr8 connection still uses the same Google account (revoking would cut that connection off too), or when we can't confirm which account the connection belongs to; and Google can't always be reached. In those cases itr8 tells you, and you can remove itr8's access yourself at myaccount.google.com/permissions, which removes it for every connection to that account.
Disconnecting doesn't delete information that's already part of your projects. To see which of your projects have used data from a Google account, open Projects with Google data in the Google section of itr8's Integrations page. A project created from one of them, or that received its content through itr8, is marked too and appears on the list. Deleting a project deletes its conversation, memory, documents and files, including what agents read from Google. You can also delete your account. Deleted content is removed as described in Section 6. If you'd rather we do it, email privacy@itr8.ai from your account's address and tell us which projects you own; we'll confirm with you, then delete them. You can also keep a project and delete only its conversation, project memory and ledger notes, with Delete Google data in the project's settings. itr8 then lists the documents, files, feeds and scheduled tasks created or changed since Google data first entered the project, so you can review them.
For questions about this section, contact privacy@itr8.ai.
6. Data Retention
We retain personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide the Services, maintain your account and workspace state, keep backups and business records, resolve disputes, enforce agreements, and comply with legal obligations.
Our retention periods vary by category. In general:
- Account and profile data: retained while your account is active and generally for up to 3 years afterward for security, legal, tax, audit, and recordkeeping purposes.
- Conversation, project, memory, and workspace content: retained until you delete it or close your account. After deletion or account closure, we generally remove this data from active systems within 30 days, and backup copies may persist for up to 90 days.
- Stored API keys, secrets, and credentials: retained until you remove them or close your account. We stop using deleted secrets for new requests promptly and generally remove them from active systems within 30 days; encrypted backup copies may persist for up to 90 days.
- Logs, diagnostics, and security records: typically retained for 30 days to 12 months, depending on the type of log and our operational, security, and legal needs.
- Mobile number and text messaging records: your verified number is kept while it's on your account. Records of opt-outs (STOP) are kept after you remove the number, to enforce your opt-out from itr8 Agent Texts. Texts you send to our number aren't read: we keep only what's needed to process STOP and HELP, and delete message content within 15 minutes.
We may retain information for longer if required by law, needed to resolve disputes, investigate abuse, enforce our agreements, or preserve evidence.
7. Security
We use reasonable technical and organizational measures designed to protect personal information. For example, stored provider API keys and user secrets are encrypted at rest in our systems.
However, no system is completely secure. We cannot guarantee absolute security, and you use the Services at your own risk, especially when enabling local access, browser automation, tool execution, or transmission of sensitive data.
8. Security Incidents and Breach Notification
If we determine that a security incident involving your personal information requires notice under applicable law, we will notify affected individuals, regulators, or others as required by that law.
9. Your Choices
Depending on the feature, you may be able to:
- update profile information and settings in the app;
- add, change, or delete stored provider keys and user secrets;
- control what files, devices, tabs, sessions, or local resources you connect or expose;
- turn itr8 Agent Texts off in Settings or reply STOP to any text; and
- limit cookies or storage through your browser or device settings.
If you do not want us to process certain information, do not submit it, do not connect it, and do not enable the related feature.
10. Privacy Rights
Depending on where you live, you may have rights under applicable law, such as the right to request access to, correction of, deletion of, restriction of, or objection to certain processing of your personal information, and the right to obtain a copy of certain personal information in a portable format.
To exercise applicable rights, contact us at privacy@itr8.ai. We may need to verify your identity and may deny or limit requests where permitted by law.
California
We do not sell personal information, and we do not share personal information for cross-context behavioral advertising as those terms are used in California law.
EEA/UK
If you are located in the EEA or UK, additional rights may apply, including the right to lodge a complaint with your local supervisory authority.
Our legal bases for processing generally include:
- performance of a contract with you;
- our legitimate interests in operating, securing, and improving the Services;
- your consent, where required; and
- compliance with legal obligations.
11. International Transfers
We and our service providers may process information in the United States and other countries where privacy laws may differ from those in your jurisdiction.
Where required by applicable law, we use appropriate safeguards for cross-border transfers, such as contractual commitments or other lawful transfer mechanisms.
12. Children's Privacy
The Services are not intended for children under 18, and we do not knowingly offer the Services to children.
13. Sensitive Information and Local Access Warning
Because itr8 can process files, prompts, secrets, and local device data, you should use care before submitting sensitive information. Do not submit sensitive personal data — such as health data, financial data, credentials, regulated data, or third-party confidential information — unless you have a clear reason, legal authority, and an understanding of the risks.
If you enable the native helper or local-access tools, use particular caution before exposing local folders, files, terminal sessions, browser sessions, desktop content, clipboard data, or other sensitive local resources. Only enable access you are comfortable allowing.
14. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we may provide notice through the Services, by email, or by other reasonable means. Your continued use of the Services after the updated policy takes effect means the updated policy applies going forward.
15. Contact Us
For privacy questions or requests, contact itr8, Inc., a Delaware corporation headquartered in Palo Alto, California, at privacy@itr8.ai.
Because itr8 can route content to multiple AI and infrastructure providers and can interact with your local environment if you enable those features, the scope of data processed depends heavily on how you use the Services, whether a request is routed through your own provider accounts or itr8-managed provider accounts, and what access you grant. Please use care and only enable the tools and permissions you are comfortable allowing.