Skip to content

ToneCustoms — Privacy & Data Handling ​

Status: Draft disclosure — owner confirmed no separate customer database, licensing-data store, or website analytics service outside Tebex and Discord (October 2026). Other platform and support practices remain subject to verification.

This document identifies the disclosures needed before publishing a definitive ToneCustoms privacy policy. It does not claim that a specific collection, storage, transfer, or deletion practice is already in place.

Confirmed current setup ​

ToneCustoms has confirmed that it does not independently collect or store customer information in a separate database, licensing system, or website analytics service outside its use of Tebex and Discord. This statement describes ToneCustoms' own setup; it does not mean Tebex, Discord, GitHub Pages, or other infrastructure providers collect no data under their own policies.

Practices to verify ​

AreaQuestions to document
Store / checkoutWhich business/payment details are processed by Tebex and which details ToneCustoms receives?
Discord / botsWhat user IDs, messages, role information, logs or interaction events are collected?
LicensingIs any license or server identifier retained? If so, for what purpose and duration?
SupportAre tickets, screenshots, logs, email addresses, or attachments stored? For how long?
AnalyticsAre site, store or script usage events collected?
Data sharingWhich service providers process information and under which terms?
Rights and contactHow can customers request information, correction, or deletion when applicable?
SecurityWho can access records, what safeguards apply, and how are incidents handled?
RetentionDefine periods or objective retention criteria for each category of data

Owner verification checklist ​

Complete this review using the actual Tebex, Discord, documentation-hosting and support settings before approving a final public notice.

  • [ ] Identify which personal information ToneCustoms receives from Tebex, distinct from data processed only by Tebex
  • [ ] Confirm whether Discord bots or support tickets store user IDs, messages, attachments or moderation logs
  • [x] Owner reports no separate ToneCustoms licensing-data store or website analytics service; verify again if the infrastructure changes
  • [ ] Identify third-party processors and links to their published privacy notices
  • [ ] Record where support records are stored, who can access them and how long they are retained
  • [ ] Identify the correct private contact route for privacy inquiries
  • [ ] Check applicable legal and platform requirements before approval

Publication gate: Leave this page marked as a working outline until these items are checked. Do not substitute assumed retention periods or data-collection claims for actual settings.

Customer safety in the meantime ​

Never publish passwords, API keys, webhook URLs, private license keys, payment information or personal server access details in public GitHub issues or Discussions.

For the checkout privacy notices and payment processing terms, refer to the actual provider's terms presented during purchase.

Before publishing a binding privacy notice, verify actual data flows and applicable privacy requirements.

Policy index

Built for Roleplay. Made with Purpose.