Privacy Policy
How this website and IROMUSIC handle your data.
Last updated: October 7, 2026
1. Scope
This policy covers two things: this marketing website (iromusic.live) and the IROMUSIC app and service, operated by IROMUSIC Team.
2. What this website stores
iromusic.live itself is a static site with no analytics, no tracking pixels, and no third-party cookies. The only thing it stores in your browser is a single localStorage entry, iromusic_lang, to remember whether you prefer the Persian or English version. It never leaves your device and isn't sent to any server.
3. Information the app/service may collect
To provide an account, sync your library across devices, and enable playback and downloads, the IROMUSIC app/service may collect: account details you provide (e.g. email, device identifiers), usage data (what you play, download, or search for), and technical data (device type, app version, crash logs). Each time you sign in on a device, we also store the IP address and the user agent (browser or app identifier) of that sign-in. You can also give us a mobile number; that is optional, and it is stored with your account. We keep these while your account exists, including after you sign out of a device, and erase them with the rest of your account data after you delete your account (see "Data retention").
Analytics and crash reports. The IROMUSIC app has one setting, "Share Analytics" (Settings, Privacy). It is on by default in the web app and the Android, iOS and macOS apps, and off by default in the browser extension. When it is on, the app sends usage events (for example screens opened, searches run, plays and downloads) and crash reports to Google Firebase. On Windows and Linux, and in the web app, crash reports go to our own server instead. On Windows and Linux, the Share Analytics setting exists from app version 6.3.5. It is on by default there, and turning it off stops the app from sending error reports and failed-download reports to our server. Earlier versions of the Windows and Linux apps have no such setting, so it cannot be turned off there, and they send error reports to our server by default. On the other platforms, when you turn the setting off, the app stops sending new reports from that device. Failed-download reports are the exception: even with Share Analytics off, when a download fails, the web app and the Android, iOS and macOS apps still send our server a report that names the file (its catalogue ID and the host name it was fetched from, not the full link), the type of error, and the app version and platform, without your account details. On Windows and Linux these reports stop only from app version 6.3.5; earlier versions there send them as well. Turning it off does not delete reports that were already sent. Because the setting is on by default, collection starts at first launch, before you have opened the setting.
Search history. When you are signed in, we store the text of the searches you run, with your account, to show recent searches and suggestions and to see which searches return nothing. You can download it with your account data. We keep it for 90 days after you last ran the search, or until you delete your account. A weekly summary of searches that returned nothing is prepared with an AI service (see "Processing by the AI provider").
Problem reports. If you report a problem, the category you pick, the text you write, your answers, the app version and platform, and a keyed hash of your network address are stored. Guests can report too. We blank the text, your answers, the address hash and our internal notes 90 days after a report is closed, and remove the emptied record a year after that, which is 455 days (about 15 months) after it was closed. Reports that are still open are kept until they are handled. If you delete your account, your reports stay but are no longer linked to you.
4. How that information is used
To operate the service (authentication, sync, recommendations), maintain security, fix bugs, and improve the product. We don't sell your personal data.
5. Third parties (sub-processors)
We share the data below with these providers, only as needed to run the service:
- Google Sign-In — if you sign in with Google, we receive your email, name, and profile photo from your Google account.
- Firebase Analytics and Google Analytics 4 (Google) — usage events from the app (see "Analytics and crash reports"). Events carry a content identifier or a screen name, never search text. If you are signed in, events are linked to a pseudonymous user identifier derived from your account number, and to your plan, app language and profile type. Google receives the technical data its SDK collects by default, such as device and approximate location information. Google signals is turned off.
- Firebase Crashlytics (Google) — crash and diagnostic reports from the Android, iOS and macOS apps, while "Share Analytics" is on (it is on by default).
- Firebase Cloud Messaging (Google) — your device's push token, to deliver push notifications.
- Object storage — an S3-compatible storage provider hosts media files and cover art.
- AI model gateway — see "Processing by the AI provider" below.
- Telegram — if you link a Telegram account to receive deliveries, we store your Telegram chat identifier and name and send messages through the Telegram bot interface.
- Email delivery provider — we send account and service email through an SMTP provider, which receives the recipient address and message. We may also send occasional release announcement emails; each one has an unsubscribe link.
We don't have a live payment processor yet — checkout is currently disabled.
Processing by the AI provider. We use an AI model gateway to run some features. It is operated by us and forwards requests to the model providers it routes to, which we do not control and cannot name here. What is sent: (1) every week, up to 30 of the most frequent search phrases, taken from all signed-in users, that returned no results, with no account identifier, to write an internal summary of gaps in the catalogue; (2) catalogue information such as titles and genres, to write tags, short descriptions and artist notes; (3) when an internal incident diagnosis is turned on, error text from our servers after we remove keys, tokens and email addresses with a fixed set of rules. Before the weekly digest is sent, search phrases that contain an email address, a web address or domain name or a run of seven or more digits are removed; the other phrases are sent as typed. The app does not currently send your searches to the gateway for natural-language search. We record the model name, the amount of text and the duration of each call, and keep those records for 90 days.
6. Data retention
We keep account and usage data while your account exists. If you delete your account, you are signed out of every device immediately, your email address is released, and the remaining personal data is permanently erased 30 days later. Some records are kept on a fixed schedule instead:
| Record | How long we keep it |
|---|---|
| Search history | 90 days after you last ran the search, or until you delete your account. |
| Problem reports | Text, answers, address hash and notes blanked 90 days after the report is closed; the emptied record removed 365 days after that (455 days after closing). Open reports are kept until handled. |
| AI call records | 90 days. They hold the model name, the amount of text, the duration and any error message from the provider. |
| Analytics events at Google | Event data 2 months. User-level data 14 months, restarting each time the user is active again. |
| Error reports sent to our server (web, Windows, Linux) | 30 days. |
| Server logs | 14 days. |
| Browser security reports | 3 days. |
| App release records | Not deleted on a schedule. They list installers and download counts and hold no personal data. |
Crash reports sent to Google are kept under Crashlytics' own settings. We do not state a period for them here.
7. Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data. Contact us via the link below to make a request.
8. Children's privacy
IROMUSIC is not directed at children under 13, and we don't knowingly collect personal data from them.
9. Changes to this policy
We may update this policy from time to time. Continued use of the site or service after changes take effect means you accept the updated policy.
10. Contact
Questions about this policy, or a data request? Reach us via the contact link in the footer.