Dig Privacy Policy
Effective date: 25 September 2026
1. Who is responsible for your information
Dig is created and operated by Mark Isayan, acting personally, at Avan, Kuchak 47 Building, Apartment 14, Yerevan, Armenia ("Dig", "we", "us"). Mark Isayan is the data controller responsible for the personal information described in this policy.
For privacy questions, requests or app support, email contact@digrecords.fr. You can also visit Dig Support.
Dig has not appointed a representative in the European Union or United Kingdom. Please direct privacy requests to Mark Isayan using the contact details above.
This policy covers the Dig iPhone app, its supporting services, and the Dig app website. It does not cover a separate record shop's business or the independent services you visit through links in Dig.
2. Information we use and why
| Information | How it reaches us and what we use it for |
|---|---|
| Account information | Sign in with Apple supplies an account identifier and may supply a name and email address, including an Apple private relay address. We use these with our internal account ID to create and secure your account and synchronize your data. Apple does not give us your Apple password. |
| Your collecting profile and records | You enter or import your collecting preferences, collection, wants, maybes, stock, sold records, ratings, notes, condition, prices paid or sought, purchase locations and shelf organization. We store these to provide your collection, insights and personalized recommendations. |
| Plans and activity within Dig | Saved places, planned visits, visit history, records listened to or declined, recent identified songs, and notification state support your planning and collecting history. These are associated with your account and synchronized. |
| Location | When you choose to use your device location, iOS provides coordinates after asking permission. You can also select a city. We save the chosen location with your account and use it for nearby events, shops, distances and maps. Coordinates can be precise even though we request a balanced location accuracy. Dig does not continuously track your location in the background. |
| Searches and scans | Typed searches, barcodes, release identifiers and recognized artist/title information are used to find records in Discogs. A barcode lookup sends the decoded barcode, rather than a sleeve photograph. Cover identification sends the photo you take or select to our backend and Anthropic, as explained below. |
| Messages to Marvin | Your messages, conversation history, relevant collecting context and saved memories are used to answer your questions and personalize responses. See section 3. |
| Connected Discogs account | If you connect Discogs, we store authorization credentials and account identifiers to perform the imports, inventory, listing and order features you use. We do not receive your Discogs password. Public collection imports instead use the username you supply. |
| Subscription information | Apple and RevenueCat provide purchase, product, renewal and entitlement information so we can grant access, restore purchases and manage subscriptions. RevenueCat uses your Dig account ID. We do not receive your full payment-card details. |
| Product analytics | When analytics is enabled in our service configuration, PostHog receives an account ID, screen categories, action events, counts and categorical properties, timestamps and SDK device/session information. We use this to understand feature use, onboarding, retention and subscription conversion. |
| Support correspondence | Information you send when contacting us is used to answer your request and resolve problems. |
| Website waiting list | The email address and selected language you submit are sent to a Supabase service for the waiting list and the launch message you requested. This list is separate from app accounts. |
| Network and service information | Our hosting and service providers receive connection information, such as IP addresses, and may keep request/security logs to deliver, protect and troubleshoot their services. |
Providing account information is necessary to use the current app. You do not have to connect Discogs, use the microphone, upload a photo or enable device location. Refusing a device permission prevents the feature that needs it; typed record search and selecting a city provide alternatives. The current onboarding requires a display name, which may be a nickname; its other collecting questions can be skipped.
3. AI features and music recognition
Marvin and cover identification
Marvin uses Anthropic's Claude service through Dig's backend. When you send a message, we send the message, relevant conversation history, the current record or screen context, and a summary of your collecting profile. This summary can include your chosen name, musical tastes, collection counts, buying habits, purchase places, price ranges, wants and recent listening decisions. Marvin can also request relevant collection and wantlist details through its tools. Tool results and saved memories can be included in further requests to Anthropic. Marvin may use Anthropic's web search and Discogs to answer a question.
We store Marvin conversations and memories in your Dig account. Deleting a conversation does not by itself delete separately saved memories. Account deletion removes both from the active Dig account database.
Cover identification sends a resized image to Anthropic to read the artist, title and, when visible, year. The resulting text is then used to search Discogs. Dig's identification endpoint does not create a stored photo library, but the image is processed by our service providers and may remain in their systems under their applicable retention arrangements. Choose sleeve photos that do not include people or information you do not want to share.
What's playing
After you tap Listen and allow microphone access, ShazamKit processes short-lived audio on the iPhone and sends a musical fingerprint to Apple's Shazam service. Dig does not save the recording or fingerprint, or send either to Supabase or Anthropic. Listening stops when cancelled, when you leave the screen, or when the app goes into the background or is interrupted.
The identified song's artist, title and available album information are used to search Discogs for possible records. We save up to ten recent identifications, including song information, artwork/provider links, dates and any release you choose, and synchronize that history with your Dig account. Recognition does not identify a physical pressing and does not add music to your Apple Music or Shazam library. Clear recent history removes the visible entries and syncs that change; internal deletion markers can remain to prevent deleted data returning.
4. Services that receive information
| Service | Its role and information received |
|---|---|
| Apple | Sign-in, App Store subscriptions, Shazam recognition, maps/geocoding, and music searches/previews. Information depends on the feature, including authentication, transactions, fingerprints, location or music query data. |
| Supabase | Account authentication, cloud storage/sync and backend processing, including collecting data, saved locations, conversations and connected-service credentials. The website waiting list uses a separately configured Supabase project. |
| Anthropic | Marvin messages, context, tool results and cover images, as described in section 3. |
| RevenueCat | Account identifiers, subscription transactions/status and SDK technical information used for purchase validation and access management. |
| PostHog | The limited product analytics described above. When the RevenueCat integration is enabled, it also receives subscription lifecycle/revenue events joined to the same Dig account ID. |
| Discogs | Catalogue queries, barcodes, recognized music metadata, and connected-account requests such as imports, inventory, orders or listing actions. |
| Deezer and Apple music services | Artist, album and track searches and requests for preview audio/artwork. Direct requests also expose your connection information to those providers. |
| OpenStreetMap/Overpass services | Live shop searches can send the selected search area's coordinates and radius directly to an Overpass server. Bundled shop data can be searched locally. |
| Artwork and content hosts | Requests for catalogue artwork, documentary posters and editorial content, including Wikimedia/Wikipedia and other hosts specified by those services. These hosts receive normal network request information. |
| Expo | App update checks and downloads, with the technical information required to serve compatible updates. |
These providers may act on our instructions for some services and independently for others, such as your Apple or Discogs account. Opening a seller, event, streaming or other external link takes you to that provider's own service and privacy policy. We may also disclose information where required by law, to protect rights and service security, or as part of a lawful business transfer with appropriate notice and safeguards.
Dig's reviewed app does not include advertising SDKs or data-broker integrations. We do not use its analytics to target third-party advertising. Dig's client-generated analytics events exclude your name, email, search text, barcodes, images, precise location, credentials and Marvin message content. Session replay, automatic touch/error/console capture and GeoIP enrichment are disabled. An account ID is still personal information; these events are not anonymous.
5. Storage, retention and deletion
We retain personal information for the purposes described in this policy. Retention depends on the type of information, whether it is still needed to provide a feature you requested, deletion or withdrawal requests, and any applicable security, transaction, dispute or legal requirements. Where a fixed period is not specified, the following criteria determine how long we keep it.
| Information or copy | Retention criteria and deletion triggers |
|---|---|
| Account, profile, collection, plans and activity | Kept to provide your account and synchronized history until you delete the relevant information or your account. Dig does not currently apply automatic expiry merely because an account is inactive. |
| Marvin conversations and memories | Saved conversations remain until you delete them or your account. Separately saved memories remain until account deletion; deleting a conversation alone does not remove those memories. |
| AI requests processed by Anthropic | Provider copies of messages, context, tool results and cover images follow the retention arrangements applicable to Dig's API organization and the features used, including applicable security or legal exceptions. These are separate from the conversations and memories saved in your Dig account. |
| Product analytics | Retained to assess feature use, onboarding and subscription conversion, subject to the provider's applicable retention arrangements and erasure requests. The need to compare usage across time determines the analysis period; a dashboard date filter or identity reset does not erase stored events. Dig does not currently apply a separate automatic age-based purge to PostHog events. |
| Subscription and transaction records | Retained as needed to validate access, restore purchases, handle refunds or disputed transactions, prevent fraud, and meet applicable accounting or legal obligations. Deleting a Dig account does not itself erase Apple's independent transaction records. |
| Service and security logs | Retained for troubleshooting, incident investigation and abuse prevention under the relevant service's log rotation arrangements, and longer where a specific incident or legal obligation requires preservation. |
| Website waiting list | Retained for the launch notification you requested until you withdraw or the launch communication and any necessary delivery follow-up are complete. A limited record may be kept where needed to honor your withdrawal or meet legal obligations. Joining the list does not authorize an ongoing newsletter. |
| Support correspondence | Retained while handling your request and any related follow-up or dispute, and for applicable legal obligations. Resolved correspondence should not be kept indefinitely merely because the mailbox can store it. |
| Backups and exports | Deleted records may remain until the applicable backup rotation or export retention period ends. These copies are separate from the active account database and are subject to access restrictions and any required legal preservation. |
| Device copies and synchronization deletion markers | Local copies support offline use; deletion markers prevent deleted records from returning during synchronization. Their handling and current limitations are explained below. |
Your account data is stored on your device for offline use and synchronized with our backend. Signing out hides the account's local copy and preserves pending offline changes for that account; it does not delete the account or its data.
Use Settings → Delete account, or Account → Delete account from the subscription screen, to request permanent deletion. The implemented flow deletes your active Dig authentication record and private database records, including collection/preferences/history, conversations/memories and saved Discogs credentials. It also clears the requesting phone's active account copy and pending changes. Shared event and shop listings are not private account records.
Deleting your Dig account does not delete an independent Apple or Discogs account, cancel a subscription, or remove a separately submitted website waiting-list entry. Manage subscriptions in Apple's subscription settings. Contact our privacy address to remove a waiting-list entry.
The current automatic deletion flow does not delete previously ingested PostHog events or RevenueCat customer records. Signing out of these services does not erase those records. Other offline devices and legacy local database archives may retain copies; account deletion is not a promise of immediate erasure of every copy or backup.
For requests covering separately retained provider records, waiting-list entries or support correspondence, email contact@digrecords.fr. Any continued retention must have an applicable purpose or legal basis; account deletion is not authorization to keep all associated records indefinitely.
6. Legal bases and international processing
Dig is intended for worldwide availability.
Where EU or UK data protection law applies, the proposed allocation is: providing requested accounts, sync and paid features under our contract with you; consent for optional processing where required, including non-essential analytics and waiting-list communications; legitimate interests in proportionate service security and support; and legal obligations for records we must retain. Device permission alone is not consent to every subsequent use or disclosure of the data.
Your information may be processed outside your country by the providers above.
7. Your choices and rights
You can edit your collecting information and location, manage iOS camera/photo/microphone/location permissions, disconnect Discogs, clear recent identified songs and delete conversations or your account using the available app controls. To stop sending new Marvin messages or cover images, stop using those features; this does not erase requests already processed.
Depending on applicable law, you can request access, correction, erasure, restriction or a portable copy of your personal information. You can object to processing based on legitimate interests and to direct marketing. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing. Contact our privacy address; we may need proportionate information to verify your identity.
You may complain to your local data protection authority, including the CNIL in France or the ICO in the UK where applicable.
Dig personalizes record suggestions and Marvin responses. It is not designed to make automated decisions with legal or similarly significant effects on you.
8. Website storage and waiting list
The website saves your chosen language in browser local storage. Its listening demonstration requests music information and previews from Apple. Joining the waiting list supplies an email and language preference for the requested launch notification; it does not automatically create a Dig account or authorize an ongoing marketing newsletter.
9. Children and policy changes
We will update this policy when our processing changes and show the revised effective date. Where required, we will notify you of material changes and obtain any necessary new consent before introducing the relevant processing.