Trust & Safety
This page explains how safety works on ASAI: what we actually do, what we do not do, and how to reach a human when something goes wrong.
It is written to be read by anyone — users, parents, journalists, regulators. Our aim here is accuracy rather than reassurance. A safety page that describes systems we have not built would be worse than no page at all, because you would rely on protections that are not there.
If you are looking for the rules themselves, see the Acceptable Use Policy. If you are in a crisis right now, see Crisis & Safety Resources.
Effective: 31 July 2026 · Version: 2.0
Operator: APERTURESyndicate OÜ (Republic of Estonia (EU), Registry code 17384111)
1. Our position
AI companions and creative chat platforms have caused real harm elsewhere in this industry. We take that seriously, and we have made product choices because of it — no streaks, no "your character misses you" notifications, no engagement-maximising design.
But taking it seriously also means not overstating what we have built. APERTURESyndicate is a two-person company. ASAI has published rules, a way to report violations, and the ability to remove content and close accounts. It does not have an automated safety-monitoring apparatus, and this page will not pretend otherwise.
2. What we actually do
2.1 We publish rules and enforce them when we learn of a breach
The Acceptable Use Policy, the Roleplay Content Policy, and the Community Guidelines set out what is not allowed. When we become aware that content or an account breaches them — almost always because somebody told us — we review it and act.
2.2 We accept reports by email and act on them
Write to [email protected]. This is a real inbox read by a real person. We aim to acknowledge reports within 72 hours on working days, and we prioritise anything involving minors, credible threats, or imminent danger.
Reports about illegal content under EU law follow the procedure in our DSA Notice & Action page.
2.3 We remove content and close accounts
We can unpublish a character or world, delete specific content, restrict publishing rights, or terminate an account entirely. Every enforcement action is recorded with the reason for it.
2.4 We tell you why
If we remove your content or restrict your account, you get a statement of the reason and the rule it relates to. This is our obligation under Article 17 of the EU Digital Services Act, and we treat it as a floor, not a target.
2.5 We never train on your content without you asking us to
Model training on your conversations is opt-in and off by default. If you have not turned it on, your content is not in a training export — the export filters on consent. See AI Data & Training for the full policy.
2.6 We cooperate with law enforcement within the law
For an imminent threat to life we respond without waiting for a court order. For anything else we require a properly served subpoena, warrant, or international equivalent. We do not proactively hand user data to governments.
If child sexual abuse material is brought to our attention, we remove it, preserve what the law requires us to preserve, and report it to the competent authorities. We do not scan for it — see below.
3. What we do not do
This is the part most safety pages leave out. Please read it, because it determines what you can and cannot rely on.
3.1 We do not run a safety classifier on your messages
There is no separate model inspecting each message you send or each reply you receive. Nothing sits between you and the conversation.
Model behaviour is shaped by instructions in the system prompt — the model is told to decline real-harm instructions, sexual content involving minors, and similar categories. That is a strong tendency, not a guarantee. A language model can be argued out of its instructions, and ours can too.
3.2 We do not detect crises automatically
ASAI has no self-harm detector. If you write something that would alarm any human reading it, no alert fires, no modal appears, no chat is paused, and no incident record is created. The system does not know.
In roleplay this matters especially. Characters are explicitly instructed to stay in role and not to insert safety notices or disclaimers. A character will not stop the scene to hand you a crisis line. It is not built to do that.
If you are struggling, please go straight to Crisis & Safety Resources — the numbers there are real, staffed, and free in most countries.
3.3 We do not review characters before they are published
Publishing is immediate. There is no automated pre-publication check and no human queue. Review happens afterwards, and only when somebody reports something. See Publication & Review.
3.4 There is no report button in the product
We have not built one yet. Reporting today means emailing [email protected]. We know a button would be better and we intend to add one; until this page says we have, we have not.
3.5 We do not proactively read your conversations
We do not monitor, sample, or scan private chats looking for violations. Staff access to conversation content happens only when it is necessary to act on a specific report, to comply with a lawful order, or to fix a bug you have asked us to fix.
This is a deliberate privacy choice, and it has a direct cost: things we would want to catch, we will not catch, because we are not looking.
3.6 We do not verify your age
Account creation asks how old you are. Nothing checks the answer. See Age & Eligibility.
3.7 We do not run our own models
Inference happens at third-party providers, not on our hardware. See AI Data & Training for who they are and what that means for your data.
4. No engagement-maximising design
This one is real, and it is a design commitment we intend to keep.
ASAI has no streaks, no escalating notifications, no "your character misses you" messages, no daily login rewards. We do not push you to come back.
We make money from subscriptions — from people who find ASAI useful enough to pay for it, not from people who cannot put it down. Usage on every plan is capped by design (see Product Terms), which means the business does not benefit from you using ASAI more than you meant to.
5. Personas we do not allow
Some character archetypes are prohibited by policy regardless of framing:
- Therapist, psychologist, counsellor, doctor, or other licensed-professional personas — even fictional, even with disclaimers
- Personas claiming to be real, identifiable living people
- Characters written or depicted as minors in romantic or sexual contexts
- Characters designed to manipulate users or manufacture dependency
These are rules, not filters. They are enforced when we find out about a breach, which usually means when you tell us. See Content Policy.
6. When something goes wrong
Email [email protected]. Include links or enough detail for us to find the content, and tell us what is wrong with it. We accept reports in English or Estonian.
- Illegal content under EU law — see DSA Notice & Action
- Copyright and trademark — see Copyright & DMCA
- A minor's account — see Age & Eligibility
- Imminent danger to someone — contact emergency services first, then us
We aim to acknowledge within 72 hours on working days. Anything involving a minor or a credible threat jumps the queue.
7. Transparency and our size
APERTURESyndicate is a micro enterprise: two people, based in Republic of Estonia (EU). Under Article 19 of the EU Digital Services Act, micro and small enterprises are exempt from the obligations in Articles 20 to 28 — including the internal complaint-handling system and the periodic transparency reports that larger platforms must publish.
We are therefore not publishing a quarterly transparency report, and we are not promising a formal appeals apparatus with review deadlines. An earlier version of this page promised both. We could not staff them, and a promise we cannot keep is worse than an honest limit.
What remains binding on us, and what we do:
- We describe our moderation in our terms (Article 14)
- We accept and act on notices of illegal content (Article 16)
- We give a statement of reasons when we restrict content (Article 17)
If you think we got a decision wrong, write to [email protected] and say so. A human will read it and can reverse the decision. We simply are not going to dress that up as a two-tier review process with an SLA, because it is one of us reading your email.
8. Working with researchers and journalists
We welcome external scrutiny. Contact [email protected].
We will not give anyone access to identifiable user content. We can discuss our policies, our design decisions, and how the system actually works — including the parts described in Section 3.
9. Things we will not do
- We will not train models on your content without your explicit opt-in
- We will not sell user identity data to advertisers
- We will not market ASAI to children
- We will not use addictive design patterns
- We will not host characters claiming licensed professional expertise
- We will not describe safety systems on this page that we have not built
If any of these change, it will be announced in advance, not quietly edited in.
10. Changes to this page
Material changes are announced at least 30 days in advance by email and in-product notice, and the date at the top of this page is updated.
Version history
- 2.0 — 31 July 2026 — Corrected to match the product as built. Removed descriptions of a per-message safety classifier, automatic crisis intervention, pre-publication character review, an in-product report button, safety-incident retention, and quarterly transparency reporting — none of which exist. Added Section 3 setting out what we do not do.
- 1.0 — 16 May 2026 — Initial publication
Operator
APERTURESyndicate OÜ
Republic of Estonia (EU) · Registry code 17384111 · VAT EE102972654
[email protected]