Skip to content

Privacy Policy

Last updated August 24, 2026

This policy explains what data Agentele collects, why, and what control you have over it. The short version: your conversations are yours, we store them to make your agents work, we never sell your data, anything you ask one agent to keep private stays with that agent, and you can export or permanently delete everything from Settings.

1. What we collect

  • Account data — email address, display name, timezone, and authentication records (including Google sign-in identifiers if you use Google OAuth).
  • Agent data — the agents you create: their personality, schedules, portraits, and the memory facts they distill from your conversations.
  • Conversations — messages, voice-call transcripts, and photos you attach, stored so agents keep context and memory. Photos are stored as files with long, unguessable web addresses; anyone given such a link can open it, so treat an attached photo as shareable rather than private.
  • Usage and billing — metered usage events (tokens, minutes, cost), your plan and its expiry, credit balance, and gift-code redemptions.
  • Technical data — standard server logs and push-notification subscriptions for the devices you enable.

2. How your data is used

  • To run the product: generating agent replies, voice, portraits, memories, and scheduled proactive messages.
  • To apply your plan's fair-use limits and meter usage.
  • To secure the Service and prevent abuse (rate limits, approval queue).
  • We do not sell your data, show you ads, or use your conversations to train our own models.

3. Who processes it

  • Supabase — database and authentication, hosted in the EU (Frankfurt, eu-central-1). All data is protected by row-level security: only your account can read your rows.
  • Vercel — application hosting and AI Gateway routing.
  • AI model providers (Anthropic, OpenAI, and others via the gateway) — receive conversation content to generate replies, transcriptions, speech, and images. They process it as vendors under their API terms; API traffic is not used to train their consumer models.
  • Payment processors — when card checkout is enabled, payments are handled by a merchant of record (e.g. Paddle or Lemon Squeezy); we never see or store your card number.

4. Bring-your-own-key (BYOK)

If you add your own provider API key, it is encrypted at rest with per-record envelope encryption and is only decrypted in memory to call your provider. It is never written to logs and never shown back to you in full.

5. Retention and deletion

  • Your data is retained while your account is active.
  • Export — Settings → download a full JSON export of your agents, memories, and conversations at any time.
  • Delete — Settings → delete account permanently removes your profile, agents, conversations, memories, schedules, usage records and uploaded files. This is immediate and irreversible.

6. Things you ask an agent to keep private

Anything you tell one agent to keep between the two of you stays with that agent. So does anything that reads as obviously sensitive — health, medication, drug or alcohol use, sexuality, mental health, money trouble, legal matters, relationship trouble — which is marked without you having to ask for it.

  • It does not reach your other agents. A marked fact is left out of briefings sent between agents, group calls, the mind map, task extraction, search across your agents, proactive messages and push notifications, and anything an outside app you connected can read. This is enforced in code at each of those exits, not by asking the agent to be careful.
  • It asks before including one. If you ask an agent for something that would contain a marked fact — a summary, a handover, a note for someone else — it writes the rest and then asks whether to include it, giving only the number of things being held back, never what they are.
  • You decide what is marked. Every fact an agent holds, and every mark on it, is listed on that agent's memory page with the reason it was marked. You can add a mark, remove one, edit the fact or delete it.
  • What it is not. It is a rule about what your agents pass to each other and to other apps — not a second copy of the data held somewhere else, and not encryption we could not read. Marked facts are stored like any other data described in this policy. A per-agent memory download leaves them out unless you ask for them; the full account export in Settings includes them, clearly labelled, because it is your own complete data.

7. How we learn without collecting you

We want new agents to start out better than the last ones. To do that we look at which settings work — never at what anyone said.

Concretely: we look at whether a wake-up call that rings gets answered more often than one that texts; whether agents scheduled at 06:45 get replied to more than ones scheduled at 09:00; whether warmer agents get answered more than cooler ones; whether people who build three agents still have them a month later. We never look at what you or your agents said. Message content, voice transcripts, memories, photos, agent names and personalities are not part of this and are never read by it.

  • Configuration and outcome only — the template an agent was built from, its warmth/formality/energy numbers, the hour and cadence of its schedule, whether it rings or texts, how many agents are on the team; joined to whether the outreach was replied to, whether the calls were answered, and whether the agent was still in use after 30 days.
  • A 25-account minimum — a statistic is only ever stored if at least 25 different accounts contributed to it. Below that it is discarded rather than saved. This is enforced twice: in the code that computes it, and as a constraint in the database that rejects the row outright.
  • Nothing is linked to an account — the table these statistics live in has no user column and no link to your profile. There is nowhere in it to put your identity, so a row cannot point back at you even in principle.
  • Nothing is sold or shared — these numbers exist to make the product suggest better defaults. They are not sold, licensed, or handed to advertisers, data brokers or model trainers. We charge for the Service so that we never have to.
  • Opting out — Settings → Privacy & data → “Help improve the defaults” → tick “Leave my account out”. Your account is then excluded from the calculation entirely, before it runs. There is no penalty and nothing else changes.

8. Cookies

We use only the cookies required for sign-in sessions. No advertising or cross-site tracking cookies.

9. Age

The Service is for adults 18+. We do not knowingly collect data from minors.

10. Changes and contact

We will announce material changes in the app. Privacy questions or requests: support@agentele.ai.