Skip to content
Bredkey
Back to Bredkey

Privacy Policy

Effective 18 November 2026

Nam Hoang operates Bredkey, an identity service supporting administrator invitations and optional self-service sign-up. This policy describes the information Bredkey handles when you create an account, sign in or connect an application.

Information we collect

  • Account details: your email address, account identifier, role and status. An administrator supplies your email address when inviting you, or you provide and verify it during self-signup.
  • Sign-in details: a password hash, passkey public keys and credential details if you add a passkey, and hashed one-time sign-in, sign-up and recovery codes. Bredkey does not store your password in readable form or your passkey's private key.
  • Service records: sessions, invitations, pending sign-up requests, application registrations and permissions, and audit records of account and access actions.
  • Technical information: an IP address and verification signals used to limit repeated sign-in and sign-up attempts. The hosting and reverse-proxy software may also create standard request and error logs.

Why we use it

We use this information to create and review accounts, verify sign-ins and email addresses, send invitations and one-time codes, prevent automated abuse, maintain account security, let administrators manage users and applications, and issue identity tokens to applications you approve. An email address and password are needed to create an account; without them, Bredkey cannot provide password sign-in. Passkeys are optional.

Who receives it

Administrators can see account email addresses, sign-up requests, roles and status and can issue recovery codes. The configured email provider receives the destination address and invitation, verification or sign-in message needed to deliver email. When self-service sign-up is enabled, the sign-up page uses Cloudflare Turnstile to verify human submissions; Cloudflare receives technical request and browser signals needed to verify the check under Cloudflare’s Privacy Policy. When you approve a connected application, it receives a stable account identifier and any approved claims, which may include your email address and preferred username. That application's own privacy policy governs what it does with the information it receives. The hosting operator can access service data and backups to run the service. We do not use Bredkey for advertising or sell account information.

Cookies and security

Bredkey uses necessary cookies for account and OpenID Connect sessions, sign-in and sign-up verification challenges and protection against forged requests. They are not advertising cookies. Account data is stored in a SQLite database on the Bredkey host, and the documented backup process copies the database and signing keys. Passwords are protected with a salted hash; sign-in tokens and recovery codes are stored as hashes. Production traffic is intended to use HTTPS. No system can guarantee absolute security.

How long information stays

Account sessions last up to 30 days. Email sign-in and sign-up verification codes expire after 10 minutes, passkey challenges after 5 minutes, invitations after 7 days, and application grants generally after 14 days. Expired temporary records are cleaned periodically. Bredkey does not currently set an automatic deletion date for account records, passkeys, audit events, pending sign-up requests or unused invitation records. Backup retention is managed by the operator outside the application.

Your choices and requests

You can manage passkeys and revoke connected application permissions in your account. For access to, correction of, or deletion of information held about you, contact Nam Hoang. Account deletion is not currently self-service, and some records may need to be retained for security or legal reasons. You can also ask your Bredkey administrator for help with account access.

Contact and changes

Email Nam Hoang at pnam@hgphnm.com, use WhatsApp, or send an SMS to +64 27 359 3808. We will update this page and its effective date if our practices change. See the Terms of Service for conditions of use.

Bredkey© 2026 Bredkey
Terms of ServicePrivacy Policy