TapePass Privacy Policy

Effective October 18, 2026

What TapePass does

TapePass helps you share playlists and individual songs across supported music services. You do not need a separate TapePass account. You connect music accounts using each provider’s authorization screen.

Music information and shared tapes

With your permission, TapePass reads the playlist or song information you choose and searches supported services for matching recordings. This can include playlist titles, artwork URLs, curator names, track order, song titles, artists, albums, durations, recording identifiers such as ISRCs, and service-specific playlist and track identifiers. Song information may be sent to a destination music service to find matches and create a playlist you authorize. TapePass does not upload or store music audio.

When you create a TapePass link, the shared playlist or song information, your sharing display name, selected tape title and colors, and any personal message you add are sent to our Supabase-hosted backend. Simply viewing a source playlist does not publish a TapePass link. Copies of created and received tapes are saved locally so you can reopen and share their links.

Anyone with a shared link can access it

A TapePass link is not a private or password-protected message. Anyone with the link can access its shared music information, sender name, tape design, and any included personal message without signing in. Recipients can forward or post the link. Do not include information in a shared title, display name, or personal message that you do not want others to see.

Messaging and social-media services may retrieve and cache a tape’s title, artwork, song count, and sharing credit to display a preview. Their presentation, retention, and handling of anything you post are governed by those services. Removing a hosted share cannot remove copies or previews already held by recipients or other services.

Your profile and photo

Your profile bio and selected genres, music languages, moods, and occasions are saved on your device. Your display name is also used as sender credit when you create a shared tape. TapePass does not provide a public profile directory or searchable username.

Share my profile sends your display name, bio, and interests as text through the system share sheet to a destination you choose. Your profile photo is not included in that text or in TapePass shared-link records.

If you select a profile picture through the system Photos picker, TapePass processes that selected image and stores one compressed thumbnail locally, at most 512 pixels square and 100 KiB. Re-encoding removes the original image metadata, including location metadata. TapePass does not retain a separate copy of the original image or a history of previous profile photos. Save applies a replacement or removal. TapePass does not upload your profile photo to its backend. Apple may download your selected image from iCloud if it is not available on your device.

Playlist requests and local notes

Request a Tape keeps your request text, occasion, language, and mood as a local draft. Sharing opens the system share sheet; you choose the destination and send the message. The request includes your display name when set. Including your saved musical interests is optional, and the request does not include your profile bio or photo. TapePass does not upload request drafts to its backend or operate an in-app request inbox. The recipient replies through the messaging service you used. Sharing or cancelling the share sheet does not clear your draft; use Clear draft to remove it.

Personal notes and sender-name corrections you add to Received Tapes stay in your local saved list. They are not included in a reshared tape. TapePass’s reshare flow also omits the received personal message; you may add a new message for your own single.

Connected music accounts

Music-service passwords are entered with the provider, not collected by TapePass. Supported providers’ authorization tokens are stored in the iOS Keychain and may be used by TapePass and its share extension. Tokens are sent to the corresponding provider for authorized requests, not included in shared tape records or link previews. Apple Music access uses Apple’s authorization system.

You can disconnect supported services in TapePass and revoke TapePass’s access through the provider’s account settings. Disconnecting does not delete existing TapePass links, saved tapes, or playlists already created in your music library. Manage those playlists directly in your music service.

Local storage and automatic cleanup

These limits apply to transfer history and the song-link cache, not total app size, saved tapes, device backups, or caches managed by iOS and other services. Older installed versions may retain data differently until updated and opened.

Removing a saved tape versus deleting a shared link

Removing a tape from My Tapes or Received Tapes removes its entry from your local list. It does not disable the shared link, delete its hosted record, remove copies on another person’s device, or delete playlists in a music service. Transfer history is separate and follows the automatic-cleanup limits above.

Shared tape records currently have no automatic expiration or in-app control to delete the hosted share. To request deletion of a hosted record, email tapepassapp@gmail.com and include the TapePass share link so we can identify it. Hosting providers may retain backups and operational logs separately under their retention settings. Recipients’ copies and third-party preview caches are outside TapePass’s control.

Services that process information

Supabase hosts shared tape records. Cloudflare serves tapepass.app and its preview pages. Apple Music, Spotify, and TIDAL process authorized music requests under their own privacy policies. Artwork may load directly from music providers’ image servers. These services receive network information needed to handle requests, such as IP addresses, and may keep operational or security logs under their policies. An app or social platform you choose in the share sheet receives the content you send.

Our Supabase API gateway retains operational request logs, including IP addresses, approximate city, region and country inferred from the network connection, request paths, timestamps, response status codes, and response timings. We use these logs to investigate failures, maintain performance, and protect the service. This is network-derived approximate location, not GPS or precise device-location access. The current Supabase Free plan provides one day of API and database log retention; that window can change with the hosting plan or usage limits. No external Supabase log drain is configured. Hosted shared-tape records have the separate retention described above.

The current iOS app does not include advertising or third-party behavioral analytics SDKs. The website uses Cloudflare Web Analytics, which adds a browser script to collect website traffic and page-performance measurements. Cloudflare describes this service as cookie-free analytics that does not track people across websites. See Cloudflare Web Analytics for details. TapePass does not use shared music information for targeted advertising. Apple may provide beta feedback, crash reports, and device or app diagnostics through TestFlight. Information you send by email or beta feedback is used to respond to support requests and investigate issues.

Your choices and contact

You choose the music to share, whether to create or send a link, which profile information to share, which photo to select, and whether to authorize a destination service. You can edit your profile, remove your photo, clear a request draft, remove saved tapes, disconnect services, and request deletion of hosted shares.

For privacy questions, support, or hosted-share deletion requests, email tapepassapp@gmail.com. Include the relevant TapePass link for a shared-record request. Do not send passwords or authorization tokens. The same email and policy link are available in the app under Help → Privacy & Support. During the TestFlight beta, you can also use Send Beta Feedback.

Policy updates

We will update this policy as TapePass’s data handling changes and display the effective date here.