EchoFlow Labs
Scope
This policy applies to the English Lens iPhone app and the EchoFlow services that process text you submit through the app or the Learn with EchoFlow Action extension.
Account and authentication
English Lens uses Supabase Auth for sign-in. The app offers Sign in with Google, Sign in with Apple, and experimental passkeys on the sign-in screen. Sign-in can still fail because of network issues, third-party provider outages, device settings, or passkey limitations.
After a successful sign-in, the app bridges session credentials to the iOS Keychain so you can stay signed in across launches. Supabase stores account identifiers and authentication tokens needed for your account. EchoFlow Labs does not operate a separate password database.
When you use Google or Apple sign-in, those providers handle authentication under their policies; we receive the account information Supabase needs to authenticate you.
Text you submit
When you share, paste, or type text in English Lens, that selected user content is sent to the EchoFlow backend and to a large language model (LLM) to generate translation, explanations, and retelling results. Processing is tied to your request—not to build a browsable history inside the app.
English Lens does not read text from other apps unless you explicitly share or enter it.
On your device
- The iOS client does not store a local history of past prompts or results.
- Source text is not placed in ordinary logs, analytics payloads, or crash metadata.
On our servers
- The backend may cache a normalized, validated result in Redis for up to seven days, subject to eviction for cost or latency. This cache is operational—not a user-visible history feature.
- A usage ledger in the database stores aggregate identifiers such as token counts, cost figures, and request identifiers. It does not store full prompt or result text in that ledger.
What we do not do
- We do not sell your personal information.
- We do not use English Lens for advertising or cross-app tracking.
- This site does not use analytics or advertising cookies.
Retention and deletion
Cached results in Redis expire within the window described above or sooner when evicted.
You can delete your English Lens account in the app under Settings. That flow removes your Supabase Auth account and the operational app account data we control through it.
To finish deletion reliably and retry failed deletion steps, we retain a minimal deletion-safety record on our backend, keyed to your former Supabase user identifier. It holds when deletion was requested and a brief summary of Sign in with Apple revocation status where applicable. We consult this record during Sign in with Apple credential registration so a deleted account cannot complete late Apple registration against that same deleted user identifier. It does not prevent creating a new Supabase account with a new user identifier through Google, Apple, or passkeys. We keep this record indefinitely for those safety and operations purposes; it is not used for advertising, profiling, or in-app features.
If you used Sign in with Apple, you may also need to revoke the app’s access in your Apple ID settings or follow Apple’s account-management steps where applicable (including guidance such as Apple’s TN3194 on handling account deletions) to fully disconnect the Apple credential.
For questions about data we hold, or if you cannot complete in-app deletion, email harvey@eflabs.tech. See also our terms of service.
Changes
We may update this page when practices change. Material updates will be reflected here with a revised date.
Contact
EchoFlow Labs — harvey@eflabs.tech