Privacy Policy
Last updated: 2026-07-18 · Product: RetroGarden (retrogarden.net)
1. Scope
This policy covers the RetroGarden portal (accounts, billing metadata, instance control) at portal.retrogarden.net. Each customer instance is a separate community application with its own users and content; instance operators are independent controllers for that community data.
2. Data we process (platform)
- Account: name, email, password hash, role (user/admin), creation time
- Instances: slug, site name/tagline, status, hostname, optional billing IDs
- Operational: provision logs, container logs surfaced in the portal (short retention), server metrics needed to run the host
- Billing (when enabled): Stripe customer/subscription identifiers and payment status metadata needed to gate provisioning — full card numbers stay with Stripe; we do not store PAN/CVC
- Technical: IP address and user-agent may appear in short-lived access/application logs used for security and abuse rate limiting
3. Why we process it
To provide the service (authenticate you, provision and control instances), secure the platform, bill for plans, and comply with legal obligations. Legal bases typically include contract performance and legitimate interests in operating a multi-tenant host.
4. Sharing
We do not sell personal data. Processors may include infrastructure (VPS), DNS/CDN (e.g. Cloudflare), email/SMTP providers, and Stripe for payments when enabled. Instance community content is not used for advertising.
5. Retention
- Account and instance metadata: while the account/instance exists, plus short admin retention after delete
- Container / application logs: rolling window, target about 7 days
- Backups (when enabled): according to the ops backup schedule
6. Security
Passwords are stored hashed. Portal sessions use HTTP-only cookies; HTTPS is required in production. Instances share host infrastructure with isolation via separate containers and databases — not a dedicated single-tenant machine unless agreed.
7. Your choices
You may update profile-related instance settings in the dashboard, stop or delete instances you own, and request account closure by contacting the operator. Instance end-users should contact their garden’s administrators for community-data requests.
8. Content responsibility
Platform policy: instance admins own community content; see Terms §4 for default content / abuse rules.
9. Contact
Privacy questions: operator inbox for retrogarden.net
(e.g. [email protected]).