Privacy

Your data, explained in plain language.

Beemy asks for access to the most private parts of your life. That means your email, calendar and the tools you run your day on. Here is exactly what we do with that access. Here is what we never do.

Last updated5 min read

The short version

We read what we need to be useful. We never sell it. Ask us to delete it at any time.

One audit record stays, on purpose. See Retention and deletion.

  • TLS 1.3Encrypted in transit
  • AES-256Encrypted at rest
  • your data stays yoursNever sold, never trained on
  • account + dataPurged and key-shredded on request

What we access, and why

When you connect an account, Beemy starts read-only. Today that means Gmail, with Google Calendar in the same connection.

Beemy reads what it needs to triage, learn your voice and draft on your behalf. It does this before it sends, replies or changes anything.

Outlook/Microsoft 365, Slack, Google Docs, RSS feeds, Reddit, newsletters, a mobile companion and a browser extension are rolling out. Each one ships as it clears its own safety gate. See the current status of every integration on Integrations.

We also collect what you give us directly. That means your name and email if you join the waitlist or use the contact form. It also means whatever you tell us in that message.

You can see exactly what's connected. To take one source away, ask us to erase the silo that holds it. See Leaving for how that works.

How we use your data

We use your data for one purpose: to serve you. It powers triage, drafts in your voice, digests and reports. It also powers the escalations that reach you with a plain "why this reached you."

Beemy learns from your corrections: an edited draft, a re-prioritised item, a skipped digest entry. That makes it more accurate for you. It is never used to train shared models. It is never sold, to anyone, for any reason.

The silo model

Personal, work and public knowledge live in architecturally separate stores. They are not a shared database with a privacy toggle on top. A work reply can't surface your personal life. A personal message can't surface your work. No path exists between them to leak across.

Read why we built it this way in our manifesto. See the mechanics on Trust & Security.

How your data is stored & secured

Every byte moving between you and Beemy travels over TLS 1.3. Stored data is encrypted at rest with AES-256. Access controls limit who and what can reach it.

Region pinning is not live today. We scope it with you in the enterprise rollout. See Enterprise.

Retention & deletion

We keep your data for as long as your account is active, so Beemy can keep doing its job. You can ask us to erase one silo without closing your account. Your work data can go while your personal data stays.

Ask us to delete your account. A person on our side runs it. Your data, drafts and history go with it. It is not a soft flag on a database row. We purge every row and destroy the encryption key.

One record survives on purpose: the audit trail that proves the deletion happened. See Leaving for the full exit path and what each move does. It also shows exactly what that one record holds.

Service providers & sub-processors

We rely on a small number of service providers to run Beemy. They are cloud hosting and the AI model providers behind triage and drafting. Each one operates under contract. Each is bound to the same never-sold, never-trained-on terms as the rest of this policy. Each processes only what it needs to provide the service.

Our sub-processor register names every one of them. It shows what each can see and where it is based.

Cookies & analytics

This marketing site uses Google Analytics to understand traffic at a page level. It shows which pages get visited, roughly how many people visit, and where from. It sets first-party cookies to do that. We don't use that data to identify you personally. We don't sell it or share it with ad networks. See Google's privacy policy for how Google handles it. You can also install the Google Analytics opt-out browser add-on to stop it.

Your rights & controls

You control what Beemy can do through the autonomy dial. Category by category, you decide what stays in your drafts folder for review. You also decide what Beemy may do on its own.

You can ask us, at any time, to give you access to your data or to delete it. There is no self-serve export today. See Leaving for the exit path. Region residency is scoped with you in the enterprise rollout. See Enterprise for details.

Children

Beemy is not intended for anyone under 18. It is not directed at anyone under 18. We don't knowingly collect data from children. If you believe a child's data has reached us, contact us and we'll delete it.

International data & residency

We can scope data, encryption keys and model inference to one region in the enterprise rollout. Beemy is built with the same silo isolation available for that regional deployment. Outside that scoped deployment, this is not a default switched on for every account today. See Enterprise for the full picture.

Changes to this policy

If this policy changes in a material way, we'll update the date below. Where the change is significant, we'll also let active users know directly. We won't rely on a silent date bump.

Get your time back.

Beemy is in private beta. We send invites in rolling batches. We cannot promise a date. When your invite arrives, connect Gmail. Beemy sorts your inbox in that first session.

We use your email only to write to you.

Talk to us