Privacy Policy

1. Who we are and what this covers

Outro LLC (“Outro,” “we,” “our,” or “us”) makes Outro, a desktop app for music producers, and operates the website at getoutro.app, the Outro account area, the Outro cloud service with which the app communicates, and the shared-track pages at fb.getoutro.app. This policy covers all of them (together, the “Service”).

This policy explains what we collect, why we collect it, who else handles it, how long we retain it, and how you may see or delete it. We have written it to match how the Service actually works. If anything in this policy is unclear, email support@getoutro.app.

Outro is in beta and is free to use. We do not take payments, and we therefore hold no payment details. We do not sell your personal information.

You join the beta by completing the form on our website and then creating an Outro account. Section 2.1 describes what we collect when you complete the form, section 2.2 describes your account, and sections 5 and 8 describe the services that may be told of your sign-up.

2. What we collect

2.1 The waitlist and joining the beta

When you join the beta on our website, by completing the Join beta form (the “waitlist”), we collect:

• Your email address and, if you provide them, your first and last name;
• The genre of music that you make, the computer operating system that you use and, if you tell us, your artist or studio name and your DAW;
• Your consent to receive email from us, the time at which you signed up, and the IP address from which you signed up, which our email provider keeps as a record of that consent; and
• Which link or campaign brought you to our site, if you arrived through one (for example, an ad or a post).

We also keep a record in our own database of your email address, the time at which you completed the form and the fact that you did so. We use that record to recognize the Outro account that you create afterwards as a beta account, and to decide whether to send you the one invitation email described below.

After you complete the form, we take you straight to our account sign-up page, in the same browser tab. To fill in your email address and your first and last name for you there, the form passes them to that page through your browser’s session storage, which the page empties as soon as it has read them. They are never placed in a web address or a cookie. You then create your Outro account and confirm your email address, either with a code that our sign-in provider, Clerk, emails to you or by signing up with Google (section 2.2). We recognize a beta account only for an email address that Clerk has confirmed.

If you complete the form but do not create an account within 24 hours, we may send you one email invitation to create it, which Clerk sends on our behalf. We send that invitation once and do not repeat it, and we do not send it to an email address that already has an account.

If you joined the waitlist before we added those questions, we may email you a personal link to a short form that asks them. That form also asks for your email address, solely to check that the link is being used by the person to whom it was sent. We do not store the address that you type there.

In order to stop bots, the waitlist form and the Support page use Cloudflare Turnstile, which receives your IP address and information about your browser. When you create an account, our sign-in provider, Clerk, may also run a Cloudflare Turnstile check in your browser, which receives the same information.

2.2 Your Outro account

Outro accounts are operated by our sign-in provider, Clerk. Clerk holds your name, your email address, the artist name that you choose to show on shared tracks, the primary DAW that you choose in the app, and your password or the sign-in service that you connect (such as Google). We never see your password. Our own records refer to your account by its id.

When you link the desktop app to your account, we store the following for each linked computer:

• The name of the computer as your operating system reports it, and which operating system it runs, so that you can recognize the computer in your account's device list;
• When the computer was linked and when it last connected; and
• A one-way hash of the token that the app uses to sign in (the token itself stays on your computer).

When you download the app from your account page, we record which version and which operating system’s installer you were given, and when. We do not record your IP address or your browser.

2.3 Feedback and shared tracks

When you use Feedback to share a track, we store:

• The name of the project to which the track belongs;
• The audio file that you upload, and its file name, label, length and size;
• The share link, and the name that we show guests as the person who shared the track (your artist name or, if you have not set one, your name); and
• Comments and replies on the track, each with the name that its author gave and the moment in the track to which it points.

Anyone who has a track’s share link can play the track and comment on it, without an account. Guests type a name in order to comment. We store that name with the comment, and the guest’s browser remembers it for next time. We use a one-way hash of a guest’s IP address to limit the rate at which the guest can comment. We do not store the IP address itself.

2.4 Support messages and bug reports

When you contact us from the app, we store what you send. Section 6 describes this in full, including diagnostic reports.

2.5 Information collected automatically on our website

As with most websites, our hosting provider receives your IP address, your browser type and the pages that you request, and uses your IP address to determine which country or region you are in. We use that determination to decide whether to ask for your cookie consent (section 8). If you allow analytics and advertising cookies, the services listed in section 5 also receive information about your visit.

To prevent abuse, we count requests to parts of the Service. We store those counts against one-way hashes of IP addresses, account ids, project ids and share links, and never against the raw values, and we delete them after one day.

2.6 Shared Projects

In this policy, “Shared Project” means a project that its owner (the “Owner”) has invited other Outro accounts to work on, and “Collaborator” means each person who joins a Shared Project in response to that invitation. A project that you have not shared remains on your computer, as section 3 states. When you share a project, we retain a shared copy of the following information in Outro’s cloud:

• The name, BPM and key of the project, and the genre and DAW set on it;
• Its lists and statuses, and its tasks, namely titles, descriptions, due dates, subtasks, comments, assignees and tags, together with links to other tasks, to notes and to Feedback comments (for an attachment, we retain its name and whether it is audio, and never the file itself or its location on your computer);
• Its notes, namely the title, the text, the tag and whether the note is pinned;
• Activity, namely a record of who changed what on a task, with the name that person had at the time (or "Former member" once that person has deleted their account);
• Information about each person on the Shared Project, namely their account id, whether they are the Owner or a Collaborator, the name shown to the others (your artist name or, failing that, your first and last name or, failing that, "Producer", and never your email address) and when they joined or left;
• Mentions, namely who a comment or note mentions, a short excerpt (the start of the comment, or the title of the note), the name of whoever wrote it, and whether the person mentioned has read it; and
• Which notes someone currently has open (for under a minute), and whether someone has changes that they have not seen.

The Owner and every Collaborator can see all of the information listed above, except that only the person mentioned can see a mention of that person. If you link a folder, or a project file, to the Shared Project, the Owner and every Collaborator can also see the Folder Inventory (as defined in section 2.8). Your project folder itself, the contents of the files in it, your session log and the other settings that belong only to you remain on your computer, except the files that you send in a Transfer (section 2.9), and what is sent to us from a folder or project file that you link is limited to the Folder Inventory. Collaborators may also open the Owner’s Feedback tracks for that Shared Project, play them, comment on them and upload tracks of their own. Section 2.3 describes what Feedback stores.

2.7 Shared Project invites

To invite a person to a Shared Project, the Owner enters that person’s email address. We store the address in lowercase on the invite record, together with a one-way hash of the token in the invite link and the relevant dates. We send one email from support@getoutro.app through Google Workspace. That email contains the Owner’s name, the name of the project and the invite link, and no other information about the project. Where the invited person has no Outro account, that address and the invite record are all the information that we hold about that person in our database until that person signs up.

An invite is valid for 7 days. To accept an invite, you must sign in to an Outro account that has the invited address as a verified email address. The Owner may see the addresses of pending invites. Collaborators may not. We delete the address typed on the invite record from our database 30 days after the invite ends, whether the invite was accepted, declined, cancelled or has expired (see section 7).

2.8 Folder Inventories in Shared Projects

Where you link a folder, or a single project file, to a Shared Project, your app sends Outro a list of what that folder or file contains (a “Folder Inventory”), and the Owner and every Collaborator can see the Folder Inventory. In this section, “Shared Folder” means the folder that you link to the Shared Project or, where you link a single project file, the folder that holds that file.

A Folder Inventory contains: (a) the folders and file names that the Files tab shows, written relative to your Shared Folder, together with the size of each file and a fingerprint of each file, being a code worked out on your computer that tells Outro whether two people hold the same file; (b) your DAW; (c) the names of the Audio Plugins used by your 20 newest project files; and (d) the names of the samples that those files use, with a fingerprint for each sample that Outro finds and a record of whether Outro found it on your computer (samples are read for FL Studio, Cubase and Pro Tools projects). A sample stored outside your Shared Folder goes up as a name, a fingerprint and a record of whether it was found, and never as a location.

A Folder Inventory never contains file contents, anything above your Shared Folder, full paths, the name of your Shared Folder itself or the time at which you saved a file. Outro never learns which plugins you have installed, and learns only which ones your projects use.

Nothing is sent until you link a folder or project file, and, when you unlink it, your app asks Outro to delete the Folder Inventory. We retain only your latest Folder Inventory, and we delete it (a) when you leave the Shared Project or are removed from it, (b) when sharing ends for everyone, (c) when the project is deleted, or (d) when you delete your account.

2.9 Transfers

2.9.1 Definitions. In this section 2.9 and in sections 3.7 and 7:

(1) “Owner”, “Collaborator” and “Shared Project” have the meanings given in section 2.6.

(2) “Transfer” means the sending of one or more files from the Shared Folder of a member of a Shared Project (the “Sender”) to one or more other members of that Shared Project whom the Sender selects (each a “Recipient”).

(3) “Shared Folder” means the project folder that a member uses on their own computer for a Shared Project.

(4) “Fingerprint” means a code, calculated from the contents of a file by the SHA-256 method, that the receiving app uses to check that the file has arrived intact.

(5) “Allowance” means the limit on the total size of the Transfers that an account may have in progress at one time.

(6) “Sponsorship” means an Owner’s permission for a Collaborator who cannot send Transfers on their own to send Transfers against the Owner’s Allowance.

2.9.2 What we collect and retain. When a Sender sends a Transfer, we collect and retain:

(1) the files, in storage provided by Cloudflare (R2) that is used only for Transfers;

(2) for each file, its name and its location within the Shared Folder (for example, Stems/kick.wav), its size and its Fingerprint and, for a .zip file, the names of the files inside it. We do not receive the location of the Shared Folder on the Sender’s computer;

(3) the note, if any, that the Sender adds, being one line of not more than 200 characters;

(4) the Outro account identifier of each Recipient, the time at which the Transfer was sent and the time at which it ends;

(5) for each Recipient, which files that Recipient downloaded or skipped, whether that Recipient dismissed the Transfer, and the times of those events;

(6) where applicable, whether an Owner has granted a Sponsorship to a Collaborator and the time at which it was granted; and

(7) for each account, a running total of the size of the Transfers in progress, which we use to apply that account’s Allowance.

2.9.3 Who may see a Transfer.

(1) The Sender may see the Transfer, each Recipient, whether each Recipient has downloaded, skipped or dismissed it, and the number of files that each Recipient has downloaded.

(2) A Recipient who has not dismissed the Transfer may see the Sender’s name, the note, the files, and which files that Recipient has downloaded or skipped. A Recipient may download the files. A Recipient may not see who else received the Transfer or what any other Recipient did. A Transfer that a Recipient has dismissed is no longer visible to that Recipient.

(3) No other member of the Shared Project may see a Transfer, with one exception. When a Sender selects the intended Recipients of a new Transfer, the app may ask us whether a Transfer from another Sender is still waiting for any of them. If so, we tell the asking Sender only: who sent it; when it was sent; the path and Fingerprint of each file; and which of the people the asking Sender selected it is waiting for. We do not tell the asking Sender the note, the sizes, or anyone whom the asking Sender did not select.

(4) Outro staff may look up a Transfer by its identifier, or search by sender, Shared Project or file name, in order to act on a report of abuse or a copyright notice (Terms of Service, section 9). A search lists not more than 50 Transfers, each with its identifier, the Sender’s account identifier, the Shared Project, state, date, number of files and total size. We write each search to our server log together with the staff member’s identifier, what the staff member searched by and what the staff member typed (for an email address, the matching account identifiers). We do not log the results. The lookup shows the state and dates of the Transfer, the Sender’s account identifier, the number of Recipients, the note, and the name and size of each file. It does not show who the Recipients are or what they did, and it provides no means of opening or downloading a file. If staff end a Transfer, we delete its files and record that action on the Sender’s account.

(5) Our cloud service stores each file as it arrives and passes it to the Recipients. It does not open, play or scan the file.

(6) A note is visible to every Recipient and is not private from them. A Sender should not include personal details in a note.

2.9.4 Sponsorship.

(1) An Owner may grant Sponsorship to not more than 2 Collaborators in total, counted across all of the Owner’s Shared Projects. Transfers sent under a Sponsorship count against the Owner’s Allowance. The Owner may withdraw a Sponsorship at any time.

(2) If the Owner’s plan ceases to include Sponsorship, the Sponsorship is paused: new Transfers under it are refused, and Transfers already sent are completed as normal.

(3) The Owner may see, for each member of the Shared Project, whether that member can send Transfers on their own or needs the Owner’s Sponsorship, because the Owner could not otherwise know to whom to grant it. The Owner cannot see which plan any member is on.

(4) A Collaborator may see this information only for themselves and not for any other member.

(5) A Collaborator sending under a Sponsorship cannot see the Owner’s Allowance or how much of it is in use. The app may ask us whether a proposed send fits, and we answer only yes or no. Before we check, we round the size of the proposed send up to the next 256 MiB. The answer is therefore approximate, and the exact refusal, if any, is given when the send is made.

(6) A Sponsorship ends when the Collaborator leaves the Shared Project or is removed, when the Shared Project ends, or when the Owner withdraws it. A Collaborator who is invited back starts without a Sponsorship.

2.9.5 Retention. Section 7 states how long a Transfer is retained and what happens when a member leaves.

2.10 File Requests

2.10.1 Definitions. In this section 2.10 and in sections 3.8 and 7:

(1) “Owner”, “Collaborator” and “Shared Project” have the meanings given in section 2.6; “Folder Inventory” has the meaning given in section 2.8; and “Transfer”, “Sender”, “Recipient”, “Shared Folder” and “Fingerprint” have the meanings given in section 2.9.1.

(2) “File Request” (called Get files in the app) means a request, made in the app by one member of a Shared Project (the “Requester”) to another member of the same Shared Project (the “Holder”), that the Holder send one or more files from the Holder’s Shared Folder to the Requester.

2.10.2 What a File Request does.

(1) A File Request sends no file. The Holder decides whether to send any of the files asked for, which of them to send, or to decline.

(2) A File Request can name only a file that is listed in the Holder’s Folder Inventory.

(3) If the Holder sends files in response, they are sent as a Transfer from the Holder, as Sender, to the Requester, as Recipient, and sections 2.9 and 3.7 apply to that Transfer.

2.10.3 What we collect and retain. When a Requester makes a File Request, we collect and retain:

(1) the Shared Project, the Outro account identifier of the Requester and the Outro account identifier of the Holder;

(2) for each file asked for, its name and its location within the Holder’s Shared Folder (for example, Stems/kick.wav), its size and its Fingerprint, which we copy from the Holder’s Folder Inventory and not from the Requester;

(3) the state of the File Request, namely open, sent, declined, cancelled or expired;

(4) the time at which the File Request was made, the time at which it expires and, once it has ended, the time at which it ended;

(5) where the Holder sent files in response, a reference to the Transfer; and

(6) where the Holder declined, any reason that the Holder gave (section 2.10.5).

2.10.4 Who may see a File Request.

(1) While the File Request is open, the Holder may see who made it, the files asked for, their sizes and when it was made.

(2) The Requester may see whether the File Request is open, sent (while the Transfer is being uploaded), declined, cancelled or expired and, where it was declined, any reason that the Holder gave.

(3) No other member of the Shared Project may see a File Request.

(4) The names, sizes and Fingerprints that a File Request holds are those that every member of the Shared Project can already see in the Holder’s Folder Inventory (section 2.8).

2.10.5 Reason for declining.

(1) A Holder who declines a File Request may give a reason. The reason is optional, is one line of plain text of not more than 200 characters, and is shown in the app only to the Requester.

(2) A reason is visible to the Requester and is not private from the Requester. A Holder should not include personal details in a reason.

(3) We delete a reason when the Requester closes the declined File Request, and in the other cases that section 7 states.

2.10.6 Retention. Section 7 states how long a File Request is retained and what happens when a member leaves.

3. The Outro desktop app

The desktop app keeps your work on your computer. Your projects, tasks, notes, session log, templates and the files in your project folders remain in a database and in folders on your own machine, and the scanning of your project folders takes place on your machine. We never receive any of it, except as listed below. The only information about your files that is sent to us is the Folder Inventory described in section 2.8 and the files that you send in a Transfer (section 2.9), and only once you link a folder, or a project file, to a Shared Project.

The app contacts Outro to check for updates, to link and check your account and to save settings that you choose to sync to your account, such as your artist name and primary DAW. It never sends your projects, your files or information about how you use the app. The only exceptions are items that you choose to send, namely (a) a track that you share through Feedback, (b) a project that you share with other accounts as a Shared Project, (c) the Folder Inventory for a folder or project file that you link to a Shared Project (section 2.8), (d) a message that you send to Support, (e) the files that you send in a Transfer (section 2.9), and (f) a File Request that you make, and the decision and any reason that you give when you decline one (section 2.10). Each kind of contact is described below.

3.1 Update checks

The app checks for updates automatically. Every installed copy does so, whether or not it is linked to an account: (a) when it starts, (b) every 6 hours after that, and (c) when you press Check for updates. Each check asks getoutro.app for two small files, one that names the newest version of Outro and one that states whether older versions are still supported. If an update is available, the app downloads it only when you press Install, and the installer comes from our storage at Cloudflare (R2).

A check is an ordinary web request, and accordingly we and Vercel, which hosts the feed, receive your IP address and the name of the file requested. That name, latest.yml or latest-mac.yml, shows whether the copy runs on Windows or on a Mac. The request also carries a user agent that names only the update software (electron-builder), and a random id that the update software generated on your computer and keeps in the app’s data folder. We do not read or store that id. The request does not include your account, your projects or the version of Outro that you run.

Our database holds one item of information about a check: the abuse-prevention count described in section 2.5, being a count of requests in each 10-minute period, kept against a one-way hash of your IP address and not linked to your account. It is deleted after one day (section 7).

3.2 Linking and checking your account

When you link the app to your Outro account, it opens your browser at getoutro.app with the name of the computer as your operating system reports it and which operating system it runs, so that you can recognize the computer in your account’s device list. The app then exchanges a one-time code for a sign-in token. Each time the app starts after that, it checks the link by asking which account the token belongs to, and we note when the computer last connected. When you sign out of the app, the app tells us to unlink the computer. Section 2.2 lists what we store for each linked computer.

3.3 Settings you sync to your account

Two settings sync to your account, namely your artist or studio name and your primary DAW. Section 7 states how long each is retained.

When you save your artist or studio name in Settings, the app sends the name, up to 80 characters, to us with its sign-in token, and we save it on your account with our sign-in provider, Clerk. Clearing the name works in the same way. Guests see the name as the name of whoever shared a track, and on the comments and replies that you post (section 2.3).

The app sends your primary DAW, with its sign-in token, when you link the app to your account and whenever you change the primary DAW in Settings. We save it on your account with Clerk. If you are on our mailing list, we update the DAW recorded there to match. If you clear it, we remove it from your account, and the mailing list retains the DAW that it already had.

3.4 Feedback and support

When you share a track through Feedback, the app sends the project’s name, the audio file, and your comments and replies. When you send a support message, a bug report or a feature request, the app sends what you write, as section 6 describes.

Each time the app starts, and when you open Support, the app asks whether we have replied to a message that you sent. It sends the receipt codes that it holds and, if it is linked, its sign-in token. With neither, it sends nothing.

3.5 What stays on your computer

The app has no analytics, no usage tracking and no automatic crash reporting. Nothing about how you use it is sent to us unless you send it, with the sole exceptions that the Folder Inventory for a folder or project file that you link to a Shared Project (section 2.8) is sent once you link it, and not before, and that the files that you send in a Transfer (section 2.9) are sent when you send them.

On your computer, the app keeps your account sign-in in your operating system’s secure storage, encrypted where the system provides encryption. On Linux without a keyring, the app tells you that the sign-in is only obscured and is not encrypted. The app also keeps a receipt code for each support message that you send, so that it can show you our replies.

3.6 Shared Projects

The first time that any person accepts your invite to a project, the app uploads the tasks and notes of that project to Outro’s cloud (being the information listed in section 2.6). After that, the app sends each change that you make to the Shared Project and, while the app is open, asks at regular intervals for other people’s changes. The app also asks whether any person has invited you to a Shared Project, namely (a) when the app starts or you link your account, (b) about once a minute after that, and (c) when you return to the app’s window. Nothing about a project that you have not shared is sent.

If a folder, or a project file, is linked to a Shared Project, the app also sends the Folder Inventory described in section 2.8. The app reads the folder or file (a) when you open the Files tab or Compare, (b) when the app comes into focus, at most once every 5 minutes, (c) about a minute after the app starts, and (d) when you change the link. The app sends the Folder Inventory only when it has changed, and at most once every 30 seconds. Nothing is sent before you link a folder or project file, and, when you unlink it, the app asks Outro to delete the Folder Inventory.

If you stop sharing, leave a Shared Project or are removed from it, the app keeps the copy that it holds, and section 7 states what we retain.

3.7 Transfers

To send a Transfer, the app uploads the files that the Sender has chosen to Outro’s storage in parts, using links that remain valid for 15 minutes, and sends us the information described in section 2.9.2. When a Sender selects the intended Recipients, the app may ask us whether a Transfer from another Sender is already waiting for them and whether the proposed send fits the Sender’s Allowance (sections 2.9.3 and 2.9.4). To receive a Transfer, a Recipient chooses which files to download. For each file, the app asks us for a download link that remains valid for 15 minutes, downloads the file, checks its Fingerprint and saves it on the Recipient’s computer: in the Recipient’s Shared Folder or, where the Recipient has linked a single file instead of a folder, in a download folder that the Recipient chooses. The app then tells us which files the Recipient downloaded or skipped. Deletion of a Transfer from our storage does not delete copies that people have already saved.

3.8 File Requests

To make a File Request, the app sends us, with its sign-in token, the Outro account identifier of the Holder and, for each file asked for, its location within the Holder’s Shared Folder and its Fingerprint, and we add the other information described in section 2.10.3. To decline a File Request, the Holder’s app sends us the Holder’s decision and any reason that the Holder gave (section 2.10.5). To cancel or close a File Request that the Requester made, the Requester’s app tells us. The information about your Shared Projects that the app asks us for about once a minute (section 3.6) includes how many File Requests are waiting for you and how many of your own are open. When you open the Files tab, and afterwards when that information changes, the app asks us for the File Requests that name you and shows them on the Files tab. Nothing is sent before you press Send request, Decline, Cancel request or, on a declined or expired request, Close. If the Holder sends files in response, the app sends them as a Transfer (section 3.7).

4. How we use your information

• To run the Service: we process your account, linked computers, shared tracks, Shared Projects, comments and support messages, the files in Transfers (section 2.9), and File Requests and decline reasons (section 2.10), in order to provide the features that you use.
• To answer you and fix problems: we use support messages and diagnostic reports to reply to you and to find bugs. We group reports about the same problem so that we can see how many people it affects.
• To run the waitlist and beta: we use your waitlist answers to decide which operating systems and genres to support first, we use your sign-up record to recognize your beta account and to send the one invitation described in section 2.1, and we email you about Outro. Every email contains an unsubscribe link.
• For advertising and marketing: we may use personal information, including contact information such as your email address in hashed form, for advertising and marketing purposes, including to deliver, measure and improve advertising on third-party platforms such as Meta (Facebook and Instagram). See section 5.
• To understand and grow our audience: if you allow it, analytics and advertising cookies tell us how people find and use our website and which ads lead to signups.
• To keep the Service safe: we use bot checks, rate limits and sign-in tokens to protect accounts and to prevent abuse.
• To meet legal obligations and enforce our Terms of Service.

If you are in the European Economic Area, the UK or Switzerland, our legal bases are: performing our contract with you (your account and the features you use), your consent (marketing email, and analytics and advertising cookies); our legitimate interests in supporting users, fixing bugs and keeping the Service secure; and, for the use of personal information for advertising and marketing described in section 5, our legitimate interests in promoting Outro and/or your consent where required by applicable law.

5. Who else handles your information

We use the following service providers to operate Outro. They handle your information on our behalf, for the purposes described in this policy.

• Vercel: hosts our website and cloud service, and receives every request to them.
• Neon: our database, which holds what we store as described in sections 2 and 6.
• Cloudflare: stores the audio files that you share and the files in Transfers (Cloudflare R2), and operates the bot check on the waitlist form and the Support page (Turnstile). It also operates the bot check that Clerk may run in your browser when you create an account.
• Clerk: operates Outro accounts and sign-in. When you create an account with a password, it sends the email that contains the code that confirms your address, and it sends the one invitation email described in section 2.1.
• Mailchimp (Intuit): our email list. It holds your waitlist details and sends our emails.
• Google Workspace: our email. Support messages, our replies, your emails to us and notices of new waitlist signups pass through and are stored in our mailboxes.
• Atlassian Jira: our internal bug and feature tracker. It may receive short excerpts of support messages, with the email addresses and account ids that we can detect removed. It never receives diagnostic reports, reply addresses or account ids.

If you allow analytics and advertising cookies on our website, these services also receive information about your visit (section 8):

• Google Analytics: which pages you visit, and whether you joined the waitlist. Our server also reports to Google Analytics that you created an account, under the identifier in Google’s own cookie on your browser, even though no analytics script runs in the account area (section 8).
• Meta (Facebook and Instagram) and Reddit: that you visited, and whether you joined the waitlist, so that we can measure our ads. For Meta, our server also reports that you joined the waitlist, that you opened our account sign-up page and that you created an account, with your IP address, browser details and Meta’s own cookie and click identifiers, so that an ad blocker does not prevent those events from being recorded. These events never include your email address, your name, your answers or your account id (section 8).
• Mailchimp: which pages you visit, linked to your waitlist contact if you have one.

Advertising on third-party platforms

We may use personal information, including contact information such as your email address in hashed form, for advertising and marketing purposes, including to deliver, measure and improve advertising on third-party platforms such as Meta (Facebook and Instagram). For these purposes, we may disclose that information to those platforms, which process it under their terms with advertisers and their own privacy policies.

You have the right to object to, or opt out of, this use of your personal information at any time. To do so, email support@getoutro.app from the email address you use with Outro. We will give effect to your request within a reasonable time. Opting out of this use does not unsubscribe you from our emails, and unsubscribing from our emails does not by itself opt you out of this use.

Our community is on Discord. If you follow a link to it, Discord’s own privacy policy applies there.

We may also disclose information if the law requires it, to protect people’s safety or our rights, or to a company that takes over Outro, which would remain bound by this policy.

Outro is based in the United States, and your information is processed there and wherever our providers operate. For transfers from the EEA, the UK and Switzerland, we rely on our providers’ data protection terms, such as the European Commission’s Standard Contractual Clauses.

6. Support messages and bug reports

When you contact us from the Outro app, or from the Support page on getoutro.app, with a bug report, a feature request or a support message, we retain what you send so that we can answer it and keep track of it. A support message contains:

• What you wrote: the kind of message, its subject and its text
• A reply email address. It is required for bug reports and support messages, so that we can answer you, and optional for feature requests. It is always required on the Support page
• The version of Outro and the operating system you sent it from. A message from the Support page records only that it came from the website
• A diagnostic report, only if you chose to attach one to a bug report (see 6.1)
• Up to three screenshots, only if you chose to attach them to a bug report or a support message from the Outro app. They are stored as you sent them, are visible only to us, and are never included in a reply or sent to any other service
• Your Outro account id, only if your app was linked to an Outro account when you sent the message, or you were signed in to your Outro account on the website

6.1 Diagnostic reports

A diagnostic report helps us to find the cause of a bug. You may attach one only to a bug report, and you can see the complete report in the app, exactly as it will be sent, before you send it. You may also copy the report or save it to your computer. A report contains:

• The Outro version, build and edition, whether it is an installed release, and the versions of the software it runs on
• Your operating system, its version, processor type, amount of memory and language setting
• The version of the app's local database, and how many projects, tasks, notes and session log entries it holds. Only the counts, never their contents
• Whether the app is linked to an account and how its sign-in is stored (yes or no and the storage type, never which account), and whether Outro links open in the app
• Up to 200 of the app's most recent internal events: short technical messages about what the app did and any errors. The app keeps these in memory only, never in a file, and they are gone when it closes
• If you choose to include the current project: its genre, DAW, BPM and key, whether a folder is linked, and how many tasks, notes and files it has. Never its name, folder or file names

Before you see it, the app removes from the report the file paths, computer name, user name and project names that it can recognize, and anything that looks like a key or token. A report is at most 128 KB.

6.2 Replies

Our replies to you are kept with your message as its reply thread, together with any answer you send back, whether you write it in Outro or email it to us. We send replies from support@getoutro.app. They may quote the start of your message, and never include a diagnostic report.

6.3 How long we keep it

• The diagnostic report is deleted 90 days after your message is closed. If your message is never closed, the report is deleted with the rest of it, 2 years after the last activity.
• Screenshots you attach are deleted on the same schedule as the diagnostic report: 90 days after your message is closed, or with the rest of it 2 years after the last activity. They are also deleted straight away if you ask us to erase the message.
• The text of your message, its reply thread, your reply address and the link to your Outro account are deleted 2 years after the last activity on it.

After that, your message’s own record keeps only:

• The kind of message: a bug report, a feature request or a support message
• Where it got to: its status, and which of our internal issues it was filed under, if any
• Its dates, where they apply: when you sent it, when it last had activity, when it was closed, when its diagnostic report was deleted and when it was erased
• Whether you sent it from the Outro app or the website, and the version of Outro and the operating system you sent it from
• A random reference id, and a one-way hash of the receipt code it was given when you sent it. The receipt code itself is never stored

It holds nothing you wrote, and no reply address or account id. It still counts toward the number of reports we have had about the same problem.

6.4 Copies that the deletion windows do not reach

• When you send a message, we email ourselves a notice containing its text, your reply address and your account id, if any, so that we see it quickly. Those notices, our replies and the emails that you send us remain in our support mailbox until we delete them.
• An excerpt of what you wrote, with any email addresses and account ids we can detect removed, may be copied into our internal issue tracker (Jira) to track a bug or a feature request. Diagnostic reports are never copied there.
• Titles, summaries and notes written by Outro staff about an issue, which may quote what you wrote, are kept in our internal admin area.

If you ask us to delete a message, we delete these copies too.

6.5 Deleting a support message

You may delete a support message yourself, at any time, from Support in the Outro app: open the message in your history and choose Delete. Doing so erases its text, its reply thread, your reply address, your account link and any diagnostic report, immediately and permanently, leaving only the anonymous record described in 6.3. You may also email us at support@getoutro.app and ask us to delete one.

7. How long we keep information

• Your account and shared tracks: we retain them until you delete them or your account (see below).
• Your artist name: we retain it on your account until you change or clear it, or delete your account. A copy is placed on each share link when you create it, and on each comment or reply that you post, so changing or clearing your name later does not change those copies. They retain it until the track is deleted.
• Your primary DAW: we retain it on your account until you change or clear it, or delete your account. The copy on our mailing list is part of your waitlist details (below).
• A shared track you delete: its audio file, comments, replies and share link are deleted with it. Uploads that never finish are deleted after 24 hours.
• Share links that you revoke: cease to work immediately. We retain a record that the link existed until the track is deleted.
• Linked computers: unlinking a computer ends its access immediately. We retain a record of the computer (its name, operating system and dates) until you delete your account.
• Shared Projects that you own: we retain them for as long as you share them. Sharing ends when (a) you stop sharing, (b) you delete the project, (c) you delete your account, or (d) the last Collaborator leaves or is removed. The next item states what we retain after that.
• When sharing ends for everyone (that is, where (a) the Owner stops sharing, (b) the Owner deletes the project, (c) the Owner deletes their account, or (d) the last Collaborator leaves or is removed): we freeze the project as it stood (the “End State”) so that the app of each Collaborator can take a final copy. If the Owner deleted their account, the Owner’s account id is removed from the End State. We retain the End State, together with the shared tasks, notes, comments and activity of the project, until the earlier of (i) the time at which every computer linked to each affected account has picked up the End State and (ii) the expiry of 30 days, and we then delete them. We delete the record of the project itself (its name and the persons who were on it) at 30 days. For the avoidance of doubt, where an affected person has no linked computer, the period of retention is the full 30 days. Our daily clean-up performs the deletion.
• When a Collaborator leaves or is removed: if other Collaborators remain, the Shared Project continues for everyone else. If that person was the last Collaborator, sharing instead ends for everyone, as provided in the preceding item. That person receives a frozen copy of the project as it stood when they left or were removed. We retain that copy until the earlier of (a) the time at which every computer linked to that person’s account has picked it up and (b) the expiry of 30 days, and we then delete it. What that person wrote remains in the project. That person is also removed from the tasks to which they were assigned.
• Feedback tracks in a Shared Project: when a Collaborator leaves or is removed, the tracks that the Collaborator uploaded into the Owner’s Feedback project move to the Collaborator’s own Feedback project. When sharing ends for everyone, including because the Owner deleted their account, the same applies to every Collaborator. We do not delete those tracks, and the Owner’s share links on them stop working.
• What you add to a Shared Project that you do not own: (a) the tasks, notes and comments that you wrote remain in the project after you leave or are removed, for as long as the project exists, unless the task or note in which they sit is deleted; (b) any member may change or delete the subtasks, links and tags that you added; (c) the activity that you caused and the mentions that you wrote also remain; and (d) your Feedback comments and replies also remain, for as long as their track exists. If you delete your account, all of the foregoing remains, except for Feedback comments on tracks that you uploaded, which are deleted with those tracks. What remains is shown under the name “Former member”, and your account id is removed from it. Nobody, including the Owner, is able to delete a Former member’s tasks, notes or comments directly. They are deleted only if the task or note in which they sit is deleted, or when the project is deleted from our servers. Words that other people wrote and that name you, such as a mention of you inside another person’s note, remain as written until that text is edited or deleted, or the project is deleted from our servers.
• Your Folder Inventory in a Shared Project: we retain only your latest Folder Inventory (section 2.8). We delete it from our live database (a) when you unlink the folder or project file (your app asks us to do so), (b) when you leave the Shared Project or are removed from it, (c) when sharing ends for everyone, (d) when the project is deleted, or (e) when you delete your account. Earlier recovery history of the database is addressed under “Deleting your account” below.
• Shared Project invites: an invite ceases to be valid 7 days after it is sent, or sooner if the Owner cancels it or you decline it. We delete the address typed on the invite record from our database 30 days after the invite ends (whether accepted, declined, cancelled or expired). If the Owner deletes their account, the pending invites of the project are cancelled and the addresses typed on them are deleted from our database within 30 days. The invites that an account accepted are deleted with that account.
• Transfers: A Transfer is retained for up to 7 days after its upload finishes. It ends sooner when every Recipient has downloaded, skipped or dismissed it, or when the Sender cancels it. It also ends when sharing ends for everyone (the Owner stops sharing or deletes the Shared Project, or the last Collaborator leaves or is removed), and when its Sender leaves the Shared Project, is removed or deletes their account. An upload that stalls for 24 hours is ended. Once a Transfer has ended, no one may download it. A person who leaves or is removed stops receiving Transfers from that Shared Project. A Sponsorship ends with the membership or the Shared Project.
• Transfer files: Our daily clean-up deletes the files of an ended Transfer, normally within one day. Files are deleted immediately when the Sender cancels or when we end the Transfer. If a deletion fails, the clean-up retries each day. As a backstop, the storage itself deletes any Transfer file after 9 days.
• Transfer records: The file names, sizes, Fingerprints, note, Recipients and receipts are deleted once the files are confirmed deleted, by the same daily clean-up. Our database host may retain earlier recovery history that we cannot edit (as already stated for account deletion).
• File Requests: A File Request is retained for as long as it is open, which is not more than 7 days, and for 7 days after it ends unless it is deleted sooner as stated below, together with any reason that the Holder gave. It ends when the Holder sends the files, when the Holder declines it, when the Requester cancels it, or when it expires. A File Request is deleted at once instead when sharing ends for everyone (the Owner stops sharing or deletes the Shared Project, or the last Collaborator leaves or is removed), and when a member it names leaves, is removed or deletes their account, as stated below. The Requester may delete a declined or expired File Request, and any reason, at once by closing it, and a File Request that the Requester cancels is normally deleted at once.
• File Request records: Our daily clean-up deletes an ended File Request, and any reason, from our live database 7 days after it ends, normally within one day. Our database host may retain earlier recovery history that we cannot edit (as already stated for account deletion).
• File Requests when sharing ends or a member leaves: When sharing ends for everyone, or when the Requester or the Holder leaves the Shared Project, is removed from it or deletes their account, every File Request that names that member, or every File Request of the Shared Project in the first case, open or ended, is deleted at once, together with any reason.
• App downloads: we retain the record of each download from your account page (version, operating system and date) until you delete your account.
• Account link codes: expire after 5 minutes and are deleted after a day.
• Support messages: as described in section 6.
• Waitlist details: we retain them until you ask us to delete them. Unsubscribing stops our emails but does not delete your details, so email us if you want them deleted. Our notice of your signup remains in our mailbox until we delete it.
• Your sign-up record (section 2.1): we retain it until you ask us to delete it. If you create an account with that email address, it is deleted with the account.
• Abuse-prevention counts: one day.
• Cookies: as listed in section 8.

Deleting your account

You can delete your Outro account from your account settings at getoutro.app/account. When you do, we delete the information linked to it, namely (a) your Feedback projects and tracks, with their audio files, comments, replies and share links (which stop working); (b) any tracks that you uploaded into another person’s Feedback project; (c) the invites that you accepted; (d) your linked computers; (e) your app download records; and (f) your storage records. Tracks that Collaborators uploaded into your Feedback projects are not deleted; they move to the Feedback projects of the persons who uploaded them. Support messages sent while your app was linked to the account are erased in the same way as the in-app Delete described in section 6.5. The copies described in 6.4 (our mailbox notices and any issue-tracker excerpts) are not removed automatically, so email us if you want them deleted as well. Most of this happens immediately. Audio files are removed from storage by our daily clean-up, so the deletion of all of it from our live database and storage may take up to 30 days. In addition, our database host may retain earlier recovery history of the database, which we are unable to edit.

Each Shared Project that you own ends for everyone, as described above, and the invites sent for it are cancelled, with the addresses typed on them deleted from our database within 30 days. The persons who were on a Shared Project that ends in this way keep the copy that their own computers already hold. You also leave each Shared Project that you joined and, if you were the last Collaborator in a Shared Project, sharing ends for everyone. What you added to a Shared Project that you do not own remains in it, shown as “Former member” with your account id removed (see above). Your Folder Inventories are deleted as well (section 2.8). Transfers that you sent end, and their files are deleted by the daily clean-up described above. You are removed as a Recipient from Transfers sent to you, and your account identifier is removed from any Transfer record that is still awaiting deletion. Every File Request that names you, together with any reason, is deleted at once (section 2.10).

Deleting your account does not affect the data that the desktop app keeps on your computer. That data remains yours: you may remove it by uninstalling the app and deleting its data folder. Deleting your account also does not remove you from the waitlist, or delete support messages that you sent while the app was not linked to an account. Email us in either case.

8. Cookies and similar technologies

We use the following on our website:

• Needed for the site to work: a cookie that records which region you are browsing from, so that we know whether to ask for consent (30 days); a cookie that remembers your cookie choice (180 days); and, in the account area, Clerk’s sign-in cookies.
• Campaign cookies: if you arrive through a tagged link, such as an ad, we store the campaign it came from for 30 days, and add it to your waitlist details if you sign up.
• Analytics and advertising: Google Analytics, the Meta Pixel, the Reddit Pixel and Mailchimp’s site script, which set their own cookies.
• On shared-track pages: your browser remembers the name under which you comment.

If you are in the European Economic Area, the UK, Switzerland or California, or we cannot tell where you are, we ask first: analytics and advertising scripts load only if you choose Accept. Elsewhere, they load when you visit. If you were asked, you may change your choice by clearing this site’s cookies in your browser, and you will then be asked again. Elsewhere, you may block or delete this site’s cookies in your browser settings, and you may email us if you want us to stop.

None of the analytics or advertising scripts run in the account area, on shared-track pages or in the desktop app.

Although no analytics or advertising script runs in the account area, our server may report your sign-up to Meta and to Google Analytics from there. It does so only if you chose Accept or you are in a region where we do not ask (the same rule as for the scripts above), and it sends nothing if you chose Reject. When you open the account sign-up page, our server may report that visit to Meta. When you finish creating your account, it may report the registration to Meta and to Google Analytics. Our server sends each report after your request has been answered. A report to Meta contains the IP address and browser details of your request, the identifiers in the cookies that Meta sets on your browser (and the click identifier that we keep from an ad link), and the address of the sign-up page. A report to Google Analytics contains the identifiers in the cookies that Google sets on your browser, and the name of the event and a fixed sign-up method. None of these reports contains your email address, your name or your account id.

The only identifier that is derived from your account id is the one on the registration report to Meta. It is a keyed hash (HMAC) of your account id, made with a secret key that we do not share with Meta, so that Meta counts one registration once and cannot work out your account id from it. We send no other form of your account id in these reports.

9. Your rights and choices

Wherever you live, you may ask us to:

• Tell you what personal information we hold about you, and give you a copy
• Correct information that is wrong
• Delete your information
• Stop sending you marketing email (or use the unsubscribe link in any email)
• Stop using your personal information for advertising on third-party platforms (section 5)

To make a request, email support@getoutro.app from the address that you use with Outro. We may ask you to confirm that the request comes from you. We answer within 30 days, or 45 days where the law allows. If you disagree with our answer, you may reply and ask us to look again. If you are in the EEA, the UK or Switzerland, you may withdraw your consent at any time, and you may complain to your local data protection authority.

California residents

California law gives you the right to know what personal information we collect, use and disclose, to delete it, to correct it, and to opt out of its “sale” or “sharing,” and we will not treat you differently for using these rights. We do not sell personal information. Letting Meta and Reddit measure our ads with their pixels can count as “sharing” for cross-context advertising. Visitors from California are asked before those pixels load, and you may opt out by choosing Reject or by emailing us. Disclosing personal information, including your email address in hashed form, to Meta for advertising purposes may also constitute “sharing” for cross-context behavioral advertising. You have the right to opt out of that sharing by emailing us, as described in section 5. We do not use sensitive personal information. You may use an authorized agent, and we will ask for proof that you authorized that agent.

The categories that we collect are described in sections 2, 3 and 6: identifiers (name, email address, account id, IP address), the content you share (audio, project names, comments, support messages), the files in Transfers (section 2.9) and File Requests and decline reasons (section 2.10), activity on our website (if you allow it), and approximate location (the country or region of your IP address). We disclose them only to the providers in section 5, for the purposes in section 4.

10. Security

We protect your information in ways that fit a small team operating an early product:

• Everything is encrypted in transit (HTTPS)
• Sign-in tokens, account link codes and support receipt codes are stored on our side only as one-way hashes
• Diagnostic reports are cleaned of paths, names and secrets on your computer, before you see them
• Audio files are played through links that expire after an hour, and a share link reaches only the one track it was made for
• Transfer files are downloaded through links that remain valid for 15 minutes
• Support data is held in our database and can only be reached by Outro staff, through a restricted admin area and the copies described in 6.4

No system is perfectly secure. If a breach affects your personal information, we will tell you as the law requires.

11. Age

Outro is for people 16 and older. We do not knowingly collect personal information from anyone younger. If you believe that someone under 16 has given us their information, email us and we will delete it.

12. Changes to this policy

When we change this policy, we update the effective date above. If a change is significant, such as a new use of your information or a new kind of service provider, we will also tell you by email or in the app before it takes effect.

13. Contact us

Questions, requests or complaints about your privacy: support@getoutro.app

By mail:

Outro LLC
5900 Balcones Drive, STE 100
Austin, TX 78731, United States

See also our Terms of Service.