Legal information

Imprint

Provider information under Section 5 of the German Digital Services Act (DDG), where applicable.

Service provider

Contact

Email: jannis-support@proton.me

Storm Studios Discord

Privacy notice

This notice explains how Anchor's website, Discord sign-in, dashboard, and bot handle personal data. Discord's own services are also governed by Discord's Privacy Policy.

Controller and contact

For the processing described in this notice, the contact is Jannis Dufft. You can reach the operator at the postal address and email in the Imprint.

Website requests

When you visit the site, the hosting provider may process technical request data needed to deliver and secure it, such as your IP address, the requested page, time of access, browser information, and response status. The hosting provider is FPS.ms. Its privacy policy describes its own processing and log practices.

Discord sign-in and dashboard

If you choose Discord sign-in, Anchor requests the Discord identify and guilds permissions. The dashboard uses your Discord user ID, username, avatar, server IDs and names, and the server permissions needed to show servers you can manage. Discord access and refresh tokens are kept in a server-side PHP session and are not sent to browser JavaScript. The session cookie is named anchor_dashboard, is marked Secure and HttpOnly, and is removed when you log out; the browser session cookie ends when the browser session ends.

Optional Discord command permissions

Editing command permissions in the dashboard requires a separate Discord authorization with the applications.commands.permissions.update scope. This lets Anchor read and update command access rules for roles, members and channels in servers you are authorized to manage. Anchor processes the relevant Discord user, server, command, role, member and channel IDs, permission rules and an audit record of the change. This scope is not needed for ordinary sign-in. The additional authorization does not bypass Discord permissions or Anchor’s moderation checks. You can revoke the authorization in Discord’s Authorized Apps settings; doing so does not automatically undo rules you previously saved.

Paddle checkout and Pro access

Real purchases are not currently available. The following also describes the existing sandbox integration, where no real money is charged. If you open a Paddle checkout, Paddle processes the contact, billing and payment information you enter, together with technical checkout data, under its own privacy notice. For purchases processed through Paddle, Paddle acts as the merchant of record. Anchor links the transaction to your Discord user ID and the selected server IDs using an internal checkout reference. Anchor stores Paddle customer, transaction and subscription IDs, the price identifier, quantity, subscription status, billing/access dates and whether an introductory offer has been used. These records activate and manage Pro access and help investigate payment problems. Anchor does not receive or store your full payment-card number or card security code.

Checkout references and subscription records are used to provide the requested service and administer payments under Article 6(1)(b) GDPR where applicable. Fraud prevention and payment troubleshooting may rely on Article 6(1)(f); legally required retention may rely on Article 6(1)(c). The current configuration has no fixed automatic deletion period for Pro account records. Duplicate-event identifiers used by the billing integration expire after approximately 30 days. You may request access or deletion through the operator; records still needed for applicable legal obligations or unresolved claims may need to be retained. Paddle applies its own retention rules and may use its own checkout cookies or similar technology; see its privacy notice.

Bot and server data

Application forms store the applicant’s Discord and server IDs, the selected form and question snapshots, answers, submission and review dates, reviewer IDs, decision reasons, configured role actions and delivery status. Drafts expire after 24 hours. Pending applications remain until reviewed or withdrawn; closed applications expire after 90 days. Responses are accessible to the applicant and authorized reviewers or server administrators. Review summaries are posted only in the configured private Discord channel; decisions may be sent by direct message. The server’s team makes acceptance decisions. Anchor does not automatically evaluate answers. Do not request or submit passwords, tokens, health data or other sensitive personal information. Authorized staff may download answers as CSV; they are responsible for access and retention of those exports. Member-data export and deletion include applications; open applications and unfinished role changes must first be resolved. Discord messages are separate copies and are not automatically erased with the database record.

Staff modules store server and member IDs, shift start and end times, breaks, time corrections and their reasons, and leave requests with dates, optional reasons, decisions and review history. These records support voluntary Discord community staff workflows. Leave reasons are visible to the applicant and authorized management; public absence lists omit reasons. Do not submit health information or other sensitive personal details. Records remain until removed through the server’s member-data deletion workflow or a request to the operator. Active shifts or leave requests must be resolved first. Discord log messages and direct messages are separate copies controlled by their recipients.

Enabled modules may also process member XP, levels and role rewards, welcome settings, join and leave events, and ticket feedback. Daily activity totals are retained for 90 days without message content. If server administrators enable ticket transcripts, Anchor reads messages in the relevant ticket channel and sends an archive containing message content and attachment links to the configured Discord channel. Administrators control access to that archive and its retention. Online transcripts are stored for up to 90 days. After Discord sign-in, the ticket creator and authorized ticket staff can view them; access is checked on every request.

To provide the bot and dashboard features, Anchor processes server identifiers and settings, channel metadata, moderation records, and ticket metadata. Moderation records can include the affected member's ID, moderator's ID, action type, reason, duration, status, and creation time. Ticket metadata can include ticket, member, and channel IDs, status, priority, and claim time. The dashboard API does not request a server's full message history. Discord hosts messages in Discord channels and applies its own privacy terms. Server administrators choose whether to install Anchor and remain responsible for their moderation decisions and for giving their members any notices they need.

Purposes and legal bases

These data are used to authenticate dashboard users, display servers they may manage, apply requested settings, provide bot features, protect the service, and investigate abuse or technical failures. Processing needed to provide a requested service is based on Article 6(1)(b) GDPR where applicable; security and abuse prevention may rely on Article 6(1)(f) GDPR and the operator's legitimate interests.

Service providers and international processing

Anchor uses FPS.ms for web and bot hosting, MongoDB Atlas for the bot database, and Discord for account sign-in and Discord features. The MongoDB Atlas data region is selected in the database configuration. Depending on the provider and its configuration, data may be processed outside the European Economic Area. Provider terms and safeguards apply to those services.

Cookies and browser storage

The dashboard uses one session cookie to maintain sign-in. The website does not use analytics or advertising cookies. Your theme and language preferences are saved in your browser's local storage and are not used for analytics. No external font service is loaded.

Retention

Discord sign-in tokens remain in the server-side session until logout, token expiry, or session cleanup by the hosting configuration. Bot settings, moderation records, and ticket metadata are stored in the bot's MongoDB Atlas database while needed to operate Anchor. The current setup does not define a fixed automatic deletion period for those records. You can contact the operator to request access or deletion; applicable legal obligations and the rights of other people may affect a request.

Your rights

Depending on the circumstances, you may request access, correction, deletion, restriction, or portability of your data, and object to processing based on legitimate interests. You may also complain to a data-protection supervisory authority. To exercise a right, contact the operator at jannis-support@proton.me.

Provider privacy information

These links lead to privacy information published by the services used by Anchor:

• Discord Privacy Policy
• FPS.ms Privacy Policy
• MongoDB Privacy Information
• MongoDB Data Processing Agreement
• Paddle Privacy Notice

Terms of use

These terms apply to the Anchor website, dashboard, and Discord bot. The operator is Jannis Dufft; contact details are in the Imprint.

Using Anchor

You may use Anchor only if you are allowed to use Discord under Discord's terms and the laws that apply to you. By adding Anchor to a server or using the dashboard, you agree to these terms. Discord's own terms and policies also apply to your Discord account and servers.

Server permissions and responsibility

Only install or configure Anchor for a server you own or are authorized to manage. You are responsible for the permissions you grant, your server rules, the settings you choose, and reviewing actions taken by your moderators. Anchor is a tool and does not replace human moderation or your responsibilities toward server members.

Acceptable use

Do not use Anchor to break the law, violate Discord's rules, access accounts or servers without permission, interfere with the service, bypass security controls, or harm other users. Do not submit data you are not authorized to share.

Features and availability

Anchor is under development. Features may change, be unavailable, or be removed as the bot is completed. The operator does not promise uninterrupted availability or a particular feature set. Nothing in these terms excludes liability where the law does not allow it to be excluded.

Anchor Pro and payments

Anchor provides a free plan and optional Anchor Pro access for additional features and higher limits. Pro is assigned to the Discord server or servers selected for the subscription, not automatically to every server on your account. You must be authorized to manage each selected server. Functions, limits, planned prices and purchase availability are shown on the public Anchor Pro page. Real purchases remain disabled until the payment setup and provider approval are complete; sandbox purchases do not charge real money.

Billing and renewal

When paid subscriptions become available, the monthly plan is billed per selected server and renews monthly until cancelled. The checkout must show the recurring price, any applicable taxes, billing frequency and any introductory price or multi-server discount before you agree to pay. If an introductory offer has an end date, its duration and the subsequent recurring price must be shown before purchase. The confirmed checkout and purchase receipt identify the terms of that order. Complimentary Pro grants do not create a paid subscription or authorize future charges.

Cancellation and refunds

For subscriptions processed through Paddle, you can cancel future renewals through the Paddle customer portal linked in your receipt, or request cancellation at paddle.net. Cancellation takes effect at the end of the current paid billing period; paid access normally remains until then. Cancellation does not by itself refund earlier payments. Refund requests and any statutory withdrawal rights are explained in the Refund Policy. Mandatory consumer rights remain unaffected.

When Pro access ends

After paid or complimentary Pro access expires, the server returns to Free limits. A notice and a 7-day adjustment period give the server’s administrators time to reduce excess configuration. Remaining excess entries are then archived. This adjustment period does not extend paid Pro benefits. Existing tickets, moderation cases and submitted applications are retained.

Anchor Pro · Refund Policy · Paddle Buyer Terms · Paddle support / cancellation

Suspending or ending access

You can stop using the dashboard by logging out and stop using the bot by removing it from your server. The operator may restrict access when reasonably needed to protect the service, respond to misuse, or comply with law. Where practical, the operator will explain a restriction through the website or the contact email.

Intellectual property and Discord

Anchor's original website and service materials remain with their respective rights holders. You receive permission to use Anchor for its intended purpose while these terms apply. Anchor is an independent service and is not endorsed by or affiliated with Discord Inc.

Liability and applicable law

Mandatory statutory liability remains unaffected. German law applies where legally permitted; mandatory consumer-protection rules that apply in your country of residence continue to apply. These terms do not limit rights you cannot waive under applicable law.

Changes and contact

The operator may update these terms when the service or legal requirements change. Material changes will be identified on this page with a new update date. Questions can be sent to jannis-support@proton.me.