Privacy Policy¶

Draft: not yet reviewed by an attorney

This page is a starting-point draft, written to plainly and accurately describe what data Frogge actually collects and how it's actually handled, based on the real system as of the date below. It has not been reviewed by a licensed attorney or a privacy professional, and should not be treated as a compliance program (GDPR, CCPA, or otherwise) until it has been. Have it reviewed, confirm what data-subject-rights process you can actually support, and update the effective date before relying on this page or linking it anywhere official.

Effective date: (set once reviewed and adopted)

This Privacy Policy explains what information Frogge (the Discord bot, the web Dashboard, the FroggePlugin in-game companion, and their supporting background services) collects, how it's used, and who it's shared with.

Information we collect¶

From Discord, when you use the bot or sign into the Dashboard:

Your Discord user ID, username, and avatar.
The Discord server (guild) IDs you're a member of, and (only for the Dashboard's sign-in, to determine which servers you can manage) which of those you hold Manage Server permission on, via Discord's identify and guilds OAuth scopes.
Server data relevant to the features you use: roles, channels, and members, as needed for whichever module you're using (e.g. Events needs to know who signed up for a shift).

Content you or your venue provide directly:

RP character profile content (names, descriptions, images, and other fields you fill in).
Event, shift, staffing, VIP, verification, form-response, custom-embed, and Server Log configuration data: whatever a given module is designed to store, as described on each Features page.
Financial records you choose to log in the Finance module (amounts, categories, notes). This is a record-keeping tool for your own venue's books, not a connection to any real payment method.
Images you upload (character images, card art, embed images), stored via our cloud storage provider.
If you use Verification, the FFXIV character name and world you enter, and whether Lodestone ownership proof was completed.
If you use Stream Alerts, the Twitch usernames a venue admin chooses to track (this is a public username lookup; you don't connect a Twitch account).
If you link FFXIVVenues, your venue's public listing data.

Collected automatically:

Basic operational logs (e.g. errors, request activity) for debugging and keeping the Service running, retained by our infrastructure providers for a limited time.
IP addresses may be incidentally logged by our hosting providers as part of normal web/network operation; we don't use this for tracking or profiling.

We don't ask for or store your Discord password, payment card details, or your FFXIV/Square Enix account credentials at any point.

How we use this information¶

To operate the features you and your venue use: this is the primary purpose of nearly everything collected above.
To enforce these settings and permissions correctly (e.g. checking a role before granting VIP access).
To detect and prevent abuse of the Service.
To maintain and improve the Service, including debugging issues.

We don't sell your personal data, and we don't use it for third-party advertising.

Discord. By design, using a Discord bot means Discord itself handles the underlying message and interaction delivery; anything Frogge posts or reads in a channel is subject to Discord's own systems and terms.
Twitch. Stream Alerts checks Twitch's public API for whether a tracked username is live. Frogge doesn't have access to your (or a tracked streamer's) Twitch account.
FFXIVVenues. If you link a venue, Frogge reads that listing's public data. Nothing is ever written back.
The Lodestone (Square Enix). Verification looks up the publicly viewable Lodestone page for the character name/world a member enters. This is a public-data lookup, not an account connection.
Infrastructure providers. Data is stored and processed using Google Cloud Platform (database, image storage, logging) and, for the Dashboard, Vercel. These providers process data on our behalf and don't use it for their own purposes.

We don't otherwise share personal data with third parties, except where required by law.

Data retention¶

Data is retained for as long as your venue actively uses Frogge. As of this writing, removing the bot from a server does not automatically delete that server's stored data. If you'd like a venue's data deleted, contact us (below) and we'll process that request.

Your choices and rights¶

Several modules give you direct control over your own data without needing to contact us: deleting your own RP character(s) via /profile, revoking your own verification isn't currently self-service (an admin can revoke it), and admins can remove records through each module's own Remove actions.

For anything else (access, correction, or deletion of data we hold about you), contact us at the address below and we'll do our best to accommodate the request. We haven't yet formalized a region-specific rights process (e.g. GDPR/CCPA data subject request handling); if you're in a jurisdiction that requires one, say so when you contact us.

Children's privacy¶

Frogge is not directed at children and follows Discord's own minimum age requirement. We don't knowingly collect information from anyone below that age; if you believe we have, contact us and we'll remove it.

Security¶

We take reasonable measures to protect the data described above, but no online service can guarantee complete security. Report a suspected security issue to the address below.

International users¶

Frogge's infrastructure is hosted on Google Cloud Platform, primarily in the United States. If you're accessing the Service from elsewhere, your information will be processed in the United States.

Changes to this policy¶

We may update this policy as the Service evolves. Material changes will be reflected by an updated effective date on this page.

Contact¶

Questions about this policy, or a data request: support@frogge.tech.