Effective Date: September 21, 2026 for any Account created on or after that date. For an Account existing on that date, this document takes effect thirty (30) days after itogai gives notice under the Customer Terms of Service. This document is new, so no prior version is displaced and none governs in its place. Last Modified: September 21, 2026 Document Version: PSR-2026-09-21 v5.0
This register lists every surface on which Itogai LLC (“itogai”) delivers the Subscription Service, what each surface does, what device capabilities each may request, and what each requests as built. It is incorporated by reference into the Customer Terms of Service and the Privacy Policy.
Why this register exists
No itogai contract or policy enumerates the surfaces it applies to. Scope is defined by what itogai does, never by where itogai does it: the Subscription Service means the itogai relationship intelligence platform wherever and however it is accessed. A new surface is covered by every existing document from the day it exists.
That rule leaves one question a person is entitled to ask, which is what surfaces exist and what each asks for on their device. That is what this register answers, and adding a surface updates this page rather than amending a contract.
The two columns that matter
“May request” is the envelope. It is what the contracts and policies permit that surface to ask for. It changes only by amendment.
“Requests” is what the surface, as built, asks for and the moment at which it asks. It changes by reversioning this register.
A capability listed as “may request” but not as “requests” is not in use. A capability a surface requests that this register does not carry is both a breach of this register as incorporated and a defect in the surface. itogai corrects the surface and gives notice under Section 4.
1. Surfaces
1.1 Platform
| What it is | The authenticated web application. The full Subscription Service |
| Delivered at | platform.itogai.app, with onboarding entry at platform.itogai.app/start |
| Runs on | itogai’s own hosting, single origin, application and client served together |
| May request | Browser notifications. Clipboard access on explicit user action. File selection on explicit user action. Microphone access, where a person chooses to record a voice input |
| Requests | Browser notifications, on explicit opt-in. File selection when the person chooses to upload. Microphone access at the moment a person chooses to record a voice input |
| Microphone | Requested only at the moment a person chooses to record a voice input, and only on this surface. Declining it stops that action and nothing else |
| Does not request | Location of any precision. Camera. Device contacts |
| Analytics and monitoring present | Product analytics and error monitoring with masked session replay, each identified in the Sub-processors register. No research telemetry, no advertising software, no third-party font or asset host |
1.2 Marketing website
| What it is | The public informational website. No authenticated functionality |
| Delivered at | www.itogai.app, with itogai.app and itogai.com redirecting to it |
| Runs on | A third-party website platform, identified in the Sub-processors register |
| May request | Nothing from the device |
| Requests | Nothing from the device |
| Cookies | Strictly necessary, functional, analytics and marketing categories, as the Cookie Policy describes |
| Assistant | A public assistant on the website answers a visitor’s questions about itogai. Text a visitor types is sent to a model provider in the AI Provider Register. It asks for no account, requests nothing from the device, and holds no conversation once the page closes |
1.3 Mobile application
| What it is | The itogai application for iOS, iPadOS and Android |
| Distributed through | The Apple App Store and Google Play |
| Authentication | Standards-based authorization code flow with PKCE, conducted in the system browser. A password is never entered into, handled by, or visible to itogai’s application code |
| Credential storage | Authentication tokens are held in the operating system’s own secure keystore and nowhere else |
| May request | Photo library access, to set a profile photo. Camera access, to take a profile photo. Notifications |
| Requests | Photo library access and camera access, each only at the moment a person chooses to set a profile photo |
| Notifications | Within the envelope for this surface. Where a release exercises it, notifications are requested on explicit opt-in only, and no notification permission, entitlement or service extension is declared in a build that does not use one |
| Does not request | Location of any precision. Microphone. Device contacts. Calendar. Health data. Any advertising identifier |
| Declared and not exercised | A permission declared in a build and not exercised by that build is a defect, and itogai does not ship one |
| Contains no | Advertising software, attribution software, analytics software, crash reporting software, or device fingerprinting of any kind |
| Account deletion | Available from inside the application, without contacting anyone and without switching to another surface. A deletion request page is also published at itogai.app/support and is reachable without signing in |
| Purchases | None. The application offers no purchase, upgrade or checkout path of any kind, and sells nothing. Plans and Sparks are bought only on the web platform. Section 3.4 of the Customer Terms of Service states this |
| Support | itogai.app/support, maintained for the life of any store listing |
On a denied permission. Where a person declines a permission, the action that requested it stops. A refusal never triggers a network request and never writes a value into the person’s profile.
1.4 Browser extension
| What it is | A browser extension that lets a person save a contact from a page they are already looking at and, on a site the person has consented to, read a conversation that is on screen to extract relationship signal |
| Declared sites | WhatsApp Web. No professional network is a declared site: the only path from one is the archive the customer exports and uploads, as Section 3.1 of the Privacy Policy states |
| May request | Read access to the page the person is viewing, on the sites the extension declares, for the purpose of saving a contact the person chooses to save, and of reading a conversation the person has on screen on a site they have consented to |
| Requests | Read access to the page the person is viewing, on the sites the extension declares, at the moment the person chooses to save a contact, and, on WhatsApp Web where the person has consented for that source, while a conversation is on screen |
| Never stored | Message text. A conversation read on a consented site is on-screen reading under Section 3.1 of the Privacy Policy, handled at Level 2 only with content signals on for that site: read in memory, signal extracted, raw text discarded. The extension never reads an email page, never runs on a site the person has not consented to, and never runs while the person is not on that site |
1.5 MCP server
| What it is | A Model Context Protocol server that lets a person work with their own itogai data from an AI assistant they already use, such as Claude, ChatGPT or Gemini, or any compatible client. It reads the person’s contacts, circles, paths, signals and scores at the depth the person’s plan allows, and it prepares actions: a draft, a note, an introduction request, an enrichment. Every action that sends a message, spends a Spark or changes a record is confirmed by the person inside itogai before it happens. The server returns the requesting person’s own data and nothing else |
| Delivered at | mcp.itogai.app |
| May request | Nothing from a device. It authenticates against the Subscription Service and returns the requesting person’s own data |
| Requests | Nothing from a device |
2. What no itogai surface does
Stated once, because it applies across every surface present and future, and because a negative stated per surface invites the reading that it was omitted deliberately somewhere:
- No itogai surface requests a device’s precise or coarse location.
- No itogai surface requests microphone access except the platform, and there only at the moment a person chooses to record a voice input. No surface listens, records or transmits audio at any other time, and no mobile surface requests it at all.
- No itogai surface reads a device’s address book.
- No itogai surface contains advertising, attribution or ad measurement software.
- No itogai surface collects a device advertising identifier or performs device fingerprinting.
- No itogai surface sends a message without a person having reviewed that specific message and clicked send on it.
Any of these changing is a material change under the notice rule in Section 4.
3. Backend hosts
The host a surface communicates with is an implementation detail and is recorded here rather than in any contract, because nothing in any itogai document turns on which host it is.
| Surface | Communicates with |
|---|---|
| Platform | Its own origin |
| Mobile application | platform.itogai.app |
| Browser extension | platform.itogai.app |
| MCP server | mcp.itogai.app, which communicates with platform.itogai.app |
A build that ships pointing at a development environment is a defect. Every production build carries its production host, identity tenant and client identifier from its build profile rather than from an unset default.
4. How this register changes
One definition governs every itogai register and every legal document wherever a change affects personal data. Where a document turns on something else, it states its own trigger, and the same thirty (30) days’ notice applies:
A change is material when it expands the categories of personal data processed, expands the purposes of processing, expands the categories of recipients, or reduces a right the customer holds.
Material: thirty (30) days’ advance notice, by publication and by email to the registered account owner, with the objection route stated at the end of this Section. Adding a device capability to the “may request” column requires an amendment to the Customer Terms of Service and the Privacy Policy. It is material, and it is not made by reversioning this register. So is a surface beginning to request a capability it did not previously request.
Routine: published immediately with the version incremented. Adding a surface that requests no capability beyond those already in this register is routine. So is removing a capability or changing a host.
The route to object. During the notice period the Customer may object in writing to legal@itogai.com. itogai and the Customer will discuss the objection in good faith, and if they cannot agree a path forward within thirty (30) days of the objection, the Customer may terminate the affected portion of the Subscription Service for material breach of the Data Processing Agreement, and itogai will refund prepaid fees attributable to the period after termination. Separately, a material change to this register gives every Customer the right to terminate before it takes effect and receive a pro rata refund of prepaid unused fees, under Section 20.5 of the Customer Terms of Service. That right does not require the Customer to object first, or to explain why.
Subscribe to changes: write to legal@itogai.com with the subject line “Register notifications”.
5. Contact
legal@itogai.com for this register. privacy@itogai.com for data subject and privacy rights requests. support@itogai.com and itogai.app/support for product support.
Postal address: Itogai LLC Attn: Legal Department 4821 Jumping Way Lake Worth, Florida 33467 United States of America
Changelog
New in this release. This register did not exist before September 21, 2026. It exists so that no contract has to enumerate the places itogai runs, and so that a person can see what each surface asks for on their device.
Amended September 21, 2026, before first publication. The second column is Requests, what each surface asks for as built and the moment at which it asks. This register describes each surface as designed and carries no status line. Whether a surface is available is shown in the product. The browser extension entry now states its declared sites and what it never stores, the MCP server entry states the actions it prepares and the confirmation each one requires, and the marketing website entry names the public assistant that runs on it.
Document version: PSR-2026-09-21 v5.0. Published at itogai.app/legal/product-surfaces.
© 2026 Itogai LLC. All rights reserved. itogai, the itogai logo, Trustbound, TrustGraph, TrustRings, TrustReach, and Akai are trademarks of Itogai LLC.