Terms of Service

Kleevee is email and calendar infrastructure. We give the applications and AI agents you build a real mailbox — an address, an inbox, a calendar — reachable over our REST API, our MCP interface, and standard mail protocols.

We are infrastructure, not an assistant. We do not write, generate or choose the content of your messages, and we do not decide who receives them. Your application does. That division matters for everything below: you are the sender of record for every message your account transmits, and you are responsible for it.

You must give an accurate email address and confirm it before sending. You are responsible for keeping your API keys secret and for everything done with them. Treat a leaked key as an incident: revoke it in the dashboard and issue a new one.

One account is for one organisation. Creating additional accounts to work around a quota or a suspension is a breach of these terms.

An autonomous agent acting on your instructions is you, for the purposes of these terms. “The model decided to” is not a defence. Before you point an agent at our API, you are expected to bound what it can do — who it may contact, how often, and about what.

Our per-inbox allow lists and block lists exist precisely for this, and we recommend using them for any agent that is not under direct human review. Our burst limits will stop a runaway loop within minutes, but they are a backstop, not a substitute for your own constraints.

Everything in this section applies to every message sent through Kleevee, by any interface, on any plan. It is not negotiable and it is enforced.

You may only send to recipients who have a genuine reason to hear from you: people who have asked you to contact them, are in an existing conversation or relationship with you, or are receiving a transaction they initiated.

The following are prohibited without exception:

• Unsolicited bulk email of any kind, including to purchased, rented, harvested, scraped or otherwise non-consenting lists.
• Sending to an address after a hard bounce or a complaint from that address, or attempting to evade the suppression list.
• Falsifying, forging or obscuring the From, Sender, Reply-To or Return-Path headers, or any other attempt to disguise the origin of a message.
• Phishing, credential harvesting, impersonating a person or organisation, or any message designed to deceive the recipient about who sent it.
• Distributing malware, ransomware, spyware, or links intended to install any of these.
• Sending on behalf of a third party you have not disclosed to us, or reselling access to your inboxes as a sending service.
• Operating an agent that sends without a human-defined purpose and boundary — for example a loop that discovers and contacts addresses on its own initiative.
• Harassment, threats, or repeated contact with a recipient who has asked you to stop.
• Circumventing quotas, rate limits, or creating multiple accounts to increase your effective sending volume.
• Any use that is unlawful in your jurisdiction or the recipient's, including violations of CAN-SPAM, CASL, GDPR or the ePrivacy Directive.

Kleevee is built for transactional and conversational mail. We do not offer list upload, list import, campaign scheduling or mail-merge features, and their absence is deliberate rather than a gap in the roadmap.

We process delivery feedback continuously. When an address hard bounces, or a recipient marks your message as spam, that address is added to your account’s suppression list automatically and immediately.

Suppression is enforced before a message is built. You cannot send to a suppressed address through any interface, and the API will tell you the address was blocked and why rather than silently dropping it. Soft failures — a full mailbox, a temporary greylist — do not suppress, because they do not mean the address is bad.

Sustained high bounce or complaint rates put every other customer’s deliverability at risk. We monitor both per account and may pause sending on an account that exceeds a safe threshold, with notice where the situation allows for it.

Each plan carries a monthly send ceiling, a daily ceiling, and a short-window burst ceiling. These are enforced at send time and charged per accepted recipient. Exceeding one returns an error; it does not queue the message for later.

Storage and retention limits apply per plan. Messages older than your plan’s retention window may be removed. Export anything you need to keep.

If we believe an account is breaching Section 04, we may pause its sending, suspend it, or terminate it. Where the breach is ambiguous or looks like a misconfiguration we will normally contact you first. Where it is clear-cut — phishing, malware, forged headers, purchased lists — we will act immediately and tell you afterwards.

Report abuse originating from Kleevee to abuse@kleevee.com. We read that address and we act on it.

We work to keep the service running and mail flowing, but we do not promise uninterrupted availability, and we are not liable for indirect or consequential loss arising from a delayed or undelivered message. Build retries and failure handling into anything that matters.

We may change these terms. Material changes will be announced by email to account owners before they take effect. Continuing to use Kleevee after that is acceptance.

General enquiries: support@kleevee.com. Abuse reports: abuse@kleevee.com. How we handle personal data is described in our Privacy Policy.