Skip to content
Add to Discord

Privacy Policy

Effective date: September 15, 2026
Last updated: September 15, 2026

This Privacy Policy explains how Raplaz Technologies LLC ("Raplaz Technologies," "we," "us," or "our") collects, uses, and shares information when you use LogDog (the "Service"): the LogDog Discord application, the LogDog web dashboard at app.logdog.gg, and the related websites at logdog.gg and docs.logdog.gg.

This policy is our notice of how we handle information. It works alongside our [Terms of Service](/terms), which govern the agreement between us and the people who install and operate LogDog.

1. A note on the data LogDog handles

LogDog's core function is to read a VRChat group's audit log (activity the group already records about its own members) and deliver it into a Discord server chosen by that group's administrators. Much of the information LogDog processes is therefore about your VRChat group's members, not about the person who installed the bot.

LogDog can also act in the connected VRChat group on an administrator's behalf (for example, banning or unbanning a member, responding to join requests, posting announcements, or assigning VRChat group roles) when a moderator chooses to use those features from Discord or the dashboard. These actions are directed by your moderators; LogDog carries them out through the VRChat account you authorize.

If you operate a server that uses LogDog, you are responsible for handling the information LogDog delivers to you lawfully and fairly within your community (see Section 8).

2. Information we process

Discord information

  • Discord server (guild) IDs, channel IDs, and role IDs you configure.
  • The Discord user ID and username of administrators or moderators who configure the bot or take actions through it (for example, who added or last edited a moderation reason), used for attribution and auditing.
  • Basic Discord profile information (user ID, username, display name, and avatar) for members who have linked their VRChat account, members tracked by role sync, and any member of a server LogDog is in whose Discord username, display name, or avatar changes while the bot is online. This is the same information Discord already shows to anyone who shares a server with them. We cache it so logs, the dashboard, and moderation views can show a readable name and avatar instead of a raw numeric ID. Cached entries are not removed when a person leaves a server.
  • If you enable announcements sync, the messages posted in the specific Discord channel or channels you choose for it, including later edits and deletions, so they can be mirrored as posts in your VRChat group. A permitted moderator can also post any single message to VRChat through the "Post announcement" right-click menu, in which case LogDog reads that one message. The title and text of each mirrored announcement are stored while the server's configuration exists. LogDog does not read messages in any other channel or in any other way.

VRChat information (from the connected group)

  • VRChat user IDs and display names of members involved in logged events (joins, leaves, bans, kicks, role changes, instance activity, posts, and similar), and the group's ban list (VRChat user IDs, names, and ban dates) so moderation views and screening can show prior history.
  • Group, instance, and world identifiers and related metadata associated with those events, and instance occupancy as aggregate player counts over time (LogDog does not record who was in an instance).
  • Event timestamps and audit log identifiers.
  • Group calendar events (title, description, times, and world) when you enable scheduled-event sync, so they can be mirrored as Discord scheduled events, and group posts when you enable announcements sync.
  • A cache of resolved VRChat user display names, and a shared world and group catalog (names, descriptions, images, and, for worlds, the VRChat ID and display name of the world's author) so embeds, lookups, and world picks can show names and images instead of raw IDs. The catalog is built from VRChat's public listings and is shared across the Service.
  • Cached VRChat public profiles of the people who appear in your group's audit log or join requests, and of anyone a moderator looks up with `/getvrcuser`. Profiles of people who join or apply to a monitored group are fetched before the event is delivered. A cached profile may include the display name, bio and bio links, pronouns, status, join date, last login and platform, trust tags and badges, avatar thumbnail, and the age-verification status VRChat reports. This is drawn from VRChat's own public profile data and may include people who have never used LogDog: it is fetched so that logs, join requests, and screening are readable and informed, and it is refreshed periodically while it stays in use.

Request screening (optional)

  • If a server enables request screening, LogDog evaluates each join request against rules the server's administrators configure (for example account age, VRChat trust rank, the age-verification status VRChat reports, keywords in the applicant's bio, and prior bans or denials recorded in that group's own history) and can automatically approve, deny, or flag the request. The rules, including whether anything is denied automatically, are chosen by the server; the outcome and the reasons are shown to its moderators, and moderators can override any automated result by hand. LogDog processes members aged 13 and over as VRChat and Discord allow, and a server may choose to screen on the age-verification status VRChat reports.

Configuration and operational information

  • Your LogDog settings: channel routing, enabled/disabled events and categories, notification (/notify) role mappings, feature-permission (/permissions) role grants, screening rules, reason presets, and similar.
  • Free-text moderation reasons that an administrator or moderator chooses to attach to a logged event, stored together with the Discord user who wrote or last edited each one. This text is authored by your moderators and may describe a member or their conduct.
  • A short-lived delivery queue of pending events (with a snapshot of how each should be formatted and routed) so events can be delivered reliably.
  • A short-lived action queue for the moderation and role actions a moderator triggers from Discord or the dashboard (bans/unbans, join-request responses, role changes), so LogDog can carry them out in the VRChat group reliably.
  • If a server enables role sync, the mappings between a Discord role and a VRChat group role, and a record of which VRChat group roles LogDog has applied to which linked member, so roles stay in step and are removed when a member leaves or unlinks.
  • World picks, playlists, and world suggestions a server's members and staff create, together with the Discord user ID of whoever submitted, added, or resolved each one.
  • An activity record of actions taken through LogDog (who changed a setting, who took a moderation action, and when), viewable by the server's administrators.
  • Diagnostic and operational logs used to run, secure, and troubleshoot the Service. These can include Discord and VRChat user IDs alongside the event being logged, and are kept on monitoring systems we operate.
  • Exports: server administrators can download their group's audit log, ban list, and activity records as CSV files from the dashboard or bot. What they do with an exported file is their responsibility (see Section 8).

Account-linking information (optional)

  • If a server enables account linking and a member chooses to link, we store the connection between that member's Discord account and their VRChat account (their Discord user ID and VRChat user ID) and the age-verification status VRChat reports for that account (for example, whether VRChat lists it as 18+ age-verified). This is used to grant the Discord roles the server has configured. We reflect the status VRChat provides. LogDog does not itself verify anyone's age or collect dates of birth.
  • During linking, we briefly process a one-time code the member places in their VRChat bio so we can confirm they own the account.
  • A member's link is to LogDog rather than to a single server: where a server is configured to trust cross-server links, an existing link can grant that member their configured roles in other participating servers without re-linking, which means that server learns the member's VRChat identity and age-verification status (see Section 5).
  • Each VRChat account can be linked to one Discord account. If the same VRChat account is later verified from a different Discord account with a fresh bio code, the link moves to that account and the previous Discord account loses the roles the link granted; we notify the previous account by direct message.
  • Linking is optional and member-initiated, and a member can remove this information at any time with the `/unlink` command, which removes the link and the roles it granted across every server.

Web dashboard information

  • You sign in to the dashboard with Discord. Discord shares your user ID, username, display name, and avatar, and the list of servers you belong to with your permissions in them, so we can show you only the servers you administer. We store your user ID and username, the Discord access tokens needed to refresh that server list (encrypted at rest), and the times you signed in and were last active.
  • For security, each sign-in and each session records a salted hash of your IP address and browser user agent, never the raw values, so we can detect unusual activity and let you see and end your sessions. Our network provider (Cloudflare) sees your IP address in the ordinary course of delivering the site, as any web host would.
  • The dashboard shows VRChat avatars and world images through an image proxy that caches them for about a day.
  • The dashboard uses only the cookies it needs to work: a session cookie (which expires after 30 days, or after 7 days without activity) and a short-lived cookie that protects the sign-in flow. Your browser also keeps a few preferences locally (theme, time zone, pinned servers). We do not use analytics, advertising, or tracking cookies on the dashboard or on our websites.

Premium information

  • If you have premium access, we process the entitlement data needed to apply premium (for example, which users have an active, qualifying subscription, pledge, or grant, and the source of that entitlement). Payments are handled by Discord (App Subscriptions) or Patreon. We do not receive or store your payment-card details.

Messages we send you

  • LogDog may send you a direct message on Discord when something concerns you directly: a welcome note when you add the bot, a confirmation when you link your VRChat account (including the age status VRChat reported and the roles granted), a security notice if your link is moved to another Discord account, a thank-you when you subscribe to premium, and an update when a world you suggested is approved. These are one-off notices, not marketing, and you can close your DMs to stop receiving them.

We do not sell your information, and we do not use it for advertising.

What LogDog does not collect. Apart from the announcement channels you explicitly choose for announcements sync, LogDog does not read the messages, direct messages, or voice activity in your Discord server. Its access to VRChat is limited to the connected group's audit log, calendar, posts, and ban list, the public profile and reference lookups needed to make that activity readable, and the moderation, posting, and role actions an administrator directs it to perform. We do not use third-party analytics or advertising services.

3. How we use information

We use the information above to:

  • operate and provide the Service: read audit-log activity and deliver it to the channels you choose, and show it in the dashboard;
  • apply your configuration (routing, event toggles, notifications, screening rules, reason attribution, access delegation);
  • where a server enables it, link a member's Discord and VRChat accounts at the member's choice and grant the configured roles based on that link and the age-verification status VRChat reports;
  • carry out the moderation, posting, and role actions an administrator directs: banning or unbanning members, responding to join requests (including automatically, under screening rules the server sets), mirroring announcements and scheduled events, and synchronizing VRChat group roles for linked members;
  • resolve and cache names, profiles, and world data so logs and lookups are readable;
  • provide and reconcile premium entitlements;
  • maintain reliability, security, and integrity (rate-limit handling, error recovery, abuse prevention, and sign-in protection for the dashboard); and
  • communicate with you about the Service and respond to support requests.

4. Legal bases (where applicable, e.g. GDPR/UK GDPR)

Where data-protection law requires a legal basis, we rely on:

  • Legitimate interests: to operate, secure, and improve the Service;
  • Contract: to provide the Service and premium features you request; and
  • Consent / legal obligation: where applicable.

In more detail: contract covers the dashboard, premium, and carrying out the actions an operator directs; consent covers account linking, which a member starts and can withdraw with /unlink; legitimate interests cover the name and profile caches that make delivered activity readable, the world catalog, security logging, and abuse prevention. Automated screening decisions and the delivery of a group's audit log are made under rules chosen by the server operator, who acts as the controller for them (see Section 8), and screening results can always be reviewed and reversed by that server's moderators.

5. How information is shared

We share information only as needed to run the Service:

  • Discord: we deliver event messages into the Discord servers and channels you configure, and we sign you in to the dashboard through Discord; your use is also governed by Discord's own privacy policy.
  • VRChat: we read audit-log and related data from VRChat, and carry out the actions you direct, through an account you authorize; VRChat's own terms and privacy policy apply to that data on their platform.
  • Other Discord servers that use LogDog: an account link belongs to the member, not to one server. If a member joins another server that has enabled account linking and cross-server trust, that server learns the member's linked VRChat identity and the age-verification status VRChat reports when the member chooses to link there, without a new bio code. A server that has not enabled cross-server trust learns nothing until the member verifies again.
  • Discord and Patreon: for premium, entitlement information is processed in connection with Discord App Subscriptions and/or Patreon; their own policies govern payment data.
  • Service providers: we use Cloudflare and Oxylabs to help operate and deliver the Service. They process information only as needed to provide their services to us, under their own terms and privacy policies.
  • Hosting and backups: the Service runs on infrastructure operated by Raplaz Technologies, and backups are stored on private, access-controlled storage we operate. We do not use analytics, advertising, or data-broker services.
  • Legal reasons: if required by law, or to protect the rights, safety, or property of Raplaz Technologies, our users, or others.

We do not otherwise sell, rent, or trade your information.

6. Data retention

We keep information for as long as needed to provide the Service:

  • Configuration is retained while LogDog is installed and active in your server. If you remove the bot, delete your configuration, or revoke audit-log access, the associated configuration is removed or scheduled for removal after a short grace period (currently around 24 hours), subject to routine backups.
  • Queued events and actions: the short-lived delivery and action queues are cleared once each item is delivered or carried out.
  • Event history: the audit-log activity LogDog pulls (event details and the VRChat IDs and names involved) is retained as a durable record while the connected group is monitored; this record also serves as the cursor that prevents the same event being relayed twice. It is removed or scheduled for removal when monitoring stops, after the same short grace period and subject to routine backups.
  • Activity records of actions taken through LogDog (who changed a setting, who took a moderation action, and when) are kept as a durable record and are not deleted when a server removes LogDog, so a server that returns still has its history and a removal itself is recorded. They snapshot the Discord username of the person who acted.
  • Account-link information (the Discord and VRChat connection and the VRChat-reported age-verification status) is retained while the link is active and is removed when the member runs `/unlink`, or the link is otherwise deleted, subject to routine backups. Finished linking attempts (the one-time code and its result) are deleted after 7 days.
  • Cached profile and reference data: resolved display names, cached VRChat profiles, and the basic Discord profile information described above are retained to keep logs, lookups, and the dashboard readable, and are refreshed over time rather than deleted on a fixed schedule. This is a display cache: removing it does not remove any event history, and we delete an individual's cached profile on request (see Your rights).
  • Role-sync data (Discord and VRChat role mappings and the record of roles LogDog has applied) is retained while role sync is configured; the applied-role record for a member is removed when they unlink or leave, completed role changes are cleared after 14 days, and the rest is removed when monitoring stops, subject to routine backups.
  • Dashboard sessions end after 30 days, or 7 days of inactivity, or when you sign out, and are cleared shortly afterwards. Sign-in history (hashed, as described above) is kept for 90 days.
  • Instance occupancy samples are kept for 90 days; world suggestions are kept for 90 days after they are resolved.
  • World and group catalog (names, descriptions, images, and world authorship) is shared across the Service rather than tied to any one server. We retain it indefinitely and do not delete it when a server stops using LogDog; a world author can ask us to remove their identity from it (see Your rights).
  • Backups are encrypted and retained for up to 30 days for disaster recovery, so deleted information may persist in a backup for a short time after deletion from the live system.
  • Diagnostic logs are retained for up to one year.

Note that messages LogDog has already delivered into your Discord channels live in your Discord server and are controlled by you and by Discord, not by us. Delete them there if needed.

7. Security

We take reasonable technical and organizational measures to protect the information we process, including access controls, encryption of dashboard credentials at rest, encrypted backups on infrastructure we operate, and rate limiting and sign-in protection for the dashboard. No system is perfectly secure, however, and we cannot guarantee absolute security. If we become aware of a breach affecting your personal information, we will notify affected users and server operators, and any regulators or platforms where the law or our platform agreements require, without undue delay.

8. Your responsibilities as a server operator

Who is responsible for what. For the audit-log activity LogDog delivers to your server, and for the screening rules and moderation actions you configure, you act as the data controller and Raplaz Technologies acts on your instructions as a processor. Raplaz Technologies is the controller for the parts of the Service it runs on its own account: dashboard accounts, LogDog-wide account links, the Discord and VRChat profile caches, the world catalog, premium entitlements, the messages we send, and security logging.

If you install or administer LogDog for a community, you are responsible for:

  • having a lawful basis and authority to connect your VRChat group and Discord server;
  • informing your members, where required, that group activity is relayed to Discord and that join requests may be screened automatically under rules you set;
  • deciding whether any join request is denied automatically, and providing a way for a person to ask for human review where the law requires one;
  • taking care with bio-keyword screening, which can match words about health, sexuality, religion, politics, or other sensitive topics that may be specially protected where you operate; and
  • handling delivered information appropriately, including honoring member requests where the law requires.

We act as a processor/relay for that delivery and provide tools (configuration commands, the dashboard, removal, and access revocation) to help you control it.

9. Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict processing of your personal information, or to object to certain processing. To make a request, contact us at [email protected]. We aim to respond within 30 days. We can delete the data we hold about you on our own account: a cached profile, an account link, a dashboard account and its sign-in history, world suggestions you submitted, and your identity as a world author in the catalog. Event history, moderation reasons, and activity records are the connected server's own records: requests about those we pass to the relevant server operator and act on together with them, and we do not rewrite those records on our own unless we conclude the law requires it. A linked member can also remove their own account link at any time with `/unlink`, and can end their dashboard sessions from the dashboard. If you are in the EU, UK, or another place with a data-protection authority, you also have the right to lodge a complaint with that authority. Because much of the data LogDog handles also originates from Discord, VRChat, or Patreon, some requests may be best directed to those platforms, and we may need to verify your identity before acting.

10. Children's privacy

The Service is not directed to children under 13, and you must meet the minimum age required to use Discord and VRChat in your jurisdiction. We do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us and we will take appropriate steps to remove it.

11. International users

We operate from the United States, and information we process is stored and processed there, on infrastructure we run, and passes through our service providers' networks. United States law may differ from the data-protection law where you live. If you operate a server for members in the EU, UK, or another jurisdiction with transfer rules, you are responsible for deciding whether relaying your group's activity to a US-based service is appropriate for your community.

12. Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and may provide additional notice. Your continued use of the Service after changes take effect constitutes acceptance of the revised policy.

13. Contact

Questions or requests about this Privacy Policy? Contact us at [email protected] or through our support server at [discord.gg/Egaz4SPZ4k](https://discord.gg/Egaz4SPZ4k).

Raplaz Technologies LLC