Where your data lives

1. What EQO is, in a sentence

EQO is a personal AI agent you reach on WhatsApp, by email, in a browser, in an Android app and in a desktop app. It remembers what you tell it, runs scheduled workflows, and hosts small apps — expenses, tasks, health records — whose tools it can call on your behalf. Where all of that runs is your choice, and the next section says what each choice means.

This document is specific on purpose. Any sentence here that is not literally true of the code is a bug, and you can tell us about it at hello@tryeqo.com.

2. The four setups

Setup	Where your data is stored	What EQO receives
Local only Most private	The computer running the EQO desktop app, and nowhere else	Nothing. There is no account to send it to (section 5)
Own cloud Private	Your own Cloudflare account, under Cloudflare's terms, plus your computer	Nothing. We have no access to that account (section 6)
EQO Cloud + computer Hybrid	Your computer for its own data. Cloud chats in our Cloudflare account (section 4)	What passes through EQO Bridge on its way to your computer (section 7), and the cloud chats
EQO Cloud only EQO holds it	Our Cloudflare account, one store per account (section 4)	Everything the agent works with, because we run it. The web app, the Android app and the desktop app can all sign in to it

The path from your phone to your computer, in the two setups that have one, is EQO Bridge. Section 7 says who can see what passes along it.

3. The honest summary of the trade

An agent that reads your mail and remembers your preferences needs your mail and your preferences. We are not going to dress that up. What we can tell you precisely is where it sits, who can reach it, how long it stays, and how you get it back or get rid of it — which is the whole of this page. EQO Cloud only is the easiest setup and the one where we hold the most. Local only and your own cloud trade some convenience for keeping it away from us.

4. EQO Cloud: where it physically sits

EQO Cloud runs on Cloudflare, in an account we control. Two different stores, for two different kinds of data:

What	Where	Shape	How long
Conversations, memory, app records	A Durable Object with its own embedded SQLite database, one per account	Addressed by your account id at runtime. No cross-account query exists, because there is no table that spans accounts	Until you delete it. Memory is the product — expiring it silently would break the thing you pay for
Account and billing	A D1 database — our control plane	One row per account: identity, plan, billing state, which channels and connectors are linked, your device list, the computers attached to your account, and counters	While the account exists, plus the billing records tax law requires
Model inference	Cloudflare Workers AI, on our account — or the model provider you connect with your own key	Your prompt and the tool results go to the model for the duration of the turn	Not stored by us beyond the conversation record above. A provider you connect keeps what its own terms say
Operational logs	Cloudflare's log store	Method, path, error class, timing. Prompt and completion bodies are excluded deliberately, so a crash report cannot become a transcript	Cloudflare's retention for Workers observability

Why a store per account, rather than one big database

A shared table is one missing WHERE clause away from a leak, and that class of bug is the most common way small products lose customer data. A Durable Object is addressed by your account id before any code runs, so the isolation is in the addressing rather than in every query we write. It is also the reason we can delete your data by destroying a store instead of hunting for rows.

5. Local only: the desktop app with no account

Without an account, the EQO desktop app keeps your chats, memory, apps and files in a database on that computer. EQO receives none of it: there is no account to send it to. If you later sign the computer in to EQO Cloud or to your own cloud, section 7 applies from then on.

• Models. A computer with no account uses only models running on it, such as Ollama or a compatible server you run yourself. Cloud models are refused until you sign in.
• The browser. By default the agent uses the Chrome already on that computer. If you choose a cloud browser provider instead in Settings → Browser, that provider sees the pages it opens for you (section 9).
• Your phone at home. If you turn it on in Settings, a phone on the same Wi-Fi can reach the computer directly, without going through any EQO server.

6. Your own cloud: EQO in your Cloudflare account

You can deploy EQO's server to your own Cloudflare account and sign the EQO apps in to it. Your conversations, memory and app records are then stored in that account, and Cloudflare holds them under its terms with you, as described in its customer data processing addendum. The model is your account's own Workers AI, or a provider you connect with your own key.

EQO has no access to that account. The server you deploy holds no EQO credential, so it does not report usage, conversations or anything else to us. We wrote the code it runs; we do not operate it. The exceptions are only the EQO-run services you choose to route through, which pass the traffic they carry through us: EQO Bridge via EQO Cloud (section 7), and WhatsApp or email if they reach your agent through our relay.

7. EQO Bridge: reaching your computer from your phone

EQO Bridge lets your phone and your other devices use a computer running the desktop app, and the data saved in its apps, when you are away from it. The computer keeps an outbound connection to a relay, and requests travel along it. The app shows which relay is in use.

• Bridged via EQO Cloud. The relay is ours. Requests and responses pass through our servers in bounded chunks. Their contents are not written to storage or to logs; like any other request, the method, the address path and the timing appear in our operational logs (section 4). The connection is encrypted between each device and us, but it is not end-to-end encrypted: it is readable on our servers while it passes through, so we will not tell you that we cannot see it. What we promise is that we do not keep it or use it.
• Bridged via your cloud. The relay is your own cloud (section 6), and EQO is not in the path.

Either way the data itself stays on the computer. Only your account's own devices, and guests you invite yourself, can reach it.

8. Phones

The Android app

The app is a client, not a place your data lives. It signs in to EQO Cloud, to your own cloud, or to a computer of yours, and does everything by asking that server. The permissions it asks for are the ones that implies: network access, notifications, and the microphone when you talk to it instead of typing.

Phone control from the desktop app

The desktop app can operate an Android phone for you over ADB on your Wi-Fi, once you switch on "Allow EQO to control" for that phone. To do that it reads the phone's screen:

• Screenshots stay on the computer and are shown only to you, beside the chat. They are not stored in your conversation and are not sent to the model.
• The text and buttons on the screen are what the model gets, so it knows where to tap. With a local model that never leaves the computer. With a cloud model, that provider receives it as part of the prompt.
• If you watch from another device through EQO Bridge via EQO Cloud, the screenshots travel through that relay (section 7).
• EQO never types a PIN, a password or a one-time code, and it stops for you before any step that would send, pay, book or delete.

9. Who else receives data, and why

• Model providers you choose. If you connect a model provider such as Gemini, OpenRouter, Inception Labs (Mercury), Fireworks AI or Azure with your own key, your prompts and tool results go to that provider and its terms apply to them. With a model running on your own computer, nothing goes to a provider.
• Browser providers you choose. If you pick a cloud browser such as Browser Use, Steel, Browserbase or Cloudflare Browser Rendering, it opens and sees the pages the agent visits for you, under that provider's terms. EQO Cloud uses a provider of our choosing for its own browser.
• Web search. When the agent searches the web, it sends the short search phrase to You.com, the default search provider, and receives titles, links and snippets. EQO Cloud uses You.com's keyless profile by default; when we have configured a Tavily or Brave Search key, the query goes to that provider first and You.com is the fallback. Searches are limited per account per day. On a computer or own-cloud server, its operator can instead configure You.com with a key, Tavily, Brave Search or a SearXNG instance; that provider receives the query under its own terms.
• WhatsApp. Messages to and from your agent travel through WhatsApp, which means Meta handles them like any other WhatsApp message. Their terms apply to that leg. If you would rather nothing reach Meta, use email, the web client or the app.
• Email. Your agent has an address on our domain. Inbound and outbound mail passes through the mail providers between us and you, as all mail does.
• App connectors. On EQO Cloud, Gmail, Calendar, Drive, Slack, Notion and the rest connect through Composio's managed OAuth. Traffic runs from us to Composio to the target API, and those OAuth tokens sit with Composio, not with us. You grant each connection yourself and can revoke any of them at any time, which immediately ends our access to that app. Composio's own terms apply to what they hold.
• Payments. Card details go to Dodo Payments, the merchant of record, on their surface. We receive the fact that you paid and what for.
• Sign-in. Firebase Auth answers exactly one question — who are you.

There is no advertising network, no data broker and no analytics vendor in any of those paths. We have not sold access to your data and we are not planning a product that depends on doing so.

10. What we do not do with it

• We do not train models on your conversations, your memory or your app records. The models we host run on Cloudflare Workers AI; we send a prompt and get text back.
• We do not build an advertising or resale profile of you.
• We do not read your data to improve the product by browsing it. Product decisions here come from counters — how many turns, how many tool failures — not from transcripts.

11. When a human at EQO can see your data

This applies to what we hold: EQO Cloud, and traffic passing through EQO Bridge via EQO Cloud. Two cases, and we would rather enumerate them than write "as necessary".

• You ask us to. A support request where you want us to look at what went wrong. We look at that account, for that problem.
• The law compels us. A valid legal order. We will tell you unless we are prohibited from telling you, and we will not volunteer more than the order requires.

Outside those two, access is restricted to the engineers who operate the service and is used for keeping it running, not for reading it. We are a small team; we are not going to pretend to a certification process we do not have.

12. Secrets and credentials

EQO will not accept a password or an API key typed into a conversation. A secret in a chat is in that chat's history forever, is re-sent to the model on every subsequent turn, and can be printed straight back out by the model. If you send one, we will tell you to rotate it rather than use it.

Access to your apps happens through OAuth grants instead, described in section 9. A model or browser provider key you add in Settings is kept in an encrypted vault on the server it belongs to — your computer, your own cloud or EQO Cloud — and is never shown back in full.

13. This website

tryeqo.com loads no analytics, no advertising pixels and no third-party cookies, and it sets no cookie of its own. It is static files on a Worker with no storage bindings.

The one third party your browser contacts on this page is Google Fonts, which serves the two typefaces and therefore sees your IP address and user agent when it does. If that ever becomes unacceptable, the fix is to self-host two font files, and we will.

14. Getting it out, and getting rid of it

• Export. Settings → Data → Export my data gives you your conversations, your agent's memory and your app records as JSON. Not a summary: the contents of your store.
• Delete everything. Settings → Data → Delete my account destroys the per-account store. The conversations, the memory and the app records go with it, and we cannot get them back for you afterwards — that is what deletion means.
• Connector access. Revoke each grant from the app, or from the provider's own security page.
• Close the account. Email hello@tryeqo.com and we delete the control-plane row, your channel routing, your device list and your attached computers along with the store. We keep the billing records tax law requires us to keep, and nothing else.
• Local and own cloud. That data is not ours to delete. Remove it from your computer, or delete the deployment from your Cloudflare account.

Backups are the usual caveat and we will not hide it: a deleted store can persist in Cloudflare's own point-in-time recovery window before it ages out. Nothing we run reads from it, and we do not restore an account we deleted at your request.

15. Where you are, legally

Whatever your jurisdiction, the rights people usually want here — see it, take it, correct it, delete it — are all available as buttons rather than as requests, which is the arrangement we prefer. If you need something the buttons do not cover, write to us and a person will do it.

16. Children

EQO is not built for, marketed to, or knowingly made available to anyone under 16. If we learn that an account belongs to a child, we close it and delete the data.

17. Changes

If this policy changes in a way that affects where your data goes, we will say so in the app before the change takes effect, not quietly amend this page. The date at the top is the only version marker, and older versions are in the git history of the site.

18. Contact

hello@tryeqo.com reaches a person. Privacy questions, deletion requests and "your page says X but the code does Y" all go to the same place.

Who operates EQO

EQO is operated by eStreetz Technologies Pvt Ltd, a company registered in India. “EQO”, “we” and “us” throughout this document mean eStreetz Technologies Pvt Ltd. Reach us at hello@tryeqo.com.