Stripe handles secure billing, and Owner/admin review still controls optional access eligibility. These terms define membership, billing, access, and safety boundaries; they do not guarantee any specific application or uptime level.
Monthly membership contributes to hosting, storage, maintenance, support, documentation, backups, monitoring, and community operations. It does not purchase, rent, license, or reserve any specific application, feature, capacity level, uptime level, or permanent access right.
Eligible trialing supporters can set up one primary private server-access account while the perk is available. After the first successful monthly payment, the household owner may create up to four additional separate Jellyfin users. All household users share a two-simultaneous-stream capacity limit. Membership does not buy separate application guarantees, expanded capacity, operational priority, or uptime. Access can be limited, paused, disabled, or revoked when billing lapses, abuse is detected, legal or privacy risk appears, capacity changes, operations require it, or an administrator places the membership under review.
Eligible first-time supporters receive one 7-day free trial per verified supporter identity and network, then membership costs $9 per month. A shared network may already have used its trial; in that case the supporter can begin paid membership immediately. A card is required in Stripe Checkout and will be charged automatically when the trial ends unless the supporter cancels first. Returning supporters with prior subscription history are charged $9 when they restart and do not receive another trial. Stripe Checkout and the Stripe Billing Portal handle payment methods, invoices, cancellation, and billing management; local portal state follows Stripe events.
Refunds, disputes, and chargebacks are handled through Stripe records, payment-network rules, support review, and Owner policy. A billing issue can place optional access in admin review while records are reconciled.
The verified owner is responsible for household users, their credentials, child settings, and signing adult accounts out on shared devices. Credential sharing outside the household, automated scraping, misuse of access limits, or attempts to bypass controls may result in disabled access. Accounts are disabled rather than deleted where practical.
The portal should collect only the information needed to operate membership, billing support, security, provisioning, audit logs, and abuse prevention. Supporters should not send passwords, API keys, payment-card numbers, private tokens, or unrelated personal information through support requests.
Checkout uses the approved Stripe-hosted billing flow when available. The portal mirrors billing status for membership support and account decisions, while optional access remains eligibility-controlled.
Questions? Use the help page or return to supporter tiers.