Privacy Policy

Last updated: September 28, 2026 · draft for review

This document describes Weeps' data practices during the closed beta. It is a technical draft — not legal advice — and will be reviewed before launch.

Points pending formal legal review: the default-on telemetry consent model during the beta; how third-party storages chosen by the user are described; retention periods and the subprocessor list.

1. Controller and contact

Weeps is developed and operated by the project's maintainer ("we"). For any personal-data request — access, correction, deletion or portability — write to contact@weeps.app.

2. What we collect

Weeps is local-first: your library, files and metadata stay on your device by default. Cloud features are optional and require an invited account. When you use cloud features, our backend (Google Firebase) stores only:

• Account — email, display name and linked sign-in providers (Google, email/password);
• Subscription — plan state (active, grace, etc.), product type, source (test/redeem code) and registered devices;
• Workspace binding — the identifier of the workspace linked to your subscription;
• Storage registry — label and portable locator of each attached storage (e.g. a Google Drive folder id or a network path), never file contents;
• Sync metadata — a journal of track-metadata and user-state changes (rating, plays, tags) needed to sync between devices. We never upload audio or cover art;
• Feedback you send — type, title, description, app/OS version and optional diagnostics, when you use the in-app feedback submission;
• Cost state — technical counters for the platform's cost guard-rail.

3. Metrics and error reports

Three independent consents, editable in Preferences → Privacy. During the closed beta, usage, error and performance metrics are collected by default; you can turn them off in Preferences → Privacy. If you opt out, you stay opted out — your choice is never reverted.

• Usage analytics (Google Analytics 4 + our own telemetry) — first-run style events (first track played, onboarding, etc.) and feature-usage events (which screens/features you open and how long you spend in each — e.g. radio, podcasts, editor, stems, Remote Play), with platform and app version. They never include track names, artists, stations, filenames or library contents;
• Error reporting (Sentry) — crashes and errors with sanitized file paths;
• Performance metrics — workspace-open and library-render timings, aggregated daily, at most one report per day. They never include filenames, library contents or listening history. Withdrawing consent deletes pending local data.

4. Retention

• Sync journals: 90 days (automatic TTL);
• Account, subscription, binding, storage registry, feedback and feature-usage events: while the account exists (deleting the account removes all of it);
• Invites/redeem codes: until redeemed or revoked.

5. Deletion

You can delete your account in Preferences → Account. Deletion removes your sign-in, subscription, workspace binding, storage registry and cloud sync data. Local libraries and files are never touched — they stay on your device and in the storages you chose.

6. Providers and subprocessors

• Google Firebase (Auth, Firestore, Cloud Functions, Hosting) — account and sync backend, in the project's configured region;
• Google Analytics 4 — on by default during the closed beta, can be disabled (see item 3);
• Sentry — on by default during the closed beta, can be disabled;
• Storage providers you choose (e.g. Google Drive) — the app only accesses what you attach; that data is governed by the provider's own terms.

7. Cookies and local storage

The site uses only technical cookies and GA4 (when enabled). The app keeps preferences and tokens in the operating system's secure storage.

8. Changes

Material changes will be announced on this page before taking effect.