Privacy Policy

1. Who we are

Aimi, Inc. (“Aimi”, “we”, “us”) is the controller of the personal information described here. This policy covers Aimi Session, the Aimi Mixtape listening site, and our websites (together, the “Service”). Our Terms of Service govern your use of it.

The Service is operated from, and directed to, the United States. Your information is stored and processed here. It's reachable from elsewhere and you're welcome to use it, but it is a US service and this policy is written on that basis; where your own country's law gives you rights beyond those set out here, we'll honour them (section 11).

Questions about anything below: support@aimi.fm.

2. What we collect

Information you give us

• Account details — your name, email address and a password, which we store only as a salted hash. We never see your password.
• Profile — if you set one up: handle, display name, avatar, tagline.
• Your content — projects and sessions, audio you upload, generated stems and renders, MIDI, arrangements, mixes, lyrics, titles and artwork.
• Your messages — prompts and conversations with Aimi, and any direct or group messages, comments and challenge entries you send to other members.
• Support correspondence — what you write to us, and our replies.

Information we generate as you use the Service

• Credit records — a ledger of your balance, each grant, purchase, refund and turn charge, and the conversation a charge belonged to.
• Usage records — which features you used and when, producer turns taken, and AI token totals, so we can meter credits and understand where the product is working.
• Technical and security data — IP address, browser user-agent and timestamps recorded against your login sessions; server request logs; error diagnostics.

Information from others

• Payments — Stripe tells us that a purchase succeeded, which pack it was and the checkout identifier, so we can add credits. Full card numbers never reach us; Stripe handles them.

We don't buy personal information from data brokers, and we don't ask for anything we don't need. There is no advertising or cross-site tracking anywhere in the Service.

3. How we use it

We use personal information to:

• create and run your account, and keep you signed in;
• store, render, stream and export your projects and audio;
• run Aimi on your instructions (see section 4);
• meter, grant, sell and reconcile credits, and process purchases and refunds;
• power the community — publishing, remix trees and attribution, follows, comments, challenges;
• provide support, and tell you about material changes to the Service or these policies;
• keep the Service secure and available: abuse and fraud prevention, rate limiting, debugging;
• understand aggregate usage so we can improve the product;
• develop, train, evaluate and improve machine learning and AI models — using only the tracks you publish, never private projects and never your conversations with Aimi; see section 4;
• comply with legal, tax and accounting obligations, and enforce our Terms.

Why we train on published tracks

To make Aimi, the AI Producer, better at arranging, mixing and generating music for the people using it. Music made in the product is what teaches it, and there is no substitute for real sessions: what Aimi has to learn is how people actually combine, sequence and mix material. We use only what you choose to publish, and you can switch it off (section 11).

Publishing is what brings a track into scope, and nothing else does. Private projects, the audio you uploaded into them, and your conversations with Aimi are never training material — not by policy alone, but because the system that assembles training material cannot reach them.

You can switch it off at any time, and you don't have to ask us or give a reason. One switch in Settings covers everything you have published as well as everything you publish next, and withholds the audio you uploaded into those tracks. You can also mark an individual project to stay out even if you publish it later. Unpublishing a track takes it out too.

Switching it off costs you nothing else. Your track still publishes, still plays, still appears on Mixtape, and others can still remix it where remixing is available at all.

It doesn't reach backwards into a model already trained (section 8), and it doesn't affect processing carried out before you switched it off. Turning the switch back on restores the default for new tracks only: anything already withheld stays withheld until you re-include it deliberately.

4. AI processing

Aimi runs on models operated by third-party providers. When you give Aimi an instruction, we send that provider what it needs to answer: your prompt, the relevant state of your session (track names, arrangement, settings, lyrics), and recent conversation turns. Generating audio additionally sends the musical description of what you asked for to our generative-audio provider.

We send the minimum the task needs, and we don't attach your name, email or payment details to those requests. We select providers whose API terms limit use of submitted content to returning a result to us.

Producer conversations are stored with your account so you can pick a session back up, and so we can investigate problems and abuse. Settings lists every conversation and deletes any of them, transcript and all, and deleting your account deletes them all. They are never training material.

Model training — only what you share

We train our models only on projects you choose to share. While a project is private, neither it nor the audio you uploaded into it is used as training material. Keep everything private and none of your work is ever trained on.

Sharing a project opens it up to be built on, by two audiences at once: other members, who can fork and remix it, and our machine learning models, which can learn from it. When you share, we may analyse the shared project — its structure and arrangement, the audio in it including audio you uploaded, and the generated output it contains — and use it to develop, train, evaluate and improve machine learning and AI models, our own and models we develop together with providers.

Unsharing takes the project out of future training runs. It cannot reach into a model that has already learned from it, so it works forwards rather than backwards — see section 8.

Where it does the job we work with aggregated or de-identified data, and we don't attach your name, email or payment details to training material. Training doesn't change who owns your music (Terms, section 6), and we never sell your content.

Separately, we always analyse how the Service is used — feature usage, producer turns, error diagnostics and aggregate statistics — to operate, secure and improve it. That's usage telemetry rather than training on your music, and it applies whether or not you ever share.

Questions, or a request about a specific project: support@aimi.fm.

5. Who we share it with

We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We disclose it only to the following:

These providers act as our processors (or, for Stripe's own compliance duties, as an independent controller) under contracts that restrict what they may do with the data.

We may also disclose information: to other members, where you publish or message (section 6); to professional advisers such as auditors and lawyers under confidentiality; to authorities where we're legally required, and we'll tell you unless we're prohibited from doing so; to protect rights and safety — ours, yours or the public's; and to a successor entity in a merger, acquisition or sale of assets, in which case this policy continues to apply until you're told otherwise.

6. What's public

Nothing you build is public until you publish it. Your projects, uploads and producer conversations are private to your account.

When you publish a track to the community or to Mixtape, the track, its title, artwork and description, your profile handle, display name and avatar, and the remix lineage of the session become publicly visible — to listeners without an account, and to search engines. Comments, likes, reposts, follows and challenge entries are visible to other members. Direct and group messages are visible to the people in them.

Unpublishing removes a track from display and discovery, but copies already downloaded, cached externally, or remixed by others under the licence in our Terms may persist.

7. Cookies

We use cookies and equivalent browser storage for two things:

• Signing you in — a session cookie that keeps you logged in, and remembers security state. Strictly necessary; the Service can't work without it.
• Your preferences — local storage for interface settings so the studio comes back the way you left it.

We do not use advertising, profiling or cross-site tracking cookies. The pricing section of our landing page embeds Stripe's pricing table, and Stripe may set its own cookies there under Stripe's privacy policy.

8. How long we keep it

• Account, profile, projects, uploads and conversations — for as long as your account is open. Deleting your account deletes them, and deletes the uploaded audio from our storage rather than only removing the listing. You can delete an individual project or conversation at any time.
• Backups — deleted content can persist in routine encrypted backups for a short period before it ages out.
• Published tracks — removed from display when you unpublish or close your account, and the rendered audio behind them is deleted. Remixes others have already made from them remain, including the copy of your uploaded audio their session holds (Terms section 8) — though withholding that audio from training still reaches it.
• Login session records (IP, user-agent) — retained while the session is valid and for a short security window after.
• Credit ledger and purchase records — retained after account deletion where we need them for tax, accounting and fraud-prevention obligations, typically seven years, reduced to what those obligations require. We strip your identity out of them when the account goes: the financial history remains groupable as one former account, without naming you.
• Support correspondence — up to three years after the matter is closed.
• Aggregated, de-identified and derived data — including datasets, statistics and models trained on shared projects under section 4 — may be kept indefinitely. Once data no longer identifies you, deleting your account doesn't remove it, and a model already trained can't be untrained.

9. Security

Data is encrypted in transit (TLS) and at rest by our cloud provider. Passwords are stored as salted hashes. Access to production systems is limited to staff who need it, authenticated through our cloud provider's identity controls, and administrative actions on accounts are recorded in an audit log.

No system is perfectly secure. If a breach affects your personal information, we'll notify you and the relevant regulators as the law requires.

10. International transfers

We're based in the United States, and the Service runs on infrastructure in the United States. If you use it from outside the US, your information is transferred to and processed in the US and in other countries where our providers operate.

Where a transfer out of your country needs a specific legal mechanism, we use the applicable standard contractual clauses or another lawful transfer mechanism, together with the technical and organisational measures described in section 9. Write to support@aimi.fm for details of the safeguards in place.

11. Your rights

Wherever you live, you can: access your information, correct it, export your projects and audio at any time from the app, and delete your account and its content.

Depending on where you live, your local law may give you further rights — a copy of your information in a portable format, restriction of or objection to particular uses, withdrawal of consent where we relied on it, or a complaint to your national data-protection regulator. We honour those rights on request wherever they apply, and we'd appreciate the chance to sort a problem out before you escalate it.

You can stop us using your published tracks for model training, whoever and wherever you are. It's a switch in the app, not a request: you don't need to write to us, give a reason, or wait for us to agree, and it covers the tracks you've already shared. It costs you nothing either — your tracks stay published and everything else keeps working.

Most of these rights are controls in the app, not requests you have to make of us. Settings holds them:

For anything not covered by those, write to support@aimi.fm from your account email. We respond within 30 days, and we won't charge you or treat you differently for asking. We may need to verify your identity before acting on a request.

Note that we can't delete your personal information from a published track that others have already remixed without unpicking their work; in that case we remove your track and your attribution links on request, and the derivative works remain. Two things reduce how often that arises: a project containing audio you uploaded is never handed on as a session in the first place (Terms section 6), and withholding your uploaded audio from training reaches the copies inside existing remixes.

12. US privacy rights

State privacy laws differ, and several only apply to companies above a certain size. Rather than make you work out which one covers you, we extend the same rights to every US resident, whatever state you're in and whether or not it has a privacy law yet:

If we turn a request down

You can appeal, and we'll tell you how at the time we decline. Write to support@aimi.fm with “appeal” in the subject; we'll review it and reply within 45 days with our decision and the reasoning behind it. If we still say no, you're entitled to complain to your state Attorney General, and we'll say so then rather than leave you to find out.

What we don't do with your information

We do not sell personal information, and we do not share it for cross-context behavioural advertising — including that of anyone under 16, and we have not done so in the preceding 12 months. There is no advertising or cross-site tracking anywhere in the Service.

That's why you won't find a “Do Not Sell or Share My Personal Information” link here, and why we don't act on browser opt-out signals such as Global Privacy Control: those mechanisms exist to stop a sale or an ad-targeting share, and we make neither. We'd rather say that plainly than have their absence look like an oversight.

What we've collected in the last 12 months

All for the purposes in section 3, and disclosed only to the service providers in section 5: identifiers (name, email, IP address, account ID); commercial information (credit purchases and balances); internet and network activity (feature usage, request logs); audio and other user content; and inferences drawn only from your own usage, for product improvement.

On sensitive information. We don't collect it in order to infer anything about you, and we don't use audio to identify anyone. A vocal you upload is treated as your creative work, not as a voiceprint: we run no speaker recognition, no voice matching and no voice-similarity search, and nothing in the Service tries to work out who is singing.

Exercise any of these at support@aimi.fm, or use the controls in section 11. You may use an authorised agent; we'll ask for proof of authorisation.

13. Children

The Service isn't intended for children under 13, and we don't knowingly collect their personal information. If you believe a child under 13 has given us information, write to support@aimi.fm and we'll delete the account and its data.

Our Terms require anyone under 18 to use the Service with a parent or guardian's involvement. To be straight about how that works in practice: we ask you to agree to those Terms, we don't ask your age, and we have no way to verify that a guardian was involved. If you're a parent or guardian and you'd like an account and its content removed, write to us and we'll do it.

14. Changes to this policy

We'll update this policy as the Service changes. Material changes come with reasonable advance notice in the app, by email, or both, and the “last updated” date above always tells you which version you're reading.

15. Contact

Aimi, Inc.
Privacy questions, requests and complaints: support@aimi.fm

See also our Terms of Service.