Privacy Policy

Honest about this droplet. No analytics vendor list. Updated 30 Aug 2026.

This policy describes what this instance of Porter stores. The operator (the person running the machine) can see the database because they host it. Data is not sold.

Where it lives

Porter keeps a local SQLite file on the operator’s DigitalOcean droplet. There is no separate cloud database and no third-party analytics product.

What Porter stores

• Guild IDs, channel IDs, and role IDs needed to run commands and settings
• Discord user IDs tied to those features (who opened a ticket, who was warned, who linked VRChat)
• Warns, staff notes, and moderation cases (reason text, who issued them)
• XP / rank data if leveling is turned on
• VRChat usernames and display names if a member links an account (never a VRChat password)
• Optional AI persona / prompt text if staff configure AI chat
• A dashboard login cookie named porter after password or Discord OAuth sign-in (session only; not sold)

Depending on what staff enable, SQLite may also hold ticket records, application answers, shop config, reaction-role panels, and similar server settings. Message content is processed in memory for filters, automod, logs, and optional AI when those tools are on. Transcripts and log posts go back into Discord channels you choose.

What we don’t do

We don’t sell this data. We don’t run Google Analytics or a hidden tracker list. We don’t ask members for Discord or VRChat passwords. The operator dashboard shows first-party counts of public page views (home, terms, privacy). Visitor IPs are hashed and not stored in the clear.

Asking to delete

Ask the server’s staff, or the operator of this instance. Staff can clear warns and notes. Kicking the bot stops most new collection; it does not automatically wipe the SQLite file.