Draft for owner review
Privacy policy
A working draft describing the data flows already designed for KeyVault.
Information KeyVault handles
Discord sign-in provides an account identifier, username, optional global display name, and optional avatar reference. KeyVault also stores server-side session records needed to keep a browser signed in.
The service handles the groups, products, variants, encrypted product keys, delivery configuration, panel memberships, payment references, and audit records that users submit or create.
Why the information is used
Account data is used to authenticate users, recognize the configured platform owner, enforce roles, and show the correct workspace. Inventory and delivery data is used to provide the key-delivery functions requested by users.
Operational records may be used to secure the service, diagnose failures, prevent abuse, and document sensitive changes. Raw product keys should never be written to application logs.
Cookies and sign-in
KeyVault uses temporary OAuth state and an HttpOnly browser-session cookie. These are necessary for Discord sign-in, request verification, and authenticated navigation; they are not described as advertising cookies.
Logging out revokes the server-side session and asks the browser to remove its session cookie. The final policy should list production cookie names, lifetimes, and secure-cookie settings.
Service providers and transfers
Discord processes OAuth sign-in under Discord’s own terms. Stripe processes enabled card checkout and billing-portal activity. No production cryptocurrency provider receives data unless the operator later selects and configures one.
The owner must document the final hosting, database, email, monitoring, and payment providers, including relevant international data transfers, before launch.
Retention and security
The implementation is designed around encrypted inventory secrets, hashed session tokens, scoped authorization, and audit records. No technical measure eliminates every risk, and the production policy should describe the controls that are actually deployed.
Final retention periods are still an owner decision. They should cover account records, expired sessions, inventory, delivery history, payments, audit events, backups, and deletion requests.
Your choices and contact
Depending on applicable law, users may have rights to access, correct, export, restrict, object to, or delete personal information. The final policy should explain how a request is verified and which records must be retained for security or legal reasons.
The owner must add the data-controller identity, a monitored privacy contact, jurisdiction-specific rights, and any required supervisory-authority information before publishing this page.