Sazly Privacy Policy

Who we are

Sazly is published by Almoutasem Nabil (“we”, “us”), based in Jordan. We are responsible for the personal information described in this policy. You can contact us at support@pipekit.tech.

This policy uses these terms for the different ways people use Sazly:

Signed-in users

People who use the Sazly iOS app with Sign in with Apple or Google Sign-In.

Hosts

Signed-in users who start a shared ride and play music from their Apple Music subscription.

App guests

Signed-in users who join someone else’s ride in the iOS app.

App Clip guests

People who join a ride in the Sazly App Clip, with a first name and no account.

Web guests

People who join a ride on sazly.online in a web browser, with a name and no account.

Information we collect

Signed-in users

• Sign in with Apple. Apple shares the name and email address you choose to share. The email may be your real address or an Apple private-relay address. Firebase Authentication (Google) stores that email and name, and the app uses the name to pre-fill your profile.
• Google Sign-In. Google shares your name, email address and profile photo. Firebase Authentication stores your email and a link to your Google profile photo, and the app suggests your Google name as your display name.
• Your profile. We store your display name, your unique username, your profile photo, the email address from your sign-in and the date you joined. The profile photo is either your Google photo link or a photo you pick in Edit Profile, which is resized to 256 pixels and stored in your profile record. Picking a photo doesn’t give Sazly access to your photo library. If you use Sazly Pro, your profile also holds your Pro status and any custom join code.
• Friends. You find friends by their exact @username or by scanning their profile QR code. When you send a friend request, your display name and username are saved in the other person’s requests, and theirs are saved in your list of sent requests. When a request is accepted, each of you is saved in the other’s friend list with a display name and username. If you change your name or username, your entry in your friends’ lists is updated.
• Notifications. The first time you open the app, it asks for permission to send notifications. Every install gets a push token from Apple’s push service and Firebase Cloud Messaging. While you’re signed in, that token is saved to your profile record, along with the platform and the time it was last updated. This starts as soon as you sign in, before you have finished setting up your profile. We use it to notify you about friend requests and accepted requests, and to tell hosts when someone joins their ride or requests a song. Notifications include names, usernames and, for song requests, the song title and artist.
• Camera. The camera is used only to scan QR codes, and only when you choose to scan. Sazly uses the text in the code (a room code or a friend’s profile link). Sazly doesn’t save or upload camera images.
• Ride history. A summary of every ride you host or join is saved to your account (see Everyone in a ride).

The app asks for access to Apple Music, the camera and notifications only. It doesn’t ask for your location or contacts.

Hosts

• Your Apple Music library. See Apple Music and your library.
• The ride record. When you start a ride, we store the room code, your Sazly user ID and display name, a random identifier created when the app was installed, the music service, your ride settings (including the car colour and the user IDs of riders you banned), what’s playing (the song, whether it’s playing and the position), what’s up next (the first 25 songs plus any requested songs), the size of your library and when the ride started and was last active. The app keeps this record up to date while the ride is live.
• Searches for your riders. When a guest searches Apple Music, the search runs on your phone, using your Apple Music account and your country’s catalogue, and the results are sent back to the ride.
• Live Activity. Your lock screen and Dynamic Island can show the room code, the current song and artist, what’s up next, how many requests and riders there are, and the car colour. This is shown on your device and not sent to us. Small copies of the album artwork are saved on your device for it.
• Custom join code (Pro). A code you claim is saved with your user ID in a list of reserved codes and copied to your profile.
• Ride allowance. Our server keeps a count of the shared rides you have started this month (in UTC). It updates the count when the first guest joins a ride.

Everyone in a ride (hosts and all guests)

What you do in a ride is stored in that ride on our servers and can be seen by the host and everyone else in it:

• Your membership: your display name, your username (signed-in users only), when you joined, whether you are the host, and whether the host has blocked you.
• Song requests: the song’s details, your user ID and name, the request’s status, and the user IDs of people who voted for it.
• Searches: the text you searched for, your user ID and the results. The host’s phone deletes each search about 90 seconds after answering it.
• Reactions: an emoji, your user ID, your name and the time. In the iOS app and App Clip, a reaction can also carry a small image (a Genmoji, a sticker, or any image you paste, including a photo), shrunk to at most 112 pixels. The web page sends emoji only.
• Votes on the current song: 👍 or 👎, the song’s ID, your user ID, your name and an optional reaction.
• Playback commands: play, pause, next or previous, with your user ID and name. The host’s phone deletes each command once it has carried it out.
• Ride summary. When a ride ends, a summary is saved to the ride history of the host and of every rider still in the ride at that moment, App Clip and web guests included. Riders who left or were removed earlier don’t get a copy. It contains the host’s name, the ride’s name if it has one, the start and end times, the number of songs played, the number of people in the ride when it ended, the number of reactions, the most-voted song, the name of the person (host included) with the most songs played or queued and how many that was, and up to 60 played songs (title, artist, album, length and an artwork link). It doesn’t list every rider’s name, reaction or image. Each copy can only be read by the account it belongs to.

App guests

App guests are signed-in users, so everything under Signed-in users and Everyone in a ride applies.

App Clip guests

• Anonymous sign-in. The App Clip signs you in with Firebase Anonymous Authentication. This creates a random user ID with no email or password, and the ID is reused on later visits.
• Your first name. The name you type is used in the ride and saved on your device inside the App Clip, so you don’t have to type it again.
• Ride data as described in Everyone in a ride, including optional image reactions. A ride summary is saved under your anonymous user ID when the ride ends, but the App Clip has no screen for viewing it.
• The App Clip doesn’t include analytics or push notifications, and it doesn’t use the camera or your location.

Web guests (sazly.online)

• Anonymous sign-in. The page signs you in with Firebase Anonymous Authentication. This creates a random user ID with no email or password, and the ID is reused on later visits from the same browser.
• Your name (up to 24 characters), used in the ride.
• Ride data as described in Everyone in a ride (emoji reactions only). A ride summary is saved under your anonymous user ID when the ride ends, but the web page has no way to view it.
• Browser storage. The page saves your name and the ride’s code, so it can rejoin you after a refresh; these are cleared when you tap Leave or enter another code. It also saves your language choice. The Firebase library saves your anonymous sign-in and a local copy of ride data (including other riders’ names in the queue) in your browser’s storage. Leaving a ride doesn’t clear these; clearing this site’s data in your browser does.
• No cookies, analytics or ads. The page sets no cookies and loads no analytics, advertising or third-party embeds.
• Connections to providers. To work, the page is served by Firebase Hosting, loads the Firebase library from Google (gstatic.com), connects to Google’s Firebase servers, and loads album artwork from Apple’s servers. Like any web server, these receive your IP address and standard browser information, and Apple’s artwork servers may see that the request came from sazly.online.

Everyone using the iOS app

• Images from Apple and Google. Album artwork is loaded directly from Apple’s servers, and a Google profile photo from Google’s servers. Those servers receive your IP address.
• Sharing you choose to do. You can share an invite (the room code and a sazly.online link) or a recap image (the host’s name, the ride’s name and stats, the top requester’s name and up to 9 album covers) through the iOS share sheet or to Instagram Stories. Only the app you pick receives it. Sazly doesn’t include an Instagram SDK. For Instagram, the image is put on the clipboard and expires after 5 minutes.
• Information on your device. See Information stored on your device.

Apple Music and your library

• What Sazly reads. With your permission, Sazly uses Apple’s MusicKit to read your Apple Music subscription status, your library songs and playlists (the name and artwork of each playlist, and its songs when you pick one), and your App Store country. It also searches and looks up songs in the Apple Music catalogue.
• Your library list. When you open the Host screen, Sazly reads your whole library. For each song that is in the Apple Music catalogue it keeps the catalogue ID, title, artist, album, length and an artwork link. This list is saved on your device as a cache and stays there until you delete the app or iOS clears the app’s cache. Signing out or deleting your account doesn’t remove it.
• When you start a ride, the whole list is uploaded to that ride on our servers so that riders can browse it. Anyone who joins the ride can read it, and joining doesn’t need your approval: anyone can find a live ride and join it unless you lock joining or ban them (see Anyone using Sazly). The list is deleted when you end the ride (see How long we keep information for rides that aren’t ended normally).
• Also shared with your ride: what’s playing, what’s up next and the results of guests’ searches. Song titles and artists appear in notifications about requests, and up to 60 played songs are kept in ride summaries.
• Never sent: audio, your Apple Music account credentials or tokens, and playable music. Sazly doesn’t send the App Store country that MusicKit reports; it writes it only to logs on your device. Your App Store country is still included in purchase data (see Purchases and Sazly Pro).
• “Save ride as playlist” creates a playlist in your Apple Music library.

We use Apple Music data (your library, playlists, what’s playing and your queue) only to run rides and Sazly’s features. We never use it for advertising or marketing, never use it to identify you or your device, and never share it with third parties except service providers that help us run and improve Sazly and the people who can see ride records as described in What other people can see.

Apple handles MusicKit requests under its own privacy policy. Sazly currently works with Apple Music only.

Purchases and Sazly Pro

• Apple processes all payments. We never receive your card or bank details or your Apple Account password. Our servers don’t store the price you paid, your currency or your Apple Account details, although the signed transaction the app sends to verify a purchase contains the price and currency (see below).
• Linking a purchase to your account. Every purchase carries an “app account token” created from a one-way hash of your Sazly user ID, so Apple’s records of the purchase can be matched to your account. The app saves which user ID each token belongs to on our servers.
• Verifying purchases. After a purchase or restore, and when the app opens if our servers don’t yet reflect a purchase, the app sends the signed transaction from Apple to our server (a Cloud Function), which checks Apple’s signature. The signed transaction contains transaction IDs, the app’s bundle ID and the product ID, purchase, signing and expiry dates, the app account token, the App Store country (storefront), the price and currency, any offer used, whether it was bought directly or shared through Family Sharing, whether it was a live or test purchase, and device-verification values that Apple includes. Our server doesn’t store the signed transaction itself. Restore Purchases asks the App Store to sync your purchases, which may ask you to sign in to your Apple Account.
• Updates from Apple. Apple sends our server notifications about renewals, expiries, refunds and revocations, which we use to keep your Pro status correct.
• What we store:
  • for each kind of purchase (subscription, Lifetime or Day Pass): the product ID, the original transaction ID, whether it’s active, the expiry date, whether it’s in a billing grace period, whether it was a live or test purchase, the latest event (for example, a renewal or a refund) and when it was updated;
  • which Sazly account claimed each purchase, and whether it was refunded or revoked;
  • your Pro status on your profile: whether it’s active, when it expires, which product, that it came from the App Store and when it last changed; and
  • your ride count for the current month.
• Why: to unlock Pro on every device where you sign in, to apply the free tier’s limits, and to stop a refunded purchase, or one that belongs to another account, from being used.

Your Pro status can be read and listed by anyone signed in, including anonymous guests. See Anyone using Sazly.

How we use information

• To provide Sazly: signing you in, profiles and friends, running rides (the library, queue, searches, votes, reactions and playback), and ride history.
• To send notifications you have allowed.
• For Sazly Pro: verifying purchases, unlocking Pro, applying free-tier limits and preventing misuse of purchases.
• For safety: host tools such as blocking and banning, enforcing our Terms and responding to reports.
• To diagnose problems and keep Sazly working and secure, using server logs.
• To comply with the law and respond to lawful requests.

Where the law requires a legal basis (for example, in the EEA or UK), we rely on performing our agreement with you to provide Sazly; on our legitimate interests in keeping Sazly secure, diagnosing problems and preventing purchase misuse; on your consent for device permissions such as notifications, camera and Apple Music access; and on legal obligations where they apply.

Service providers

We use these providers to run Sazly. They process information on our behalf or as described.

We share personal information with service providers only as needed to run Sazly. Every service provider that processes personal information for us, including Google (Firebase and Google Sign-In), may use it only to provide its service to us, is required to protect it to the same or an equal standard as this policy, and may not use it for its own purposes such as advertising. Apple provides Sign in with Apple, MusicKit, the App Store and push notifications under its own privacy policy.

Google (Firebase and Google Sign-In)

• Firebase Authentication: sign-in, including anonymous sign-in for guests.
• Cloud Firestore: our database for profiles, friends, rides, ride history and purchase records.
• Cloud Functions: sending notifications, counting rides and verifying purchases. Our functions run in Google’s us-central1 region in the United States.
• Firebase Cloud Messaging: delivering push notifications, with Apple’s push service.
• Firebase Hosting: serving sazly.online.
• Google Cloud Logging: server logs. When our functions send a notification, they log the recipient’s user ID and the notification’s title, which includes names such as “Sam joined your ride”. Purchase handling logs user IDs, product IDs and, in some cases, original transaction IDs. Google’s platform also records standard request information, such as IP address and user agent.
• Firebase Analytics: the iOS app includes Google’s Firebase Analytics library, but analytics collection is switched off in the app’s configuration, so no analytics events are sent. The App Clip and the web page don’t include analytics.
• Google Sign-In, if you choose to sign in with Google.

Apple

• Sign in with Apple, including revoking Sazly’s access to your Apple sign-in when you delete your account.
• MusicKit and Apple Music, for your library, catalogue search and playback.
• The App Store, for payments, purchase verification data and Restore Purchases.
• The Apple Push Notification service, and Apple’s servers that host album artwork.

Spotify

The iOS app includes Spotify’s iOS software development kit, which is set up when the app opens. Spotify hosting isn’t currently offered, so Sazly doesn’t sign you in to Spotify or use the kit to connect to Spotify. We will update this policy before offering Spotify hosting.

Apps you share to

When you share an invite or a recap image, the app you choose, such as Messages or Instagram, receives what you share under its own privacy policy.

Legal and business reasons

We may disclose information if the law requires it, to protect the rights, property or safety of our users, the public or us, or as part of a merger, acquisition or sale of Sazly, in which case this policy continues to apply to your information.

What other people can see

People in the same ride

The host and every rider can see:

• your display name, and your username if you’re signed in;
• songs you request, with your name on them, and your votes;
• your reactions, with your name and any image you send;
• playback commands you send, shown with your name;
• the text of catalogue searches you run, with your user ID and the results, for about 90 seconds after the host’s phone answers them;
• the host’s name, the host’s library list, what’s playing, what’s up next and the car colour.

The host also receives notifications with riders’ names and the songs they add. After the ride, the name of the person (host included) with the most songs played or queued appears in the ride summary of everyone still in the ride when it ended.

Friends

People you send friend requests to, and your friends, see your display name and username.

Anyone using Sazly, including people outside your rides

Anyone can get an anonymous sign-in, with no account and nothing to enter, just by opening sazly.online in a web browser. The App Clip gives out the same kind of sign-in. Under our current database access rules, anyone signed in, including those anonymous guests, can use their own tools to read and list the records below, even if they aren’t your friend and aren’t in your ride. In practice, anyone with a web browser can download these records for every user and every live ride:

• Profile records of signed-in users: display name, username, profile photo, email address, push notification token with its platform and when it was last updated, custom join code, Pro status (whether it’s active, when it expires, which product and when it last changed) and when the account was created. Someone who signed in but didn’t finish setting up a profile can still have a record holding their push token.
• Live ride records for every live ride: the room code, the host’s name and user ID, the random install identifier, what’s playing and up next, and ride settings, including the user IDs of banned riders. Because these records can be listed, anyone can find live rides and their codes without being given a code, and can link a host’s user ID to their profile, including their email address.
• Every username and every custom join code, with the user ID that owns it. Because a custom code doesn’t change, anyone who knows it can see when you’re hosting, your host name and what’s playing.

Joining a ride doesn’t need the host’s approval. Anyone signed in can join any live ride, including one they found by listing rides, unless the host has locked joining or banned them. Once they have joined, they can read everything inside the ride: the host’s library list, the queue, searches, riders’ names, reactions and images, votes and playback commands. A join also sends the host a notification with the name the person entered and, on the free tier, can count as one of the host’s rides for the month.

People you share with

Invites and recap images you share are seen by whoever you send them to, and by anyone they pass them on to.

No selling, ads or tracking

• We don’t sell or rent your personal information.
• Sazly shows no ads, and we don’t use advertising networks or attribution services.
• We don’t track you across apps or websites owned by other companies. Sazly doesn’t ask for tracking permission, so it can’t access your device’s advertising identifier.

How long we keep information

Deleting your account and data

How to delete your account

In the Sazly iOS app, go to Settings → Delete account. You’ll be asked to sign in again with Apple or Google to confirm.

If you signed in but didn’t finish setting up your profile, the app can’t delete that sign-in yet. Your sign-in account (with your email address) and a profile record holding your push token may already exist. Email us at support@pipekit.tech with the email address you signed in with, and we will delete them.

What deleting your account removes

• Any ride you are hosting is ended, and you leave any ride you have joined.
• Your profile record: display name, username, email address, profile photo, push token, custom join code link and Pro status.
• Your username reservation and your own friend list.
• Your Firebase Authentication account.
• If you signed in with Apple, the app asks Apple to revoke Sazly’s access to your Apple sign-in. If you signed in with Google, the app signs you out of Google on your device.

What remains after deletion

The current deletion process doesn’t remove:

• your ride summaries, including the summary created when deletion ends a ride you were hosting;
• friend requests you received or sent, including requests waiting in other people’s inboxes;
• your display name and username in your friends’ friend lists;
• ride summaries in other riders’ histories that name you as the host or the top requester;
• your custom join code reservation, which stays linked to your former user ID;
• purchase records, app account tokens and your monthly ride count;
• server logs; and
• information stored on your device, such as the library cache, artwork and settings, until you delete the app.

To ask us to delete information that remains, email support@pipekit.tech with your username or the email address you signed in with. We may keep records we need for legal reasons or to handle purchases and refunds.

Signing out

Signing out in Settings ends any ride you’re hosting, leaves any ride you’ve joined, asks our servers to remove the push token from your profile, removes the token from your device, and signs you out of Google and Firebase. Removing the token from your profile is best effort (see How long we keep information), and signing out from the profile setup screen doesn’t remove it. Signing out doesn’t delete your account, the library cache, the app’s local copy of Sazly data or other data on your device.

Guests

Tapping Leave removes your membership from the ride. On the web page, Leave also clears your saved name. The App Clip and web page have no way to delete your anonymous sign-in or your copy of a ride summary. You can remove what’s on your device by clearing sazly.online’s site data in your browser or removing the App Clip. For copies on our servers, email us with the room code, the date and the name you used, so that we can find them.

Information stored on your device

iOS app

• Settings and preferences: onboarding status, library sort order, car colour and background choices, your music service choice, when you were last asked for a review, when you last tapped a ride recap, and a few flags about whether you have joined or hosted a ride (kept on your device only). If Spotify was ever connected on the device, its saved sign-in is kept here too.
• A local copy of Sazly data: the database library keeps a cache of Sazly data the app has loaded, such as your profile, profiles you looked up (which can include other people’s email addresses), friends and friend requests, ride history, and ride data including queues, riders’ names, reactions and images, and host library lists. Signing out or deleting your account doesn’t clear it; it stays until you delete the app.
• Identifiers and codes: a random install identifier (which is also part of the ride record when you host), the code of the last ride you joined, and your custom join code.
• Files: the cache of your Apple Music library list, small artwork images for the Live Activity, and recap images in a temporary folder.
• Keychain: Firebase and Google Sign-In store their own sign-in data.
• Device logs: the app writes technical logs to iOS’s system log that can include song titles, riders’ names on playback commands, push tokens and error details. They stay on the device unless you share a diagnostics report.

Signing out clears the last-joined ride code and the saved custom join code. The rest stays until you delete the app.

App Clip

Your first name, your anonymous sign-in and a local copy of ride data. They stay until iOS removes the App Clip and its data. Leaving a ride doesn’t clear your saved name.

Web page

See Web guests. The page sets no cookies.

Children

Sazly isn’t directed to children under 13, and we don’t knowingly collect personal information from children under 13. If you believe a child under 13 has given us personal information, contact us at support@pipekit.tech and we will delete it.

International transfers

We are based in Jordan, and our providers process information in other countries. Our Cloud Functions run in Google’s us-central1 region in the United States. Google Firebase and Apple may store and process information in the United States and other countries where they operate. These countries may have data protection laws that differ from the laws where you live.

Security

• Access to our database is controlled by Firebase Authentication and security rules. What happens inside a ride can only be read by people who have joined it, but joining doesn’t need the host’s approval unless the host locks joining. Ride summaries can only be read by the account they belong to. Detailed purchase records can only be read by our server; the Pro status on your profile is the exception described below.
• Some records are readable more widely, as explained in Anyone using Sazly.
• Purchases are verified against Apple’s signatures on our server.
• Sazly’s apps and web page connect to Firebase over encrypted (HTTPS) connections.

No system is completely secure. If you find a security problem, please tell us at support@pipekit.tech.

Your rights and choices

Choices in the app and on your device

• Turn notifications, camera and Apple Music access on or off in iOS Settings.
• Change your name, username and photo in Edit Profile.
• Remove friends, and decline or cancel friend requests.
• Release a custom join code with “Give the code back”.
• Leave a ride, sign out, or delete your account.
• Clear sazly.online’s site data in your browser, or remove the App Clip.

How to withdraw consent

• Notifications, camera and Apple Music: turn them off for Sazly in iOS Settings.
• Sign in with Apple: stop using Sign in with Apple for Sazly in iOS Settings → [your name] → Sign-In & Security → Sign in with Apple.
• Google Sign-In: remove Sazly from the third-party connections in your Google Account.
• Anything else: email us at support@pipekit.tech.

Your rights

Depending on where you live, you may have the right to access the personal information we hold about you, correct it, delete it, receive a copy in a portable format, restrict or object to how we use it, and withdraw consent you’ve given. You also have the right not to be treated differently for using these rights. To make a request, email support@pipekit.tech. We may need to confirm that the information is yours before we act. You can also complain to your local data protection authority.

Payment and billing records are held by Apple. For those, use your Apple Account settings or contact Apple.

Changes to this policy

We will update this policy when the way Sazly handles information changes, and we will change the “Last updated” date above when we do. If a change is significant, we will let you know in the app or on this site before it takes effect.

Contact

Almoutasem Nabil
Jordan
Email: support@pipekit.tech