Sway Privacy Policy
What Sway stores for accounts, public profiles, live rooms, private Catalog work, release preparation, payments, safety, and support.
Sway processes account and public-profile data, live-room activity, private Catalog and collaboration records, release-draft and rights-review records, payment-related records, moderation records, and support or deletion requests so the service can run, protect access, and maintain an auditable history.
Data Sway may store
- account, login, Pro Mode, performer-profile, booking, social-link, and public-page records
- live-room session, queue, request, tip, and boost records
- original master and supporting-file bytes, filenames, media types, byte counts, checksums, storage locations, versions, integrity results, and project ownership records
- project membership, collaborator connections, selected-file access grants, comments, timecodes, change requests, approvals, revocations, and related audit events
- release-draft metadata, artwork references, UPCs, ISRCs, territories, recording credits, rights documents, declarations, review decisions, and readiness results
- content a performer chooses to publish on a public performer profile or an eligible public release page
- payment processor identifiers and related lifecycle status
- moderation reports, blocks, and audit events
- support and data deletion request metadata
- limited device, route, and friction telemetry needed to keep the service working
Private work and public pages
Uploading a file does not make a private Catalog file public. Project files and release drafts are available to the owner and to collaborators or reviewers who receive applicable access. A grant can be revoked for future access, but revocation cannot retrieve a copy someone already downloaded or erase audit evidence that Sway must retain. Performer-profile fields and eligible release information that a performer deliberately publishes can be viewed by anyone with the public page.
Third-party services
Sway may rely on payment, email, hosting, object-storage, and database providers when configured. Those providers may process information required to deliver the service. Provider-backed music delivery, royalty processing, collaborator payouts, pre-saves, and catalog cutover are not live; this policy does not imply that Sway currently sends a release to stores or a replacement distributor.
Deletion requests
Use the data deletion page or submit the API request path from inside the app. Sway may retain records that must be preserved for payments, fraud prevention, disputes, collaborator access history, rights evidence, moderation, legal obligations, or audit history. Creators should keep their own source-file backups; a deletion request and any required retention will be evaluated against the account, project, access, and legal records involved.