Overview
LoginSeal is the account you use to sign in to LoginSeal and to any other application that supports LoginSeal as a sign-in provider. One account, one password, one place to manage your privacy.
What is LoginSeal
LoginSeal is a single sign-in account. Instead of creating a new username and password every time you try a new app, you sign in once with LoginSeal and the app receives a confirmation that you are who you say you are. Your password is never shared with the app.
It uses the same OpenID Connect standard as "Sign in with Google" or "Sign in with Apple", so the experience will feel familiar.
Signing in
When you click "Sign in with LoginSeal" inside a third-party app, you are sent to loginseal.eu. You enter your password (and a 6-digit code if you have two-factor authentication enabled), then a consent screen lists exactly what the app is allowed to see about you. Once you approve, you are sent back to the app, signed in.
The next time you open another app that uses LoginSeal, sign-in is silent: you are already signed in here, so the app gets its confirmation without you having to type anything. You only see the consent screen the first time you authorise a given app.
Your account
You have one LoginSeal. It can have multiple ways of signing in: email and password, Google, GitHub, or Apple. If you sign in with a social provider that returns a verified email matching your existing account, the two are linked automatically so you do not end up with duplicates.
Your password, two-factor secret, recovery codes, email verification status, and preferences (language, timezone) all live here on loginseal.eu. That is the single source of truth: change it here, and every connected app sees the change immediately.
Your privacy and data
Apps you sign in to never see your password, your payment details, or any data from other apps. They only receive what the consent screen tells you they will receive, expressed as named scopes (for example
profile.read
returns your display name and avatar; it never returns your email unless you also approved
email.read).
You can revoke any app, or any individual permission you previously granted, from your profile at any time. Revocation takes effect immediately.
Building an integration
If you are a developer and you want your application to use LoginSeal as a sign-in provider, the third-party API documentation walks you through registering a client, the OAuth 2.0 / OIDC handshake, tokens and claims, and webhooks.
Sign in and request developer access to unlock the full integration guide.
Sign in- Getting started : register a client and run a first sign-in.
- Auth flow : authorisation code with PKCE, step by step.
- Tokens and claims, Webhooks, and a Sample integration.