Privacy policy

Last updated 19 October 2026

RefBooth measures finished music masters. To do that it has to receive your audio, keep it while you use the report, and know who you are so it can show that report only to you. This policy says exactly what is collected, why, for how long, and how to get rid of it. It is written to be read.

Who is responsible

The data controller is AL MANNAN GENERAL TRADING FZE-LLC, trading as Solaryxdev, registered at Business Centre, Sharjah Publishing City Free Zone, Sharjah, United Arab Emirates. Its registration details are on our imprint. You can reach us at support@refbooth.com. That address is read by a person.

What we collect, and why

What we do not do

• We do not send your audio or your report to any other company, and your e-mail address only to our payment provider when you buy a paid plan.
• We do not use your audio to train anything, and we do not build models from it.
• The iPhone and Android apps contain no analytics, no crash reporting and no advertising identifier. Our websites count visits with a statistics tool we run ourselves, described below. It does not follow you to other sites and is never connected to your account.
• We do not sell data, share it for advertising, or profile you.
• Nobody at Solaryxdev listens to your uploads. Measurement is automated.

Visit statistics

Not switched on yet. Until it is, no statistics script loads on either site, nothing is counted and no statistics question is asked. This section describes what happens once it is.

refbooth.com and the app at app.refbooth.com count visits with Umami, an open-source statistics program that we run on our own server in the European Union (Germany). No other company receives this data, and the program sends nothing to its makers.

Whether it runs depends on where you are. Where the law asks for your agreement first, which includes the European Economic Area, the United Kingdom and Switzerland, the statistics script does not load until you choose Accept. Everywhere else it loads, and a short notice says so with a Don’t count me button. Wherever you are, it never loads in a browser that sends a Global Privacy Control or Do Not Track signal, and you can change your answer at any time with Privacy choices at the foot of every page or the switch on our cookies page. Where you are is worked out from your network address as described under Your country; if it cannot be worked out, we ask first.

When it runs, a short script in the page sends our server:

• the address of the page, without the part after "?" or "#", except that on refbooth.com, where you allowed statistics, the campaign names in a link you followed (utm_ values) are kept in it; the app sends no part of the address after "?";
• the website that linked you here, reduced to its domain;
• in the app only, the name of a step when you take it: an upload started, a report opened, Compare opened, or a checkout started, with the plan and billing period you picked (refbooth.com sends no such steps);
• your browser's language setting.

From the request itself our server also derives the browser and operating-system names and the device type, from your browser's user-agent string, and the country, looked up from your network address at that moment. It records no region or city.

The statistics do not store your network address. It is used at the moment of the request for that lookup and to form a visit code: a one-way hash of your network address, your browser's user-agent string, our site identifier, the date and a secret key we hold. The code changes every day at midnight UTC. It lets us count how many different visitors came that day and how many pages a visit covered; it cannot recognise you on another day or on another website, and we never combine it with your account, your e-mail address or anything you upload. Because someone holding both our secret key and your network address could recompute the same day's code, we treat these statistics as personal data and protect them accordingly. (Like every request to our server, the statistics request is also written to our access log, with the address shortened as described under Server logs.)

Individual statistics records are kept for 13 months and then deleted automatically. Copies inside our encrypted backups (see Backups) age out up to six months after that, so the last copy is gone within about 19 months. Totals that contain no visit codes may be kept longer.

The statistics script itself stores nothing on your device. Your answer to the statistics question is kept in one cookie, rb_consent, described on the cookies page.

Your country, and prices by country

To show prices in your currency, and to know whether to ask before counting your visit, our server looks up which country your network address belongs to when a page asks for prices. The lookup uses a database from DB-IP, kept on our own server: your address is not sent to DB-IP or anyone else, it is used for that one lookup and then discarded, and the lookup itself neither logs nor stores it. (The request that asks for prices is written to our access log like any other, with your address shortened to its network, as described under Server logs.) Only the country, never your address, is used further. IP Geolocation by DB-IP.

The country found this way is only a suggestion. You can pick another in the price list; your pick is kept in the page address and, until you close your browser, in the session cookie rb_country (see the cookies page). When paid plans open, the price you pay is the price for the country you are billed in, whatever country the page suggested; the terms of service say how checkout applies it.

Product news

If you tick the box when you sign up, or switch on Product news in Settings, we e-mail you about RefBooth: new features, changes to what the streaming platforms publish, and offers on our plans. At most twice a month, and usually less. The box is never ticked for you, and saying no changes nothing else about your account.

You can stop at any time. Every message has an unsubscribe link that works in one click, without signing in, and the switch in Settings does the same. Stopping takes effect at once. Mail about your account, such as sign-in codes, receipts and notices about your plan, is not product news and still arrives.

We keep when you said yes and when you said no, to show that you agreed. Product news is plain text, sent through our own mail server: it carries no tracking pixel and no tracked links, so we do not know whether you opened it, and your address is not given to a mailing-list company.

Server logs

Our web server writes one line for every request it receives on refbooth.com, app.refbooth.com and panel.refbooth.com, whoever sends it, including the statistics request and the request for prices. When a request fails because of an error on our side, it writes a second line with the same content and a description of the error. Every line goes through the same filter, and holds:

• the time, and how long the answer took;
• your network address shortened to its network: for an IPv4 address the last of its four numbers is replaced with 0, and for an IPv6 address everything after the first 48 bits is replaced with zeros, so the line names a network, not a device; and the port your connection came from;
• the name and address of what was requested, with any sign-in, share, download or cancellation token in the address replaced by REDACTED, and the method, protocol and encryption used;
• the headers your browser sent, such as its user-agent string, language and the formats it accepts, except cookies, sign-in and password headers, the page that linked to the request, the name of an uploaded file, the statistics script's own headers, and the headers a proxy uses to pass on a full network address (X-Forwarded-For, Forwarded, X-Real-IP, True-Client-IP, CF-Connecting-IP and X-Client-IP), which are removed before the line is written;
• the status, size and headers of the answer, except any cookie it sets.

The program behind app.refbooth.com that answers the app's requests (our API) writes one more line for each request that reaches it: the time, your network address shortened in the same way and the port, the method, the address requested with the same tokens replaced by REDACTED, the protocol and the status of the answer. It records no headers.

We use these lines to keep the service secure and working: to see and block floods of requests and other abuse, and to find the cause of an error. That is our legitimate interest, and a log that could not show where a flood came from would not serve it. The lines stay on servers we operate in the European Union, go to no other company, and are never combined with the visit statistics or used to count or follow visitors.

How long they are kept: Not yet fixed. Our log store deletes them on a schedule whose length we are still confirming; this page will state it, and until then we will tell you on request.

Where your data is

Your audio, reports, account record, our visit statistics and our server logs are stored and processed on servers we operate in the European Union (Germany), with encrypted backups held in the European Union. Nothing is replicated outside it. The exception is a purchase: your e-mail address, and the billing details you enter in the checkout, go to Stripe, our payment processor, which may process them outside the European Union under the safeguards its own policy describes. Solaryxdev is established in the United Arab Emirates; where our staff access data from outside the European Union for support or operation, we apply the safeguards the GDPR requires for such access.

Legal basis

We process your email address, audio and reports because that is the service you asked for (performance of a contract). We keep short sign-in records, and server logs with shortened network addresses, because protecting accounts and the service from abuse is a legitimate interest that does not override yours. What you were charged is kept to show you what you pay and to check it against our prices, as part of the same contract; we keep the invoices because tax law requires it (legal obligation). The country lookup, and the campaign recorded on your account, rest on our legitimate interest in showing you the right price and in knowing which announcements work; you can object by writing to us. Visit statistics rest on your consent where the law requires it, and on our legitimate interest in understanding how the service is used everywhere else; in both cases you can say no or change your mind at any time, as described under Visit statistics. Product news rests on your consent; you can withdraw it at any time, as easily as you gave it, and withdrawing it does not affect what was sent before. Nothing essential depends on consent, so withdrawing it never breaks the service.

Your rights

You can see everything we hold about you inside the app: your library is the list, and each report can be exported. You can delete any track at any time from its report, and you can delete your whole account under Settings › Data in the web app, from the You tab in the iPhone and Android apps, or as described at refbooth.com/delete-account. Deletion is immediate and complete: every track, every file and the account record are removed in one operation, with no grace period. One thing is kept: if one of our administrators ever changed something on your account (a plan granted, say), the record of that change stays in our administration log, with your account's internal number and, in place of your e-mail address, a one-way hash of it, so the log still shows what was done and that the account was deleted. The address cannot be read back from the hash, but someone who already knows your address could check it against it. Otherwise the only remaining copies are inside the rolling encrypted backups described below, which age out on their own schedule and are never used to bring deleted data back.

If you are in the European Union or the United Kingdom you also have the rights of access, rectification, erasure, restriction, portability and objection under the GDPR, and the right to complain to your supervisory authority. Write to support@refbooth.com and we will answer within 30 days.

Backups

We keep encrypted backups so a failure does not lose your work. They rotate on a fixed schedule (daily copies for a week, weekly for a month, monthly for six months) and a deleted item leaves the backup set as that schedule rolls forward, so the last trace of it is gone within six months. Backups exist to recover from a failure of ours; they are never restored to bring back something you deleted.

Children

RefBooth is not directed at anyone under 16 and we do not knowingly hold data about them. If you believe a child has an account, write to us and it will be removed.

Security

Traffic to and from RefBooth is encrypted. Sign-in uses a one-time code rather than a stored password, so there is no password of yours to leak. Access to production systems is limited to the people who operate them.

Changes

The date at the top is the date of the current version. The app links to this page, so the current wording is always one tap away. A change that reduces your rights will be announced in the app before it takes effect.