TEZ Browser

Privacy and support for the Android app app.tez.browser, published by xAGI Labs.

Contact: saurav@xagi.in

Privacy policy

TEZ provides web browsing and optional, limited free AI assistance. This policy explains how the app and its backend process information.

Ordinary browsing and device storage

Websites receive requests directly through Android WebView and apply their own privacy policies. TEZ stores normal browsing history, bookmarks, preferences, site permissions, cookies and site data on your device. Browsing history is not routinely uploaded to TEZ's AI service. Search requests go to your selected search provider.

Where supported by WebView, private tabs use a separate disk-backed profile. TEZ attempts to clear its browsing data when the private session closes and delete remaining private profiles at the next launch. Private browsing does not hide activity from websites, network providers or downloaded files. Downloaded files can remain after private tabs close.

When you request AI assistance

When you start an Ask Tez task or request a summary, your request and selected information from the current webpage are transmitted to our Cloudflare backend and OpenAI for processing. This includes visible text, control labels, minimized web addresses, the assistant's action history, and locale/time information. We filter sensitive fields and pages, but automatic redaction cannot guarantee that all personal information in page text is removed. Do not request AI processing of content you do not want sent to these providers.

AI assistance is disabled in private tabs. The app is designed not to send cookies, passwords, screenshots or form values you entered yourself. The AI provider receives a pseudonymous safety identifier derived from your random TEZ account identifier. AI results can be incorrect.

Access, operational data and retention

Enabling free AI creates a pseudonymous account linked to a random installation identifier, without an email sign-up. Reconnecting the same installation retains its usage allowance. The backend stores account/session timestamps, hashed invite and refresh credentials, request/token quotas and spending counters. To limit registration abuse, we store a keyed, daily-changing hash of the network IP address and daily registration counts. These counters are pruned on subsequent registrations after their UTC day ends; raw IP addresses are not stored in these application records. Shared networks may encounter registration limits. Refresh credentials on the device are protected using Android Keystore encryption.

Our backend does not routinely persist page text, prompts or AI results as application records. If you choose “Report AI content” and confirm Send report, we store the reported output, selected reason, report identifier, account identifier and timestamp for safety review for up to 30 days. Reports are available only to authorized operators; they are not sent to the AI provider. We use reports to investigate abuse and improve content safeguards. Operational logs contain request identifiers, route templates, status, timing, model and usage/error metadata, rather than page content or credentials. Cloudflare processes network and service metadata under its service policies. Account quota history is pruned after seven days and aggregate spending history after thirty days; active account/session records can remain until removed.

OpenAI requests use store:false; this does not disable provider abuse-monitoring retention. Data may be processed outside India. See OpenAI's privacy policy and Cloudflare's privacy policy. We do not promise zero retention or India-only processing.

Permissions and speech input

Websites may request camera, microphone or location access. Access requires the applicable Android and site permissions. You may revoke permissions in Android settings or TEZ's site settings. File selection and downloads process the files you choose. Optional voice input uses your device's speech-recognition service, which may send audio to its provider under that provider's settings and policy.

Your controls and deletion requests

In TEZ Settings, choose “Delete AI account and data” and confirm to permanently remove your AI account, sessions, refresh credentials, installation mapping, usage records and safety reports. AI is turned off and local session credentials are removed. A token-blocking tombstone is kept for up to two hours to stop existing tokens, then removed automatically. Aggregate service spending records (up to 30 days), daily registration-abuse counters and provider security records are not erased by this action. Re-enabling AI creates a new anonymous account. You can also disable AI, disconnect the session, clear local history/cookies/cache, and manage site permissions. Disconnecting alone clears local access and does not delete backend records. Uninstalling removes app-private local data, but public downloaded files may remain.

To request deletion of your TEZ AI account and associated server data, email saurav@xagi.in with the subject “TEZ account and data deletion.” Describe your request so we can help identify the anonymous account and verify ownership; we may ask you to confirm through your existing app session. You may request deletion of safety reports without deleting the AI account. Do not send passwords, access tokens or API keys. We may request non-secret information to identify the account. We aim to respond to deletion requests within 30 days. We will explain any data retained for security, legal obligations or provider retention requirements; provider abuse-monitoring records follow the provider policies linked above. You can submit a request without reinstalling the app.

Support and changes

For privacy questions, app support or problems with AI responses, contact saurav@xagi.in. We update this page when our processing changes; the effective date above identifies the current policy.