Files
community-rule/docs/privacy-policy-facts.md
T
adilallo b4d0d085d3 Record the retention and hosting facts the privacy policy still has in brackets.
Login links work for 60 minutes, unused rows are gone within a day, logs last 14 days, and backups are 30 days on MEDLab Cloudron in the United States. Live /privacy stays on the current page until counsel reads this text.
2026-11-10 15:34:35 -07:00

3.0 KiB

Privacy policy facts

Numbers and hosting details the new privacy policy leaves in brackets. Live /privacy stays on the current page until university counsel has read this text. Do not switch the route on from this file.

How long things are kept

What Period Where it is built
Login and save-progress links Work for 60 minutes. Unused rows, and any draft they carry, are deleted once expired. A daily job runs the delete, so they are gone within 24 hours of expiry. MAGIC_LINK_TTL_MS, Cloudron scheduler prune-expired
Email-change links Same as login links: 60 minutes, then gone within 24 hours. EMAIL_CHANGE_TTL_MS
Unused invitation tokens The unused token is cleared once the invite expires. Gone within 24 hours of expiry. The invitation row stays so it can be sent again. Daily prune
Workshop inquiries that do not lead to a workshop 12 months, then deleted. WORKSHOP_INQUIRY_RETENTION_MS
Ask an organizer messages Not stored on CommunityRule. They are emailed to MEDLab. MEDLab deletes mailbox copies after 12 months. Mail only
Unused accounts Kept until the person deletes the account. There is no unused-account timer at launch. —
Server logs (app logs and Cloudron request logs) 14 days. Cloudron removes logs older than that. That is the shortest period the platform allows. Cloudron log viewer
Backups 30 days (30 daily on the Cloudron backup site). Cloudron also keeps a pre-update snapshot for up to three extra weeks. Operator setting, see the runbook
Reply to a data request 30 days Process, not an app timer

Invitation lifetime while it still works is a product decision, not set here. At launch the invite token uses the same 60-minute window as login.

Where it runs

Servers are in the United States. MEDLab operates them with Cloudron: the app, the PostgreSQL database, mail, and file storage on that host. Sign-in mail relays through Amazon SES.

Who reads workshop inquiries

Only the people who answer them: MEDLab staff with the workshop inbox and the operator page. Inquiries live in the WorkshopInquiry table until the 12-month delete.

Analytics

Umami, self-hosted beside the app, with no cookies and aggregate counts only. Name it in the policy. The counter itself ships with the counts-by-group work, not this pass.

Product copy the build already matches

  • Login sent. A login link works for 60 minutes. The sent state and the login email both say so.
  • Offline. Answers stay in this browser until the person reconnects. The offline notice already says that.

After counsel, and after launch

  • /privacy can show the new policy only after university counsel has read it, including the Colorado Open Records Act line, Terms, Cookies, the legal cards, and CC0 for cards and templates.
  • An email to every account holder before a change to who can read Rules is after launch. Nothing about who can read Rules changes at launch.