Last updated 27 September 2026

Privacy notice

Account Router is a private integration service operated by Zayn Khan for accounts the operator is authorized to use. This notice describes the service currently implemented. New integrations may require an updated notice and additional authorization.

Information accessed and its purpose

Depending on the connected account and requested task, the service may access account identifiers, email messages and drafts, calendar events and attendees, files and their metadata, or repository information. It uses this information to perform the operator’s requested actions and verify that each action uses the intended account.

Where information is stored

OAuth tokens and application secrets are stored in macOS Keychain on the operator’s Mac. Local registry and database records store account identifiers, client scopes, routes and execution status. Audit records contain operational metadata rather than message bodies.

Actions awaiting human approval, which may include message content and recipient details, are encrypted in the local database using a Keychain-held key. An approval expires after 30 minutes; expiry stops execution but does not automatically delete its stored record. Local records and backups remain until the operator removes them.

Information shared to perform a task

The router sends authorized requests to the relevant service provider and returns results to the assistant or client that requested them. Those results may contain account content, and the chosen client or AI provider has its own data-handling terms.

If optional automatic routing through Jev is configured, the task description submitted for classification is sent through OpenRouter. Browser tasks use the operator’s browser and may involve a configured model provider. Explicit account selection does not require automatic classification. Provider credentials are not included in model requests.

Limited use

Account Router’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Account Router does not sell Google user data or use it for advertising. Its Google-data access supports the requested account features; it contains no model-training functionality. Use through a connected assistant must also comply with Google’s Limited Use requirements.

Access, revocation and deletion

The operator can revoke an assistant client through the private dashboard, disconnect an account by revoking access with its provider, and remove local credentials and records. Google access can be revoked in the Google Account’s third-party connections settings. Removing a router credential does not by itself delete provider content or copies held by a requesting assistant.

This information website

These static pages do not contain analytics, account sign-in, advertising or tracking scripts. The hosting provider may process ordinary web-request information such as IP addresses and access times.

Contact

For questions about account access or local record deletion, contact khanzayn95@gmail.com.

Back to Account Router