Privacy Policy

Last updated: 2026-09-18

This Privacy Policy explains how Importify Limited ("Importify", "we", "us") collects, uses, and protects your personal data when you use Riffloop — our Chrome extension, the Riffloop Studio web app at studio.riffloop.app, the Riffloop app for Android, and the Riffloop app for iPhone (together, the "Service"). Importify Limited is the data controller for the personal data described here.

Importify Limited · Unit 1603, 16th Floor, The L. Plaza, 367–375 Queen's Road Central, Sheung Wan, Hong Kong · riffloopapp@gmail.com

What we collect

• Account. Your email address, plus your name and profile picture if you sign in with Google. You can instead create an account with an email address and password, in which case we store your email and a hashed password. The Android and iPhone apps sign in to the same account. The iPhone app also offers Sign in with Apple: Apple gives us your email address (or, if you choose to hide it, a private relay address that forwards to you) and, on your first sign-in only, the name you choose to share.
• Usage. Records of separations you start (source URL or upload filename, time window, quality, stem) and the resulting outputs.
• Saved sections. Labels, time windows, and stem-mix preferences you save for replay in Studio or the extension.
• Billing. If you upgrade to Pro on the web, PayPro Global (our authorized reseller / merchant of record) handles your payment and card data — we never see card numbers. We keep your PayPro order and subscription IDs, plan, and invoice history. Purchases made inside the Android app are handled by Google Play, which is the merchant for those transactions; we never see your card details there either. We receive and store the Google Play purchase token and the order, subscription and product identifiers, so we can verify the purchase and apply Pro to your account. Purchases made inside the iPhone app are handled by Apple through the App Store, which is the merchant for those transactions; we never see your payment details there either. We receive Apple's signed record of each purchase (the transaction and original transaction identifiers, product identifier, purchase and expiry dates, and whether it was a test purchase) and an app account token, an identifier derived from your Riffloop account ID that lets us match the purchase to your account. Apple also notifies us of renewals, refunds and cancellations, so your plan stays accurate.
• Analytics. We use Google Analytics 4 on the Riffloop website, in the Studio web app and in the extension to understand how the Service is used (see "Analytics" below). This is tied to a random, per-install / per-browser identifier and event data (e.g. which features are used, when a usage limit is reached, upgrade and checkout interactions, your plan tier, and the extension version). It does not include your name, email, or the audio or videos you process.
• Usage events on our own servers. Every part of the Service, including the Android and iPhone apps, also reports a short record of what you do to our own servers, so we can see which features are used and where people get stuck. If you are signed in, that record is stored against your account and kept until you delete the account. If you are not signed in, it is stored under a random identifier instead and deleted after 90 days; the apps send nothing at all until you are signed in, and hold their records on your phone until then. Each record is one event name from a fixed list, plus a few numbers and short words. The list covers opening the app, signing in and out, adding a song, the steps of the first-run walkthrough, starting, finishing, failing or stopping a separation, downloading a separation model, reaching a free-plan limit, the upgrade screen and what happened next including a purchase, and using a feature such as chords, the metronome, key, speed, a saved loop, muting a part, exporting, or starting playback. The numbers and words are things like the plan you tapped, how long a separation took, or how many parts you asked for. A record never contains song titles, file names, URLs, video identifiers, your email or the audio itself, and a separation that fails reports the type of error, never its message. These events stay with us: they are not shared with anyone, not used for advertising, and not used to track you across other companies' apps or websites.
• Uninstall feedback. If you remove the extension and choose to answer the short "Before you go" survey, we collect the reason you select, any optional free-text note you submit, your plan tier, and the anonymous per-install identifier.
• Technical. Standard server logs (IP address, user agent, timestamps), kept for up to 30 days for security and abuse prevention.

What we don't collect

• The Riffloop browser extension, the Android app and the iPhone app separate audio entirely on your device — that audio is never uploaded to our servers. The Android app has no upload capability at all: the songs you add, the stems it produces and anything you record with it stay in the app's own storage on your phone. The iPhone app works the same way.
• We don't send the audio you process, or the specific videos you watch, to our analytics. The usage events described above carry no song titles, file names, URLs or video identifiers either.
• If the Android app crashes it writes the error to a file on your phone, so it can show you what happened the next time you open it. That file is never sent to us.
• We don't keep uploaded audio files after separation completes — they're deleted within 24 hours. This applies to audio you upload to Riffloop Studio on the web; the Android and iPhone apps never upload audio.
• We don't keep separated stems indefinitely — stems cached by the web app are pruned after 7 days of inactivity.
• We don't sell or rent your personal data, and we don't use it for cross-site advertising.

How we use it

• To run the Service: separate audio, sync your sections, enforce usage limits.
• To bill you (via PayPro Global, Google Play or the App Store) if you purchase Pro.
• To understand and improve the Service: which features are used, and where people get stuck. On the website, in Studio and in the extension this includes aggregate, pseudonymous analytics; the usage events described above are linked to your account while you are signed in.
• To prevent abuse (rate limits, Terms enforcement) and keep the Service secure.
• To respond to your support requests.

The Riffloop app for Android

The Android app does its work on your phone. Separation runs on the device, using models the app downloads from Google Play — your songs are never sent to us, and the app has no feature that uploads audio.

• What the app sends us. Only account and practice data: signing in, checking your plan and your daily separation allowance, verifying a Google Play purchase, and syncing the sections and loops you save (their titles, labels, time positions and stem-mix settings). No audio is included.
• What the app reports about its use. Once you are signed in, the app reports the usage events described under "What we collect" to our own servers over an encrypted connection, linked to your account, so we can see which features are used and where people get stuck. They carry numbers and short words only, never song titles, file names or URLs. The app contains no third-party analytics or advertising SDK: the events go to us and nobody else, they are not used for advertising, and they are not used to track you across other companies' apps or websites. They are deleted when your account is deleted.
• Microphone and recorded audio. If you use the app's capture feature, Android asks your permission and shows its own recording indicator. What is recorded is written to the app's private storage on your phone so you can trim it and practise with it. It is never uploaded to us.
• Screen-capture permission. Capturing audio that another app is playing uses Android's media-projection permission, which you grant in Android's own dialog each time. We use it only to record audio; the app does not capture, store or transmit images of your screen.
• Notifications. With your permission, the app shows a notification while a separation is running and when it finishes, so you can leave the app meanwhile. Nothing is sent to us.
• Removing your data. Uninstalling the app deletes everything it stored on your phone. To delete the account itself and the data we hold on our servers, including your usage events, email us and we will remove it within 30 days.

The Riffloop app for iPhone

The iPhone app (iOS 26 or later) also does its work on your phone. Separation and chord and beat analysis run on the device, and your songs are never sent to us.

• What the app sends us. Only account and practice data: signing in, checking your plan and your daily separation allowance (each separation is counted with the song's title, the part you chose and the quality), verifying an App Store purchase, and syncing the loops you save (their titles, labels, time positions and the part they play). No audio is included.
• Signing in. You can use Sign in with Apple, Google, or an email address and password. Google sign-in opens in a secure browser window and then returns you to the app. The app keeps your sign-in token in the iOS Keychain on your phone.
• What the app reports about its use. Once you are signed in, the app reports the usage events described under "What we collect" to our own servers over an encrypted connection, linked to your account, so we can see which features are used and where people get stuck. They carry numbers and short words only, never song titles, file names or URLs. They are deleted when your account is deleted.
• Separation models. The app downloads its separation and analysis models from Apple, using Apple's Background Assets service. These downloads come from Apple, not from us, and carry none of your songs or account data.
• Capturing audio from other apps. If you use the app's capture feature, it records the audio another app is playing through Apple's ReplayKit screen broadcast, which you start yourself. iOS shows its recording indicator while the broadcast runs. The app keeps only the audio: iOS also passes it frames of your screen, which the app ignores and never stores or transmits. The capture feature does not use the microphone. The recording is saved on your phone so you can trim it and practise with it, and it is never uploaded to us. Audio that the playing app protects from copying cannot be captured.
• Notifications. With your permission, the app shows a notification when a separation finishes. The notification is created on your phone. The app does not use push notifications, and nothing is sent to us.
• No tracking. The app contains no third-party analytics or advertising SDK. Its usage events go to our own servers and nobody else, and are not used for advertising. The app does not track you across other companies' apps or websites, and it does not ask for Apple's tracking permission.
• Purchases. Pro bought in the app is billed by Apple (see "Billing" above). It applies to your Riffloop account, so it also works on the web and in the Android app. Refunds and cancellations for these purchases go through Apple.
• Deleting your account. In the app, go to Profile > Delete account. This deletes your Riffloop account and the data we hold for it, including your saved loops and your plan, and deletes the songs and stems stored on that phone. Deleting your account does not cancel an App Store subscription: Apple keeps billing it until you cancel it in your Apple Account's subscription settings. Uninstalling the app also deletes everything it stored on your phone.

Analytics (Google Analytics 4)

We use Google Analytics 4, a service provided by Google, to collect pseudonymous usage statistics across the Riffloop website, the Studio web app, and the extension. Analytics events are associated with a random identifier stored on your device (a cookie on our websites, or an identifier in extension storage for the extension) — not with your name or email. On our websites, Google Analytics sets cookies (e.g. _ga, _ga_<id>). We use this data only in aggregate to improve the Service; we do not use Google Analytics for advertising. Google processes this data as described in its own privacy policy. The Riffloop apps for Android and iPhone do not use Google Analytics, or any other third-party analytics SDK. They report usage events to our own servers instead, as described under "What we collect".

Cookies & local storage

We use a small number of cookies and similar technologies:

Essential cookies are required for the Service to function. Analytics cookies help us improve it. You can control or delete cookies through your browser settings; blocking essential cookies may prevent sign-in from working.

Third-party services

• Google — sign-in (Google account) and Google Analytics.
• Google Play — distribution of the Android app, in-app purchases (the merchant for purchases made in the app), and delivery of the separation engines the app downloads.
• Apple: Sign in with Apple, distribution of the iPhone app, in-app purchases through the App Store (the merchant for purchases made in the iPhone app), and hosting of the separation models the iPhone app downloads (Background Assets).
• PayPro Global — billing / payment processing (merchant of record) for purchases made on the web.
• Cloudways / DigitalOcean — hosting infrastructure.

Each has its own privacy policy governing the data it processes.

Legal bases for processing (EEA / UK)

Where the EU or UK GDPR applies, we rely on the following legal bases:

• Performance of a contract — to provide the Service and process your purchases (account, usage, saved sections, billing).
• Legitimate interests — to secure the Service, prevent abuse, and improve the product through the analytics and usage events described above, balanced against your rights.
• Consent — where required for analytics cookies or similar technologies; you may withdraw consent at any time.
• Legal obligation — to keep billing and tax records.

International data transfers

Importify Limited is based in Hong Kong, and our service providers (including Google, Apple, PayPro Global, and DigitalOcean) may process data in various countries, including outside the EEA and the UK. Where personal data is transferred internationally, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (or equivalent) offered by those providers.

Data retention

• Uploaded audio: deleted within 24 hours of separation.
• Cached stems: pruned after 7 days of inactivity.
• Server logs: up to 30 days.
• Anonymous analytics events: 90 days.
• Usage events linked to your account: until you delete your account, at which point they are deleted with it.
• Account, saved sections, usage history: until you delete your account (then removed within 30 days), subject to any records we must retain by law.
• Billing records: retained as required for tax and accounting purposes.
• On your Android device: the songs, stems and recordings the app creates stay on your phone until you delete them or uninstall the app. We never receive them.
• On your iPhone: the songs, stems and recordings the app creates stay on your phone until you delete them, delete your account, or uninstall the app. We never receive them.

Your rights

Depending on where you live, you have some or all of the following rights over your personal data:

• Access — request a copy of the data we hold about you.
• Rectification — correct inaccurate or incomplete data.
• Erasure — delete your account and associated data (available in Settings, or by contacting us).
• Restriction & objection — restrict or object to certain processing, including analytics based on legitimate interests.
• Portability — receive your data in a portable format.
• Withdraw consent — where processing is based on consent.

To exercise any of these, email riffloopapp@gmail.com. If you are in the EEA or UK and believe we have not handled your data properly, you have the right to lodge a complaint with your local data protection supervisory authority.

California residents

If you are a California resident, you have the right to know what personal information we collect, to request its deletion or correction, and to opt out of the "sale" or "sharing" of personal information. We do not sell or share your personal information, and we will not discriminate against you for exercising your rights. Submit requests to the email above.

Children

Riffloop is not directed at children. We do not knowingly collect personal data from children under 16 (or the minimum age of digital consent in your country, which may be as low as 13). If you believe a child has provided us data, contact us and we will delete it.

Changes to this policy

We may update this Policy from time to time. We will post the new version with an updated "Last updated" date and, for material changes, notify signed-in users by email.

Contact

Importify Limited — privacy enquiries and data requests: riffloopapp@gmail.com

Unit 1603, 16th Floor, The L. Plaza, 367–375 Queen's Road Central, Sheung Wan, Hong Kong