Privacy Policy
Germany-first launch draftGDPR/TDDDG review, the processor list and international-transfer map remain required before launch. Version: privacy-v1-2026-08-22.
1. Controller
Controller: [LEGAL_OWNER_NAME], [LEGAL_OWNER_ADDRESS], [LEGAL_OWNER_EMAIL]. Data-protection contact: [PRIVACY_EMAIL]. If a data-protection officer is appointed, the contact will be published here.
2. Data we process
Depending on your use, Fedilo processes account and authentication data, chosen creators and sources, Personal Feed and Playlist configuration, consent records, provider connection state, support messages, subscription and invoice status, referral attribution, creator payout status and limited technical logs.
3. Why we process data and legal bases
Account creation, Feed delivery, provider connections, subscription management and requested product functions are processed to perform the contract or take steps you request. Security, fraud prevention, abuse detection and narrowly scoped operational logging may rely on legitimate interests. Consent is used where required.
4. Chosen creators and provider media
Before normal app use, you make a separate External Media decision. If allowed, provider-hosted previews and players remain click-to-load. The product must not silently load provider players while ordinary content is viewed. Local disclosure can include technical metadata such as IP address, device and browser information shared with the provider after Play.
5. External Media consent record
The first-run decision records its version and provider/purpose coverage. You can change it in Privacy settings. A materially expanded coverage set requires another explicit decision. This permission never grants entitlement, follows a creator or connects an account.
6. Connected accounts
If you authorize a provider account, the provider sends only the authorized data and tokens required for approved scopes. Tokens are encrypted, excluded from ordinary exports and deleted or revoked when no longer required, subject to provider behavior and legal retention duties.
7. Payments and creator payouts
Payment-card data and, where applicable, creator bank or identity-verification data are handled by the selected payment/payout provider, such as Stripe. Fedilo generally receives identifiers, subscription state, invoice/payment state, connected-account state and capability/KYC status rather than full payment or identity documents.
8. Recipients and processors
Data may be disclosed to hosting, database, email, observability, support, payment, fraud-prevention and provider-integration vendors only as needed. A current processor/subprocessor list must be published before Production launch.
9. International transfers
Some providers or processors may process data outside the EEA. Where required, transfers rely on an applicable adequacy decision or appropriate safeguards. [INTERNATIONAL_TRANSFER_MAP_REQUIRED].
10. Retention
Retention depends on operational need, account deletion, active subscriptions, billing and tax duties, security evidence and provider requests. Credentials and sensitive evidence receive stricter retention. The final production schedule remains subject to legal review.
11. Your rights
Subject to applicable law, you may request access, rectification, erasure, restriction, portability and information about processing, object where appropriate and withdraw consent at any time. See data export & deletion.
12. Automated decisions
Fedilo does not use a recommendation engine to decide what enters your chronological Feed. Automated safety, integrity or fraud controls may operate only within documented safeguards and do not replace legally required human review.
13. Security
Risk-based controls include encryption in transit, credential protection, least-privilege permissions, logging, incident response, MFA and recent re-authentication for sensitive actions.
14. Contact
Privacy requests: [PRIVACY_EMAIL]. Identity verification may be required before sensitive requests are fulfilled. Referral attribution is described in Cookies & referrals.