This Privacy Policy explains how simail (“simail”, “we”, “us”), operated by [operating entity, to be confirmed], handles personal information when you use simail.ai, app.simail.ai, docs.simail.ai, api.simail.ai and related simail services (the “Service”).
Summary
- simail is in private beta and is offered only to users in the United States.
- simail is not for legal, healthcare or financial-services use, and must not be used to process regulated or confidential client data.
- We do not sell or share personal information for advertising, and we do not use your email content or account data to train AI models.
- Our infrastructure provider, Cloudflare, is our subprocessor: it hosts the Service and processes email for us, and its systems automatically scan email content (for example for spam, malware and abuse). We therefore do not claim that no system ever reads your mail; we commit that it is not used for training and is accessed only as described here.
- You can withdraw from the waitlist or delete your organization at any time.
Information we collect
Account and sign-in
| Data | Why |
|---|---|
| Email address | to send sign-in and verification codes, identify your account, send service notices |
| Name, if you provide one (optional; otherwise left empty) | to address you in the console |
| Sign-in codes (stored only as a hash, valid 10 minutes) | to verify that you control the email address |
| Passkey data: public key, credential ID, device type, backup flag, transports, authenticator model identifier (AAGUID), optional name | to let you sign in with a passkey. We never receive biometric data or private keys |
| Session data: session token, a keyed hash of your network range (not your IP address), browser user agent (shortened to 256 characters), timestamps | to keep you signed in (7 days) and protect your account |
| Bot-check result (Cloudflare Turnstile) | to block automated sign-up abuse |
| Account status and role | to apply the beta gate and permissions |
Waitlist
When you join the waitlist we collect your answers: use case, expected number of inboxes, expected monthly volume, industry, whether you use another agent email service (and which), your agent framework, an optional short note, your acknowledgment of the usage commitments, and whether you want to be notified once. We also record a referral or campaign tag from the link you followed (shortened), a keyed hash of your network range (not your raw IP address), the network operator number (ASN) your request came from, whether your email domain is a known disposable-email provider, and when your email address was first seen.
If an AI agent registers interest for you (POST /v0/waitlist), it can send only the non-personal
fields above. We do not accept your email address from an agent. The entry stays unverified until
you open the claim link and verify your own email; the link and the unverified entry are deleted after 24 hours.
Mailboxes and email content (customer data)
When you or your agents use the Service we process the content of email sent to and from your inboxes: messages (headers, bodies, attachments, raw message files), drafts, threads, labels, contacts derived from your correspondence, allow and block lists, webhooks you configure, and delivery events (delivered, bounced, complained). This content may contain personal information of third parties who write to you or receive mail from you. You are responsible for having the right to process it.
API and usage
API keys (stored only as a keyed hash; the key itself is shown to you once), key scopes and permissions, request metadata (request ID, time, endpoint, result), usage counts (messages received and sent, recipients, storage, API calls), and an audit log of security-relevant actions.
Logs
Service logs record metadata such as request IDs, timings and error codes. They do not record email addresses (only domains or keyed hashes), message content, sign-in codes or secrets, and are kept for 7 days.
How we use information
- To provide and secure the Service: deliver and receive mail, run pre-send and inbound safety checks, apply your policies and limits, detect abuse, prevent loops and duplicate sends.
- To run the beta: review waitlist entries, issue invitations, and contact you if you asked to be notified.
- To communicate about your account: sign-in codes, security notices (for example a passkey was added), approval requests, export-ready and deletion notices. We do not send marketing email.
- To comply with law and enforce our Terms of Service and Acceptable Use Policy.
No training. We do not use email content, attachments or account data to train machine-learning or AI models. Cloudflare processes this data as our service provider under its customer terms [counsel to confirm Cloudflare’s data processing terms on use of customer content].
Automated processing. The Service checks every message automatically: inbound classification (spam, auto-reply, bounce, verification-code mail), prompt-injection heuristics, a screen that holds messages resembling out-of-scope regulated or privileged material for human review, and pre-send checks on outbound mail. These checks are rule-based. Optional model-based features (attachment text extraction, model-based injection scoring) are off by default and run inside Cloudflare only if your organization turns them on.
Automated waitlist decisions. Waitlist entries that select the legal, healthcare or finance industry are declined automatically, and entries from disposable email domains are flagged and not counted. You can ask us to review a decision by writing to privacy@simail.ai.
Who can see your information
- Your organization. Members of your organization can read mail in the inboxes their role allows. Your agents can read mail in their key’s scope.
- simail staff do not read your mail, except when you ask us to (for example for support), when needed to investigate abuse or a security incident, to remove misdelivered material, or when required by law. Such access is logged.
- Subprocessors that help us run the Service, listed on our Subprocessors page. Cloudflare is the subprocessor for hosting, storage, email routing and email sending.
- Recipients and integrations you choose. Mail you send goes to its recipients. If you connect a webhook, Telegram or Slack, we send the data you configured to that destination.
- Legal requirements. We may disclose information if required by law, subpoena or court order, or to protect the rights and safety of users and the public. Where allowed, we will notify you.
- Business transfers. If the Service is transferred to a successor, this policy continues to apply to existing data.
We do not sell personal information and do not share it for cross-context behavioral advertising.
Retention
| Data | Retention |
|---|---|
| Email content | until you delete it, or according to your organization’s retention setting; trash is purged after 30 days |
| Inbox backups | 35 days |
| Data exports | 7 days |
| Events and webhook delivery logs | 30 days |
| Unverified agent waitlist entries and their claim links | 24 hours |
| Unclaimed agent inboxes | 24 hours |
| System email log (recipient stored only as a keyed hash) | 30 days |
| System email delivery events (delivered, bounced, complained; recipient stored only as a keyed hash) | 30 days |
| Rate-limit and abuse counters keyed by a hash of your email | counting windows up to 2 days; the sign-in code sequence counter up to 7 days. They are cleaned up when the same counter is next used, so a counter for an address that never returns can remain longer; it is named only by a keyed hash. Deleted at once when you withdraw |
| Expired sign-in codes, passkey challenges and sessions | deleted by a scheduled job once expired |
| System email delivery problems (recipient as a keyed hash) | a hard bounce pauses system email to the address for 30 days; a spam complaint stops non-essential notices (not sign-in codes or security notices) until cleared |
Masked email (for example a***@d***.com) in decided platform admin requests and the matching Telegram confirmation messages to our operator |
kept permanently (the masked form cannot by itself identify you) |
| Service logs | 7 days |
| Database point-in-time recovery (Cloudflare) | 30 days |
| Audit log entries (opaque IDs only, never your email address) | kept permanently to protect the log’s integrity |
| Daily usage counts (no content) | kept permanently |
Withdrawing from the waitlist
Withdrawing hard-deletes your account, sessions, passkeys, waitlist entry and system-mail records.
What remains: database recovery copies for up to 30 days (used only for disaster recovery), audit log
entries that contain only an opaque ID that can no longer be linked to you (and their delivery queue rows,
also opaque, for 7 days), logs for up to 7 days (which do not contain your email address), an anonymous
count of withdrawals, and, if a platform administrator acted on your application (for example invited or
declined it), your masked email address (for example a***@d***.com) in that decided admin request and
in the operator’s Telegram confirmation message, both kept permanently.
Deleting an organization
An organization owner can delete the organization. After a 7-day grace period we delete its mailboxes, messages, attachments, drafts, keys, webhooks, backups and exports. Recovery copies may persist for up to 30 days.
Your choices and rights
You can access and export your data in the console, correct your account details, delete messages, withdraw from the waitlist, or delete your organization. You can also write to privacy@simail.ai to request access, correction or deletion; we will verify your request through your email address. Depending on your state of residence you may have additional rights (for example under the California Consumer Privacy Act); we will honor them as required by law and will not discriminate against you for exercising them.
Do Not Track. The Service does not track you across other sites and does not change its behavior in response to Do Not Track signals. simail does not use advertising or analytics cookies; the console uses only a strictly necessary session cookie.
Security
We protect data with encryption in transit (TLS), encryption at rest provided by Cloudflare, keyed hashing of API keys, invite codes and sign-in codes, strict tenant isolation, and an append-only audit log. See Security. No system is perfectly secure; tell us about any problem at security@simail.ai.
Location
The Service is offered only in the United States. Data is processed on Cloudflare’s network, which may process it in locations outside your state. Do not use the Service if you are located outside the United States.
Children
The Service is not directed to children and is not for anyone under 18. We do not knowingly collect personal information from children under 13. If you believe a child has given us information, contact privacy@simail.ai and we will delete it.
Changes
We will post changes on this page and update the date above. For material changes we will notify account holders by email or in the console before they take effect.
Contact
[Operating entity, to be confirmed] · privacy@simail.ai · simail.ai