Privacy Policy

Information we process

When you sign in with Discord, WithUsually may receive your Discord account identifier, display name, avatar, and email address. We also store account activity needed to operate the service, including orders, reward transactions, and administrative records related to your account.

Payments

Payment processing is handled by Stripe when commerce is enabled. WithUsually does not store full payment card numbers. Stripe may process payment, billing, fraud-prevention, and transaction information under its own privacy terms.

How information is used

We use information to authenticate accounts, provide purchased products or services, maintain rewards and order history, prevent abuse, respond to support requests, secure the platform, and comply with legal obligations.

Infrastructure and security

The service uses infrastructure providers including Google Cloud and Cloudflare. Reasonable technical controls are used to protect account and application data, but no online system can guarantee absolute security.

Order emails and agreement records

We use Resend SMTP, or another email provider configured by the operator, to send transactional order messages. The provider processes recipient addresses and message contents such as order items, payment totals, tips, and points. Our database retains delivery attempts, provider acceptance status, and an order snapshot to retry failed messages and resolve delivery questions. A sent status means the email provider accepted the message, not proof it reached your inbox. Order emails do not subscribe you to marketing, and they do not contain tracking pixels.

For new checkouts, we record the terms version presented and your affirmative acceptance time. These records support transaction history and dispute handling. We do not add device fingerprinting or record an IP address for this feature.

Guest orders

Guest checkout requires an email address for transaction messages, keys, and order access. It does not create a Discord login or merge with an existing account that uses the same email. An internal guest record links the purchase to its delivery records. Secure emailed links expire after seven days and create a seven-day, order-specific browser session when opened. Anyone with access to the link or that session may view the order, so keep them private. You can request a new link using the order reference and email. Linking an order to a signed-in account requires proof of access and an explicit confirmation.

Optional visitor analytics

With your permission, we measure views of public pages, sessions, and estimated distinct browsers. We store random browser and session identifiers locally, and keyed hashes of those identifiers with page paths, referral hostnames, a broad screen-size category, and timestamps on our server. We do not send those events to an advertising provider or store raw IP addresses, emails, account identifiers, URL query strings, or fragments in these analytics records. Account, admin, checkout, cart, and guest-order pages are not measured.

Declining does not affect purchases. Analytics stays off when a supported browser signals Do Not Track or Global Privacy Control. You can change your choice using Analytics preferences in the footer; declining clears local measurement identifiers. Individual events are retained for up to 90 days plus scheduled-cleanup time. An opted-in browser identifier expires after 90 days and a session renews after 30 minutes of inactivity. Basic security rate limits use short-lived keyed hashes of network addresses; those records are separate from visitor reports.

Retention and requests

Records may be retained for operational, security, accounting, dispute, and legal purposes. For questions or requests concerning your account data, contact WithUsually through the official support community or published support channel.

Changes

This policy may be updated as features, vendors, or legal requirements change. The date above identifies the current version.