Back to Snag

Privacy Policy

Effective Date: April 26, 2026
Last Updated: July 28, 2026

Snag is developed and maintained by Ganotis Holdings, Inc. (“we”, “our”, or “us”). This Privacy Policy explains what information Snag handles and how it is used.

Summary

Snag saves your song identification history on your device and can sync that history through your private iCloud account so it is available across your Apple devices. Private iCloud sync means your private Snag history is not accessible to anyone without access to your iCloud account, including the developer of Snag. We do not store your private Snag history, notes, location history, or recordings on Snag’s servers during normal app use, except when you explicitly choose Share Recording through the unidentified-recording sharing prototype.

The Snag app does not include advertising trackers or third-party product analytics. Snag may send identified-song metadata to Snag’s servers to let you share links to your Snags with other people, resolve Spotify links, and power aggregate features such as top-snagged songs. Snag may also send an anonymous activity event when a Snag is saved, including whether it was identified, its source type, its timestamp, and a random identifier for that saved Snag. This information does not include your name, email address, Apple ID, device location, contacts, advertising identifiers, notes, or recorded audio.

Through the unidentified-recording sharing prototype, you can explicitly choose Share Recording for an unidentified Snag. Snag then uploads that recording to Snag’s server so anyone with the hard-to-guess link can listen to it. The shared copy remains available until you choose Stop Sharing or delete the Snag. If the Snag is later identified, the hosted audio copy is deleted and the same link changes to an identified-song page. Normal app use and identified-song sharing do not upload your recordings to Snag’s servers.

The snag.tv website uses Google Analytics for basic website traffic analytics on its public marketing pages and regular identified-song share pages. The unidentified-recording route does not load Google Analytics, including after the song is identified and the route changes to an identified-song page. This website analytics does not include your private Snag history, notes, location history, or recordings from the app.

What Snag Does

Snag records short audio clips while attempting to identify songs using Apple’s ShazamKit framework. Recordings are saved so you can replay them, retry identification later, and keep a personal history of songs you have heard. Your history syncs through Apple’s private iCloud services when iCloud is available for Snag. Audio clips may also sync through your private iCloud account when audio sync is available.

You can disable iCloud sync for Snag in iOS Settings by turning off iCloud access for Snag. If iCloud sync is off or unavailable, new snags remain on the device where they were captured.

Permissions

Microphone

Snag requires access to your device’s microphone to record audio clips for song identification. Recordings are saved in Snag for replay and retry. They are not uploaded to Snag’s servers during normal app use or identified-song sharing. A recording is uploaded only when you explicitly choose Share Recording in a build that includes the unidentified-recording sharing prototype.

You can revoke microphone access at any time in iOS Settings. Without microphone access, Snag cannot record or identify audio.

Sharing an Unidentified Recording

If you explicitly choose Share Recording for an unidentified Snag through the unidentified-recording sharing prototype, Snag uploads a copy of that recording to Cloudflare so it can be played through a hard-to-guess snag.tv link. Anyone who has the link can listen. The shared copy does not include your location, notes, name, email address, Apple ID, local record identifier, filename, device name, or other account information.

The shared copy remains available until you choose Stop Sharing or delete the Snag. If the Snag is later identified, the hosted audio copy is deleted and the same route converts to an identified-song page. Choosing Stop Sharing deletes only the hosted audio copy. Your recording in Snag stays on your device unless you separately delete the Snag.

Snag records aggregate page-view and first-play counts for these links. These counters do not store recipient IP addresses, user agents, referrers, account identifiers, or device identifiers. Unidentified-recording pages do not use Google Analytics.

Location (Optional)

If you enable the optional location feature in Snag’s Settings, the app will save the GPS coordinates and a venue or place name with each snag, so you can remember where you heard a song. Location data is stored with your Snag history and may sync through your private iCloud account. It is not uploaded to Snag’s servers.

The optional location feature uses Apple’s Core Location framework to perform reverse geocoding (turning coordinates into a readable place name) on your device. You can disable the location feature in Snag’s Settings or revoke location access in iOS Settings at any time.

Third-Party Services

Apple ShazamKit

Snag uses Apple’s ShazamKit framework to identify songs. When you record a snag, an audio fingerprint is sent to Apple’s Shazam Catalog for matching. This communication happens directly between your device and Apple’s servers. We do not see, store, or process this audio fingerprint. Apple’s handling of ShazamKit data is governed by the Apple Privacy Policy.

Apple iCloud

Snag uses Apple’s iCloud and CloudKit services to sync your private Snag history across your Apple devices. This data is stored in your private iCloud account, not on Snag’s servers. That means it is not accessible to anyone without access to your iCloud account, including the developer of Snag. Your iCloud storage availability and iCloud settings are controlled by Apple.

Apple Music and Spotify

When a song is identified, Snag may display links to Apple Music or Spotify. Tapping one of these links opens that service. A converted unidentified-recording share page may also load album artwork directly from an Apple content-delivery domain. In that case, the visitor’s browser makes the artwork request to Apple and Apple may receive standard web-request information such as the visitor’s IP address, browser information, and the artwork URL. Snag does not send your private Snag history, notes, location history, or recordings with that artwork request or when the service links are displayed.

Google Analytics on snag.tv

The snag.tv website uses Google Analytics to understand basic website traffic and page usage on public marketing pages and regular identified-song share pages. Google may process website visit information such as pages viewed, browser and device information, approximate location derived from IP address, and referral information. The unidentified-recording route does not load Google Analytics, including after the song is identified. This applies to website visits, not to use of the Snag app. Google’s handling of Google Analytics data is governed by the Google Privacy Policy.

Cloudflare

Snag uses Cloudflare to host snag.tv and to store copies of unidentified recordings that a user explicitly chooses to share. Cloudflare processes requests needed to upload, play, and delete those shared copies. Cloudflare’s handling of this data is governed by the Cloudflare Privacy Policy.

Snag Servers

Snag may contact Snag’s servers for the following limited purposes:

For identified sharing and related services, Snag may send identified-song metadata such as title, artist, ISRC, Shazam ID, timestamp, artwork URL, Apple Music URL, and Spotify URL. Anonymous activity events may include identification outcome, source type such as iPhone, Apple Watch, or video import, timestamp, and a random per-Snag event identifier used to prevent duplicate counting. The event identifier is not a user, account, or device identifier.

For an unidentified recording that you explicitly choose to share through the unidentified-recording sharing prototype, Snag sends the recording, its capture date and time, its duration, and a random management credential. Snag stores only a cryptographic digest of that management credential. The shared page records aggregate page-view and first-play counts. Snag does not store recipient IP addresses, user agents, referrers, account identifiers, or device identifiers for these counters. The shared record does not include your name, email address, Apple ID, device location, notes, local record identifier, filename, or device name.

Data Storage

Your private Snag history, notes, optional location data, and recordings are stored on your device using Apple’s standard storage frameworks. History can sync through your private iCloud account. We do not maintain a Snag account database or a server-side copy of your private Snag library. Snag’s servers may retain the limited anonymous activity events and identified-song metadata described above for aggregate reporting.

An unidentified recording that you explicitly share through the unidentified-recording sharing prototype is an exception to normal private-library storage. The server keeps the shared copy until you choose Stop Sharing or delete the local Snag. If the Snag is later identified, the server deletes the recording and retains only the identified-song page at the same URL. Choosing Stop Sharing does not delete the recording from your device or private iCloud history.

If you delete the Snag app, data stored locally by Snag is removed from your device. Data that has synced to iCloud is managed through your iCloud account and Apple’s iCloud settings. Deleting the app does not stop an active shared-recording link. The prototype stores its management credential only in the originating DEBUG app installation. If that credential is lost or becomes unavailable, including through app deletion, local storage failure, or replacing the DEBUG build with a build that does not include the prototype management interface, you may lose the ability to stop the link from the app. Stop sharing any active recording before deleting or replacing that DEBUG build.

Data We Do Not Collect

Snag does not collect any of the following:

Future Features

Future versions of Snag may include optional AI-powered song identification features that use third-party services such as audio fingerprinting APIs and speech transcription APIs. If and when these features are introduced, this Privacy Policy will be updated to disclose what data is sent, to which providers, and for what purpose. You will be notified of material changes before such features are activated for your account.

Children’s Privacy

Snag is not directed to children under the age of 13, and we do not knowingly collect any information from children under 13. If you are a parent or guardian and believe your child has provided information through Snag, please contact us so we can address the issue.

Changes to This Policy

We may update this Privacy Policy from time to time. The “Last Updated” date at the top of this page reflects the most recent revision. Material changes will be communicated through the app or on snag.tv before taking effect.

Contact

If you have questions about this Privacy Policy or about Snag’s handling of your data, contact Ganotis Holdings, Inc. through snag.tv.

This Privacy Policy applies to the Snag iOS application and the snag.tv website.