Private by default. Verified by design.
Echofundia needs enough data to prove real participation and stop fraud — and no more. Microphone and location features are opt-in, Studio work stays on your device until you choose to share it, and personal data is never sold.
1. Data we collect
Account data: your email address, display name, chosen role and authentication records, handled through our auth provider (Supabase). We never see or store your password in plain text.
Profile and workspace data: artist profiles, applications, development plans, tracks and releases you create, campaigns and missions you run or join, evidence you submit, and your credit/reputation ledger.
Participation data: listening and mission activity needed to verify genuine participation and prevent abuse — for example qualified listening time on Echofundia channels, saves, follows and submission history.
Technical data: basic device, browser and diagnostic information used to keep the service secure and working, including client error events you can see referenced in our system health tooling.
2. Microphone, capture and location
EchoCapture and listen-now features use your microphone only when you explicitly enable them; auto-listen is off by default. Ambient recognition, when active, is used to identify music around you and record a discovery event — it is not used to record or store conversations.
Coarse location (an approximately 1 km grid) is optional, off by default, and only used if you enable it for local discovery features. Precise location is never collected.
Studio sessions are local-first: recordings, projects and exports created in the browser Studio stay on your device unless you choose to save, publish or share them to your account workspace.
3. How we use data
To run the platform: authenticate you, show your workspace, publish what you choose to publish, verify mission evidence, prevent fraud and duplicate rewards, operate the credit ledger, and — only inside a funded, active program — calculate Listen & Earn shares.
We do not sell personal data. We do not use your private demos, unpublished projects or mission evidence to train models or for advertising.
4. Processors and third-party content
We use Supabase for authentication, database and storage, and Vercel for hosting. Payment and payout features, when configured, use regulated providers (for example Flutterwave) under their own privacy terms.
Catalog, video and film pages display public references from third parties such as Apple Music, YouTube, Wikimedia Commons and MusicBrainz. Playing or opening those items is governed by the provider's own terms and privacy policy.
5. Your choices and rights
You can update your profile from your account, remove published content, and leave missions you joined. You may request a copy of your data, correction of inaccurate data, or deletion of your account and associated personal data, subject to records we must keep for fraud prevention, accounting or legal reasons (for example posted ledger entries, which are append-only by design).
To exercise a right or ask a privacy question, reach us through the routes on the About page. We respond within a reasonable period and may need to verify your identity first.
6. Retention and security
We keep account data while your account is active and delete or anonymise it afterwards, except the limited records described above. Access to private workspaces is role-gated on the server, private media is served through signed access, and reward or payout actions require verified server-side authority.
This policy may be updated; the current version and its date are always published on this page.
Questions about privacy: see About & contact.