Account information
Leviathan may store your email address, internal Leviathan account identifier, linked authentication methods, account settings, profile visibility choices, security settings and account activity required to operate the service.
PRIVACY
Your account data should be clear, limited and protected.
This policy explains what Leviathan collects, why it is used, how Google and Microsoft sign-in work, how sessions are handled and what controls users have.
LAST UPDATED
13 September 2026
Leviathan is an independent project. This policy applies to the Leviathan website and connected account services currently provided through leviathanclient.com.
Google sign-in
When you choose Continue with Google, Leviathan requests only OpenID identity, your primary email address and basic profile information. Leviathan uses Google's stable account identifier to link your Google identity to your Leviathan account.
Microsoft and Minecraft
Microsoft and Minecraft authentication is handled separately from Google. Leviathan may store linked Minecraft UUIDs, usernames, verification method and verification timestamps so ownership and account linking can be represented correctly.
Passwords and sessions
Passwords are not stored in plaintext. Leviathan uses secure session cookies for signed-in sessions. Authentication tokens and provider secrets are not intended to be exposed in public profile data or client-side code.
Security and diagnostics
Security events, rate-limit events, sign-in failures, verification state and limited diagnostic information may be processed to protect accounts, investigate abuse and maintain service reliability.
Public profile choices
Where profile features are enabled, users can control supported visibility settings for their Leviathan profile. Public Minecraft information may also come from public Minecraft services and community-observed data.
GOOGLE DATA
Google data is used for identity, not unrelated access.
Leviathan does not request Gmail, Google Drive, YouTube, Contacts or Calendar access for normal sign-in. The Google data used for login is limited to identity information needed to authenticate the user and associate the sign-in with a Leviathan account.
1RequestedOpenID identity, email address and basic profile information.
2PurposeSign in, create or link a Leviathan account, and show the connected authentication method.
3Not requestedGmail messages, Drive files, YouTube data, Contacts or Calendar data for standard login.
Authentication boundaryMinimal scopes
G
GoogleIdentity + email + basic profile
LoginM
MicrosoftSeparate Minecraft ownership flow
Linked identityL
LeviathanOwn account ID and settings
Canonical accountYOUR CONTROLS
Access, unlinking and deletion.
Leviathan is being built so users can review linked authentication methods and sign out of sessions from their account area. Where available, users may unlink supported external identities provided doing so does not leave the account without a safe sign-in method. Account deletion and data-removal requests will be handled through Leviathan support when self-service deletion is not yet available.
Connected accounts
Review which providers are linked to your Leviathan account, including Google and Microsoft/Minecraft where applicable.
Session control
Sign out of the current session and use future security controls to revoke other devices or sessions where supported.
Support requests
Privacy, account access, deletion and correction requests can be submitted through the Leviathan Support Center.
RETENTION AND SHARING
Data is kept only as needed for the service, security and legal obligations.
Leviathan does not sell personal data. Information may be processed by infrastructure and authentication providers required to operate the service, including Cloudflare for hosting and Google or Microsoft when you choose those sign-in methods. Security, fraud-prevention and legal requirements may require certain records to be retained for an appropriate period.
Questions about privacy?
Use the Leviathan Support Center for privacy, account or data requests.