Erycina

Responsibility checklist

Describe what you are planning to operate. This will tell you which areas it raises, and why it raised them.

It will not tell you whether your deployment is lawful. Nothing that runs in a browser can do that, and a tool that implied otherwise would be worse than no tool at all. What it can do is stop you from finding out about an entire area of responsibility six months after you started taking money.

Read Self-hosting first if you have not. The short version: when you run Erycina, you are operating the service, and you are the one who has to work out what that requires where you live.

This runs entirely in your browser. Your answers are not sent anywhere, stored, or logged.

Where are you and your users?

Select everything that applies. Obligations tend to follow your users, not only your server.

Who will use the instance?

Who pays whom?

Where will it run?

What will you sell?

Will you enable Terminus, the AI relationship organ?

What your deployment raises

This is a prompt list, not a legal determination. It cannot see your business structure, your contracts, or what your service actually does in practice. Use it to work out which questions you owe someone qualified, and which ones you can answer yourself.

Answer the questions above and this narrows to your deployment. Until then, here is everything it knows how to raise.

  1. Data protection

    You decide what personal data the instance collects, why, how long it is kept, who can reach it, and how someone exercises their rights over it. Erycina stores what you configure it to store; it does not decide whether that is lawful where you operate.

  2. Especially sensitive data

    An adult platform holds private messages, intimate media, payment-adjacent records, and inferences about people's sex lives. Under the GDPR, data concerning sex life and sexual orientation is a special category with a higher bar for processing. Treat a database dump as a serious incident, not an inconvenience.

  3. Age assurance

    The age of the people in the content and the age of the people viewing it are both yours to answer for. Requirements differ sharply by jurisdiction and are moving quickly. Erycina ships the mechanics you configure; it does not certify that your configuration satisfies a given regime.

  4. Performer records

    Producers of sexually explicit material may have record-keeping and labelling obligations covering performer identity and age. These records are among the most sensitive things you will ever hold: required to exist, catastrophic to leak. They never belong in a tenant's public tree.

  5. Content moderation and illegal-content reports

    If anyone other than you can upload, you need a way for a report to reach a human and a decision you can explain afterwards. That means a real contact route, a process, and a record of what you did. A form nobody reads is not a process.

  6. Intermediary and hosting liability

    Hosting other people's content changes your legal position. Frameworks such as the EU Digital Services Act attach conditions to hosting-provider protections, including acting once you have actual knowledge of illegal content. Whether and how they apply depends on what your service actually does, which is why the answer is to work out your position rather than to assume you are liable for everything.

  7. Copyright complaints

    You will receive claims: some wrong, some abusive, and some about your own stolen work. You need a route to receive them, a decision process, and a counter-notice path where one applies. Safe-harbour regimes generally require designation and procedure, not good intentions.

  8. Payment providers

    Erycina does not become your merchant of record. You choose providers that permit your business and your content, and you live inside their acceptable-use policies, underwriting, identity checks, chargeback rules, and geographic limits. A payment adapter existing in Erycina does not mean a provider permits every use of it.

  9. Holding other people's money

    Collecting money and paying it onward to other people is a different activity from being paid for your own work. Depending on where you are it can pull in payment-facilitation, money-transmission, or agent-of-payee rules, and it certainly pulls in bookkeeping you cannot improvise. Settle this before the first payment, not after.

  10. Consumer protection

    Selling to consumers brings pre-contract information duties, cancellation and withdrawal rules, renewal and cancellation expectations for subscriptions, and rules about how prices are displayed. Digital content and subscriptions have their own specific treatment in several regimes.

  11. Tax and VAT

    Erycina does not determine your tax position. Cross-border sales of digital services to consumers commonly trigger VAT or its equivalent in the buyer's country. The EU's One Stop Shop exists so that eligible businesses can register in one Member State and report cross-border B2C supplies through it instead of registering in each.

  12. Server and account security

    Patching, ingress, secrets, administrative access, and the unglamorous discipline of not leaving a database port open are yours now. Assume that a compromise of the host is a compromise of everything the host can read.

  13. Backups, recovery, and incident response

    You choose the backup scheme, you test the restore, and you decide in advance what you do on the day something is breached, deleted, or seized. An untested backup is a belief, not a backup. Work out now who you would have to tell, and how quickly.

  14. AI transparency

    With Terminus enabled, messages are processed by an AI system to spot boundary crossings, summarise conversations, and draft replies. People interacting directly with an AI system may need to be told so. Erycina's own answer is structural rather than legal: when Terminus takes over it says so and speaks as itself, and the human stops speaking as the creator.