Skip to main content

Privacy and data protection

Data PlexSub can handle​

PlexSub can store operational data, user identities, integration credentials, notification settings, and Customer Portal data. Depending on active modules, it may also show subscription status, media history or usage, content requests, downloads, support incidents, and payment references.

Do not do this​

  • Do not publish .env.
  • Do not share tokens.
  • Do not upload backups to public sites.
  • Do not paste complete logs containing credentials.
  • Do not use real data in public demos.
  • Do not grant admin access to people who only need the Customer Portal.

Credential protection​

Service credentials configured through Admin Settings are encrypted in the database. The important key is APP_SETTINGS_ENCRYPTION_KEY.

Keep that key outside Git and outside the database. Compromise of both the database and the key increases risk.

Administrator responsibilities​

Use HTTPS, keep secrets outside Git, secure backups, limit permissions, update images when appropriate, validate integrations before enabling them, and avoid real credentials in demos.

Customer privacy​

PlexSub centralises access status, requests, usage, available history, support, and account preferences. This can reduce manual sharing of messages and screenshots, but only when permissions, visibility, and providers are configured properly.

Payment data​

PlexSub can reflect payment or subscription references and statuses. The payment provider remains the legal and accounting source of truth. Store only necessary data, never paste private transaction IDs into public docs, and check provider status before cancelling or revoking access.

Demos and fake data​

A public demo must use fake data, simulated services, reset capability, no private targets, and separate demo credentials. Do not connect it to real Plex, Jellyfin, payment, or email services without a controlled, documented reason.

Privacy checklist​

  • .env is outside Git.
  • Secrets are strong.
  • FORCE_SECURE_COOKIES=1 for HTTPS deployments.
  • APP_BASE_URL is correct.
  • Backups are encrypted or protected.
  • Admin access is limited.
  • Logs are reviewed before sharing.
  • Demo and production are separate.