Who operates this project
Resona is operated by dertomtec, a registered business in Germany. Contact: .
Website hosting
The website is hosted through Strato. When you visit the website, technical data can be processed by Strato and by Resona to deliver the page, protect the service and debug errors. This can include IP address, request time, requested URL, browser or user agent, referrer, error logs and similar server log data.
Cookies and local preferences
The site uses essential session cookies for sign-in and CSRF protection. Theme choice, cookie notice choice and campaign parameters can be stored in your browser. Resona does not currently use advertising or analytics trackers on this site. External YouTube videos load only after you choose to open them. See the Cookie Policy.
Fonts, profile pictures and images
Website fonts are served from Resona's own files. On the main website, Discord profile pictures are fetched by the Resona server and served through our website, so the image request from your browser stays on Resona. The ZAP control panel may load Discord avatars directly from Discord's CDN. An editor can also add an external image URL to a page or product; viewing that image may send your IP address and request details to its host. Editors should use the local media upload for images whenever possible.
GeoSun map
The GeoSun location database works without an external map. If you press “Load map”, your browser requests map tiles from OpenStreetMap. Clicking the map or choosing “Use my location” can send the selected coordinates to OpenStreetMap's Nominatim service to find the nearest place. Browser geolocation is requested only after you choose that button.
Contact form
The contact form collects the name, email address, subject and message entered by the sender. The website stores this information with a support-case reference and status, emails a confirmation to the sender and notifies info@resonastudio.net. Authorized team members can read the case, reply by email, and close or reopen it in the website dashboard. Contact messages are not sent to the Discord bot. Case records and mailbox messages are retained while they are needed to answer the request, document the conversation or prevent abuse.
Discord profiles created by the bot
When a user joins a Discord server where our bot is active, the bot can create or update an internal profile for that user. The profile uses public Discord information such as Discord ID, Discord username, display name and profile image/avatar URL. The Discord ID is used as the stable identifier.
This profile can remain stored after the join event and can stay active even if the visible Discord data changes. It is used for moderation, support, verification, product access, abuse prevention, server tools and administration.
Roblox verification
If you verify through our own Discord verification system, the Roblox account ID is collected and added to the existing profile. Depending on the verification flow, Roblox username or display name may also be stored as labels. Ownership and product access are based on numeric IDs, not on names that can be changed.
Product and security telemetry
Our Roblox products send technical data needed for licensing, security, update checks, compatibility and support. This does not provide blanket consent to unrelated uses.
The collected product data can include:
- product id, product name and product slug
- client version, current version and whether an update is required
- pricing type and whether a license is required
- game owner id, universe id, place id, place name and place version
- server type, for example Studio or Game
- private server id and private server owner id, if available
- player count and max players
- request id generated by our own system
Account, license and support data
Account pages, dashboards and product systems can store licenses, product access states, bans or blacklist entries, support notes, audit records, verification status, admin actions and timestamps. These records are used to operate the service and to protect the products and community.
Why the data is processed
Data is processed to provide requested account features, verification, product licensing and support, and to protect the service against abuse. Where consent is required, it must be a specific affirmative choice. Visiting, joining, receiving a message or using verification does not provide blanket consent. Optional publication of your name is disabled by default and can be withdrawn on the Account page.
Sharing and external services
Data is not sold. Data can be processed through the services needed to operate the project, including Strato for website hosting, ZAP-Hosting for bot and database infrastructure, Discord for Discord accounts and bots, and Roblox for Roblox identities and product use. We may disclose data if required to protect the service, enforce rules, investigate abuse or comply with a valid legal obligation. Our business privacy page lists infrastructure providers and how to request a DPA.
AI training
Resona does not use customer messages, account records or product data to train AI models without a separate, explicit permission for that purpose.
Retention
Profiles, verification links, product records, license records and security logs can remain stored while they are needed for operation, support, product access, moderation, abuse prevention or documentation. Some records can remain after leaving a Discord server or after stopping use of a product if they are needed for security, licensing or audit reasons.
Age eligibility and children
Self-service sign-in and Roblox linking require a declaration that you are at least 16. If you are younger, your parent or guardian must contact support before setup; support must check eligibility and any required parental authorization. Do not send identity documents through bot messages. We do not collect a date of birth. An age declaration alone does not verify age or parental authorization. Discord and Roblox also have their own age requirements.
Usage counts and public names
Successful licensed product starts are counted once per Roblox server session and product, linked to the license owner's Discord account. We store product ID, account ID, a hash of the server session ID and start time. This counts server sessions, not minutes, player activity or every button press. Failed checks, checks without a session ID and repeated checks in the same session are not counted. Product totals can be public. Your display name is published only after your separate choice in Account settings; names are private by default and can also be hidden by the owner. Deletion removes your usage history.
Service notices and reminders
You can disable Verify reminders and service notice DMs with one button in a DM or in Account settings. Policy notices can target the whole server or selected roles. Only pressing “Read and agree” records acceptance of the linked version, with a timestamp. Receipt does not count as agreement and does not enable unrelated optional processing.
Your requests
Signed-in users can download a JSON export or request permanent deletion on the Account page. The red Data deletion request button in the leave DM also queues deletion from both active databases. Leaving alone does not delete your account. The completion DM is sent only after both databases confirm deletion; outages are retried automatically. Deletion removes licenses, product access, Roblox links, support records and usage history. A keyed, one-way account marker remains to prevent automatic profile recreation and invalidate old website sessions. Hosting backups, mailboxes and messages held by Discord are separate from the active databases. Statutory rights are not waived by deletion. For access, corrections and help with other copies, contact .