Privacy
Teeras builds Afterhours (coding-agent balance) and the Teeras iOS app (sleep and recovery). This page says what we collect, what never leaves your phone, what we store, and how to see, export, or delete any of it.
Health readings — sleep, HRV, resting heart rate — are read from Apple Health and processed on your iPhone only. They are never uploaded, never sold, and never used for advertising. Our cloud stores content-free agent-activity aggregates (timestamps, durations, counts) tied to your account, and the Together plans and responses you deliberately share. Export and deletion controls are available.
Health files you choose to import are read in your browser and are not uploaded to Teeras. Supported measurements, source labels, check-ins, and experiment records stay in the open tab. Apple Health records on your iPhone do not automatically sync to this workspace.
You can explicitly save a passphrase-encrypted copy in this browser. The passphrase is not stored or sent to us, and we cannot recover it. Encryption protects the saved copy; the open workspace can access decrypted data. Changes need another save. Clearing browser site data removes the saved copy.
Workspace exports are unencrypted downloads. Agent briefs show their exact contents before download and exclude measurement summaries unless you select them. Nothing is sent to an agent automatically. If you share a downloaded brief, your chosen AI provider handles it under its own policies.
Public plugin tools describe connections and experiment templates; they cannot access your private health workspace. Direct wearable account synchronization and private health access through MCP are not available in this release.
Public plugin tools return agent traffic and activity options without an account. They do not save your arrival reasons or request your chat transcript. Broad categories supplied to the activity tool are used for that response only.
On the plugin page, you can choose to save the categories you confirm: why you came, what you want now, the time you chose, and the activities offered. This is optional. Signed-in activities record your choice, start and end times, duration, and any better / same / worse reflection you choose to give. These records help your own experience and help us understand demand for useful options; they do not establish a medical condition or health benefit.
Saving categories does not enable research sharing. Your separate research setting governs research eligibility; withdrawal excludes earlier eligible activity and arrival records, and re-enabling applies prospectively. Account records remain until you delete them or your account, and are included in your export. We do not sell them or use them for advertising. ChatGPT or your other host handles its own chat history under its own policies.
In our cloud database, tied to your account, we keep: your email and name, content-free agent-activity aggregates (timestamps, durations, counts) so your dashboard and history work across sessions and devices, and the daily check-in answers you choose to give.
If you use billing, Stripe holds your card details directly — we only mirror your subscription status, and card numbers never touch our servers. If you use the outreach note-taking features, the contact details you type are sent to Anthropic to help draft a message; we never ask for that person's email address, and we never contact anyone on your behalf.
Creating a group or plan stores its name, organizer name, activity, time, place and optional booking link in our cloud. Your share sheet sends a link to the people you choose. Anyone with that link can view the invitation; forwarding it gives someone else access. The organizer can replace links, remove members, or delete a group and its plans.
Guests choose a display name. An essential browser cookie lets the same browser change or remove its response without an account. We store a one-way identifier derived from that cookie, group membership and plan responses. Names are visible to the organizer. Leaving a group removes that guest's membership and responses to its plans. If you lose your cookie, contact the organizer to remove your response. A guest's name is stored under the organizer's account: it appears only in the organizer's own data export, and it is deleted the moment the organizer removes that guest, deletes the plan or group, or deletes their account.
A yes to an invitation is not evidence that a meeting happened. Confirmed people time and private evening or weekly notes stay in the iPhone's local ledger; they are never included in an invitation or uploaded. Corrections append a new record; the original remains in your private export until you erase local history. Deleting local phone history does not delete shared invitations from the cloud. Remove those in Together, or delete your account on the web.
Questions, deletion requests, or anything else: team@teeras.com — a human reads every email. If this policy changes, we'll update the date below rather than change what we do with your health data silently.