Policy

Anti-spam and acceptable use

Effective 4 August 2026. Oizzy is operated by Klementine Ventures LLC. This policy binds every account that sends through Oizzy: accepting it is a condition of the first send, and breaking it ends an account.

1. Permission is the whole rule

You may only mail an address that gave verifiable, purpose-bound consent to you — the named sender on the message — to receive this kind of email. Consent given to another brand, another list, or another company is not consent for you. Oizzy records that permission as evidence: timestamp, source, IP, the consent text shown, and the jurisdiction stamped at capture.

Two narrow exceptions exist because the law makes them, and the product applies them per recipient:

Korea (정보통신망법 Art. 50 proviso): a recipient who transacted with you may receive email about your own similar goods or services for six months after that transaction. Oizzy expires that window automatically.
South Africa (POPIA §69(3)): the existing-customer lane, plus the single consent request the Act explicitly permits — once per subscriber, ever, ZA recipients only, logged in the ledger.

There is no equivalent lane in the EU or for recipients whose location is unknown. A consent-request email is itself marketing, so for those recipients permission has to be gathered off-channel.

2. Lists you may not upload

Purchased, rented, leased or otherwise bought lists.
Scraped, harvested or guessed addresses.
Appended addresses from a data broker.
Co-registration lists where you were not the named recipient of consent.
Third-party contact exports, CRM dumps or event lists without a consent record per person.

Imports declare a consent basis: proven (records exported from your previous platform, imported with their original timestamps), attested (you formally state consent existed but the records did not survive migration), existing customer, or none. Memberships imported with no basis land unmailable, and no setting turns them back on.

3. Content you may not send

Anything unlawful in the sender's or the recipient's jurisdiction.
Phishing, credential harvesting, malware, or links to either.
Deceptive headers, forged sender identities, or subject lines that misrepresent the message.
Content that hides who is sending or makes opting out harder than opting in.
Cold outreach, prospecting or sales sequences to people who never subscribed.
Transactional or relay traffic on behalf of a third party.

4. What every message must carry

The sender's real identity and contact details, from the audience's sender profile.
A working unsubscribe link, plus RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers.
An accurate subject line — with the (광고) prefix added automatically for Korean recipients on marketing sends.
The legal footer configured for the audience, rendered per recipient in the language their jurisdiction requires.

These are applied by the product at send time. They are not optional and cannot be switched off.

5. Opt-outs

Unsubscribes are honoured the moment they arrive — no login, no reason, no confirmation step, no delay. Opt-out latency is measured and shown on your dashboard. Mailing an address after it opted out is a termination-level breach.

6. Bounces and complaints

Hard bounces and spam complaints reported by Amazon SES suppress the address across your whole account automatically, because a poisoned address is poisoned for every list it appears on. Sustained rates above roughly 5% hard bounces or 0.1% complaints put an account under review; continued sending at those rates suspends it. Sending on the shared oizzy.space domain means one bad sender damages everyone, so this is enforced rather than encouraged.

7. Monitoring and enforcement

Every campaign runs a server-side compliance pre-flight before delivery, and deliveries are only created for recipients who pass it. Oizzy may inspect sending patterns, list sources and complaint data, and may hold, suspend or terminate an account that breaches this policy — immediately and without notice where recipients or the shared sending reputation are at risk. Oizzy sends through Amazon SES and also applies the AWS Acceptable Use Policy and SES service terms.

8. Reporting abuse

If you received mail through Oizzy that you did not ask for, forward it with full headers to ronald@oizzy.co. Reports are acknowledged within one business day. Every report is traced to the sending account through the message tags carried by each send, and the address is suppressed while it is investigated.