Controller and contact
See Legal Notice for the commercial status and available operator information. See Contact for privacy-channel availability.
The privacy contact channel is not yet available. No operational or monitored mailbox is currently confirmed.
Data processed
Accounts: user ID, name, email, bcrypt password hash, account timestamps, referral codes and referral relationships. Password reset records contain a token hash, expiry and usage timestamps.
Downloads: submitted URLs, job identifiers, user ID/email/name/role, transfer status, file name and size, progress, speed, timestamps, provider identifiers, provider errors and temporary direct links. Duplicate-request records associate an identity and request key with a job. For Usenet requests, the API also processes uploaded NZB file contents, name and size, and any source password supplied for processing; these are passed to the transfer provider where needed.
Billing: access plan, status and expiry; pending checkout provider, token and timestamps; credit transactions, descriptions and metadata; referral rewards. The schema also contains optional Stripe customer, subscription and price identifiers.
Technical information: the password-reset endpoint reads a forwarded IP address and keeps an IP/email cooldown key in process memory. Authentication, billing and error logs can include email addresses, identifiers and provider responses. Password-reset diagnostics exclude reset links and raw tokens; explicit local development may return a link to the requesting developer.
Purposes and legal bases
These records support authentication, account management, password recovery, processing and tracking downloads, duplicate-request protection, access entitlement, credits and referrals, troubleshooting and abuse prevention. Required account and URL fields are needed to provide the corresponding functions. The purpose-specific legal bases remain under review and require operator confirmation.
Providers and payments
TorBox is integrated for transfer processing when enabled; source URLs and transfer information are sent to that provider. Source hosts and download providers may receive connection information when a file is retrieved.
Stripe is the current payment provider for new credit purchases through LIVE Checkout. Whop is retained solely for legacy transaction history and reconciliation; it is not used for new purchases. Card entry uses external payment services; the application does not store full card numbers or security codes.
Internal payment orders and provider event identifiers record checkout and reconciliation status. Stripe receives the checkout correlation identifier and payment information through its hosted checkout.
Resend is used for password-reset emails when configured, receiving the recipient email and reset message. Google Fonts is loaded externally and receives browser connection information. See Legal Notice for confirmed hosting information. Provider locations and international-transfer arrangements remain under review.
Cookies and browser storage
NextAuth uses authentication/session and security cookies. Local storage keeps hidden-download preferences and Prompt Builder form inputs in the browser. No dedicated analytics integration was identified in the inspected source; this does not establish what hosting or external checkout services use.
Deployed cookie lifetimes and external-provider tracking have not yet been fully verified.
Retention
The download cleanup code targets done/expired jobs whose last update is older than JOB_RETENTION_DAYS (default: 7 days), during service activity. Cleanup can fail or be disabled; it is not a guaranteed deletion deadline. Aggregate job counts and volume are archived separately.
Idempotency records are cleaned during reads/writes after a configurable TTL (default: 10 minutes). Reset tokens expire after one hour; expiry does not itself delete the database record. Existing reset tokens are deleted on a new reset request.
Retention and deletion criteria for accounts, billing, referrals, logs, reports and backups have not yet been finalised. The code defaults above do not establish retention periods for those records.
Security
The code hashes passwords with bcrypt, hashes reset tokens, uses session checks for protected account operations and verifies Stripe and legacy Whop webhook signatures. These measures do not guarantee absolute security.
Your rights
Depending on the processing and applicable law, you may request access, correction, erasure, restriction, portability or object to processing, and withdraw consent where processing relies on it. See Contact for the current availability of the privacy channel. When available, provide enough information to identify your account; proportionate identity verification may be requested. You may lodge a complaint with the CNIL or your competent supervisory authority.
Policy changes
Changes will be reflected in the last-updated date. Material changes will be communicated where required.