Privacy Policy

What We Collect

• •Account info: Email, username, and password (hashed)
• •Links you create: The music URLs you convert and share
• •Basic analytics: Link views and clicks (aggregated, not personal)

What We Don't Do

• ✗Sell your personal information to anyone
• ✗Use your email for marketing or newsletters
• ✗Track you across other websites
• ✗Share your data with third parties for advertising

How We Make Money

MTShare is free and we intend to keep it that way. To cover our costs, we display non-intrusive advertisements on link pages. These ads:

• •Are served by Google AdSense
• •Do not use your personal MTShare data for targeting
• •Are small and non-intrusive (no pop-ups)

Affiliate Links

On track and album landing pages, the Upcoming Concerts section may include ticket-purchase links to third-party ticketing partners (currently Ticketmaster and Skiddle). Some of these links are affiliate links: if you click through and complete a purchase, MTShare may earn a small commission from the ticketing partner at no extra cost to you.

• ✓No effect on price: the price you pay is exactly the same whether or not the link includes an affiliate tag.
• ✓No effect on which events we show: events come from multiple sources (Ticketmaster, Skiddle, Bandsintown), are merged and deduplicated server-side, and are ranked purely by date and relevance to the artist — never by commission rate.
• •What gets shared: when you click an affiliate link, you leave MTShare and arrive at the partner's site. From that point on, the partner and their affiliate network (e.g. impact.com) may set their own cookies and identifiers to attribute the referral. This is governed by their privacy policies, not ours.
• •Why we do this: MTShare is run as a not-for-profit-style service. Affiliate commissions, alongside the AdSense ads above, help cover server and domain costs so the service stays free.

Your Rights

You can:

• ✓Access all your data anytime from your dashboard
• ✓Delete your account and all associated data
• ✓Export your links and data

Data Deletion

You have the right to delete your personal data at any time. When you delete your account:

• ✓Your account and profile information will be permanently deleted
• ✓All universal links you created will be removed
• ✓Any associated analytics data will be erased

Alternatively, you can email us at [email protected] with the subject "Data Deletion Request" and we will process your request within 30 days.

European Union (GDPR) Rights

If you are located in the European Union, you have additional rights under the General Data Protection Regulation (GDPR):

• ✓Right to Access: Request a copy of all personal data we hold about you
• ✓Right to Rectification: Request correction of inaccurate personal data
• ✓Right to Erasure: Request deletion of your personal data ("right to be forgotten")
• ✓Right to Restrict Processing: Request limitation of how we use your data
• ✓Right to Data Portability: Receive your data in a structured, machine-readable format
• ✓Right to Object: Object to processing of your personal data
• ✓Right to Complain: Lodge a complaint with your local data protection authority

To exercise any of these rights, contact us at [email protected]. We will respond to your request within 30 days.

International Data Transfers

MTShare is operated from servers located in the European Union. If you are located outside the EU and choose to use our services, your information may be transferred to and processed in the EU. By using MTShare, you consent to this transfer. We take appropriate measures to ensure your data is protected in accordance with this Privacy Policy and applicable data protection laws.

Data Retention

We retain your personal data only for as long as necessary to provide you with our services and for legitimate business purposes, such as maintaining the performance of the service, making data-driven business decisions, and complying with our legal obligations. When you delete your account, we will delete or anonymize your personal data within 30 days, unless we are required to retain it for legal purposes.

Data Protection & Security

We treat sensitive data — passwords, OAuth tokens for connected music platforms (Spotify, YouTube, Tidal, Apple Music, etc.), and any third-party API credentials we hold on your behalf — with the following protection mechanisms:

• ✓Encryption in transit: all traffic between your device and MTShare is served over HTTPS (TLS 1.2 or newer). Our connections to third-party APIs (YouTube Data API, Spotify Web API, Tidal API, Apple Music API, etc.) are likewise made over HTTPS. Plaintext HTTP is rejected at the edge.
• ✓Encryption at rest for OAuth tokens: access tokens and refresh tokens we hold for connected platforms are encrypted before being written to the database, using Fernet (authenticated symmetric encryption built on AES-128 CBC with HMAC-SHA256) with a per-user-derived key. The per-user key is derived from a master secret via HKDF with the user's identifier as salt, so a single decrypted token can't be used to decrypt another user's tokens.
• ✓Password hashing: account passwords are stored as bcrypt hashes — we never store, log, or transmit your plaintext password. We can't recover a forgotten password; you reset it via a one-time email link.
• ✓No tokens or credentials in logs: our application logs deliberately exclude OAuth tokens, password hashes, and other credential bytes. Where errors involve credential-handling code paths, we log only the exception type name (not the message), to prevent third-party libraries from accidentally leaking token-shaped strings through error chaining.
• ✓Token lifetime minimisation: for Apple Music specifically, the Music User Token never persists beyond the lifetime of a single "save to your library" job — it's encrypted at request time, used by our worker to make the save call, and wiped from the database the moment the job reaches a terminal state (succeeded or failed). For other platforms' refresh tokens, we hold only the minimum needed to keep the connection working and delete them immediately when you disconnect.
• ✓Scope minimisation: we request only the OAuth scopes strictly required to operate the feature (e.g. "modify private playlists" on each platform). We do NOT request scopes for read-history, profile photos, contacts, email, or any other data we don't use.
• ✓Access controls: the production database is not exposed on the public internet. The database container has no published host port and is reachable only from within the application's private container network. Direct administrative access requires first reaching the host server, which is restricted to our small operations team via SSH key authentication (no password login) and host-level firewall rules. Application-level access to user data goes through the authenticated API only; cross-user data access is prevented at the SQL layer by always scoping queries to the authenticated user's ID.
• ✓Infrastructure: production servers are hosted in a data centre in the European Union, operated by a Tier IV-equivalent provider. Backups are encrypted, retained for 30 days, and deleted on a rolling basis.
• ✓Provider revocation: you can revoke our access to any third-party platform at any time, either from inside MTShare (Profile → Connected Platforms → Disconnect) or from the provider's own account-permissions page (e.g. myaccount.google.com/permissions for Google/YouTube). When you disconnect, we delete our copy of your tokens immediately.

If you become aware of a security issue affecting MTShare, please email [email protected] with the subject "Security" and we will respond within 72 hours.

YouTube data

When you connect a YouTube account to MTShare to use the Save to YouTube feature, MTShare uses YouTube API Services. By doing so you also agree to be bound by the YouTube Terms of Service and the Google Privacy Policy.

What MTShare accesses, when, and why

• •Create a playlist (one call per save). When you tap Save to YouTube on a playlist page, MTShare calls POST youtube/v3/playlists to create a new private playlist on your YouTube account, named after the source playlist.
• •Add matched videos (one call per video). MTShare then calls POST youtube/v3/playlistItems once per matched video to add it to the playlist created above.
• •Identify your channel (one call at connect time). MTShare calls GET youtube/v3/channels?mine=true&part=id once when you first connect, to record your YouTube channel ID so subsequent saves target the correct account. We do not display, share, or otherwise process the channel ID beyond this internal attribution.

What MTShare does not access

• ✗Your existing playlists, watch history, subscriptions, ratings, or recommendations.
• ✗Any modification or deletion of playlists, videos, or other content you own.
• ✗Video uploads, edits, or moderation on your behalf.
• ✗Comments — read or write.
• ✗View, watch-time, or audience analytics.

What we store and for how long

We store your YouTube OAuth access and refresh tokens encrypted at rest (Fernet with a per-user-derived key) so that subsequent Save actions work without re-authorising every time. We hold no other YouTube-derived data. Tokens are used only to fulfil Save actions you initiate from MTShare; we do not run background jobs that touch your YouTube account.

If you delete your MTShare account or we delete it on your request, all stored YouTube tokens for that account are removed within 30 days, in line with the rest of our retention policy.

How to revoke MTShare's access

You can revoke access at any time, in two ways:

• ✓Open your MTShare profile → Connected platforms → tap Disconnect next to YouTube. This deletes the encrypted tokens from our database immediately.
• ✓Visit Google's third-party access page, find MTShare, and click Remove Access. This revokes the tokens at Google's side; the next time MTShare tries to call YouTube on your behalf, the call fails and we delete our copy of the tokens.

For questions about how MTShare handles YouTube data, email us at [email protected].

Spotify data

When you connect a Spotify account to MTShare to use the Save to Spotify feature, MTShare uses the Spotify Web API. By doing so you also agree to be bound by the Spotify Terms of Service and the Spotify Privacy Policy.

What MTShare accesses, when, and why

• •Identify your account (one call at connect time). MTShare calls GET /v1/me once when you first connect, to record your Spotify user ID so subsequent saves target the correct account.
• •Match tracks via search (one call per track on save). When matching tracks from another platform into Spotify, MTShare calls GET /v1/search to find the closest equivalent on Spotify.
• •Create a playlist (one call per save). When you tap Save to Spotify, MTShare calls POST /v1/users/{user_id}/playlists to create a new private playlist on your Spotify account, named after the source playlist.
• •Add matched tracks (one call per batch of up to 100). MTShare then calls POST /v1/playlists/{playlist_id}/tracks in batches to add the matched tracks to the playlist created above.

What MTShare does not access

• ✗Your existing playlists, library, listening history, top tracks/artists, or followed artists.
• ✗Any modification or deletion of playlists, tracks, or other content you own.
• ✗Playback control or currently-playing state.
• ✗Profile data beyond your Spotify user ID (no email, display name, country, or subscription info is stored).

What we store and for how long

We store your Spotify OAuth access and refresh tokens encrypted at rest (Fernet with a per-user-derived key) so that subsequent Save actions work without re-authorising every time. We hold no other Spotify-derived data. Tokens are used only to fulfil Save actions you initiate from MTShare; we do not run background jobs that touch your Spotify account.

If you delete your MTShare account or we delete it on your request, all stored Spotify tokens for that account are removed within 30 days, in line with the rest of our retention policy.

How to revoke MTShare's access

You can revoke access at any time, in two ways:

• ✓Open your MTShare profile → Connected platforms → tap Disconnect next to Spotify. This deletes the encrypted tokens from our database immediately.
• ✓Visit Spotify's apps page, find MTShare, and click Remove Access. This revokes the tokens at Spotify's side; the next time MTShare tries to call Spotify on your behalf, the call fails and we delete our copy of the tokens.

For questions about how MTShare handles Spotify data, email us at [email protected].

Cookies

We use essential cookies to keep you logged in. We also use Google AdSense which may set its own cookies for ad delivery. You can manage cookie preferences in your browser settings.

Contact

Questions about privacy? Email us at [email protected]