Art TL stores the original image, its checksum, notes, capture time, and available EXIF/GPS metadata in the owner's private account so batches can be recovered, deduplicated, and linked to possible museums or exhibitions.
Art TL · Music TL
Privacy Policy
This policy explains how Art TL and Music TL handle private taste evidence, image uploads and metadata, playlist imports, connected accounts, generated profiles, and native app data.
Art TL turns private images, reviewed artwork evidence, aesthetic references, and visit context into a personal taste memory. Music TL turns playlist and listening context into a profile, timeline, people directory, and recommendations. Private source material is distinct from anything the owner chooses to publish.
Recognition never makes a proposal public or factual by itself. Art uploads require a signed-in account for the bulk taste flow, and provider processing begins only after the batch notice is accepted.
Data
Information the app may process
After the owner confirms the batch notice, Art TL may send a newly generated pixel derivative to the configured image-recognition provider. The derivative is stripped of EXIF, GPS, device, filename, and local-path metadata before transmission. Originals are not sent as files.
Artwork matches, visual-region references, museum or exhibition suggestions, and generated profile text remain private proposals until the owner reviews them. A public profile is a separate, explicit projection of accepted evidence.
Spotify playlist URLs or IDs, anonymous guest IDs, imported artist/composer counts, generated music profile text, and playlist sync timestamps.
If Google sign-in is enabled and used, the app may receive account identity fields needed to keep imported music state attached to that account.
If Spotify OAuth is enabled and connected, the app may use Spotify authorization data to read listening or playlist context requested by the user.
The iOS and macOS apps use a local anonymous ID and the configured music.tl API to load profiles, events, recommendations, and guest import state.
Hosting, storage, and provider systems can create ordinary server logs, error traces, request metadata, and diagnostic records needed to run the service.
Use
How information is used
Art TL uses originals and private metadata to preserve the collection, recover interrupted batches, deduplicate files, and propose artwork, artist, object, museum, or exhibition context. Exact GPS remains a private source attribute; only an owner-accepted venue or exhibition label may enter generated taste evidence.
When recognition is enabled and the owner consents, Art TL may send a metadata-free pixel derivative to a configured vision or retrieval provider. EXIF, GPS, device details, original filenames, hashes, local paths, account identifiers, and private notes are excluded from that provider image payload and from public status responses.
The app uses imported music context to build recommendations, profile summaries, artist/composer lists, playlist readbacks, source filters, and event matches. Public profile data is only intended to be shared when the user chooses to publish a profile.
The app may send playlist or listening requests to Spotify, account requests to Google, and application requests to hosting or storage providers needed to operate music.tl. External music, video, venue, and profile links open the destination provider directly.
Controls
User controls
Art owners can review, reject, or accept attribution, description, visual-region, museum, and exhibition proposals; unreviewed evidence is not eligible for public profile publication. Account settings provide a complete private archive and confirmation-gated deletion.
Guest users can remove browser cookies or local app data to reset the anonymous guest state. Account-backed users should use the connected provider controls to revoke Google or Spotify access when those providers are enabled.
Profile publishing controls live in settings. If a profile is unpublished, it should no longer be treated as a public music profile by the app.
Policy status
Publication is not owner attestation
This repository-owned privacy policy candidate is hosted at the public /privacy route. It must still be reviewed by the account owner before App Store submission; a live URL does not by itself provide the business, privacy-nutrition, content-rights, or age-rating attestations required by Apple.