Privacy Policy
Last updated: November 9, 2026
LoggerBot, managed by Baki operates LoggerBot. This notice explains what information may be handled when you use our Discord bots, website, dashboard or paid features, why it is used, which service providers may receive it, and what choices or rights may be available to you.
Key points
- The server administrator chooses which events the bot logs; the information in a log depends on those settings and Discord permissions.
- We use account and service data to provide LoggerBot, operate subscriptions, respond to requests, and protect the service from abuse.
- Log Viewer summaries are retained for 1 hour on Free, 12 hours on Pro Lite, and 30 days on Pro. The full Pro message cache can remain for up to 28 days.
- Discord, Stripe, AWS, GitHub and vpnapi.io receive information where needed for the features they provide. We do not sell personal information or use message contents for advertising.
- You can send a privacy request through LoggerBot Support. Some information may need to remain for security, accounting or legal reasons.
1. Who this notice covers
This notice applies to people who visit the LoggerBot website, sign in to the dashboard, install or administer a LoggerBot bot, appear in activity that a server chooses to log, or contact us about the service.
LoggerBot processes information to run the features that a user or server administrator requests. Server administrators decide which logging functions to enable and how the resulting Discord channels are accessed. They should provide any notices required by law or Discord rules to people in their server.
2. Information we handle
- Discord account and server details: user, server, channel, role and message IDs, usernames, avatars, membership or permission information, and server settings needed to operate enabled bot features.
- Event and log information: depending on the server configuration, Discord permissions and selected loggers, the bot may process event types, message text, attachment links, edits or deletions, moderation actions and reasons, voice events, timestamps, and the people involved.
- Information you send us: support conversations, feedback, reports, and information you choose to provide when asking for help or exercising a privacy right. Feedback posted on the website is shown publicly with your Discord name and avatar.
- Dashboard sign-in and use: Discord OAuth identifiers and tokens, profile details, the servers your account may manage, and settings or actions needed to provide the dashboard.
- Subscription and license details: plan, license and server associations, subscription status and dates, Stripe customer or subscription references, and the Discord account related to a purchase. Stripe handles card payments; our checkout integration does not provide LoggerBot with your full card number.
- Website and installation measurements: a random first-party visitor ID, pages viewed, visit times, referral source, browser and device category, and an approximate location derived from the connection IP using a local GeoIP database. Adding the bot through the website may also record the source, the click or install event, the visitor ID and the server ID Discord returns. Raw IP addresses are not stored with visit records.
- Security signals: connection IPs are checked against IP bans. When you sign in, open the dashboard or start a checkout, the connection IP is also sent to vpnapi.io to check for VPN, proxy, Tor or hosting-provider connections; public pages are not checked. On the dashboard, browser and device signals are combined into a SHA-256 fingerprint that is only compared with the ban list and is not stored. A ban record may include an IP address, Discord account ID or fingerprint.
3. Where information comes from
- From Discord, when an installed bot receives events or when you use Discord OAuth to sign in or choose a server.
- From you or your server administrator, through bot settings, dashboard actions, subscription choices, feedback, support conversations and reports.
- From your browser or device, through site visits, cookies, local storage and security checks.
- From payment or infrastructure providers, as needed to confirm and manage a purchase or deliver a feature.
- From top.gg, when someone votes for LoggerBot or publishes a review there. A vote gives us the voter’s Discord user ID. A public review, with the name and avatar shown on top.gg, may also appear on our feedback page.
4. How we use information
- To receive configured Discord events and provide logging, moderation, Log Viewer, dashboard, account, license, gift, vote-reward and support features.
- To authenticate dashboard sessions, check which servers an account can manage, and link purchases with the right account and license.
- To answer support and privacy requests, investigate service problems, and communicate about relevant account or service matters.
- To measure website visits and install sources, maintain reliability, detect abuse, apply security restrictions, and protect the service and its users.
- To process billing information through the relevant provider, comply with legal duties, and address payment disputes or legal claims.
5. Legal grounds
Where data protection law requires a legal basis, the relevant basis depends on the activity. It may be necessary to provide a feature you or a server administrator requested, to meet a legal obligation, or to pursue legitimate interests in operating, maintaining and protecting LoggerBot. Where consent is the required basis, we will request it for that activity. A server administrator remains responsible for ensuring that the server’s use of logging is lawful and appropriately explained to its members.
6. When information is shared
We do not sell personal information or use Discord message content to serve advertising. We share or make information available only as needed to provide LoggerBot, protect the service, or meet legal requirements.
- Discord provides the platform, bot APIs and OAuth sign-in, and receives content or events delivered to Discord channels.
- Stripe processes the checkout, subscription, payment, invoice and billing-portal information required for paid plans.
- Amazon Web Services hosts production infrastructure. vpnapi.io receives the connection IP when its VPN, proxy, Tor or hosting check is used.
- GitHub stores our private backups of service settings, support tickets and support transcripts.
- Authorized LoggerBot administrators may access service, support, analytics and security records when needed to operate and protect the service.
- We may disclose information if required by law or where reasonably needed to address abuse, protect someone’s safety, or establish, exercise or defend legal claims.
7. Cookies, local storage and sign-in
Cookies needed for Discord login and account security support dashboard sessions. The site also uses a first-party visitor-ID cookie for analytics for up to 12 months, a traffic-source cookie for up to 30 days, and a short-lived VPN-check cookie for up to 6 hours. On the beta site, a cookie that identifies the beta build lasts for the browser session.
Language, theme and dismissed-interface preferences may be kept in your browser’s local storage. Clearing cookies or local storage may sign you out or reset preferences. Restricting cookies may stop sign-in or other parts of the site from working.
Dashboard authentication uses Discord OAuth. When you sign in, the site may request Discord’s guilds.join permission, shown on Discord’s consent screen, to add your account to the LoggerBot Support server. This join attempt is separate from authentication; a failed attempt does not prevent dashboard sign-in.
8. Processing in other countries
Discord, Stripe, AWS and other providers may handle information in countries outside your country of residence. Where required, transfers rely on safeguards described by the relevant provider or otherwise required by applicable data protection law. Consult their privacy materials for details.
9. How long information is kept
Retention depends on the type of information and why it is needed. When information no longer serves an operational, safety, accounting or legal purpose, it is deleted or otherwise handled according to the applicable requirements.
- Log Viewer: searchable event summaries are automatically retained for 1 hour on Free, 12 hours on Pro Lite and 30 days on Pro. The summary is not a second copy of the complete Discord embed.
- Full Pro message cache: new message text and attachment links may be cached for up to 28 days to support later edit and deletion logs. The cache is removed when its period expires or the relevant Pro license ends.
- Live visitor list: temporary visitor details are removed after 90 seconds without activity.
- Ban records: IP addresses, Discord account IDs or fingerprints used for a ban remain until staff remove the ban.
- Other settings, moderation cases, message counts, support tickets, account and license records, feedback, analytics and install-attribution records: retained as needed for service operation, safety, accounting or legal purposes. Visit and install-attribution records currently have no fixed automatic expiry.
- Discord channel messages: messages delivered to Discord are stored and controlled by Discord and the server’s administrators, not LoggerBot. Removing the bot does not delete messages already sent there.
10. Security
We use access controls and technical and organizational safeguards intended to protect the information handled by LoggerBot. Access is limited to authorized people who need it to operate or support the service. No online service, transmission or storage method can be guaranteed completely secure.
11. Your privacy rights
Depending on the law that applies where you live, you may be entitled to request access to or correction or deletion of personal information, to restrict or object to certain processing, or to receive a copy of information you provided. You may also have a right to withdraw consent where processing relies on consent, and to complain to a data protection authority. In the Netherlands, that authority is the Autoriteit Persoonsgegevens.
Rights may be subject to legal limits and do not always require us to delete information that must be retained for security, accounting or legal reasons.
12. Requests about Discord server logs
If your information appears in logs because a Discord server uses LoggerBot, contact that server’s owner or administrators about the server’s logging settings and any message stored in its Discord channels. You can also contact LoggerBot Support about information held by LoggerBot itself. Removing the bot stops future events from being processed for that server, but does not erase Discord messages or records that must remain for security or legal reasons.
13. Children
LoggerBot is not designed to collect information directly from children. Server owners and administrators must follow Discord’s age rules and applicable law when deciding whether to enable logging and how to inform their members.
14. Changes to this notice
We may update this notice when LoggerBot’s features, data handling or legal requirements change. The date at the top of the page identifies the current version. If a change is significant, we will provide additional notice where appropriate.
15. Contact and privacy requests
For questions about this notice or to make a privacy request, contact LoggerBot, managed by Baki privately through LoggerBot Support. Include your Discord user ID and the relevant account or server so we can understand your request. Do not send passwords, OAuth tokens, card details or sensitive message content in a public channel. We may ask for information reasonably needed to verify the request.