Make it yours. Keep it yours.
A trusted identity is only the beginning. Your private Memories, community participation and local-notice preferences must have different permissions, clear ownership and a way to leave. Test how those boundaries should work.
i
This is a fictional account simulator—not registration, account settings or a working deletion service.
Each button runs a new disposable SQLite fixture on the server. No username, email, address, phone, real consent, passwords, photographs or sensitive reports are collected. Nothing here signs you in, joins a real community, sends a notification or deletes a real account.
ACCOUNT LIFECYCLE EXERCISES
A member should control more than a profile picture.
Choose what happens to a synthetic account. Each result is calculated on the server with an isolated fixture and never changes actual user data.
SERVER-EXECUTED FIXTURE
LOADINGLoading checks…
Select a scenario to examine the member lifecycle.
What the checks showed
No real user action performed · no public content or personal record stored
Permission to use the app is not permission to share everything.
Permanent key, not email
Link the verified issuer and subject with a server-held secret. A changed email must not break ownership.
Purpose by purpose
Private Memories, community sharing, location alerts and personalization are separate choices. No bundled opt-in.
Owner-only export and withdrawal
Access controls and revision checks prevent other members from changing your settings; deletion needs verified recent identity and safe retention rules.
Joining isn't staff access
Joining an Orbit never awards moderator or merchant ownership rights. Publishing still requires a staffed, independent review process.