Version 2026-09-11
Privacy notice
Operator and contact
Sugar is an independently operated project, not a limited company. Its operator is [TO COMPLETE BEFORE PUBLISHING: operator’s full legal name], using the name Sugar.
Contact: [TO COMPLETE BEFORE PUBLISHING: public contact email]
Correspondence address: [TO COMPLETE BEFORE PUBLISHING: address for legal correspondence]
Country: [TO COMPLETE BEFORE PUBLISHING: operator’s country]
Who is responsible
The operator controls personal data used to run Sugar’s accounts, security, support and host revenue records. Hosting providers and Discord are responsible for their own systems. Where Sugar processes data solely on a host’s instructions, the parties must document that processing separately.
Information Sugar uses
Sugar receives Discord user and server identifiers, usernames and profile images for admin sign-in; connected hosting service identifiers and names; customer email and order details supplied by hosts; licence and subscription status; billing event identifiers, dates, amounts and currencies; host contact details; and support communications. Security and audit records can include the acting Discord user, action, server, result, timestamps and technical request information.
Information comes from you, your Discord interactions, Discord sign-in, and your connected provider’s billing and server systems. Sugar’s hosting checkout happens with the provider; Sugar does not need your card details. Claim tokens and provider credentials are used to authorise connections. Do not put passwords or payment details in support messages.
Purposes and lawful bases
Account linking and requested server actions are used to provide the service under the applicable agreement. Security checks, fraud prevention, troubleshooting and operational logs support the operator’s legitimate interests in keeping the service secure and reliable, balanced against users’ rights. Provider payment records are used to administer provider agreements and meet applicable accounting and legal obligations. Support information is used to answer the request. Where consent is the basis for an optional use, it must be requested separately and can be withdrawn.
Sharing and service providers
Sugar sends requested commands and necessary service identifiers to your host and sends responses through Discord. Authorised operators can access records needed for support, security and billing. Information may also be disclosed when legally required or to establish or defend legal claims. Sugar does not sell personal information or use it for advertising.
[TO COMPLETE BEFORE PUBLISHING: actual infrastructure and email providers, purposes and storage countries]
International transfers
[TO COMPLETE BEFORE PUBLISHING: transfer destinations and applicable safeguards, or confirmation that no restricted transfers occur]
Retention
[TO COMPLETE BEFORE PUBLISHING: actual retention periods or deletion criteria for accounts, events, audit logs, support, billing, tokens and backups]
Removing Sugar from Discord does not automatically erase provider billing records or cancel hosting. Ask the operator about deleting Sugar information; records required for legal obligations or unresolved disputes may need to be retained.
Your choices and rights
Depending on applicable law, you can request access, correction, deletion, restriction or portability of your information, and object to processing based on legitimate interests. You can withdraw consent where processing relies on it. Contact the operator using the details above; identity checks may be needed to protect your information. You can complain to your local data protection regulator. In the UK this is the Information Commissioner’s Office.
Automated checks
Sugar automatically checks permissions and licence status before allowing commands. Ask the operator or your host to review an incorrect access decision. Sugar does not use your data for advertising profiles.
Cookies and browser storage
See the cookie notice for sign-in and setup storage. This notice is version 2026-09-11.