Privacy Policy

Effective and last updated August 4, 2026

Scope

This policy explains how Chiho AI (“Chiho,” “we,” “us,” or “our”) collects, uses, discloses, retains, and lets you control personal information across chiho.ai, the Chiho Telegram CRM, and Chiho tools used from ChatGPT or another compatible AI client (collectively, the “Service”).

This policy covers both account holders and people whose details appear in a connected account's authorized Telegram or CRM content. A business or team customer may be responsible for its own instructions to Chiho; this policy still describes the data Chiho processes to provide the Service.

Data we collect and return through tools

Account, authentication, and connection data

Your name, email address, Firebase account identifier, team membership, subscription tier, OAuth grants and scopes, agent-token status, connected Telegram account identifiers and display names, and connection or reauthentication status. We never return passwords, bearer tokens, Telegram session strings, access hashes, or encryption keys through Chiho tools.

Telegram content and metadata

For Telegram accounts you choose to connect, we process chat, contact, group, and folder names; Telegram peer and message identifiers; usernames where the core Chiho service needs them; message text and media type; sender display names; message dates; folder membership; and connection health. Chiho accesses only the accounts and chats within the scope you authorize.

CRM and automation data

Tags, suggested priorities, company links and roles, summaries, next steps, follow-up tasks and their due dates, automation rules and instructions, and automation activity. These records may describe people in your connected chats because they are the contacts you ask Chiho to organize.

Tool inputs and action data

When you use Chiho from ChatGPT or another compatible AI client, we receive the tool name and the fields needed for the request. Depending on the tool, those fields can include an account or chat identifier, search text, message text, recipient or group, an explicitly supplied Telegram user identifier, schedule, folder, tags, company, task, rule, preview identifier, approval decision, and idempotency value. Consequential Telegram actions use previews or explicit approval where the tool requires them.

Tool outputs returned to your AI client

We return only the data needed to answer or complete the request: connection status; scoped account, chat, group, folder, and contact display names and opaque routing identifiers; requested message text, dates, sender display names, and message identifiers; CRM tags, companies, summaries, tasks, rules, and activity; preview recipients and message excerpts; and action status, counts, warnings, or recipient-level delivery results. We remove internal access hashes, payload hashes, token capabilities, session data, write-run and batch identifiers, exact internal expiry timestamps, unrelated usernames, debug objects, logs, and request or trace identifiers before returning a tool result.

Billing, support, and technical data

Stripe customer, checkout, subscription, invoice, and payment-status metadata (not full card numbers); messages you send to support; IP address; browser and device type; authentication events; request time and route; error code; and strictly necessary cookie or local-storage data used for login, security, and preferences. Chiho does not currently use third-party advertising or behavioral-analytics trackers on its website.

Why we use data

Provide the website, connected Telegram CRM, OAuth connection, and requested tools.
Read, search, sync, organize, summarize, and display the Telegram and CRM data you request.
Prepare, approve, send, schedule, invite, leave, or reorganize Telegram content when you invoke a write tool.
Generate requested summaries, tag suggestions, company suggestions, tasks, and follow-up drafts.
Authenticate users, enforce personal and team scopes, apply rate limits, prevent abuse, and investigate failures.
Manage subscriptions, provide support, maintain the service, and comply with legal obligations.

Chiho does not sell personal information, use it for targeted advertising, or use customer Telegram or CRM content to train a general-purpose AI model. We may create aggregate statistics only after removing information that can reasonably identify a person or account.

Who receives data

OpenAI and your selected AI client

When you connect Chiho to ChatGPT, OpenAI transmits your Chiho tool call to us and receives the minimized tool result described above so it can answer you. A copy may remain in your AI-client conversation under that provider's privacy and retention controls. Other compatible clients act in the same role when you choose to use them.

Telegram and intended Telegram recipients

Telegram provides the connected account and chat data. For a requested write action, Telegram and the people or groups you target receive the message, invite, folder-account change, or membership action needed to perform it.

Infrastructure and authentication providers

Firebase and Google Cloud provide authentication, database, and cloud infrastructure. Our hosting, networking, email, monitoring, and security providers process limited account and technical data solely to operate and protect Chiho.

AI inference providers

When you request an AI-generated feature, relevant scoped content and instructions may be sent to OpenAI, Anthropic, or Google Vertex AI, depending on the model configured for the feature, to generate that result under their business or API terms.

Payments and professional recipients

Stripe processes checkout and billing. We may also disclose the minimum necessary data to auditors, lawyers, insurers, authorities, or a corporate successor when required by law or a legitimate business transaction.

Your team

For team-scoped connections, authorized team members and administrators can access the connected accounts, chats, CRM records, and tool activity that the team's permissions make available.

How long we keep data

We apply the following maximum periods unless you delete the data sooner or law requires a longer period:

OAuth authorization codes and access tokens: 5 minutes and 15 minutes, respectively.
OAuth consent interactions and sessions: 10 minutes for an interaction and 24 hours for a session.
OAuth refresh grants and connected-client records: Up to 30 days unless you revoke them sooner.
Agent write previews and encrypted execution payloads: 30 minutes. Automated database deletion normally follows shortly after expiry and can take up to 24 hours.
Agent write and automation-run audit records: 30 days, then automated deletion.
Direct-send rate-limit records: 5 minutes, then automated deletion.
Account, connected Telegram, message cache, and CRM data: While your account is active and until you delete the account or the data. Disconnecting Telegram stops new access but does not by itself delete existing CRM records. Account deletion removes live account and CRM data; residual provider backups are deleted on their normal cycle, no later than 35 days.
Security and operational logs: 30 days, unless a specific event must be retained longer to investigate abuse, protect users, or meet a legal obligation.
Support correspondence: 24 months after the support request closes.
Billing and tax records: Up to 7 years where accounting or tax law requires it; Stripe may retain its own records under its policy.

Your controls and privacy rights

Revoke an OAuth connection or agent token from AI Agent Access. Revocation stops future tool access, but it does not remove a result already copied into an AI-client conversation.
Disconnect a Telegram account to stop future Telegram access, or reconnect it when you choose.
Review and change CRM tags, companies, tasks, rules, folders, and other records in Chiho.
Delete your Chiho account from Profile. This deletes your live Chiho user record and associated dialogs and revokes your Firebase account access.
Use your ChatGPT or other AI-client privacy controls to manage conversations and tool results stored by that provider.
Email privacy@chiho.ai to request access, correction, export, deletion, restriction, or objection, or to withdraw consent where consent is the legal basis. We may verify your identity before completing a request.

Rights vary by location. We will honor applicable rights and explain any lawful limitation. You can decline optional data, but Chiho cannot provide a feature when its required account, chat, or action input is missing.

Security and international transfers

We use access controls, scoped credentials, encryption in transit, encrypted short-lived action payloads, audit controls, and other technical and organizational safeguards. No internet service can guarantee absolute security.

Chiho is based in the United Arab Emirates and uses providers that operate internationally. Data may therefore be processed in the United Arab Emirates, the United States, Europe, or other locations where our providers operate. Where required, we use contractual or other lawful transfer safeguards.

Children

Chiho is not directed to children under 13. People under the age at which they can consent to online data processing in their country must use Chiho only with authorization from a parent, guardian, or organization as required by law. Contact us if you believe a child provided data without required authorization.

Changes and contact

We will post updates on this page and change the date above. If a change materially affects how we use personal information, we will provide additional notice through the Service or by email when appropriate.

For questions, complaints, or privacy requests, email privacy@chiho.ai.