Last updated: October 26, 2026

This policy explains what data TuttiDAW (tuttidaw.com, operated by Suzhou Zhishimiaoyan Software Technology Co., Ltd., "WeaveJam", "we") collects, why, and the choices you have. The short version: we collect what the product needs to work, we measure usage to improve it, we don't sell your data, and your audio is yours.

What we collect

Account data

When you create an account we store your e-mail address, a display name, and — if you sign up or later set one — a password hash (never the password itself). We use the e-mail to sign you in, to reach you about your account, and for the notices described in the Terms of Service. No marketing mail without your consent.

Signing in with Google or Apple. If you choose "Continue with Google" or "Continue with Apple", or connect one of those accounts in Account settings, the provider tells us your account identifier with them, your e-mail address (Apple may give us a private relay address instead of your real one), your name and, from Google, the address of your profile photo. We use these only to sign you in and to fill in your profile; we never receive your Google or Apple password and we do not get access to anything else in those accounts. You can disconnect a provider at any time in Account settings, as long as you keep another way to sign in.

Profile photo. Your avatar is either the photo from a connected Google account or a generated initial; you choose in Account settings. We do not host uploaded photos. A Google photo is loaded directly from Google's servers wherever your avatar appears, so Google can see the address of whoever views it.

Plan waitlist. If you join the waitlist for a paid plan, we store your e-mail and the plan so we can tell you when it launches.

How you found TuttiDAW

When you visit tuttidaw.com, the site remembers how you found us, in two first-party cookies (one for your first visit, one for the latest visit that came through a link) with a copy in your browser's local storage: the campaign tags of the link you followed (utm_source, utm_medium, utm_campaign, utm_content, utm_term), a short campaign code if the link or address carried one (for example tuttidaw.com/go/…), the domain of the website that sent you (only the domain, never the full address), the first page you opened and when. It holds no identifier. Like any cookie of our site it travels with your requests to tuttidaw.com, but we only read and keep it when you create an account. If you create an account, we store it with the account, together with how you signed up (e-mail, Google or Apple) and, if you choose to answer it, your reply to "Where did you first hear about TuttiDAW?". We use it to count which of our videos and posts bring people to TuttiDAW; like your other account data, our staff can see it on your account.

We use these cookies regardless of what you choose in the cookie banner. Our basis is our legitimate interest in knowing which of our videos and posts bring people to TuttiDAW, so we can keep making the ones that help. They hold no identifier, are not shared with anyone, and are not used to follow you on other sites. You can object at any time: clearing cookies and site data for tuttidaw.com removes the copies in your browser (they are set again on your next visit), and if you have an account, write to contact@tuttidaw.com and we will delete the sign-up source stored with it.

Your projects and audio

• Cloud Studio projects — including audio you record or upload, edits, and project metadata — are stored on Microsoft Azure servers (East Asia region) so that you and your collaborators can work on them. Collaboration state is synchronized through Azure Fluid Relay.
• Cloud renders. When you ask for a cloud render or export, our render service, running on the same servers, processes the project's audio to produce the file and stores the result with the project.
• Local Studio projects live entirely in your own file system. They are not uploaded and we cannot see them.

Audio is processed only to provide the features you use (playback, mixing, rendering, the AI features you trigger). We do not listen to, analyze or train models on your recordings.

Muse AI assistant

When you use Muse, the messages you type and the project information Muse needs to answer — for example track, clip and device details its tools read from the open project — are sent through our own relay to our AI model provider (Anthropic's Claude models) to generate the reply. Files you attach in a Muse conversation are added to your project, not sent to the model.

We do not store the content of Muse conversations on our servers; your chat history is kept in your browser. For each request we record usage figures — the model, token counts, an estimated cost and the duration — to run, budget and protect the service.

AI audio tools run on your device. Stem separation, drum separation and audio-to-MIDI transcription run in your browser; your audio is not uploaded for them. We only download the AI models to your browser.

Connected AI apps

If you authorize an AI app (for example Claude) to work with TuttiDAW over MCP, we store the authorization: the app's name, when you granted it, when it was last used, and a hashed refresh token. While you have the editor open, an authorized app can read and edit the projects open in it, just as Muse can. You can revoke an app at any time in Connected apps.

Gallery, sharing and publishing

• Gallery. When you list a project in the public gallery, we store its title, description, link, tags, tempo, track count, the devices it uses, a small waveform preview and your display name, and show them publicly. The project itself stays wherever you host it; we periodically check that listed links still work.
• Publishing and cloud pickers. Publishing a project to GitHub or Hugging Face, and opening files from Google Drive or Dropbox, happen directly between your browser and those services. Your access tokens do not pass through our servers; if you tick "remember", the token is saved only in your browser.
• Collaborators you invite into a project see that project's contents by design.

Usage analytics

We use two measurement tools:

• Google Analytics (GA4) on the website, including the web studio, to understand how visitors find and use the site — only if you allow analytics in the cookie banner. Google then sets cookies; see Google's own privacy documentation for how it processes data.
• Azure Application Insights for product telemetry in the web and mobile apps: feature usage events, performance timings and error reports. These events carry a random identifier that is new on every visit — or, if you allow analytics, one that persists across visits — plus your account ID on server-side events such as sign-in; never your e-mail, and never audio content.

The desktop app sends no analytics; it only checks our download server for updates.

Feedback and error reports

• Feedback you send through the feedback form includes your message, its category, an optional contact e-mail, the page and app version, your browser type and, if you are signed in, your account.
• Automatic error reports from the web app contain the error message and stack trace, the page address and your browser type, without your account.

Diagnostics you choose to send

If something breaks, the editor can offer to upload a diagnostic log. This happens only after you confirm in the dialog. The log contains recent editor events and error traces, is stored in a private container, and is used solely to debug your issue. The upload dialog shows a report ID you can reference when contacting us.

Cookies and local storage

• Your sign-in session is kept in your browser's local storage, not in a cookie.
• We set a cookie for your language preference, and short-lived security cookies (10 minutes or less) while you sign in with, or connect, Google or Apple.
• Google Analytics and its cookies, and the persistent analytics identifier, are used only after you choose Allow analytics in the cookie banner. Until you choose, and if you choose Only necessary, neither is used. You can change your choice at any time under Cookie settings (in the site footer and in Account settings); withdrawing removes the analytics cookies we can reach and the stored identifier.
• The app also keeps data in your browser's storage to work: Muse chat history, editor caches and recordings in progress, a random analytics identifier, and publishing tokens you chose to remember.
• Two first-party cookies remember how you found TuttiDAW (see "How you found TuttiDAW" above); they hold no identifier, are only sent to tuttidaw.com and expire 180 days after your last visit (the local storage copy restores them while you keep visiting).

Analytics runs only with your permission. The sign-up source cookies are used regardless of your cookie choice, on the basis described in "How you found TuttiDAW" above. Everything else listed here is strictly necessary for the service to work and needs no consent.

What we do not do

• We do not sell or rent your personal data.
• We do not use your audio, or your Muse conversations, to train AI models.
• We do not read your Local Studio files.
• We do not run third-party advertising on the service.

Sharing

Your data is shared only with the providers that run the service, each processing it on our instructions:

• Microsoft Azure — servers, storage, real-time collaboration and telemetry (East Asia region);
• Anthropic — the AI models behind Muse, for the requests you make;
• Paddle — our reseller and Merchant of Record for purchases: it processes payments, card details and invoices for Pro and Muse point packs (we never see your card);
• Resend — delivering account e-mails such as password resets;
• Google — analytics, and sign-in if you choose it;
• Apple — sign-in if you choose it;
• Cloudflare — DNS for our domains and delivery of desktop app downloads.

Collaborators you invite see the projects you share with them. When you contact support, authorized staff may access your account to resolve the issue; such access is logged. We may disclose data if the law requires it.

Retention and deletion

• Projects and audio: kept until you delete them or your account. If Pro ends, nothing is deleted. Free accounts nobody signs in to for 12 months have their cloud projects archived after two e-mail notices: you receive each project as a .tutti download (links valid for 180 days), then it is deleted from the cloud (see the Terms).
• Billing records: we keep your plan and subscription status and the point packs you bought; Paddle keeps transactions and invoices for as long as tax law requires.
• Google or Apple connections: deleted as soon as you disconnect them.
• Muse usage records: kept with your account for billing and abuse prevention.
• How you found TuttiDAW: kept with your account and deleted with it.
• Backups: deleted content leaves backups on the normal rotation schedule.
• Telemetry, error reports and server logs: raw records expire on our monitoring retention schedule; aggregates may be kept.

Deleting your account. You can delete your account yourself: on the web in Account settings (tuttidaw.com/studio/account, Delete account), or in the TuttiDAW Android app under Projects → Account → Delete account. Your account, sign-in methods, presets, collections, favorites, gallery listings, Muse usage records and reports, feedback, waitlist entries and connected apps are deleted from our database immediately, together with the cloud projects you own (collaborators lose access to them). Their audio, renders and diagnostic reports are removed from storage, and their real-time collaboration sessions from Azure Fluid Relay, by an automatic cleanup that normally finishes within a few hours; backups follow on their normal rotation. We e-mail you a confirmation. If you can't sign in anymore, write to contact@tuttidaw.com.

Your rights

In Account settings you can update your display name and profile photo, set or change your password, connect or disconnect Google and Apple sign-in, see your plan and usage, change your cookie choice, and delete your account. Depending on where you live, you may also have the right to access, correct, export or delete your personal data, and to object to certain processing. Write to contact@tuttidaw.com and we will handle the request.

Children

The service is not directed at children. If you believe a child has created an account without appropriate consent, contact us and we will remove it.

Changes

We will update the date at the top when this policy changes, and announce significant changes in the product or by e-mail before they take effect.

Contact

Privacy questions: contact@tuttidaw.com.