Privacy Policy¶

Effective date: June 26, 2026
Last updated: June 26, 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"), a Discord application that relays VRChat group audit-log activity into Discord servers.

This policy works alongside our Terms of Service. By using the Service, you agree to the practices described here.

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, or assigning VRChat group roles — when a moderator chooses to use those features from Discord. 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¶

We collect and process only what is needed to provide the Service:

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.

VRChat information (from the connected group's audit log)

VRChat user IDs and display names of members involved in logged events (joins, leaves, bans, kicks, role changes, instance activity, posts, and similar).
Group, instance, and world identifiers and related metadata associated with those events.
Event timestamps and audit log identifiers.
A cache of resolved VRChat user display names and world and group data so embeds can show names and images instead of raw IDs.
Where a moderator uses /getvrcuser or a join request is enriched, a cached VRChat profile for the looked-up user — which may include their 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 profile data, stored cache-first with a refresh interval, and used to make logs and lookups readable.

Configuration and operational information

Your LogDog settings — channel routing, enabled/disabled events and categories, notification (/notify) role mappings, feature-permission (/permissions) role grants, 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 (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.
Diagnostic and operational logs used to run, secure, and troubleshoot the Service.

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.
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.

Premium information

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

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

What LogDog does not collect. 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, the profile and reference lookups needed to make that activity readable, and the moderation 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;
apply your configuration (routing, event toggles, notifications, 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 and role actions an administrator directs from Discord — banning or unbanning members, responding to join requests, 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
communicate with you about the Service and respond to support requests.

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.

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; your use is also governed by Discord's own privacy policy.
VRChat — we read audit-log and related data from VRChat through an account you authorize; VRChat's own terms and privacy policy apply to that data on their platform.
Patreon — for premium, entitlement information is processed in connection with Patreon; Patreon's own policies govern payment data.
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 rely on third-party cloud analytics, advertising, or data-broker services to run LogDog.
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 — the short-lived delivery queue of pending events is cleared once each event is delivered.
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.
Account-link information (the Discord↔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.
Cached profile and reference data — resolved display names and the fuller VRChat profile fetched for /getvrcuser and join-request enrichment — is retained to keep logs and lookups readable and is refreshed over time.
Role-sync data (Discord↔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, and the rest is removed when monitoring stops, subject to routine backups.
World and group reference data (world and group names, descriptions, and images) is non-personal catalog information 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.
Backups are retained for up to 30 days for disaster recovery and may persist for a short time after deletion from the live system.
Diagnostic logs are retained for a limited operational period.

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 and secured offsite backups on infrastructure we operate. 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 where the law requires — without undue delay.

8. Your responsibilities as a server operator¶

If you install or administer LogDog for a community, you may act as a data controller for the audit-log activity it delivers to your members. 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
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, 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]. Where the request concerns data we hold — such as cached display names, event history, moderation reasons, or an account link tied to a VRChat user — we can delete or restrict that data on request, and will do so coordinated with the relevant server operator where appropriate. A linked member can also remove their own account link at any time with /unlink. 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 may be stored and processed there or in other countries that may have different data-protection laws than your own. By using the Service, you understand that your information may be transferred to and processed in the United States.

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.

Raplaz Technologies LLC