Privacy policy

digr is operated as a private web application. The operator of the instance you sign into controls the server and database where your data is stored. Questions about your data should go to whoever runs that instance (for the public site, use the contact details they provide).

When you register, we collect a username, email address, and password. Passwords are stored using a one-way hash, not in plain text. We use your username and email to authenticate you, show your identity in the app (for example chat), and support account recovery or admin actions on this instance.

While signed in, digr saves data needed to provide search and listening features, including:

• Search filters, saved searches, and session restore state
• Releases you mark seen, hidden, or played; favorites and bookmarks
• Player queue, playback-related preferences, and chat messages
• Optional profile preferences (for example filter UI settings)

This data is stored in the application database (for example SQLite locally or Turso when configured) and is tied to your account on this instance.

digr uses an HTTP-only session cookie to keep you signed in. Session cookies are required for the app to work. We do not use third-party advertising cookies.

digr talks to external services to fetch catalog metadata and media information, including Discogs, Bandcamp, YouTube, and Apple Music where those features are enabled. Search terms and release identifiers needed for those requests are sent to those providers under their own policies.

Hosting and infrastructure may include Vercel (application hosting), Turso or similar (database), Cloudflare Turnstile (bot protection on registration when enabled), and Vercel Analytics (aggregate usage metrics). Those providers process data as described in their privacy policies.

Shared search or play links may be fetched by social apps (for example WhatsApp or Facebook) to build previews. Those services receive the public URL and any Open Graph metadata we publish for that link; they do not receive your password or session cookie.

Data is kept for as long as your account exists on this instance unless the operator deletes it. You can change your password and email in account settings. To delete your account, contact the operator of this deployment.

For Meta (Facebook) data deletion requests and status codes, see Data deletion.

We may update this policy from time to time. The "Last updated" date at the top will change when we do. Continued use of digr after changes means you accept the revised policy.