Privacy

IntroEdit is made by Recrate LLC. This page describes what the app and this website actually do — it was written from the code, and it changes when the code does.

The short version

• Your music never leaves your computer. Analysis, separation and rendering all run locally. Nothing is uploaded.
• You need an account to use the app: an email address and a password. That is all the account is. There are no ads.
• It counts how much it is used — four numbers: tracks added, analyzed, edits generated, edits saved. Never which tracks: no names, no paths, nothing about the audio. You can turn it off.
• It can send crash reports so bugs get fixed. They are stripped of file names, track names and your computer’s user name on your machine, before they are sent. They do say which account they came from — and you can turn them off.
• This website counts page views without cookies.

The app

Your audio and your files

Everything IntroEdit does to a track happens on your computer. Your audio, the edits it makes, your file and folder names, tags and artwork are not sent anywhere — not to us, not to anyone else.

The app keeps a few things locally — in %APPDATA%\intro-edit on Windows, and in ~/Library/Application Support/intro-edit (logs in ~/Library/Logs/intro-edit) on a Mac: your settings, a list of the edits it has saved (so it doesn’t re-import its own output), the downloaded audio models, and log files. Uninstalling or updating the app leaves that folder alone; delete it to remove them.

Your account

From version 0.2, IntroEdit asks you to sign in. Accounts are handled by Firebase Authentication, a Google service. What is stored there: your email address, a scrambled (hashed) form of your password — we never see the password itself — a randomly generated account ID, and when the account was created and last signed in. Nothing about your music, your library or what you do in the app is attached to it.

During the private beta you can’t create an account yourself: we create it for you, with the email address you gave us when you were invited, and you choose the password.

We use the email address to let you sign in and reset your password, and to reply if you write to us. We don’t send marketing email. Once you have signed in, the app keeps you signed in on that computer and works offline.

Deleting it: open account in the app’s header and choose Delete account. The account is removed from Firebase immediately, and its usage counts (below) are deleted with it; the record of the beta agreement (also below) is kept. Your music and your saved edits are untouched — they were never anywhere but your computer.

Crash reports

When something breaks, the app can send a report of what broke to Sentry, the error-tracking service we use. This is on by default and is switched off under privacy in the app’s header. Off means off: from that moment nothing at all is sent.

Never sent:

• your audio;
• track names and artist names;
• file and folder paths;
• your computer’s user name or network name.

Paths are rewritten on your machine before a report leaves it — C:\Users\you\Music\Artist - Title.mp3 becomes C:\Users\<user>\Music\<track>.mp3 — by one set of rules shared by the app and its audio engine, and tested against the same cases in both.

Sent:

• the error and where in the code it happened;
• the app version;
• which account it happened to — your account ID and email address — so a report can be matched to a support request;
• what kind of computer it is: operating system, processor, memory, graphics card, screen size, language and time zone.

Like any internet request, a report reaches Sentry from your IP address. The address itself is not stored, but Sentry keeps the approximate location it maps to (city and country). Reports are deleted automatically when the retention period of our Sentry plan ends.

Problems that are yours rather than the app’s — a moved file, a missing output folder, a cancelled job, a full disk — are not reported at all.

Usage counts

IntroEdit is in a private beta, and we need to know whether it is being used. So the app keeps four numbers for your account: how many tracks you added, how many were analyzed, how many edits you generated, and how many you saved — in total and by day. With them it stores your account ID and email address, the app version, whether the computer is a Mac or a PC, and when the counts were last sent.

That is all. A count never says which track: no track or artist names, no file or folder paths, no tags, nothing about the audio, nothing about what the edit sounds like or where you saved it. The counting is done on your computer and only the numbers leave it.

They are stored in Cloud Firestore, a Google database in the same Firebase project as your account. Your account can read, change and delete only its own counts; no other account can see them. When the app is offline the numbers wait on your computer and are sent the next time it is online.

This is on by default and is switched off under privacy in the app’s header. Off means off: counting stops, and anything that was waiting to be sent is thrown away. Counts already sent stay until you delete your account or ask us to delete them.

The beta agreement

IntroEdit is in a private beta. Before you can download it — on this site’s testers’ page — or, if you have not signed by then, the first time your account signs in to the app, you are shown a short confidentiality agreement and asked to type your full name and press I agree — that is how it is signed. When you do, it is recorded in Cloud Firestore: the name you typed, your account ID and email address, which version of the agreement it was and a fingerprint (a SHA-256 hash) of its exact wording, the date and time by the server’s clock, the app version and whether the computer is a Mac or a PC. Nothing else. You can copy the text of the agreement from that screen.

The record can be created once and read by the account it belongs to; nobody — that account included — can change or delete it, and no other account can see it. Because it is the record of an agreement, it is kept after the account is deleted, unlike the usage counts. Ask us and we will send you what it says; ask us to delete it and we will, unless we need it for a dispute. This is not switched off under privacy: it is part of joining the beta.

What else the app connects to

• Signing in. Google’s sign-in service (identitytoolkit.googleapis.com and securetoken.googleapis.com), when you sign in, set or reset a password, delete your account, and — when the app starts and a few times a day while it runs — to check that the account still exists and keep you signed in. It receives your email address and password (over an encrypted connection) and, like any web service, your IP address.
• Usage counts, and the beta agreement. Google’s Firestore service (firestore.googleapis.com): once when you sign the beta agreement, and a little after you add, analyze, generate or save — unless you have switched usage counts off. It receives the numbers described above and, like any web service, your IP address.
• Updates. At launch and every six hours the app asks GitHub (github.com) whether there is a newer version. Nothing about you is sent; GitHub sees the request’s IP address, as any website does. Nothing downloads or installs until you press the button.
• Audio models, once. The first time you analyse or generate, the app downloads the models it needs: beat detection from Johannes Kepler University Linz (cloud.cp.jku.at) and source separation from Meta’s public file host (dl.fbaipublicfiles.com). These are plain file downloads; nothing about your music is sent. After that the app works offline.

That is the complete list. The app contains no advertising, and no analytics or tracking beyond the usage counts described above: nothing follows what you click, which screens you open or how long you spend.

This website

introedit.com is hosted by Vercel. It uses Vercel Web Analytics to count page views: which page, the referring site, and the country, browser and device type. It sets no cookies, does not follow you across sites and cannot identify you — which is why there is no cookie banner. Vercel’s servers, like all web servers, process your IP address to deliver the page.

There are no advertising pixels and no third-party trackers on this site, and it loads no third-party scripts.

The testers’ page, /beta, is the one place this site signs anyone in. It uses the same Firebase account as the app: your email address and password go to Google’s sign-in service over an encrypted connection, and your browser keeps you signed in on that page until you sign out. If you have not signed the beta agreement yet, you sign it there, and it is recorded exactly as described under The beta agreement above (with “web” in place of the app version). When you press Download, our server checks your sign-in and that you have signed, and gives your browser a link to the installer on GitHub that stops working after a few minutes; GitHub sees your IP address, as for any download. Our server’s log keeps your email address and which file you asked for, so we know who has which version; hosting logs are kept for a limited time by Vercel.

“Request access” is a form. When you press the button — and not before — it sends what you entered to Formspree, a form service, which passes it to us by email and keeps a copy in our Formspree account: your email address, the DJ software and kind of computer you chose, and the kind of music you play if you filled that in. Formspree’s servers, like all web servers, also see your IP address, and check the submission for spam. We use your address to reply to you about the beta and for nothing else: no mailing list, no newsletter. Ask us to delete your request and we will, from our inbox and from Formspree. If you would rather not use the form, the email link next to it works just as well.

Email

If you write to hello@recrate.app, we keep your message so we can answer it. We don’t add you to a mailing list.

Who processes data for us

• Google (Google LLC, USA) — Firebase Authentication: your account; and Cloud Firestore: your usage counts and the record of the beta agreement. All as described above.
• Sentry (Functional Software, Inc., USA) — crash reports, as described above.
• Vercel (Vercel Inc., USA) — hosting and cookieless analytics for this website.
• GitHub (GitHub, Inc., USA) — hosts the installers and the update information.
• Formspree (Formspree, Inc., USA) — receives the “Request access” form on this website and forwards it to us.

We don’t sell data, and there is nothing here to sell.

Your choices

• Turn crash reports off in the app, under privacy.
• Turn usage counts off in the same place.
• Delete your account in the app, under account. If you can’t sign in, email us from the account’s address and we’ll delete it for you.
• Delete %APPDATA%\intro-edit (Windows) or ~/Library/Application Support/intro-edit and ~/Library/Logs/intro-edit (Mac) to remove everything the app stored locally.
• Ask us what crash reports or usage counts we hold from your account, or to delete them: email us from the account’s address.

Depending on where you live you may have legal rights to access, correct or delete personal data (for example under the GDPR or the CCPA). Email us and we’ll help.

Children

IntroEdit isn’t directed at children under 13, and we don’t knowingly collect data from them.

Changes

When the app changes what it collects, this page changes with it and the date above moves. Payments are planned; this page will describe them before they ship, not after. (IntroEdit 0.1 had no accounts and its crash reports carried no account details.)

Contact

Recrate LLC · hello@recrate.app