Privacy Policy

Last updated: April 2026

Vibes is built on the premise that your music — and the small, intimate exchanges around it — should not be product input for an algorithm. This document spells out, in plain language, what we collect and what we promise never to do.

Contents
  1. In one paragraph
  2. What we collect
  3. Contact matching (and why your address book stays on your phone)
  4. How we use what we collect
  5. What we never do
  6. Third parties
  7. Your rights
  8. Children
  9. Changes
  10. Contact

In one paragraph

We collect the songs you send and receive (because the recipients have to be able to play them back), your account profile (display name, username, optionally a photo), the friends you follow, and the basic device info Apple gives every app. We do not collect your private listening history. We do not sell your data. Phone numbers used for friend-matching are SHA-256 hashed on your device before they leave your phone — we never see the original numbers, and we cannot reverse the hashes.

What we collect

Account information

When you create an account, we store your display name, username, profile photo (if you set one), and the authentication identifier from your sign-in method (Apple Sign In, Google Sign In, or anonymous). We use Firebase Authentication for this; their privacy policy is at firebase.google.com/support/privacy.

Songs you send and receive

Every song you share — the track ID, the recipient, the timestamp, and any note you wrote — is stored in our database so the recipient can read it. Songs you receive are stored under your account so you can scroll through your inbox.

Friends and follows

The follow graph (who follows whom) is stored so we can render Following lists, the Find Friends results, and the people-you-care-about row on your home tab.

Phone hashes (NOT phone numbers)

If you opt into phone-based friend matching during onboarding, we store a SHA-256 hash of your phone number normalized to E.164 format. The plaintext number never leaves your device. We can match your hash against other users' hashes, but we cannot reverse a hash back to a number.

Reactions, comments, and engagement

If you react to a song or leave a comment, we store the reaction or comment, the song it's attached to, and the timestamp.

Device + technical information

Standard iOS app stuff: device model, iOS version, app version, locale, time zone. We use this for crash reporting (via Firebase Crashlytics) and to debug platform-specific issues.

Apple Music subscription status

If you opt in to Apple Music integration, we ask Apple for your subscription status (active or not). We don't see what you play in Apple Music — only whether you're a subscriber so we can offer full-track playback instead of 30-second previews.

Contact matching (and why your address book stays on your phone)

To find your friends already on Vibes, we use a privacy-first contact matching protocol borrowed from Signal and WhatsApp:

  1. When you tap "Find friends from contacts," the iOS Contacts API gives us your address book on your device only.
  2. We normalize each phone number to E.164 format (e.g., +14155550142) on your device.
  3. We compute a SHA-256 hash of each normalized number on your device.
  4. We send only the hashes to our servers, where we check whether any of them match the hashes of other Vibes users.
  5. We return the matched users' profiles. Hashes that don't match are immediately discarded.

Plaintext phone numbers, names, and addresses from your contacts never leave your device.

How we use what we collect

What we never do

This is the half of the policy that matters most. We will not:

Third parties

We use the following third parties to run the service:

Each of these has its own privacy policy. We do not share your data with anyone else.

Your rights

You can:

If you're in the EU/UK, you have additional rights under GDPR (rectification, restriction, portability, objection). Email us and we'll honor them.

Children

Vibes is rated 12+. We do not knowingly collect data from children under 13. If you become aware that a child under 13 has signed up, contact us and we'll delete the account.

Changes

If we materially change this policy, we'll notify you in-app before the change takes effect. The "last updated" date at the top will reflect any update. We will not retroactively expand the data we collect or how we use it without your explicit consent.

Contact

For privacy questions, GDPR/CCPA requests, or anything else: hi@vibes.app.

⚠️ Note for the maintainer: This document is a starting point drafted for plain-language clarity. Before launch, have it reviewed by a lawyer who knows COPPA, GDPR, and Apple's App Privacy disclosure requirements. The App Store will reject the submission if the in-app App Privacy "nutrition labels" don't match what's in this policy.