What the portal stores
Bits & Crumbs stores your account email and name, a password hash, account status, installation allowance, entitlement expiration, registered installation UUIDs and host fingerprints, server names, signed license files, and license issue and expiration dates. Renewal and replacement requests include the reason you provide and their review history.
Why we store it
These records let us authenticate your account, issue licenses to the installations you register, prevent issuance beyond your allowance, and provide future renewals, replacements and support. We retain earlier licenses and their relationships to preserve license history.
Cookies and security records
A secure, HTTP-only session cookie keeps you logged in for up to 12 hours. The server stores a hash of the session token and a session verification token. Login rate limits use hashed identifiers derived from the email entered and connection source address. Audit records track account imports, failed and successful logins, registrations, license issuance, and operator decisions. Portal responses are marked to prevent caching.
Support and operator administration
Support cases store subjects, messages, timestamps, status and customer/operator authorship. Replies are visible within the customer portal. Authorized operators may retain separate internal support notes and review customer and license records. Operator logins use a separate HTTPS hostname, password plus authenticator code, and a secure session cookie lasting up to one hour with a 15-minute idle limit. Customer sessions have a 30-minute idle limit. Authenticator enrollment secrets are retained in the restricted registry database for verification and must be protected in backups. Administrative policy overrides, approvals, downloads and issuance are audited with an operator identity and reason where applicable.
Optional AI support
If an operator enables the OpenAI support assistant and requests a draft, the operator question and explicitly selected case/customer context are sent to OpenAI. Structured context excludes account names, email addresses, installation UUIDs, host fingerprints, signed license files, password hashes and session credentials. Case messages and operator questions can contain personal information; common secret patterns are filtered, but this is not a guarantee that all sensitive text is removed. Internal support notes are included only when the operator selects them. AI drafts require operator review and cannot send replies or change licensing. Local AI audit records retain request metadata and token counts, not the draft or question. Requests use the API store:false setting; this does not promise zero provider retention.
Access and retention
Accounts are created by an operator; there is no public signup. Customer accounts can access their own installation and license records. Authorized operators can manage account entitlements and review requests. Records and backups are retained for account administration, license history and support. Contact the person who provided your account to request corrections or account closure; disabling an account prevents future portal access but does not itself invalidate downloaded licenses.
Files and signing keys
The portal does not need access to the files on your ByteBridge servers. You provide installation and host identifiers for license binding. The private license signing key is held by the licensing service and is never returned to your browser or stored in the account database.
