Information used for membership
The portal should collect only the information needed to operate membership, billing support, account status, optional account-access provisioning, audit logs, security, abuse prevention, and support requests.
Only collect what the membership portal needs.
The portal supports membership, billing, account status, help, and optional access workflows for supporters, including international users. It should collect only the information needed to operate membership, support, optional account access, payment references, safety, audit, and recovery workflows.
Payment data
Stripe handles payment method entry, card details, invoices, and billing portal actions. This portal stores billing references, trial status, and trial dates needed for membership operations; it must not store card numbers.
Network trial-abuse prevention
To limit free trials to one per supporter and network, the server derives the request IP address and immediately converts it into a keyed, pseudonymous fingerprint. The portal stores the fingerprint, associated account, and trial timestamps, but does not store the raw IP address in membership records or send it to Stripe metadata. A fingerprint remains personal data and is retained while needed for trial enforcement, security, disputes, and legal obligations. People sharing a household, workplace, carrier, proxy, or VPN network may share one trial and can still begin the paid membership without a trial.
Household profile information
Household profiles store an owner link, nickname, adult or child type, Jellyfin username and internal provider link, safety preset, optional viewing schedule, policy status, and timestamps. The portal does not require or store a child email address, birth date, profile password, or a separate profile IP address. Passwords are sent to Jellyfin only for the requested password change.
Support and safety
Supporters should not send passwords, API keys, payment-card numbers, setup tokens, private links, or unrelated personal information through support requests. Support and audit records should contain only fields needed to resolve membership, billing, safety, abuse-prevention, or operational issues.
International and request handling
Privacy, correction, export, deletion, support, and security requests should go through the Help page. Backup, audit, billing-reference, abuse-prevention, security, operational recovery, and legal exceptions may limit how quickly records can be changed or deleted.
Related policies: Terms, refunds and cancellation, and acceptable use.