Effective Date: September 21, 2026. This page is informational and is not a contract. It mirrors the Data Source Registry Itogai LLC (“itogai”) keeps internally, entry by entry, and it is the place the Customer Terms of Service, the Privacy Policy, the Acceptable Use Policy and the Data Processing Agreement point to when they say how data can enter an account. Nothing on this page widens or narrows those documents. Last Modified: September 21, 2026 Document Version: DSR-2026-09-21 v5.0
Everything in itogai comes from data you bring yourself and turn on yourself. Nothing is read in the background, nothing is scraped, and nothing is sent on your behalf. Sources marked “in development” are being built and may change before they are available; nothing here is a promise of a date.
Where the binding rules live. The five ways data can enter an account, and the three content levels, are stated in Section 1.5 and Section 7 of the Customer Terms of Service and in Sections 3 and 4 of the Privacy Policy. The commitments there apply to every source on this page by category, whether or not the source is named here: email message bodies never rise above Level 1, a level is raised only by your own consent for that specific source, and an upload containing email message bodies is rejected. This page names the sources so you know which tools are involved.
1. How to read the levels
Every source is handled at one of three levels, which the Customer Terms of Service (Section 7.2) and the Privacy Policy (Section 4) define and bind.
| Level | What happens |
|---|---|
| Level 1. Metadata only | itogai reads and retains envelope metadata only: who, when, how often, and comparable fields. Body content is never read and never stored. This is the default for every source |
| Level 2. Derived signal | Content is read once, in memory, to derive relationship signal, then discarded. Only the derived signal persists. Raw text is never written to itogai’s database. A source reaches this level only when you turn on content signals for it, which are off by default |
| Level 3. Retained content | Raw text persists. This applies only to what a person saves by hand. No automated path writes to this level |
Why itogai names the level rather than making a claim. The sentence “we never read your messages” would be inaccurate, so itogai does not use it. At Level 1 there is nothing to read, because only the envelope is requested. At Level 2, content is read in memory and discarded, and only a derived signal remains. Naming the level is the only description that stays true across every source.
2. Connected accounts
Connected accounts: email and calendar. Available now. You can connect an email or calendar account through your provider’s own sign-in and revoke it there or in itogai at any time. We read who you write to and meet with, when and how often. We never store the text of your emails. Today that means a Google account (Gmail, Google Calendar and Google Contacts) and a Microsoft 365 account (Outlook mail and Calendar). For a Google account, restricted scopes are requested in metadata format only and are held at Level 1 permanently, which is the subject of itogai’s App Defense Alliance CASA verification at Assurance Level 1 (formerly Tier 2).
Connected accounts: messaging and meeting tools. In development. You can connect a messaging or meeting tool through its own sign-in: Slack, Discord, Zoom, Gong, and a meeting-notes tool or a transcript you share. We read who you talk to and meet with, when and how often. If you turn on content signals for a tool, we read the text once to derive relationship signals and never store it.
Connected accounts: CRM and record systems. In development. You can connect a CRM or record system with your own credentials: HubSpot, Salesforce, Attio, Pipedrive, Zoho, Notion, Planhat, Gainsight and Odoo. We read the structured fields of contacts, companies, deals and activities and leave free-text notes alone.
3. Archive and file imports
LinkedIn archive import. Available now. You can upload the data archive you request from LinkedIn yourself. We never connect to LinkedIn on your behalf and never read LinkedIn pages for you.
CSV import. Available now. You can upload a spreadsheet of people you already know. We read the columns you map and nothing else.
Phone contacts import (VCF). In development. You can upload the contacts file your phone or your contacts app exports. We read names, numbers, emails, companies and roles to recognize the people you already know.
Cloud drive file import. In development. You can pick a spreadsheet, document or deck in your cloud drive. We read the contact details it holds and nothing else, and we do not keep the file’s text.
AI conversation import. In development. You can upload conversations you exported from an AI assistant. We read them once to understand who you mention and how, and we never store the text.
4. Conversation exports
WhatsApp chat import. In development. You can upload conversation files you export yourself from WhatsApp, one conversation at a time, without media. We read them to understand who you talk to, when and how often. If you turn on content signals for this source, we also read the text once to derive relationship signals and we never store the text itself. You can delete any import, and turning content signals off deletes what was derived from them.
WhatsApp bulk export (iPhone). In development. If you use an iPhone, you can bring in many WhatsApp conversations at once with iMazing, a third-party app that runs on your own computer and reads a backup of your phone there. You choose which conversations to export and, again, which ones to keep in itogai. itogai never receives your backup, only the file you export and upload. iMazing is made by DigiDNA; itogai receives nothing from its maker. For iPhone users who take this path, itogai can provide an iMazing license code at no cost; to send it, itogai shares your name and email with DigiDNA.
Text messages import (Android). In development. You can upload a text message backup file you create yourself on your Android phone with a backup app. itogai never asks for permission to read your messages on the phone; it reads only the file you upload, to understand who you text, when and how often. Content signals work the same way as for WhatsApp and are off by default.
Share to itogai from your phone. In development. From the itogai mobile app, an exported conversation can be sent to itogai straight from your phone’s share sheet. The same rules as the WhatsApp chat import apply: one conversation at a time, without media, read to understand who you talk to and how often, with content signals off unless you turn them on for it, and the file deleted as soon as it has been read.
Text messages import (iPhone). In development. If you use an iPhone, you can export your Messages conversations with iMazing, the same third-party app described above, and upload the file. itogai never receives your backup.
5. What itogai adds, rather than reads
These are not sources you connect. They are described here so that the full picture of where a contact record’s contents come from is in one place.
| What it produces | Where it is recorded | |
|---|---|---|
| Contact enrichment | Publicly available business information about a contact you submit for enrichment: employer, role, professional profile, business contact details | The enrichment providers are listed in the Sub-processors register |
| Public research | References to publicly available material about a contact, used to surface a relationship signal | The model provider performing it is listed in the AI Provider Register |
6. What never happens
itogai never asks for your passwords, your phone’s backup, or an encryption key. itogai never decrypts another service’s data. itogai never reads a professional network’s pages for you. itogai never imports media. Every source can be turned off, and turning content signals off deletes what was derived from them.
Third-party names. WhatsApp, LinkedIn, iMazing, DigiDNA and every other service or tool named on this page are the marks of their owners, named here so you know which tools are involved. itogai has no relationship with those companies except the license codes described above.
7. Turning a source off
itogai stops reading from a disconnected source immediately, and a raw file you uploaded is deleted as soon as it has been read and within twenty-four (24) hours if reading fails or you never finish the steps. Metadata and structured signals already derived remain part of your TrustGraph™ record until you delete them, delete the import they came from, turn content signals off for that source, or delete your account. Section 7.4 of the Customer Terms of Service and Section 11.3 of the Privacy Policy state the rules, including the seven (7) day deletion of cached metadata not yet incorporated into the structured record.
You may also revoke an authorization in the settings of the source itself, with the same effect.
8. How this page changes
This page changes when itogai’s Data Source Registry changes: a source is added, a label moves from In development to Available now, a description is corrected, or a source is removed. Those are page updates, published with the version incremented, and they change no contract. Anything that would widen what itogai reads (a new way for data to enter an account, or a higher level for a category of source) is a change to the Customer Terms of Service and the Privacy Policy, made with the notice and the consent those documents require, never by an edit to this page.
Subscribe to changes: write to legal@itogai.com with the subject line “Register notifications”.
9. Contact
legal@itogai.com for this page. privacy@itogai.com for data subject and privacy rights requests, including removal requests from people who are not users.
Postal address: Itogai LLC Attn: Legal Department 4821 Jumping Way Lake Worth, Florida 33467 United States of America
10. Changelog
New in this release. This page did not exist before September 21, 2026.
Amended September 21, 2026, before first publication. This page was first drafted as a contractual Data Source Register, incorporated by reference into the Customer Terms of Service and the Privacy Policy. It is now the informational page Supported sources and import methods, at the same address, so that a source can be added or relabeled without a contract change. No protection was dropped in the change: the three levels and the two rules that bind them now sit in Section 7 of the Customer Terms of Service and Section 4 of the Privacy Policy by category, the rule that raising a level is a material change that also needs your consent sits in Section 7.3 of the Customer Terms, the rejection of an upload containing email message bodies sits in Section 7.3 of the Customer Terms, the rule that free-text fields in a record system are not read sits in Section 3 of the Privacy Policy, and the rules on turning a source off sit in Section 7.4 of the Customer Terms and Section 11.3 of the Privacy Policy. Five entries were added for conversation exports and phone contacts, and the entries are now grouped by the way data enters an account. The App Defense Alliance names the CASA level itogai holds Assurance Level 1, formerly Tier 2, and the page now says so.
Also amended September 21, 2026, before first publication. The entry Share to itogai from your phone is listed under conversation exports, as In development, because the itogai mobile application is a live surface.
Document version: DSR-2026-09-21 v5.0. Published at itogai.app/legal/data-sources.
© 2026 Itogai LLC. All rights reserved. itogai, the itogai logo, Trustbound, TrustGraph, TrustRings, TrustReach, and Akai are trademarks of Itogai LLC.