nosyncdj Don't just hear music. Drift into the groove
Home Support Privacy Login Create Account
nosyncdj

Privacy Policy

Effective date: June 1, 2026. This policy explains what NoSyncDJ stores on your device, what the app sends to the NoSyncDJ backend, what the backend stores, and what is processed and discarded.

Data Stored On Your Device

  • Your local library data is stored in a device-local SQLite database (records, songs, BPM/key annotations, videos, playlist, and linked release identifiers).
  • Optional cover photos are stored locally as image files and picture blobs linked to records.
  • Authentication session token, backend device ID, and optional backend server override are stored in device secure storage.
  • Audio settings (engine choice, sample duration, microphone preference) are stored locally.
  • Camera and microphone access is used only for in-app scan/listen features you trigger.
  • Crash reports created by the app are written to local files and are not automatically uploaded by the app.

Data Sent To NoSyncDJ Backend

  • Account requests: email, password, and a per-install device ID (for sign-in/sign-up and device-session limits).
  • Authorized API calls: bearer token in the Authorization header.
  • Catalog features: search terms, identifiers/barcodes, release IDs, label-scan tokens extracted on-device, and mapped CSV import rows you choose to submit.
  • Metadata re-sync: local record identifiers and/or artist-title search terms used to request updated release metadata.
  • Server BPM mode: a short recorded audio clip (audio/mp4) and requested sample duration for analysis.

What The Backend Keeps

  • Account record (email and password hash) and account status fields (for example, login-disabled state and last password-change timestamp).
  • Device-session records (device ID, session ID, created/authenticated/revoked timestamps, active state).
  • API error logs used for troubleshooting (request path/method, status code, user identity when authenticated, error message/stack trace, and context values captured for failed requests).
  • As with any HTTP service, network metadata (such as IP address and user agent) is processed in transit; this backend application code does not store those fields in its API error-log records.
  • There is no automatic retention purge in current backend code; these records remain until manually removed by the operator.

Processed Then Discarded

  • Track-audio uploads for server BPM analysis are processed to produce BPM/key results and are not persisted by backend application code as user library data.
  • Catalog search requests, release lookups, and CSV import matching inputs are used to compute responses and are not written as a dedicated user library dataset on the backend.
  • Camera frames for barcode/label scan are processed on-device; recognized terms are only sent when you run backend search.

Third-Party Services

  • No third-party analytics or advertising SDKs are used by the app.
  • When you open a video URL, your device connects to the selected provider (for example YouTube). Their privacy policies apply to that connection.

Account Deletion And Contact

  • In-app "Delete account" permanently deletes the backend account record, account status records, device session records, and related backend log entries tied to that account.
  • For data requests, contact: jorgeleo@gmail.com.