Port Verdane (demo city)  /  Official department hub
Port Verdane Police Department badge
PVPD
This is a demo of a fictional department. Every name and record is made up, other visitors see what you change, and everything resets every night.Try it: pick a demo user
Port Verdane Police Department

Privacy Policy

What this hub stores about you, who looks after it, and your choices.

Placeholder text. This page hasn't been finalized yet: 7 highlighted items still need filling in. It isn't legal advice.

This Privacy Policy explains what information Port Verdane Police Department (the "department") keeps in this hub at https://demo.leowebhub.com, and how it's handled.

Who is responsible for your data

  • Port Verdane Police Department controls the data. The department decides what goes into this hub, who can see it, how long it's kept, and when it's deleted. Questions about your information go to the department's Admins first.
  • Schlongburg Studios hosts and processes it on the department's behalf. Schlongburg Studios runs the software and the servers. It uses the data only to provide the hub to the department: to store it, back it up, keep it secure, and give support when the department's Admins switch support access on. Schlongburg Studios doesn't sell it, use it for advertising, or share it with other departments or customers.
  • EDIT BEFORE LAUNCH: Schlongburg Studios's legal name, business form, country and postal address
  • Contact: EDIT BEFORE LAUNCH: privacy contact email

Port Verdane Police Department is a roleplay organization in the Port Verdane (demo city) community. It is not a real government agency, and the hub isn't meant for real-world personal records.

What the hub stores

  • Your Discord account: your Discord user ID, username and display name, when you log in with Discord. The hub never sees your Discord password or email address. Its Discord access token is thrown away right after login.
  • Department records the department enters about you: your character name, callsign, rank, dates of hire and promotion, status, subdivisions, certifications, hours, training records, reports and cases, awards, and notes.
  • Applications: your answers when you apply, and messages about your application.
  • Things you add: documents, files, comments and requests you submit.
  • Activity logs: an audit log of changes (who changed what, and when) and refused access attempts, so the department can see what happened.
  • A login cookie: one cookie that keeps you logged in. It's needed for the hub to work, and it isn't used for tracking. The hub also remembers your light/dark theme choice in your own browser. There's no advertising, no analytics and no third-party tracking.
  • Server logs: the servers may briefly keep technical logs (such as IP addresses and error messages) to keep the service running and secure. EDIT BEFORE LAUNCH: confirm what the web server logs and for how long

Who else is involved

Schlongburg Studios uses these services to run the hub:

  • Server hosting: EDIT BEFORE LAUNCH: hosting provider name and server region(s), e.g. a US East or EU data center. This is where the hub and its data live.
  • Cloudflare R2: encrypted backups. They're encrypted before they leave the server, so Cloudflare can't read them.
  • Discord: login. Discord tells the hub who you are, and whether you're in the department's Discord server and have its roles.

How long data is kept

  • The department decides how long records stay in the hub, and can delete them.
  • Backups: encrypted copies are kept for 14 days on the server and 30 days in off-site storage, then deleted automatically.
  • If the department stops using the hub, Schlongburg Studios gives the department an export of its data. 30 days later it deletes the hub and every backup of it.

Your choices and rights

  • Ask the department's Admins to see, correct or delete information about you. The department decides, as the controller of the data. Schlongburg Studios helps the department with these requests when asked.
  • EDIT BEFORE LAUNCH: rights under the laws that apply to you and your users (for example GDPR for people in the EU/UK, or CCPA/CPRA for people in California), how to exercise them, and how to complain to a data protection authority

Security

Each department gets its own hub, with its own database, files and secrets, separated from every other customer. Connections use HTTPS. Access inside the hub is controlled by the department's own access levels. Off-site backups are encrypted.

Age

Discord requires its users to be at least 13 (or older where local law says so), and the hub uses Discord to log in. EDIT BEFORE LAUNCH: confirm the minimum age you require

Changes

If this policy changes, the new version is posted here with a new date.

Last updated: EDIT BEFORE LAUNCH: effective date, e.g. 1 January 2027