Privacy

Your data goes nowhere.

This isn't a marketing promise — it's how the application was built. This page explains what that means in practice.

Local-first, genuinely

Everything you record in Teko — workouts, sets, runs, check-ins, profile, measurements, pain, cycle — is written only on your device, in a database encrypted with AES-256. The key is generated at random on first launch and kept in the operating system's keystore.

The application works offline. There is no cloud account, no automatic sync and no remote copy of your history. If that ever changes, the privacy policy will be updated first, and sending will be optional and switched on by you.

What leaves and what never does

The list of what leaves is deliberately short — and it is exhaustive. Almost everything Teko knows about you never crosses the boundary of the device.

When you use the assistant, what is sent first passes through a layer that strips e-mails, phone numbers, national ID numbers, tokens and long digit sequences — from your message and from every earlier turn of the conversation, on each resend.

When the assistant needs to understand a request of yours, it receives only the essentials of your profile: goal, days per week, time per session, equipment and level. Your age, your weight and your measurements are not sent.

The device boundary

  • Never leaves: Training and set history
  • Never leaves: Pain, injury and restriction reports
  • Never leaves: GPS routes from your runs
  • Never leaves: Body measurements and cycle log
  • Never leaves: Data read from Health Connect
  • Leaves: Messages to the assistant, if you use it
  • Leaves: The sign-in, if you use Google
  • Leaves: Whatever you choose to share

The absences are the feature

Much of what makes Teko private is what it does not have — and none of it was forgotten: it was decided.

No ads

No advertising SDK, no advertising identifier, no tracking cookie.

No analytics

No usage-analysis or profiling tool. Nobody is watching which screen you spend the most time on.

No log file

Technical events exist only in memory, already stripped of personal data, and vanish when the app closes. There is no automatic crash report.

No background tracking

Location is used only during a run you start, with a visible notification for as long as it lasts.

No writing to Health Connect

Every health permission is read. Teko reads what you allowed and gives nothing back.

No nagging to log

The app does not count your missed days or push you for consistency. That is a product decision, and a health one too.

You in control

Encrypted backup. To change phones, Teko generates a file protected by a password only you know. You choose where to keep it. Without the password the file reveals nothing — not to the developer either, who also cannot recover it.

Deletion at three levels. Erase only the training history; erase the application's data while keeping the account; or erase everything and the account, withdrawing the access granted to your Google account as well. Deletion is immediate and permanent — there is no cloud copy to restore from.

Withdraw at any time. Disconnect Health Connect, switch off cycle tracking, stop using the assistant. None of it is required for the app to work.

Full Privacy Policy

The assistant, in detail

Teko Intelligence is optional. If you never open the chat, no message of yours leaves the device.

When you do use it, your message goes to an external artificial-intelligence provider through a Teko proxy — the access key is never in the application. That processing may happen on servers outside Brazil, which constitutes an international transfer of data, based on your consent when using an optional feature.

Not sent: your full history, your GPS routes, your pain and injury reports, or your cycle log. And messages suggesting emotional crisis or disordered eating never reach the model: the app answers locally and points to sources of help.

How the assistant works and where it stops →