Privacy
Privacy policy
How DISCTALE handles the camera, your records, your location, the listening services and YouTube API Services, why, for how long, and how to use your rights.
In force for the DISCTALE app on the App Store and this website
Version of 18 November 2026
DISCTALE is provided by Giuseppe Albrizio, independent developer, Milan, Italy, under the Formray name. He is the data controller. For every privacy question or request, including the rights described in “Legal bases and your rights” below, write to admin@formray.io. This page describes the app and the website; the date at the top changes when the page changes.
Legal bases and your rights
Why we may use your data (Article 6 GDPR). To provide the app you chose to use, as a contract with you (Article 6(1)(b)): recognising records when you scan, catalogue and listening look-ups, your account, purchases, Discogs linking and the notices about your account. With your consent (Article 6(1)(a)), which you can withdraw at any time without affecting what was done before: shared digs and scans, the recognition memory (section 6), photos sent in AI mode, saved places and location reminders, news and offers by notification, and the website newsletter. For our legitimate interests (Article 6(1)(f)) in keeping DISCTALE secure and working: admitting each installation with Apple App Attest and limiting abuse, server logs, and replies to feedback and corrections you send. Crash and performance reports and daily usage totals (section 9) are on unless you switch them off in Settings; we rely on our legitimate interest in fixing faults and knowing which functions are used. To meet legal obligations (Article 6(1)(c)): the purchase and accounting records the law requires us to keep.
Your rights. You can ask to access your data and receive a copy, to correct it, to delete it, to restrict its use, to receive the data you gave us in a portable format, and to object to uses based on our legitimate interests. Where we rely on consent, you can withdraw it at any time, as easily as you gave it: the switches are in the app (Profile and Settings) and are described in each section. Write to admin@formray.io; we answer within one month, and tell you if a complex request needs up to two more months. We may ask you to confirm the request from the phone or account it concerns, because scans and digs are tied to a random code on your phone rather than to your name.
Complaints. You can complain to the Italian supervisory authority, the Garante per la protezione dei dati personali (https://www.garanteprivacy.it), or to the authority of the EU country where you live or work.
Children. DISCTALE is for people aged 13 and over, as its App Store age rating says. Where a use relies on consent, someone younger than the age set by their country (14 in Italy, between 13 and 16 elsewhere in the European Union) needs a parent or guardian to agree for them. DISCTALE does not check ages; if you learn that a child gave a consent without that agreement, write to admin@formray.io and we delete what was sent.
No automated decisions with legal or similarly significant effects are taken about you. DISCTALE does not sell personal data and does not use it for advertising by third parties.
Where data is processed and who receives it
DISCTALE’s backend, database and file storage run on Google Cloud in the European Union (europe-west1, Belgium). Database backups are kept by Google Cloud in the location Google chooses by default for a database in Belgium; we have not set it ourselves. Server logs are kept by Google Cloud Logging in its “global” location, which is not limited to the European Union, and, since 18 November 2026, also in a copy in the European Union (europe-west1). The vector database used for recognition is Qdrant Cloud, run by Qdrant Solutions GmbH (Berlin) on Google Cloud in Frankfurt, Germany (europe-west3). Google Cloud and Qdrant process this data on our behalf.
Some services are outside the European Economic Area. OpenAI (United States) receives the photos and evidence you send in AI mode, on our behalf (section 1). Vercel (United States) hosts this website and Resend (United States) sends the website emails, on our behalf. Our providers may process data outside the EEA under their applicable data-protection arrangements; see https://developers.openai.com/api/docs/guides/your-data, https://vercel.com/legal/privacy-policy and https://resend.com/legal/privacy-policy.
Other services receive data directly under their own terms and privacy policies, as independent controllers: Apple (Sign in with Apple, App Store purchases, App Attest, push notifications, iCloud, ShazamKit, Apple Maps and iTunes or Apple Music previews), Google (Google sign-in, YouTube and Google Lens), Discogs, Deezer and Spotify. Each section says what they receive.
Website: past invitations and the newsletter
Until DISCTALE reached the App Store on 6 November 2026, this website sent TestFlight invitations by email, through Resend, to people who asked for one; the website no longer collects email addresses. Vercel hosts this website and processes technical request information, including IP addresses, to operate it and limit abuse.
The newsletter was optional. We subscribed people only if they selected the separate newsletter checkbox and then confirmed through the email link. Resend stores the address and the version and timestamps of that consent in the DISCTALE newsletter list, which we use to send DISCTALE news, product updates and announcements. You can withdraw consent using the unsubscribe link in every newsletter, or by writing to admin@formray.io.
Invitation delivery records are retained according to our email provider’s service retention settings. Newsletter details are retained while you remain subscribed; limited consent and suppression records may be retained afterwards to demonstrate your choice and respect opt-outs. We do not enable email open or click tracking. This website sets no cookies of its own; it remembers only, for the current visit, which opening image it showed. It uses Vercel Web Analytics to count page views: for each view Vercel records the time, the page address, the referring site, the approximate location (country, region, city), and the browser, operating system and device type. Vercel tells visitors apart with a value computed from the request instead of a cookie, and discards a visitor’s session after 24 hours.
1. What the camera handles
DISCTALE uses the rear camera to read record barcodes, covers and centre labels. Image analysis and text recognition begin on the device. The scanner sends catalogue evidence; the separate, optional AI mode can send selected camera images only after you give its consent. If you have switched on sharing (section 6), the scanner also sends a crop of the sleeve or label it recognised.
Recognition requests send catalogue evidence to the DISCTALE backend: barcode values, text read from a centre label or sleeve, and numerical descriptors of the cover. These requests also carry your installation’s access credential, the app version and an identifier of the dig in progress. The backend does not save this evidence in its database, apart from the hour of the installation’s last scan and the daily totals described in section 9. Server logs (section 7) record the address of every request with your IP address for 30 days, and for a barcode look-up or a search you type, that address contains the barcode number or the words you searched. Unless sharing is on, no image from the scanner reaches the backend. Record covers shown in the app come from the DISCTALE backend, which reads them from Discogs and keeps a copy in its own private storage in the European Union (Google Cloud, europe-west1); that copy is catalogue data and contains nothing about you. Covers in your Discogs collection and wantlist load directly from Discogs.
In AI mode, a useful view can be captured automatically; the Photo button is optional. The image and relevant catalogue evidence pass through our backend to OpenAI, in the United States, for analysis. DISCTALE does not save these images, camera text or model answers; it keeps an accounting record of each investigation (section 7). OpenAI states that API data is not used for model training unless explicitly opted in. Its default abuse-monitoring retention can include submitted content for up to 30 days, with longer retention for legal or safety reasons. DISCTALE requests no stored response, but does not promise zero retention by OpenAI. See https://developers.openai.com/api/docs/guides/your-data. You can close AI mode at any time and withdraw future image-analysis consent in Profile using Turn off AI photo analysis; this cannot recall an image already processed.
Dig deeper → Search the web: when the camera cannot identify a record, you can choose to search the web with a photo. Nothing is sent until you tap Photo. That photo then goes directly from your phone to Google Lens, without passing through the DISCTALE backend, and Google’s results page is shown inside the app. Google’s handling of the photo is described in the Google Privacy Policy (https://policies.google.com/privacy); DISCTALE does not sign you in to Google and cannot promise how long Google keeps it. Google may set its own cookies in that page, and they stay on your phone. To help you pick, DISCTALE may look at the addresses of the links on that page and either mark the ones that lead to a Discogs release or master, or list those records above the page with their names and covers from the DISCTALE catalogue; for that list only the Discogs record numbers are sent to the DISCTALE backend. DISCTALE does not change the page and keeps nothing else it reads there. When you tap a marked link or a record in the list, DISCTALE opens that record in the app; for a master, the app asks Discogs which release is its main one. When you close the sheet, the app deletes its copy of the page and images.
2. Information stored on the device
The app stores your Crate, kept records, completed dig sessions, saved places, app preferences and locally derived Taste information in the app’s storage on the device. A linked Discogs collection is also cached locally so it remains part of the Crate experience.
So that your Crate survives a reinstall or a new phone, the app keeps a copy of your Crate, your crates (bags) and how each one looks (colour, patch and name), saved places, imported Discogs collection and collection valuation in your own iCloud account (the private CloudKit database). That copy never passes through DISCTALE’s servers and DISCTALE cannot read it; it exists only if your phone is signed in to iCloud, and it is removed when you delete the app’s data from iCloud in iOS Settings. If you back up your phone to iCloud, the app’s storage, including saved places, is part of that backup, which belongs to your Apple account.
Field-test builds can keep diagnostic event files in the app’s storage. Those files are designed to exclude images, raw barcode values, recognised text, audio, media addresses and secrets. They leave the phone only when you choose “Share test history” yourself.
3. Optional location and saved places
Location is optional. When you ask to save a dig place, DISCTALE uses your current location, to about 100 metres, and remembers the small area around that place on the device. Nearby searches send the search area to Apple Maps. If you enable reminders, iOS may monitor those saved regions so the app can ask whether you are digging there.
DISCTALE does not track your route and does not send saved-place location data to its servers. A shared dig (section 6) contains only the name of the shop, if you linked one.
4. Listening and catalogue services
The DISCTALE backend uses Discogs catalogue data to identify releases. When you have connected your Discogs account, the app reads your collection, your wantlist and record prices directly from the Discogs API on your own device, under your own authorization. Only when you tap to do so, it also writes to your Discogs account from your device: it adds a release to your wantlist or removes it, and it adds a copy of a release to your collection (folder Uncategorized) after checking that the collection does not already hold one, or removes one copy of a release from your collection. The DISCTALE backend signs each of those requests with the application credential it alone holds. While Discogs is linked, recognition and catalogue requests also carry your Discogs authorization to the DISCTALE backend, which uses it only to make that request to Discogs on your behalf and never writes it to storage; Discogs answers are kept in the backend’s memory for at most one minute. If direct access is unavailable, the app may use the backend to relay reads; writes are never relayed, and the fallback is not used when Discogs reports a rate limit. For requests from your device Discogs receives your device’s IP address, under the Discogs privacy policy. The app streams a short preview when one exists (Apple, through the iTunes catalogue, or Deezer), opens Spotify for playback through your own account, or shows a visible official YouTube player with playback controlled by your autoplay preference.
Those services receive requests under their own terms and privacy policies. DISCTALE does not promise that every recognised release has playable audio. Preview audio is streamed and never stored for offline playback.
5. Accounts and collection linking
You can scan records, use the manual search tools and Try harder and listen through YouTube without a DISCTALE account. An account is required for personal AI investigations and purchases. You can create it with Sign in with Apple or with your Google account; the two work the same way and an account belongs to the sign-in that created it (the same email through Apple and through Google is two separate accounts). We verify the identity token Apple or Google issues and retain a digest of that provider’s identifier, device-bound sessions, the name you share and the email the provider has verified, including a private relay address if you choose Hide My Email with Apple. With Google, the app opens Google’s own sign-in page in the system browser and reads only the identity token; DISCTALE never receives access to your Google account or its data, and stores no Google token. Completing sign-in requires a name and a verified email. If the provider does not supply a name, the app asks you to enter it before continuing. An older account with missing details must complete its profile by signing in again. These details identify your account in your profile and our restricted dashboard, where the sign-in provider is also shown; they are not used for advertising. The device Keychain temporarily retains a name awaiting confirmation so a failed first login does not lose it.
Apple handles payment details. DISCTALE receives and verifies transaction identifiers, product, renewal, expiry and refund status, and associates the purchase with your DISCTALE account. It does not receive your card number or bank details. Restoring a purchase requires the account it belongs to; it does not transfer the purchase to another account.
You can sign out or delete your account inside the app. Deletion takes effect at once. It clears name, email, the Apple or Google identifier digest and active access, removes linked shared digs, and detaches AI and purchase records from the account. The phone then switches sharing off, which deletes the scans and recognition memory it sent (section 6). What remains: the account’s internal number with its creation and deletion dates, without name or email; its ended sessions, with the installation identifier; minimal transaction identifiers and accounting evidence, to prevent reuse of deleted purchases and reconcile costs. Account deletion does not cancel an Apple subscription: manage it in your Apple subscription settings. Your Crate remains on the phone and in your own iCloud.
Connecting Discogs and importing your collection are optional: the Discogs authorization token is kept in the iOS Keychain on your device and is removed when you unlink from the app. The backend stores neither the token nor your collection nor the prices (section 4). Price information is shown for at most six hours after it was read.
Every installation holds an individual access credential in the iOS Keychain. New installations use Apple App Attest to obtain it automatically, without an invitation or Apple account sign-in. Apple verifies the app installation; DISCTALE retains its public key, Apple’s attestation receipt, app version and installation identifier (the identifier iOS gives the app on this phone) to verify access and prevent replay or abuse. The private key stays on the device. With the same record we keep the app version the installation last used and the hour of its last scan, and we count how many installations are in use. These records belong to the installation, not to your DISCTALE account. If you sign in, your account session carries the same installation identifier. We use it to count how many installations in use are signed in and how many are not, and, only for our operators in our support dashboard, to show beside your account the app version of the installation you are signed in on now (the one used most recently, if more than one), the day that installation was first admitted, how many installations you are signed in on, and the hour of its last scan, if that hour is not earlier than the hour you signed in there. We use this to help you when you contact us and to know which app versions are still in use. Once you sign out, nothing is shown for that installation; if you sign out while the phone has no network, the server does not hear it, and that installation can stay shown beside your account until that sign-in expires, at the latest 30 days after you signed in. None of this is used for advertising or tracking. Short-lived verification challenges expire after five minutes.
Notifications and messages from DISCTALE
From version 1.0.6. Notifications are optional: nothing is sent unless you allow them for DISCTALE in iOS. The app asks on a page that says what the permission is for. They cover the notices about your digs and saved shops and about your own account (for example a plan you were given). News from DISCTALE, meaning new features and offers now and then, works differently depending on your app version. In versions where news has its own switch, allowing notifications does not turn news on: news stays off unless you switch on “News from DISCTALE” in Settings, and the app may suggest it on a short sheet, “Hear what’s new?”, at most three times, not before the third day you open the app and only if you have already allowed notifications; it stops asking after the third time, or as soon as you turn news on, or if you turned news off yourself. In earlier versions, up to 1.0.7, one yes on that page covers news too; if you allowed notifications in a version before 1.0.6, or where iOS asked for the permission without that page, news stays off until you say yes on that page, which the app shows you once, or turn news on in Settings. In every version you can turn news off at any time in Settings, under “News from DISCTALE”, and keep the other notifications. Turning notifications off for DISCTALE in iOS Settings stops all of them.
What is sent: once DISCTALE has switched server notifications on, when you allow notifications your phone sends the DISCTALE backend the push token Apple issued for this app on this phone, and whether news is on. The phone sends it only while there is a reason to: you are signed in to a DISCTALE account, or news is on. With news on it is sent without an account too. The token is kept with the installation identifier described in section 5 and, if you are signed in, with your account, so that a notice about your account reaches your phones. Notifications are delivered by Apple (Apple Push Notification service), which receives the token and the text of each notification, under Apple’s privacy policy (https://www.apple.com/legal/privacy/). For each notification we record whether Apple accepted it for your phone; the record does not contain the token. That history, with the text of each notification, is deleted 180 days after the notification was written (the server checks every six hours). Push tokens are not used for advertising networks or tracking, and are not shared with anyone but Apple.
How long: the token is deleted when you turn notifications off for DISCTALE in iOS (at the next opening of the app), when Apple reports that it is no longer valid, and when you sign out of or delete your account with news off. If news is on when you sign out or delete your account, the token stays, no longer tied to the account, until you turn news off. When you delete your account, notices written for it stop naming the account at once, and any still waiting is cancelled.
Messages inside the app: DISCTALE can also show a short message on the camera when you open the app, for example that a new version is available. These need no permission and no account, and nothing new leaves your phone for them: they arrive with the settings the app already reads at launch. To leave out phones that are already up to date, the backend reads the app version that every request already carries; it does not store it for this. Your phone remembers only which messages it has already shown, as a short list of identifiers kept on the device.
6. Shared digs and scans (optional)
Off by default. In Profile you can switch on “Help improve DISCTALE”; in versions up to 1.0.7 the same switch is called “Share your digs with DISCTALE”. From version 1.0.8, where the app asks for it, a short line says that it shares your digs and what the camera saw and that you can turn it off at any time in Profile; the “i” beside it opens the precise list below. From version 1.0.9 that line names the photo and the text: “Shares your digs, a cropped photo of each record and the text on it. Off anytime in Profile.”; on the sheet when you reopen the app it starts with “From now on,”, and where the app asks only about scans it says “Shares a cropped photo of each record and the text on it. Off anytime in Profile.” The app asks for it in a few places, such as the introduction, after a scan that found nothing or when you save a dig, and as a short sheet when you reopen the app at most three times in all; once you switch it off yourself, the sheet no longer appears. The same switch covers three things: a summary of each finished dig, each scan, and the recognition memory. With it on, when you finish a dig the app sends that dig’s document to the DISCTALE backend: the dig’s identifier, its title if you gave one, the name of the shop if you linked one, when it started and ended, and for each record found its catalogue identity (title, artists, release and master identifiers, year, country, label, format), how it was recognised, whether it played and whether a preview existed. The document also records when you gave consent and which build you were using. From version 1.0.8, if you say yes in the middle of a dig, only the records found after your yes are sent; in earlier versions the whole dig is sent.
The dig document itself contains no photos or camera frames, text read by the camera, barcode values, coordinates of saved places, contacts, name or email, preview addresses, tracklists, or the recognition register. The register leaves the phone only through Share test history. A shared dig uses a random device code, and the backend attaches your account if you are signed in. Separate account and AI requests described above can contain other data.
Scans, from version 1.0.5. With sharing on, each time the scanner looks up a record the app also sends: a crop of the sleeve or centre label, the text read from it, the list of records DISCTALE proposed with the score each one got, how sure the recognition was and the short reason for that decision, what framed the record (the sleeve, the centre label or the whole picture), and what happened next (the record opened by itself, you chose one from the list and which row, you ignored the list, no record was proposed, you read the barcode, or you found it another way: the code, the label, typing it, listening or Dig deeper; or you tapped “Not this record”), with the time of the scan, the lens used and the app version. When you save the dig and a record found in that scan is still in the crate, the app adds that to the same scan. The crop is cut to the sleeve or label and stripped of photo metadata. The crop and the text read are sent only when the app sees a record in front of the camera. When it does not see one, it still sends at most one short row every ten seconds that says it proposed nothing, without a crop or any text read. The full camera frame is never sent. A crop can still show what is on the sleeve itself, such as a price sticker, handwriting or a fingertip at its edge. A scan carries the same random device code as a shared dig and the installation’s access record, and no name or email.
Recognition memory. With sharing on, when you pick a record from the list the camera proposed from a cover, the app also sends numerical descriptions of that view of the cover, made by one of our recognition models and, when it is ready in time, a second one (not the photo), how the match was proved, the random device code and the time. DISCTALE keeps them in its vector database (Qdrant Cloud, Frankfurt) and uses them to recognise that sleeve faster for everyone. Other people’s phones never receive the device code, the time or anything about you: only that the sleeve was learned from real scans. They are kept until you switch sharing off; there is no other time limit today.
Why: to build DISCTALE’s own set of real scans, measure how often recognition finds the right record, and improve it, which can include tuning the recognition models on these crops. Scans are not used for advertising, not sold and not shared with third parties.
If you switched sharing on before version 1.0.5, that choice covered dig summaries only. The app asks you again, once, and no scan is sent until you agree.
Shared digs are stored in DISCTALE’s own storage in the European Union (Google Cloud, europe-west1) and read only by the DISCTALE dashboard, to see how recognition and listening go dig by dig. They are not shared with third parties and not used for advertising. They are kept until you withdraw consent, and in any case deleted automatically about 400 days after they were written, with the last older copy gone within about two weeks after that.
Scan crops are kept apart, in storage in the same Google Cloud project used only for them and encrypted with a key that DISCTALE controls. Neither the app nor the backend has a way to hand a stored crop back out; they are read inside that project, by DISCTALE alone. Each scan is deleted automatically 365 days after it was received.
Switching sharing off stops all three at once and asks the server to delete every dig, every scan and every recognition-memory entry your phone sent; measurements already computed from them, which no longer contain the crops or the device code, remain. The phone repeats the request until the server confirms it. Older copies our storage keeps of a deleted dig are removed within about two weeks. If the vector database does not answer at that moment, the server tells the phone that the deletion did not finish, and the phone asks again, as it does for digs and scans. Deleting your account in the app deletes the digs that carried it and switches sharing off on that phone. You can also write to admin@formray.io.
7. Retention, logs and backups
In the app you can remove Crate items, kept records, saved sessions, saved places and local diagnostic events. Unlinking Discogs removes the connection and its token from the app; releases you added to your Discogs collection or wantlist stay on Discogs, where you can remove them. Deleting the app deletes everything it stored on the device; the copy in your iCloud stays until you remove it from iCloud.
Server logs record, for each request to the backend and to our dashboard, the time, the full address requested, the IP address and the app or browser that made it; errors and account events also record a short or full account number. The address can contain a barcode number or the words of a search you typed (section 1). Logs are used for security and to fix faults, are kept by Google Cloud Logging in its “global” location and, since 18 November 2026, also in a copy in the European Union (europe-west1); both are deleted after 30 days. When one of our operators opens a page of our dashboard that shows a person’s data, the dashboard also records which operator, when, and which account, dig or report was opened, never what the page showed. That record is in the server logs and, in a separate copy in the European Union (europe-west1), kept for 400 days.
Personal AI accounting records your account, investigation identifiers, time, status and allowance consumption, without storing the image or the model answer. Provider costs are recorded even when an investigation fails or is cancelled; the restricted dashboard separates those costs from your personal allowance. These account links remain until account deletion; the monthly allowance reset does not erase the history.
Other periods: crash and performance reports (section 9), 90 days; notification history, 180 days; YouTube matches, 7 days, and “no match” answers, 24 hours (section 8). Kept today without a fixed time limit, tied to your installation and not to your name (except where section 5 says what our operators see beside your account): messages you send with Send feedback and, when “Include technical details” is on (it is on unless you switch it off), the phone model, the iOS and app version, the part of the app you were in and a technical attachment with the latest recognition events and error lines (never an image, audio or location); corrections you make to which preview plays for a track (the record, the track and the preview you chose or rejected); the installation and session records described in section 5. You can ask us to delete them at admin@formray.io.
Backups of the database are kept for 7 days, with the ability to restore it to any moment in those 7 days; data you delete leaves the backups within 7 days. Where Google keeps them is described in “Where data is processed and who receives it”.
Listening recognition (ShazamKit)
Listen is optional and starts only when you open it. With microphone permission, Apple ShazamKit recognizes nearby music using an audio signature. DISCTALE does not save microphone audio or add matches to your Shazam library. Listening stops when a result is obtained, you close the view or you leave the app. ShazamKit is provided by Apple under its privacy policy (https://www.apple.com/legal/privacy/).
After recognition, the artist and song title are sent through the DISCTALE backend to Discogs to find possible vinyl releases. Audio identifies a recording, not a physical pressing. The result and an available Apple Music link are shown in the listening view. Closing Listen does not add a record to your Crate.
8. YouTube API Services
DISCTALE uses YouTube API Services to find the official upload of a recording when no licensed preview exists, and to show it in the official embedded YouTube player. Autoplay YouTube is off by default. When enabled in Settings, every YouTube player opened by DISCTALE starts the video when it appears, including a single result selected by the resolver. When disabled, playback waits for your tap. The player connects to YouTube when it opens; with autoplay enabled, YouTube collects playback data when the player loads, without further interaction. YouTube may set its own cookies in the player, and they stay on your phone. By using these features you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google’s handling of data is described in the Google Privacy Policy (https://policies.google.com/privacy).
What is sent to YouTube: the artist and title of the recording being searched, through the DISCTALE backend. The YouTube feature does not sign you in to YouTube, does not request access to your YouTube account, and therefore holds no YouTube user data; there is nothing to revoke. Playback happens inside the YouTube player under YouTube’s own terms and privacy policy.
What is stored: the public identifiers of the matching videos, with their YouTube title, channel, thumbnail address and length, associated with the catalogue release on the DISCTALE backend so that a record already searched is not searched again. A match is kept for at most 7 days and a “no match” for 24 hours; expired rows are deleted, which keeps every stored item inside the 30-day limit set by the YouTube API Services Developer Policies. On your device, the row you chose for a record stays until you change or reject it, and it is checked against a fresh answer before it is reused. Thumbnails and the player itself are loaded on your device directly from YouTube, under the Google Privacy Policy. The cached catalogue matches do not contain your YouTube account details.
9. Analytics and tracking
DISCTALE contains no analytics or advertising SDK and does not track you across apps or websites. Its privacy manifest declares name, email, user identifiers, purchase history, photos (optional AI photos and, with sharing on, scan crops), feedback, diagnostics, product interaction, coarse location (a shop name in a shared dig) and a device identifier (the push token, if you allow notifications). These are declared linked to you, never for tracking. Account, purchase and AI data support app functionality; the push token supports app functionality and, while news is on, DISCTALE’s own news and offers; shared digs and scans also support analysis and improvement of recognition and listening. Our server counts how many requests of each kind it receives — scans, searches, previews and the like — by day and by app version; a version that fewer than five phones use is counted together with the others. These are totals, not a record of what a person did; on a day when very few phones use a version, a total can describe very few phones.
From version 0.7.7 the app receives Apple’s MetricKit reports about itself: crashes, hangs, launch time, memory and battery-related measurements iOS aggregates about a day at a time. The app sends them to the DISCTALE backend with the app version, iOS version and device model. The backend keeps them with this installation’s access record, never with your name, account or any image. They are used only to find and fix defects, and are deleted after ninety days. This is on unless you turn it off in Settings, under “Share diagnostics”.
From version 1.0.6 the app also keeps a few daily totals of how it is used. They say, yes or no, which functions were used that day; whether that day was the installation’s first, whether the introduction was completed, whether the camera permission was given or refused, whether the first scan and the first record found happened, whether the subscription screen was seen, and whether “Help improve DISCTALE” was on; and a few counts, such as how many scans found a record and how many found none, and, for each place where the app asks for “Help improve DISCTALE”, how many times it asked and how many times the answer was yes, “Not now” or a closed page. This is on by default; you can turn it off in Settings, under “Share usage totals”, and from then on nothing is counted and what was counted and not yet sent is deleted from the phone; the phone only remembers, without ever sending it, that the first scan, the first record found and the answer to the camera permission have already happened. Once a day is over the app sends its totals to the DISCTALE backend. They contain no titles, no records, no photos, no location and no times of day. The backend adds them to the totals of every other phone, which it keeps per day and per app version, and does not keep the message or which day it was about; on the installation’s record it keeps only the date it last sent and how many times it sent on that date, to limit them. These are totals, not a record of what a person did, but on a day when very few phones send them a total can correspond to a single phone; our dashboard does not show a day for which fewer than five daily summaries arrived. Totals already added cannot be taken out again, because the backend does not keep which installation sent which total: they remain after you turn the switch off or delete your account.
From version 1.0.9, when we turn it on, the daily totals also say how far the app has gone — still at the start, first record found, signed in, first bag, Fill my bag, bag look, Collector — and how many days have passed since it was installed, in bands (the first day, one to six, seven to twenty-nine, thirty or more); whether it was used again one, seven and thirty days after its first day; how many times some functions (the introduction, Listen, Fill my bag, the bag look, sign-in, the Collector purchase, sharing) were opened, finished or left, and how long finishing took, in bands of seconds; how many times each invitation was shown and answered, and with which of its texts; how many times a few things were touched, such as scrolling the bag or opening YouTube; and how many times people moved from one screen to another or left the app from it. They are still totals added to every other phone’s: they never contain the order of your screens, a time of day, or anything about the records you scan. Our dashboard shows none of these totals, nor any step, move or answer, that fewer than five phones sent on a day.
