Khat by Taar AI
Privacy policy
Effective 16 November 2026
Khat is a native email client for Mac and iPhone. This policy describes the current preview app, its development relays and this website.
Your mailbox remains with your email provider. Khat accesses it directly from your devices. Mail caches and search indexes are local. Optional relays handle routing metadata and encrypted data as described below; they do not hold your mailbox OAuth credentials.
1. Who to contact
Khat is developed by Taar AI. For privacy questions, access or deletion requests concerning data handled by Khat services, contact dev@taar.ai. Please do not email passwords, access tokens or mailbox contents. We may need to verify a request before acting on it.
2. Google and Microsoft account access
When you connect an account, the provider handles sign-in and asks you to approve permissions. Depending on the features you use, Khat accesses:
- Account identity: your name, email address and provider account identifiers, to show and distinguish connected accounts.
- Email: messages, subjects, senders, recipients, folders or labels, message state and attachments, to display, search and manage your mailbox. Sending permission lets Khat send messages and replies you initiate; management permission supports actions such as archive, mark read and move to Trash.
- Contacts: names and email addresses for recipient suggestions and inline mentions, when read-only contacts permission is granted.
- Sending identities: provider-supported aliases and Send As addresses, to offer the identities your mailbox is permitted to use.
OAuth access and refresh credentials are kept in device Keychain storage. Khat's relays do not store them. Your email provider processes requests under its own policies and retains the mailbox itself.
3. Local storage and on-device processing
Khat stores a working mail cache, encrypted local search index, organization preferences and drafts on your devices. Downloaded attachments are also saved locally. Account information and locally learned sender or domain scores support grouping and the transactional/marketing split. Optional Apple on-device intelligence processes the information needed for a feature, such as a sender and subject for classification. Khat does not send mailbox content to a hosted AI model for these features.
Local data remains until it is removed through the app, its cache controls, or your device's storage controls. Revoking provider access stops future authorized access but does not itself erase copies already stored on a device. Removing an app or a paired device may leave downloaded files or previously received data that you must delete separately.
4. Optional encrypted device sync
Paired devices synchronize organization information, including groups, sections, Watch list preferences and learned domain scores. The Mac leads this organization state. Application records are end-to-end encrypted between trusted devices. Mailbox tokens, message bodies and local database keys are not part of this sync.
The relay forwards encrypted frames and does not spool application payloads or keep a sync-message history. It retains an encrypted routing registry containing random space/device identifiers, public signing keys and signed membership or enrollment records. It can observe connection IP addresses, timing and traffic sizes. Pairing invitations and pending requests expire after five minutes. Routing registration is retained while a space or device remains enrolled; removal and revocation controls stop the affected routes. Revocation cannot remotely erase data already received by another device.
5. Optional development notifications
The current notification service is a private development service. It processes APNs device tokens, random routing identifiers, provider subscription identifiers and state, event or history identifiers, and delivery-processing acknowledgements. Its routing state and bounded retry queue are encrypted at rest. It does not store mailbox OAuth access or refresh tokens.
Gmail events provide account-change hints. The phone uses its own provider credentials to look up the new mail. Microsoft rich events can contain message previews encrypted to a key held on the phone. The relay can temporarily hold this opaque ciphertext until the phone resolves it or it expires, for no longer than 15 minutes. Pending notification jobs expire after five minutes. Readable message subjects, bodies, senders and attachments do not belong in the relay registry.
The phone resolves or decrypts content for presentation by iOS. Apple processes push delivery, and notifications may reveal email information on your lock screen according to your iOS settings. Acknowledgements describe processing, not proof that you saw or read an alert. Remove a notification route or disable notifications to stop that route. Provider subscriptions and previously delivered notifications may also need to be removed or allowed to expire. Renewal and delivery remain best effort in this preview.
6. Remote images and links
Email images load by default. Loading remote images or following links can contact the sender's or another third party's servers, revealing information such as your IP address and the time of access. A sender may use image URLs to track opens. You can disable remote-image loading in Khat's settings.
7. Sharing and permitted use
Khat uses account data to provide the mail, contact, organization and notification features you choose. We do not sell mailbox data, use it for advertising, or use it to train generalized AI models. Google, Microsoft and Apple necessarily process the provider and platform operations described above. Infrastructure providers host the public website and development relays and may process operational network or request metadata. End-to-end encryption protects sync application records from the relay.
Khat's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
If you send a support request, we receive the information you choose to include and use it to address that request. Do not include sensitive mail unless necessary. We may disclose information when legally required or to address abuse or security threats, subject to applicable law.
8. Your choices
- Disconnect accounts in Khat and revoke authorization in your Google account connections or Microsoft account/organization permissions.
- Use your device's notification and lock-screen controls, disable remote images, and remove unwanted connected-device routes.
- Delete local caches, drafts and downloaded files when you no longer need them. Removing a local cache does not delete the provider mailbox.
- Contact dev@taar.ai to request removal of service-side routing registration or to ask about information we hold. Encrypted payload expiry follows the limits above; provider-held mail is managed with that provider.
9. This website and policy changes
This information website does not connect to your mailbox. We do not add advertising or analytics trackers to it. The hosting and delivery infrastructure may process technical request metadata to serve and secure the site. Khat is in development; we will update this policy when its data handling changes and show the new effective date here. Material new permissions are also subject to provider consent.