Back

Plain beta notes

Legal, privacy, safety, and donations

Short version: adults only, consent first, no recovery yet, beta data may be cleaned up after 2 weeks of inactivity, donations are optional, and safety always beats app mechanics.

Use the app with care

Terms

The plain rules for using Control during public beta.

  • You must be 18 or older.
  • Use must be voluntary, lawful, and consensual for everyone involved.
  • Control helps organize tasks, status, requests, and safety notes. It does not enforce consent or decide punishment for you.
  • Username/password accounts have no recovery yet. If you lose the password, the account may be lost.
  • Inactive beta account and pair data may be deleted after 2 weeks of no activity.
  • The app can change quickly during beta, including features, data rules, and demo limits.
  • Use the demo at your own risk. No online service can promise perfect uptime, privacy, or protection from leaks, hacks, bugs, or data loss.

Adult, consensual use only

Control is for adults using it by choice. Do not use it for coercion, blackmail, stalking, harassment, threats, impersonation, illegal activity, or anything involving minors.

Your account

You create a simple username and password. There is no password reset or identity verification yet, so keep your password safe. Do not share accounts.

Your pair connection

Most app data belongs to the pair connection: tasks, toys, safewords, requests, analytics, and history. Use partner codes only with someone you trust. If you disconnect, the old pair should no longer be accessible from either account.

Beta changes

This is a live beta. Features can move, break, disappear, or be reset while the project is being tested and improved. Demo accounts may be cleaned up after 2 weeks of inactivity.

Use at your own risk

Control is offered as a free gift to the community, with no fee and no promises. I will make reasonable efforts to keep it private and secure, but by using it you accept the risk of bugs, downtime, unauthorized access, data loss, leaks, or other security failures. To the fullest extent allowed by law, I am not responsible or liable for any harm, loss, or damage arising from a leak, hack, breach, outage, bug, or anything else that happens while using it. Do not put anything here that would seriously harm you if it were exposed or lost. If you are not comfortable with that, please do not use the demo.

What gets stored

Privacy

A short explanation of account, pair, demo, and beta data.

  • The public demo uses fake local demo data and does not connect to a real partner.
  • Registered accounts store username, password hash, sessions, and activity timestamps.
  • Pair spaces can store roles, partner codes, toys, task templates, tasks, requests, safewords, support requests, and analytics.
  • Profile pictures are visible to people you connect with and can be removed or replaced from Profile.
  • Task proof is encrypted for the sender and receiver devices and automatically deleted after its short retention period.
  • Uploaded toy PNGs are stored only as toy icons for that pair.
  • Payment card details should stay with the payment or donation provider, not inside Control.
  • Beta data may be removed after inactivity or during cleanup.

Demo data

The playtest demo is fake. It exists so people can understand both sides before registering. Demo clicks do not create real tasks, partners, payments, uploads, or history.

Account and pair data

When you register, Control stores enough data to sign you in and connect you to a pair space. Pair data is isolated by connection, so one pair should not see another pair's toys, tasks, settings, or analytics.

Pictures and protected proof

Your profile picture is visible to people you connect with in Control, so do not upload a picture you are unwilling to share with them. Protected task proof is encrypted for the sender and receiver devices and is automatically deleted after its short retention period. Removing a picture cannot remove copies another person previously saved outside Control.

Deletion

During beta, inactive data may be deleted after 2 weeks. Support, suggestion, bug report, and deletion workflows are still basic while the project is small.

Consent stays above the app

Safety

How safewords, limits, requests, and human care should work.

  • Consent can change at any time.
  • Yellow means slow down, clarify, or check in.
  • Red means stop active control flows.
  • Hard limits and health needs are not punishable.
  • The app can show safety state, but people are responsible for care.
  • Leave or disconnect if the pair connection is no longer safe.

Safewords

Yellow and red safety signals are part of the main product. Red should halt active controls until the controller resolves the safety state manually.

Requests and refusal

Pause, cancel, extend, release, start-later, and refusal flows exist so people can communicate inside the app instead of being trapped by it.

Human judgment

Control can organize agreements. It cannot decide what is safe, legal, healthy, or kind in a real relationship.

Boundaries

Use Rules

What is allowed, what is not, and when access can be removed.

  • Use Control only for private adult consent/accountability play.
  • Do not use the app to pressure someone who wants to stop.
  • Do not punish safety signals, hard limits, health needs, or refusal of consent.
  • Do not upload illegal, abusive, explicit, or non-consensual material.
  • Do not try to access another pair's data or interfere with the service.
  • Access may be removed if the app is abused or creates safety/legal risk.

Allowed use

Private task management, status tracking, toy libraries, safety notes, requests, and pair accountability between consenting adults.

Not allowed

No coercion, stalking, threats, extortion, non-consensual control, commercial sexual services, illegal content, minors, harassment, account sharing, or attempts to break isolation between pairs.

Enforcement

Accounts, pair spaces, uploads, or access can be removed if they violate these rules or put the project, users, providers, or platform at risk.

Optional support

Donations

Donations help keep the demo alive but do not buy control over the roadmap.

  • Donations are optional.
  • Donations help with servers, tools, development, testing, AI costs, and future art/avatar work.
  • A donation does not override consent, safety, law, or app rules.
  • Donation refunds depend on the provider used.

Why donations exist

Control needs money to keep improving: hosting, tools, development, testing, design, and eventually better avatar art. Any direct support helps the project survive while I try to keep the service free.

No special consent rights

Supporting the project does not give anyone the right to pressure another person, bypass safety, or demand private access to someone else's data.

Free while supported

Demo Access

How public demo access and future scaling should be understood.

  • The app is currently public demo software.
  • The goal is to keep the service free if community support covers maintenance.
  • Scaling, development, hosting, AI tools, and better assets have real costs.
  • Any future access changes should be explained clearly before they affect users.
  • Donations never override consent, safety, law, or app rules.

Public demo access

Demo access may change while the project is being tested. Accounts and pair spaces may be limited, reset, or removed if the service is abused or inactive.

Future changes

If the project grows enough to need access limits, memberships, or another funding model, Control should explain the cost, renewal behavior, cancellation route, and provider terms before checkout.

No consent shortcut

Support, donations, or future access checks only affect the service. They never change consent, safewords, legal limits, or relationship boundaries.

These are beta terms written for clarity, not a substitute for formal legal review before a larger public launch.