Legal Stuff

What NiceLogin does

NiceLogin is an authentication gateway. When a user logs in via a provider (Google, GitHub, Apple, etc.), we receive the provider's token, generate a signed JWT with claims, and return it to your application. That's it. There is no database on our side. No user table. No persisted session.

Data that passes through us (and leaves)

During the authentication flow, the following data temporarily transits through our infrastructure:

• → User email (from the provider)
• → User name (from the provider)
• → Avatar/photo (from the provider)
• → Provider ID (e.g., Google sub)

This data is included in the JWT we return to you and discarded immediately. We don't cache, don't log, don't persist. RAM is cleared after each request.

What we DON'T do

• ✕ We don't create user profiles
• ✕ We don't track behavior
• ✕ We don't sell data (we have no data to sell)
• ✕ We don't use tracking cookies
• ✕ We don't integrate with ad networks
• ✕ We don't store provider tokens

Data we store (about YOU, the developer)

In the portal (portal.nicelogin.com), we only store your application's configuration: client IDs and secrets from the providers you configured, your NiceLogin API keys, and authorized domains. This is necessary to route login requests.

Infrastructure

We run on Rust in serverless edge functions. No disks, no session databases, no state between requests. Each request is processed and discarded.