Privacy
What DIXL Studio keeps, where it's stored, who can see it, and how to delete it. DIXL Studio is made and run by Diego d'Ursel (D•IXL) in Brussels. Questions, or anything to delete: diego.dixelles@gmail.com.
Last changed 25 October 2026.
What's stored
- Your Google sign-in. The email address, name and profile picture link Google shares when you sign in, and when you signed in. It's created the first time you sign in, even before you're invited, and you can delete it yourself (below).
- Your studio. Tracks, sessions, versions, notes, comments, ratings, checklists, sets and releases, and the log of your timed blocks.
- Files you upload. The audio of a version (an MP3 or WAV export) and, when you add one, its Ableton Live set.
- What the studio measures from them. For each version: a waveform, loudness, peaks, tone, tempo and a second-by-second spectrum. From a Live set: its tempo and key.
- For notifications, only if you turn push on: the address your browser's push service gives it, and your browser's identification string (its user agent).
- On your device only, a few preferences, such as the keyboard sound, in the browser's storage.
- The early-access form on the home page: the email you give and your answer to "would you pay?".
- Visits to the home page. Cloudflare Web Analytics counts how many times it's opened, where visitors came from and from which country. Cloudflare says it uses no cookies, no local storage and no fingerprinting to do that, and nothing is stored on your device. The app itself isn't counted.
No ads, nothing is sold, and nobody gets your data except the services named on this page.
Where
With Google Firebase, a Google Cloud service, in the project dixl-studio:
- Your studio's documents: Cloud Firestore, region
eur3: Belgium and the Netherlands, with a third region in Finland that keeps the two in step. - Your files: Cloud Storage, region
europe-west1(Belgium). - The measuring of your audio and Live sets runs in
europe-west1too. - Your sign-in: Firebase Authentication, which Google runs from data centres in the United States.
The one exception is the home page's visit counts, which go to Cloudflare Web Analytics instead.
Who can see it
- Only you, signed in with your Google account. Each account reads and writes its own studio and nothing else; other members can't see yours, and you can't see theirs.
- Diego, technically. As the owner of the Firebase project, Diego can open any of it in the Firebase console. That's how the service works, not something the app does. Diego doesn't open a member's studio unless they ask, to fix a problem with it say; the measuring of audio runs on every account's files the same way, with nobody looking.
- Google stores and runs it for Diego, under Google's data processing terms for Firebase and Google Cloud.
- Cloudflare runs the home page's visit counter and shows Diego the totals. It never sees your studio.
How long
- Your studio and files: until you delete them.
- After you delete them, files and documents can still be recovered for 7 days, then they're gone from the service. Google takes up to about six months to clear deleted data, your sign-in included, from its own backups.
- Technical logs, which can hold your IP address, your browser, your account's id and your file paths, never what's in your files: 30 days. Firebase Authentication keeps sign-in IP addresses for a few weeks.
- An early-access email: until you're in, or until you ask for it to be deleted.
- Visit counts: as totals, for as long as Cloudflare Web Analytics keeps them. Cloudflare doesn't state a period.
How to delete it
- Everything at once: in the app, Settings → Your data → Delete my studio. Your documents, files and sign-in are deleted straight away. Download a copy first if you want one: Settings → Your data → Download my data gives you your studio and your sign-in details as a JSON file, with your audio and Live sets listed by name.
- Not let in, or not any more: sign in, and the card that says you're not on the list has Delete my sign-in. It deletes your sign-in and anything you made while you were in. An address you left on the early-access form stays on that list until you ask: write, and it's removed.
- Your invite, the address on Diego's guest list, stays until Diego removes it. Write to ask, and it's removed with your waitlist entry if there is one.
- Can't use the button (the Google account is gone, or Google never verified the address), or want only part of it deleted: write to diego.dixelles@gmail.com.
You can also ask to see what's kept about you, to correct it, or to take it elsewhere. If something isn't right, tell Diego first; you can also complain to the Belgian Data Protection Authority, dataprotectionauthority.be.