Privacy

Updated November 6, 2026

EchoAgent is a voice assistant that runs on your Mac, and its phone app also works without a Mac. Speech is recognized on your Mac or on the phone. You can use echo, the model service built into EchoAgent, after signing in; its requests pass through our server to the provider of the model you use: DeepSeek for DeepSeek V4.1 Flash, Anthropic for Haiku 5.5, and, through a third-party API service provider, OpenAI for GPT and Google for Gemini; we keep which model you use and how much, and, to improve echo, what you say to it and echo’s answers (see “Improving echo with your conversations”). Sessions you archive while signed in are also uploaded and kept (see “Archived sessions in the cloud”). Or you can use your own API key, in which case requests go straight to the provider you choose. This page explains what we collect, why, who else receives it, and how long we keep it. By using EchoAgent you agree to this policy and to the Terms.

What stays on your Mac

• Your voice. A speech model on your Mac turns it into text. Recordings are never saved or uploaded.
• Your API keys and sign-in token. Stored in EchoAgent’s config folder (~/Library/Application Support/VoiceAgent/agent/auth.json, readable only by your user account). Your own API keys are used only to call the provider you chose and are never sent to us. The sign-in token is sent only to our server to use echo.
• Conversations, background task records and settings. Stored in ~/Library/Application Support/VoiceAgent/. Conversations may include screenshot attachments; these remain with conversation history even after temporary screenshot files are cleaned up. Deleting that folder removes all of them from your Mac. It does not delete anything already sent to a model provider, or sessions already uploaded as described under “Archived sessions in the cloud”.

Your account

You need an account to use echo. We collect only what the sign-in method you choose provides:

• Email. Your email address. We email you a 6-digit code through our email provider (Resend).
• Phone number. Your mainland China mobile number. We text you a 6-digit code through our SMS provider (Alibaba Cloud).
• Google. Your Google account ID and, from your Google profile, your email address (only if Google has verified it), name and profile picture link. We never see your Google password.
• WeChat. Your WeChat identifiers for our app (OpenID and, if available, UnionID), nickname and profile picture link. We never see your WeChat password.

If you sign in with Google and with a code sent to the same email address, both lead to the same account. We also keep when the account was created, when you last signed in, and the interface language you used when signing up, so messages from our server are in your language.

Sign-in codes are stored only as a one-way digest, expire after 10 minutes, and stop working after 5 wrong attempts. Each sign-in creates a random token that stays on your Mac; our server stores only a digest of it, the sign-in method, the time and which Mac it belongs to. Signing out, or our disabling the account, makes the token useless.

Your Mac

When you sign in, EchoAgent sends a digest computed on your Mac from its hardware identifier, never the identifier itself; our server transforms it again with a secret key before storing it. Along with it we keep EchoAgent’s and macOS’s version numbers, the interface language and the last day the Mac used echo. We use this to apply the free limits per Mac as well as per account, so the free limits aren’t multiplied by creating accounts, and to detect abuse.

Network addresses

We don’t store IP addresses in our database. To limit sign-ups, code requests and feedback from one network, the server keeps a digest that changes every day and cannot be turned back into an address, together with short-lived counters. Our hosting provider may record IP addresses in its operational logs.

echo, the built-in model service

• What is sent. Everything the model needs to answer: what you say or type; so echo can understand “this page” or “this project”, the name, window title, browser address and open file or project path of the app in front when you pressed the shortcut; files and command output read while doing a task; screenshots you explicitly ask for; results of background tasks; and the earlier messages of the conversation.
• Which model. echo uses DeepSeek V4.1 Flash, run by DeepSeek, by default. On Mac and Windows you can choose Claude Haiku 5.5, run by Anthropic, instead, and with a pass also OpenAI’s GPT-6.1 Sol, GPT-6 Luna and GPT-6 Astra or Google’s Gemini 4 Argon; which of these your pass includes, and how much of your usage each can take, is shown in the app. The phone app and WeChat use DeepSeek V4.1 Flash. Anthropic doesn’t serve some countries and regions, including mainland China, Hong Kong, Macau and Russia; there echo offers only DeepSeek V4.1 Flash. Our server decides this on each request from the country or region of your network address, as reported by our hosting provider, and doesn’t store it.
• Where it goes. Requests go over an encrypted connection to our server (Vercel, Singapore region), which passes them to the provider of the model you use and streams the answer back. For GPT and Gemini, our server sends requests to a third-party API service provider, which passes them to OpenAI or Google; that provider, OpenAI and Google may process the data in the United States or other countries and regions. Anthropic is based in the United States and may process the data there or in other countries; DeepSeek may process it in mainland China or in other countries and regions. With Haiku 5.5 our server also sends Anthropic a code derived from your account ID, with no name or contact details in it, so Anthropic can tell accounts apart when checking for abuse. Our server never writes the content to its logs. From October 28, 2026 it saves part of each request to improve echo, as described in the next section.
• What the providers do with it. Each model provider processes requests under its own terms and privacy policy and may keep them for a period, for example for security, abuse monitoring or legal compliance. We may change the models or providers at any time.
• What we keep. For each account, Mac and day: how many requests you made, how many times the model was called, the number of tokens, the estimated cost, when you hit a usage limit, and upstream errors. For each account, and for free accounts also for the Mac: when the current 5-hour and weekly limits started and how much of each has been used. We use this to enforce the limits, prevent abuse, plan capacity, and for paid plans and billing. For each request we also keep whether it succeeded or failed, how long it took to start answering and to finish, and which tools were called (names only, no content), to spot slowdowns and errors.
• Answers are AI-generated and can be wrong. See the Terms.

With your own API key, requests go from your Mac straight to the provider you configured, never through our server, and the provider’s privacy policy applies.

Improving echo with your conversations

From October 28, 2026, when you use echo while signed in, we save part of each request to improve echo. This covers every version of EchoAgent for Mac and Windows, and echo conversations in the phone app and in WeChat. Signing in means you agree to this policy, including this section. Using echo before signing in (the free trial) is not saved, and nothing sent with your own API key ever reaches us. This is separate from anonymous usage statistics, which still never include what you said or typed. Archived sessions are covered in the next section.

• What we save. For each request your account makes: what you said (as recognized text) or typed for that request; the name of the app in front when you asked; which model answered; echo’s written answer; and the tools echo called and what it passed to them (for example a command it ran, a search, or text it wrote into a file or message, which can contain what you asked it to write). With them we keep your account, which device it was, the EchoAgent version, the platform and the time. We don’t save recordings, screenshots, the window title, web address, file or project path or selected text that EchoAgent attaches to a request, the results tools returned (such as file contents or command output), or the model’s reasoning.
• Why. To improve EchoAgent and the models it uses: finding where echo misunderstood or failed, checking answer quality, and testing new versions and new models. Only the maintainers can access it. We don’t sell it or use it for advertising.
• Who receives it. Each request still goes to the provider of the model you use (for GPT and Gemini, also through the third-party API service provider) to be answered, as described above; that doesn’t change. The saved copies are kept in our database (Neon, Singapore region) and are not given to model providers or anyone else. If we ever want to share them with a third party, we will update this page and ask for your consent first.
• How long. Until you withdraw your consent or delete your account; there is currently no fixed time limit. What was saved is then deleted, along with any copies we exported to work on.
• Withdrawing. You can withdraw this consent at any time and keep using echo: use Settings → About → Send Feedback (in the phone app, Settings → About → Withdraw Consent; in WeChat, send 撤回同意), or email jiaedwin0605@gmail.com from a way we can match to your account. We then stop saving your requests and delete what was saved under your account; this doesn’t affect what we did with it before. You can also ask for a copy of what was saved, or ask us only to delete it.

Archived sessions in the cloud

From November 5, 2026, when you archive a session on your computer (Mac or Windows) while signed in, EchoAgent uploads that session to our server and keeps it. Signing in means you agree to this policy, including this section. A session is uploaded only to the account that was signed in when you archived it; after you switch accounts, sessions archived under the previous account are no longer uploaded. There is one exception. Sessions that were already archived on a computer before it got the version with this rule (Mac 0.1.100b4, Windows 1.1.36, or later) have no account recorded. Those not uploaded yet are uploaded once, all to the first account signed in on that computer after the update, including any that were archived while signed out; no other account gets them. Apart from those, nothing archived while you are signed out or using the free trial is uploaded, not even after you sign in later. Chats in the phone app are not uploaded.

• What is uploaded. The full record of the sessions you archive: chats archived from the sidebar (including clones), the archived part of the All tasks log, and the finished background tasks those chats sent out. That includes what you said and typed; the answers and reasoning of EchoAgent and of the other agents it worked with (such as Codex or Claude Code); the tools called and what was passed to them; what the tools returned (such as file contents, command output and web pages); and file and project paths that appear in the session. This applies whether the session used echo or your own API key. If a background task continued a Codex or Claude Code session you had started outside EchoAgent, that session’s earlier history is uploaded with it. With it we keep your account, which device it was, the EchoAgent version, the platform, the agent and models, and when the session took place and was archived.
• What is not uploaded. Recordings, and the content of images: screenshots and pasted images are replaced by a placeholder. Before uploading, EchoAgent removes obvious keys and tokens on your device (API keys, access tokens, private keys, password fields), but no rule catches every secret, so don’t keep anything in a session that you don’t want saved.
• What it is for. The same as “Improving echo with your conversations”: finding mistakes made by EchoAgent and the agents it calls, checking the quality of answers, testing new versions and models, and looking into problems you report. Only maintainers can access it. It is not sold or used for advertising.
• Where it is stored. Compressed, in Vercel’s private storage (Singapore region), with no public link; the index is in our database (Neon, Singapore region). It is not given to model providers or any other third party. If that ever becomes necessary, we will update this policy and ask for your consent again first.
• How long we keep it. Until you withdraw your consent or delete your account; there is currently no fixed time limit.
• Withdrawing and deleting. This is the same consent as “Improving echo with your conversations” and is withdrawn the same way. Once we process your withdrawal, nothing more is uploaded and your archived sessions are deleted; they are also deleted when you delete your account. You can also ask us only to delete them, or for a copy.

The wake word and spoken answers

• The wake word (off by default). If you turn on the wake word on your Mac or in the phone app, the microphone stays on while EchoAgent is running so it can hear “echo echo”. The wake word is recognized on the device itself. Until it is heard, nothing is recorded, saved or sent anywhere. What you say after it is handled like any other spoken request: recognized on your Mac, and from the phone it reaches your Mac end-to-end encrypted. The system’s microphone indicator stays on while the wake word is on; the phone keeps listening in the background and on the lock screen until you turn it off or close the app.
• Spoken answers. When EchoAgent answers aloud it speaks one short line, not the whole answer. Without a pass it uses the voices built into macOS and iOS, on the device.
• The cloud voice (Live voice mode, with a pass). If your account has a pass, that one line, up to 200 characters of what echo wrote for you to hear, is sent over an encrypted connection to our server, which passes it to a third-party speech synthesis provider we select and returns the audio to your Mac. When you asked from the phone, your Mac forwards the audio to it end-to-end encrypted. Our server handles the text and the audio only in memory; it does not store or log them. We keep how many characters each account had spoken that day, to enforce the daily allowance. The provider processes the text under its own terms and privacy policy, may keep it for a period, and may process it outside your country or region. We may change the provider at any time.

Other services EchoAgent works with

• Codex and Claude Code. When you hand a task to them, EchoAgent starts the command-line tool you installed, on your Mac, with your own sign-in and settings. OpenAI’s or Anthropic’s terms apply.
• Your Codex and Claude Code history. Read on your Mac only when you ask about it, and passed to the model you use as context. When a chat that sent a background task to them is archived, that task’s session record is uploaded as described under “Archived sessions in the cloud”.
• Screenshot questions. Only when you explicitly ask for a screenshot does EchoAgent capture the window selected when you invoked the shortcut and send it to your model to answer your question; only when you explicitly ask is it sent through Codex or Claude Code instead. Screenshots are saved under ~/Library/Application Support/VoiceAgent/screenshots/, readable only by your account. On the next capture, screenshots older than 24 hours are deleted unless a running task needs them or a task record still offers a new-session retry after a session conflict. Provider and CLI records follow their own retention settings.

Other things we receive

Update checks

EchoAgent regularly asks our website whether a newer version exists. The request carries only EchoAgent’s version number. You decide whether to install an update, and you can turn off automatic checks in Settings → About.

Anonymous usage statistics (only with your permission)

EchoAgent asks you first. Nothing is sent unless you choose “Share”, and you can turn it off at any time in Settings → About. When it is on, EchoAgent sends only:

• a randomly generated install ID, unrelated to your Mac or your account
• the versions of EchoAgent and macOS, and EchoAgent’s interface language
• which days you used EchoAgent. With the install ID we keep only those days, whether you made a request on each of them, and the versions and language above; the counts below are added into daily totals and are not kept with the install ID
• daily counts for five things. Voice input: how many recordings started and how each ended; when one fails, which kind of problem it was (no microphone permission, no input device, a silent microphone or a recognition error) and whether you used the fix offered next to the message; the time from release to text grouped as under 1 second, 1–3 seconds or longer. Requests: whether each was spoken or typed, whether it was accepted, and how it ended, with completion time grouped as under 10 seconds, 10–60 seconds or longer. Kinds of features: which kinds of features a request used, such as screenshot questions, WeChat and Feishu, mail, reminders and calendar, files or background coding, and whether that feature reported an error. Only the kind is counted, never what you asked, opened, wrote or found. Background tasks: for Codex and Claude Code separately, how many were started, how they ended, and whether you continued or retried one that didn’t finish. Getting started: once per install, whether you saw the welcome guide, finished it, tried a request in it, made your first request, and had a first request complete

The getting-started steps usually happen before EchoAgent asks about statistics. Until you choose “Share” they stay on your Mac as a note that each step happened; they are then sent once. If you don’t share, they are never sent.

It never includes your voice, what you said or typed, files, web addresses, conversation content, exact timings or your IP address. Turning statistics off deletes the install ID and any unsent counts from your Mac. Saving what you say to improve echo is separate, described under “Improving echo with your conversations”.

Testers (when you redeem a tester code)

If you redeem a code marked for testing, your account becomes a tester account; the redeem window tells you this before you redeem. EchoAgent turns usage statistics on and from then on sends them together with your sign-in token, so besides the anonymous totals above we also keep the same information under your account: which days you used EchoAgent, its version, and the daily counts listed above. It still never includes your voice, what you said or typed, files, web addresses or conversation content. We use it to see which features testers use most and where they get stuck, and we may use your contact details to ask how it is going. Turning usage statistics off stops sending them. You can ask us to end your tester status at any time; the counts kept under your account are deleted when we do.

Crash reports (with the same permission)

If EchoAgent or one of the programs bundled with it crashes while usage statistics are on, macOS writes a crash report on your Mac, and EchoAgent sends a trimmed copy the next time it runs. It contains the install ID, the versions of EchoAgent and macOS, the interface language, when the crash happened, the type of error, and where in the code each thread was (the names of functions and program files, plus any message the program left about the error). It leaves out file paths, memory and register contents, and the identifiers macOS keeps for your Mac. Crashes from before you turned statistics on are not sent, and turning statistics off stops sending them.

Feedback and plan interest

When you send feedback, or leave your contact details to hear about plans with more echo usage, we receive what you write, the contact details you add, and the versions of EchoAgent and your operating system plus the interface language. If you are signed in, it is linked to your account; if usage statistics are on, feedback also includes the install ID.

Passes

When you redeem a code, we record the code, when you redeemed it, the Mac it was redeemed on (as the digest described under “Your Mac”) and the pass it opened. Each code works once per account and once per Mac.

The phone app

The phone app works on its own, and you can also pair it with your Mac to control EchoAgent there. This section covers what is different on the phone; the sections above about your account, echo and improving echo apply to it too.

Signing in on the phone

• What you can use. On iPhone you sign in with an email code; on Android also with Google. You can also try echo without signing in, use your own API key, or only pair a Mac; none of those needs an account.
• The trial. Trying echo without signing in creates a trial identity for this phone on our server, with no name or contact details. It counts usage toward the trial limit; trial conversations are not saved. You can delete it in Settings → Account; the phone then gets no further trial.
• Your phone. Instead of a hardware identifier the phone sends a random ID it keeps in its keychain (on Android, one computed from the Android ID). Our server transforms it again before storing it and uses it as described under “Your Mac”. The sign-in token stays in the phone’s keychain.

Speech on the phone

• On the phone. If you download the speech model (about 170 MB; the app asks first), speech is recognized on the phone. The recording is not saved and does not leave the phone: it reaches neither your Mac nor us. The text it produces is handled like anything you type. The model comes from a third-party download host, which sees your network address.
• On your Mac. Without the model, a paired phone sends the recording to your Mac end-to-end encrypted, where it is recognized and not saved. What you say after the wake word always goes to your Mac this way.

echo’s tools on the phone

echo runs on the phone and uses these tools only when a request needs them:

• Calendar and reminders. The system asks your permission the first time. echo can read, add and change events and reminders on the phone, and asks you before deleting an event.
• Location. Only while you are using the app, once, when you ask something that needs it; the system asks your permission first. Never in the background.
• Notes and memory. Stored in the app on the phone, with no cloud sync. Memory is sent with each request so echo can use it; notes are sent when a request needs them. You can see, change and delete both in Settings.
• Timed reminders. Notifications scheduled on the phone itself; they are not sent to us.
• The web. Searches go through our server to a search provider. Reading a web page is done by the phone itself, so that site sees the phone’s network address.
• Pictures you attach are sent to the model to answer you and are not saved by us.
• Handing work to your computer goes to your paired Mac, end-to-end encrypted, as described under “Pairing with a Mac”.

What a tool returns, such as event titles, your location or a note, goes to the model you use so it can answer: through our server with echo, straight to the provider with your own API key. Our server does not keep what tools returned. What echo passes to a tool is saved as described under “Improving echo with your conversations”, for example the title of an event it adds, a search, or the text of a note it writes.

WeChat

If you connect WeChat in the Android phone app, you can talk to echo in a WeChat chat, through the ClawBot channel Tencent provides. Connecting needs an account, and only the WeChat account that scanned the code gets answers.

• Where it runs. Messages pass through Tencent, under Tencent’s terms, and through a service of ours on Cloudflare, which calls echo for you. It works while your phone is off, so unlike the rest of the phone app this conversation is held in the cloud.
• What that service keeps, encrypted. Its WeChat connection token, your WeChat ID for this connection, a sign-in session for your account, the last 20 messages so the conversation can carry on, and anything you asked it to note until your phone collects it. Pictures pass through memory and are not stored. Its logs hold error types, never content.
• Saving. echo conversations in WeChat are saved like any others, under “Improving echo with your conversations”, marked as WeChat. To withdraw, send 撤回同意 in the WeChat chat, or use Settings → About → Withdraw Consent in the phone app.
• Disconnecting. Disconnecting in the app deletes everything that service keeps. Deleting your account disconnects it too; if that step fails, the service deletes it all once your session has been invalid for 7 days. We have no way to remove the chat itself, so it stays in your WeChat with nobody answering.

Pairing with a Mac

If you turn on Settings → Phone and pair a phone, the phone app can control EchoAgent on your Mac, and that work runs on your Mac.

• End-to-end encrypted. Messages between your phone and your Mac, including your recordings for speech recognition, are encrypted with a key created when you pair. The key is in the pairing code and never sent to us. The messages pass through our relay on Cloudflare, which can’t read them. While your Mac is offline or asleep, the relay keeps up to 100 of your phone’s encrypted messages for at most 24 hours and deletes each one once your Mac receives it.
• What the relay keeps. For each pairing: a random room number, fingerprints of the phone’s and the Mac’s access tokens, your Mac’s name, whether the Mac is online or asleep and when each side was last seen, and your phone’s push token. Pairing again replaces it. To have it deleted, send feedback.
• Notifications aren’t end-to-end encrypted. When a task finishes, needs your approval, or echo finishes a reply you started from the phone, your Mac sends the notification’s title and a one-line summary (for example the task’s first line or echo’s first sentence) through the relay to Expo’s push service, which delivers it through Apple or Google. The relay doesn’t keep them.
• Speech sent to your Mac is recognized there, like speech on the Mac itself, and the recording is never saved. If you use echo while signed in, the recognized text is saved as “Improving echo with your conversations” describes.

When you buy a pass, Stripe runs the payment page. We receive the order from Stripe: the plan, amount, currency, time, whether it was paid or refunded, and Stripe’s reference numbers for it. We pass your account’s email to Stripe so it can fill in the receipt. Card numbers and Alipay account details go to Stripe (and to Alipay), are handled under their privacy policies, and never reach us.

Who else receives data

We don’t sell personal information and don’t use it for advertising. We share it only:

• With service providers that run EchoAgent for us, each only for its part: Vercel (hosting, and private storage for archived sessions, Singapore region), Neon (database, Singapore region), Resend (sign-in emails), Alibaba Cloud (sign-in SMS), Google and Tencent (WeChat sign-in, when you choose them), Tencent (the WeChat channel, when you connect it), Stripe (payments, when you buy a pass), Cloudflare (the phone relay and the WeChat service, when you use them), Expo (phone notifications, delivered through Apple or Google), a search provider (search terms, when echo searches the web), the model providers behind echo, Anthropic for Haiku 5.5, DeepSeek for DeepSeek V4.1 Flash, OpenAI for GPT and Google for Gemini, and the third-party API service provider that passes GPT and Gemini requests to OpenAI and Google (request content, as described above), and the speech synthesis provider behind the cloud voice (the one line to be spoken, when your account has a pass).
• When the law requires it, for example to answer a valid request from a court or government authority, and when reasonably necessary to protect EchoAgent, our users or the public, including to investigate fraud, abuse, security incidents or violations of the Terms.
• If EchoAgent is reorganized, merged, sold or transferred, to the party that continues to provide the service, which must keep protecting the data as this policy describes.
• With your consent, in any other case.

We may use aggregated or de-identified data that can no longer identify you, such as total usage, for any purpose, including improving EchoAgent.

Where it is stored and for how long

• Our data is stored with Vercel and Neon in Singapore. Using EchoAgent means your data is transferred to and processed in Singapore and, by the provider of the model you use and, for GPT and Gemini, the third-party API service provider, possibly in the United States (Anthropic, OpenAI, Google), mainland China (DeepSeek) or other countries and regions.
• Account, sign-in sessions and daily usage: kept while your account exists. When the account is deleted, they are deleted with it, except where the law requires us to keep something longer.
• Device records (Mac, PC or phone): when the account is deleted they are no longer linked to any account. We keep them so that deleting an account can’t reset the free limits on a device, and delete them after 30 days without use, unless a code was redeemed on the device.
• Sign-in codes and third-party sign-in attempts: deleted about a day after they expire. Rate-limit counters: within two days.
• Usage statistics: kept as daily totals; batch numbers used to avoid counting a retry twice are deleted after 35 days. Testers’ counts under their account: kept while you are a tester, deleted when tester status ends or the account is deleted.
• Crash reports: deleted 90 days after the crash, or earlier once the problem is fixed.
• Improving echo with your conversations: kept until you withdraw your consent or delete your account; there is currently no fixed time limit.
• Archived sessions in the cloud: kept until you withdraw your consent or delete your account; there is currently no fixed time limit. Uploads left unfinished are deleted after 7 days.
• Phone relay: on Cloudflare. Queued messages are kept at most 24 hours; the pairing record until you pair again or ask us to delete it.
• WeChat service: on Cloudflare, until you disconnect or delete your account, as described under “WeChat”.
• Pass orders: kept as long as accounting and tax law requires, including after the account is deleted, when the link to the account is removed. Code redemptions are kept the same way, so a Mac can’t redeem the same code again.
• Feedback: kept until you ask us to delete it. Feedback linked to your account is deleted with the account; feedback sent while signed out has no link to any account.
• Backups and our providers’ logs may keep copies for a limited time before they are overwritten.

Your choices and rights

• Sign out at any time in Settings → Account. You can keep using EchoAgent with your own API key without an account.
• Withdraw your consent to improving echo with your conversations at any time through Send Feedback (in the phone app, Settings → About → Withdraw Consent; in WeChat, send 撤回同意) or by email; we stop saving, delete what was saved (archived sessions included), and you keep using echo.
• Delete your account or trial identity yourself in the phone app: Settings → Account → Delete Account. It takes effect at once, on all your devices. It deletes your account, sessions, usage records, saved conversations and archived sessions, tester records, the feedback linked to the account and the WeChat connection. Pass orders, code redemptions and device records are kept as described above, with no link to the account. Notes, memory and chats on the phone are not part of your account; clear them in Settings or uninstall the app.
• To see, correct or get a copy of your account and its data, or to delete your account from a Mac or PC, send us a request through Settings → About → Send Feedback and leave a way to reach you. We may ask you to confirm that you own the account, and we will answer within the time the law requires.
• Depending on where you live, you may have further rights under local law, such as to withdraw consent or to complain to a data protection authority.

Security

Connections are encrypted, sign-in codes and tokens are stored only as digests, and only the maintainers can access our admin tools. No system is completely secure, and we cannot guarantee that data will never be accessed, disclosed or lost. If an incident affects your personal information, we will act and notify you as the law requires.

Children

EchoAgent is not meant for children under 14, and we don’t knowingly collect their personal information. If you believe a child under 14 has given us personal information without a guardian’s consent, tell us and we will delete it.

Changes and contact

We may update this policy as EchoAgent changes. We update the date at the top, and for significant changes we will also tell you in the app or on this website. If you keep using EchoAgent after a change takes effect, the updated policy applies. For questions or requests, use Settings → About → Send Feedback and leave a way to reach you.