Chat history
Review conversations the child account participated in, including message text, sender, timestamp, conversation context and supported attachments that remain within the active retention window.
FAMILY SAFETY ยท PLANNED
Parents can supervise without making safety invisible.
Leviathan Family Safety is designed to let a verified parent or guardian supervise a child account, review social activity and apply age-appropriate controls across chat, friends, purchases, sessions and connected devices. The child should always be able to see that supervision is active and what it covers.
PARENT DASHBOARD
One place to understand a child account.
The parent view is intended to show the information needed for supervision while keeping account credentials, provider tokens and unrelated private data out of view.
Friends and requests
View the child's current friends, incoming and outgoing friend requests, blocked users and recent relationship changes. Parents can require approval before new friends are added.
Social activity
See recent direct-message contacts, group participation, party or server invites and other supported Leviathan social interactions without exposing information outside the child's own activity.
Safety events
Surface reports, moderation actions, blocked contacts, suspicious contact attempts and other relevant safety events with enough context for a parent to understand what happened.
Devices and sessions
Review signed-in devices, recent session activity and account security events. Parents can revoke child sessions where permitted without gaining access to passwords, recovery secrets or provider tokens.
Purchases and LeviCoins
Set approval requirements, spending limits and purchase visibility for LeviCoins, store items and other supported transactions tied to a supervised account.
CHAT SUPERVISION
Visible supervision, not hidden monitoring.
If a parent can read a child's Leviathan chat history, the child account should clearly show that family supervision is active. The parent dashboard should also keep an audit trail of important supervision actions so the relationship is understandable from both sides.
1Search and filtersFilter by conversation, friend, date, safety event or message type.
2Retention-awareParents can view messages only while Leviathan legitimately retains them under the applicable retention policy.
3Context preservedEdits, moderation actions and removals can be represented when the service retains those events, rather than silently fabricating missing history.
Family dashboardSupervision active
CH
Chat historyConversations the child participated in
ViewFR
FriendsFriends, requests and blocks
ReviewSA
SafetyReports, moderation and contact alerts
MonitorCONTROLS
Parents can control who can contact the child and when.
Family Safety is intended to be broader than a read-only dashboard. Parents should be able to set practical limits that affect the child account across website, app, launcher and client surfaces where the feature is supported.
Direct messages
Allow direct messages from nobody, friends only, approved contacts or supported broader groups. New contacts can require parent approval.
Voice and calls
Enable or disable supported voice features, calls and voice invitations independently from text chat.
Friend approval
Require approval for incoming requests, outgoing requests or both, with clear reasons when a request is blocked by family settings.
Groups and invites
Control group-chat, party, server and community invitations, including whether invitations from unknown users are allowed.
Time and quiet hours
Set schedules for social features, launcher use or notifications, with clear local-time handling and visible notices before a restriction starts.
Content protections
Apply supported language, media and contact-safety filters, with stricter defaults available for younger supervised accounts.
LINKING AND TRUST
A family link should be verified and reversible.
A parent or guardian should never gain access to a child account simply by knowing a username. Linking should require authenticated Leviathan accounts, a short-lived approval flow and clear confirmation on the child side or another age-appropriate verification path.
Verified guardian
Family roles are tied to authenticated Leviathan accounts and recorded with the verification method, relationship state and timestamps.
Child-visible status
The child account can always see who supervises it, which controls are active and the major supervision actions recorded for the account.
Age transition
When a supervised user reaches the applicable age or family status changes, Leviathan should provide a defined transition, review and unlinking process instead of leaving parental access active indefinitely.
PRIVACY BOUNDARIES
Supervision should not expose secrets or unrelated people.
Parent access is limited to the supervised child account and supported family-safety data. A parent must not receive Microsoft, Google or Leviathan passwords, refresh tokens, recovery codes, two-factor secrets or other credentials. Friends' private data should not be exposed beyond information necessary to represent their interactions with the child.
No credential access
Parents can manage supervision without seeing passwords, OAuth tokens, passkeys, authenticator seeds or recovery credentials.
Audit trail
Important parent actions such as changing chat permissions, approving a friend, revoking a session or changing purchase limits should be recorded.
Normal retention rules
Family supervision does not create a secret permanent archive of deleted content. Access follows the same documented retention and legal rules that apply to the service.
DEVELOPMENT STATUS
Family Safety is a planned platform capability.
The website can document the design now, but chat, friend supervision and parent dashboards should only be marked available after the underlying social, family-linking, retention, audit and permission systems are implemented and tested. The public UI should continue to distinguish planned, development and released states.
Family controls should connect to the whole account.
Privacy, security, sessions, purchases and social controls should all use the same verified Leviathan family relationship.