Security

Analysis, rendering and video export all run on your machine through the Web Audio API, WebGL/Canvas and WebCodecs. Music, images and other files you import stay in your browser: saving a project stores your settings and each imported file's name and fingerprint, never the file itself. Neither rendering nor saving uploads a file you import, so there is no server-side copy of it to leak. Transcription and vocal isolation download the model to your browser and run it locally too, so the audio is not sent to an inference service. Earlier versions of Studio kept a private copy of files that signed-in members imported; those copies were never public, and they still open in the projects that use them.

When music posting is available, publishing can upload a compressed copy of the full song or preview you selected, plus resized image copies. Saving an editor project does not upload its originals. The server checks ownership of uploaded copies, validates their type and duration, and requires the current music ownership confirmation before publication. Exact matches against previously reviewed files are reviewed by hand; the automatic check does not issue strikes or establish copyright clearance.

Accounts use Better Auth with optional passkeys and an optional authenticator app, which then asks for a six-digit code after the password at sign-in. A passkey check counts only when the passkey asks for its own PIN, fingerprint or face. Owner and administrator accounts cannot open the admin until they hold a passkey or an authenticator app, and every administrative action needs a fresh passkey or authenticator check on top of an already valid session and writes an immutable audit event; an account with admin access that already holds one also needs that check before adding another passkey. Removing a passkey or changing your username needs a sign-in from the last ten minutes, a fresh passkey or authenticator check, or a code from the app, and turning the authenticator app off needs the password and a current code or a backup code. Connecting Google to your account needs a sign-in from the last ten minutes or a fresh passkey or authenticator check. Changing your password signs out every other device, and a new password that already appears in a known data breach is refused: only the first five characters of its SHA-1 fingerprint leave the server for that check, to the free Pwned Passwords service, and if the service does not answer the password is accepted. A new password, passkey or Google connection appears in your Security notifications, so a change you did not make stands out. Account recovery uses a passkey, a single-use hashed recovery code, or an existing trusted session, and a password set through recovery signs out every device. Sonic Weaver does not send account email, so there is no reset link to intercept.

Sign-in, sign-up, recovery codes and second-step codes are limited per network address, and the counts live in the database, so a restart does not reset them. Wrong passwords are also capped per account, from every address together: after ten in fifteen minutes, that account's password sign-in pauses for up to fifteen minutes while a passkey, Google and a recovery code keep working, and a right password never counts. These limits are on for the live site.

Application data access goes through server-only data-access modules. Projects, assets, community posts, profiles, notifications and admin operations each re-verify the session and the relevant ownership, visibility, suspension or role boundary on every call rather than trusting a check made earlier in the request. Mutation routes additionally require an exact trusted origin. Answers that belong to your account are never stored by a cache and are sent with Cross-Origin-Resource-Policy same-origin, so a page on another site cannot load them. When something fails inside the server, you get a plain sentence; the server's own error text, which can name its tables and the values it was given, stays in its log.

Client upload tokens are short-lived, scoped to an authenticated owner and a random object path, and bounded by declared type and size. What arrives is then checked by magic bytes and a real decode; SVG and 3D model inputs get format-specific sanitisation, and anything unparsable or incomplete is quarantined rather than served. An SVG is checked as the browser will read it, with namespaces and character references resolved, and your own SVG opens as a download rather than as a page on this site. Community pages serve only a separate public-preview derivative, never the private source object. Downloads of your own files have a daily ceiling per account, counted in the database, so a script cannot run up the site's transfer bill; reopening a project whose files have not changed costs nothing against it.

Phone photos carry hidden details: the GPS position where they were taken, the phone that took them and when. A picture you choose for your profile, a post's still or a post's images is redrawn on your device before it is uploaded, which keeps the picture and drops those details. The server then refuses any public picture that still carries them, and the public picture addresses serve a copy without them if an older file has any.

Links can start a project already set up: a look, a background, an overlay, even edits in plain words. When a link names one of your saved projects, Classic opens it and ignores anything the link asks to change, and says so, so nobody can send you a link that rewrites your work. SW Agent only puts a message in its box from a link; nothing runs until you press Send.

Project writes carry a revision token. A save built from a stale copy of the document is rejected instead of quietly replacing newer work, which is the difference between a merge conflict and lost work.