AAudiencoreSoundCloud-first planning
Draft / informational summary

Privacy

Editing music, plans and observations saves them in this browser. Workspace copies can explicitly transfer a copy to your account; Community stores published requests and peer responses on the server when that service is enabled. Workspace data is not automatically uploaded. General browser analytics remains disabled; the separate optional Discover observation described below runs only after explicit account opt-in.

Data used by current visible flows

  • When SoundCloud registration is enabled, we confirm your SoundCloud identity, verify the email you enter and save one to five chosen music genres before creating your account. Resend receives the email address and verification message when sending is configured. Verification does not subscribe you to marketing or enable invitations. SoundCloud API credentials are encrypted on the server. Disconnect removes API access and saved profile details while retaining the separate identity used to sign in. Eligible account deletion removes that identity too.
  • Unfinished registration uses a limited browser-tab session and server records with a maximum thirty-minute validity. Codes expire after ten minutes and allow five guesses. Expired records are removed in bounded batches on later signup activity, rather than by a timed purge. Minimal sending-limit records are eligible for cleanup after twenty-four hours. After account deletion, a keyed identity marker prevents an earlier unfinished signup from recreating it for up to thirty minutes; it contains no plain SoundCloud ID. Downloaded copies, backups and the email provider have separate retention boundaries.
  • Product ideas stores independently authored proposal text, review stage, publication state and dates, staff author and original creation reference. Active members see published copy, vote counts and their own vote; author identities, other voters and private Support references are not shown. Each vote stores its account, idea and date. Withdrawal hides a proposal from members but retains its staff copy and votes. My data includes your own authored proposals and original creation references plus your own vote IDs and dates; existing export/deletion limits apply. The current browser tab retains your exact attempted vote or staff publication/edit before sending, and may retain a confirmed receipt for local cleanup. It does not copy Support conversations. Unsent typing, closing the tab and clearing storage remain outside recovery; local discard does not erase server records.
  • Staff workflow recovery uses bounded account-scoped browser-tab storage for the original reviewer role, case identifiers and revision, attempted case link, backlog item, next action, UTC date and internal explanation. It copies no requester complaint, conversation or source evidence. Matching current workflow fields do not prove that an earlier internal explanation was saved. Nothing is read or sent automatically when recovery opens. Local discard does not reverse server changes; tab closure or browser cleanup can remove the copy.
  • Invitation report recovery keeps your own attempted complaint and original invitation identifiers in account-scoped browser-tab storage before sending. Its saved receipt may include your original complaint and private ticket ID. Staff decision recovery retains only the original reviewer’s own attempted explanation, case identifiers and revision, without copying the requester’s complaint, invitation evidence or conversation. Recovery opens no case and sends nothing automatically. Local discard does not remove a server report or final outcome; closing the tab or clearing browser storage may remove the recovery copy.
  • The public preparation checklist keeps self-reported answers in the current tab. It makes no remote analysis or tracking request. You can explicitly download a private JSON note, which may include private link parameters, or confirm a browser-local music and campaign draft. Refresh loses unsaved answers. A preparation note is not a workspace backup.
  • Private music covers and Support screenshots store normalized WebP bytes, dimensions, size, checksum, timestamps and retry receipts. Originals, filenames and embedded metadata are discarded. Covers start owner-only. You can explicitly share a reviewed cover with eligible signed-in participants of one feedback request. A permission receipt records the request, selected file checksum, timestamps and private retry information; it copies no image bytes. Withdrawing permission keeps your private file. Replacing/removing the file or its source withdraws prior sharing. Hidden requests and inactive source artists prevent participant reads; already loaded or downloaded copies cannot be recalled. Screenshots are available to their owner and authorized support staff under the ticket access rules. Each file is fetched only when you choose view or download. Replacement or erasure removes the prior stored bytes and prepared export copies, retaining minimal retry information until the source or account is deleted. Workspace save/clear erases covers for removed or changed music sources. The Community export includes your normalized private images; browser workspace backups do not. Eligible account deletion cascades these records. Downloaded copies cannot be recalled; backup retention remains separate.
  • Saved musicians are private account bookmarks containing the owner, saved musician and save time. Saving creates no invitation or notification and does not grant access to private preferences or contact details. Only the owner can read or remove their list. Opted-out, inactive or muted profiles are redacted on the list and in the owner export. There is no public follower count or list of who saved you. A bookmark does not guarantee matching or availability for any request. Deleting either account cascades the saved entry.
  • My data offers an explicit Community JSON download for the signed-in account. It includes your account details, saved workspace and settings, authored requests, feedback and versions, authored discussion messages, your reports, participant invitation receipts, Community Activity and owned support tickets with their public conversation and appeal receipt. Hidden content stays redacted. Other participants’ feedback and discussion messages, staff-only notes and credentials are excluded. The direct export builds a current snapshot on request. A separate larger-export action stores an owner-only preparation job and temporary private file parts, available for 15 minutes from the request. You can remove that copy; expiry denies download immediately and cleanup removes it while the API runs or on startup. Replacing or erasing private images invalidates older prepared copies. Normal request rate limits and explicit size limits apply. The downloaded file is private and remains on your device. This scoped export is not a workspace restore file or a full export of legacy account records. My data also offers confirmed account deletion for eligible Community-only accounts. Legacy/staff-account erasure and final retention periods remain separate work.
  • Feedback edits preserve immutable versions of the original text, optional focus/timestamp context, advisory writing observations, edit explanation and time. The author and requesting artist can read this history while the source and participants are available; staff have no general history access. Moderation and appeal reviewers receive the specific version tied to their report. An edit clears the current helpfulness rating and may create a generic Activity notice. Open reports about that feedback temporarily pause editing without hiding it or exposing the complaint; reports about discussion messages do not hold feedback edits. There are at most 20 versions; individual versions cannot be erased separately. Deleting the underlying feedback, request or relevant account cascades its versions. Legacy/staff-account export and erasure, and final retention periods, remain separate work.
  • Private feedback discussions are ordinarily available only to the requesting artist and feedback author while the source and participants remain available. They store messages and each participant’s pause setting. Reporting a message shares that specific message, its author role/date, request context and your complaint with independent moderators; it does not give them the rest of the conversation or feedback history. A report does not automatically hide anything or pause discussion. Message removal hides only that message, retaining its body for limited moderation and appeal review. Deleting your own message erases its body, including after moderator removal, and removes its original reply notice; its placeholder and any report/decision remain. Erased text is not copied into reports and cannot be restored on appeal. Deleting the source cascades discussion records and their reports. Removal of the parent feedback or request hides the whole discussion.
  • Removal appeals reuse private support tickets. The affected author’s statement, correspondence and conflict-of-interest exclusions remain if the original source is deleted. Independent assigned staff can explicitly review the original request, relevant reported feedback or individual reported message, and complaint to decide the appeal; this does not grant general access to participant discussions or private workspace plans. A message appeal excludes other messages and feedback text. Author-erased message bodies remain unavailable even if a removal is overturned. The outcome, public explanation, date and private reviewer audit information are retained with the ticket. Authors see the public receipt; reporters see only outcome and date. Original-source deletion removes its context, but the support receipt and its generic Activity notice remain until their support source is deleted. Ordinary ticket resolution does not reverse moderation. Legacy/staff-account export and erasure, and final retention policy, remain separate work.
  • Community Activity stores account-owned event types, generic notification copy, timestamps, read/archive states and source references for feedback, invitations, reviewed reports and public support updates. It does not copy music titles, names, feedback text, questions, report details or support messages. Source deletion removes related notifications; current-day delivery counts remain. Category/pause preferences and a UTC daily cap are saved separately from workspace backups. Suppressed events are not queued or replayed. The authenticated interface checks the unread count and refreshes activity through the collaboration API; no external delivery or analytics service is involved.
  • Support tickets and feature ideas are private account records shared with authorized support staff. They store your subject, description, category, priority, current status, idea stage, optional reference, timestamps and public conversation. Staff also record internal notes, assignment and explained changes. Internal notes and assignment history are excluded from the owner conversation; staff do not receive automatic access to the private object referenced by a ticket. Closing a ticket does not erase it. The Community export includes your public ticket conversation. Eligible account deletion removes your own tickets, including staff conversation; independent tickets owned by others may remain. Final retention periods remain separate work. Avoid passwords, API keys, payment details or unnecessary personal information in messages. Support is in-app only. You can explicitly attach private screenshots for yourself and authorized support staff; private suggestions are separate from the independently curated Product ideas board. External helpdesk delivery is not enabled.
  • Account/profile data for the existing login foundation and related account workflows.
  • Browser-local language, appearance, creator context, campaign drafts, and planning notes used by the planning workspace.
  • Browser-local music metadata, multiple campaign plans and manually recorded observations. The release journal can export those observations to a CSV file on your device. Avoid putting private contact details in these notes.
  • When you explicitly save to your account, your music, campaign plans and observations are stored on the server for that account. A JSON backup can be exported or restored through Workspace copies.
  • Music preferences explicitly saved in Peer feedback are private account settings: primary, secondary and blocked genres, genre-discovery choice, feedback discovery and long-form discovery. They filter your community feed and explain matches. They are separate from creator settings and music workspace snapshots, and are not published on your requests or included in workspace backups. Clearing the workspace does not reset them; you can edit or empty the genre lists in Music preferences.
  • Publishing a peer feedback request shares a snapshot of its music title, artist name, link, format, genres and your question with other signed-in participants. Private campaign notes, audience details and planned budgets are not published. Feedback text is visible to its author and the requesting artist; reported content is also available to authorized moderators. Helpfulness ratings are visible to the participants.
  • Feedback may include optional focus areas and a timestamp for a track, remix, mix, podcast episode or live set. The server stores versioned advisory notes about repeated sections, repeated letters/numbers and exact reuse of the same three sections within the author’s last 20 visible responses. It does not compare different authors or retain a link or copied text from the earlier response. Notes describe submission time and remain if an earlier response is deleted. They share the response’s access and deletion rules, have no Core or trust effects, and are hidden with the text when feedback is removed by moderation. Artist summaries count visible feedback, ratings and focus areas without inferring sentiment or music quality.
  • Reports store the reporter, target, reason and explanation. Authorized moderators can inspect reported content and record a decision. The reporter can see their own report and decision explanation. Reporting does not hide content automatically; moderator removal hides it from participation, while the record remains until its author deletes it.
  • Feedback invitations are separate account records. Receiving is off by default. Enabling it makes your display name and request-specific genre-match explanation discoverable by active artists with a compatible published request; your full taste lists and contact details are not returned. Only sender and recipient can read the invitation record. Settings, muted-artist records and per-day send/receive counts are stored separately from workspace backups. Opt-out or mute closes pending invitations. Deleting the published request removes its music/question from invitation cards; minimal participant/status/date history and daily counters remain so deletion cannot reset sending limits.
  • Earlier interest notes may remain in browser storage after the interest form was retired. The current entry flow does not read, send or delete them. Internal local-review notes remain confined to that browser.
  • Safe operational logs should not include passwords, tokens, cookies, raw support text, or private message bodies.

Current limits

  • General browser analytics remains disabled: no analytics anonymous ID, page-view, CTA or login events. Optional standard Discover display observation is a separate, default-off account choice.
  • No Google Analytics, Meta Pixel, TikTok Pixel, PostHog, Mixpanel, advertising cookies, fingerprinting, or session replay is connected.
  • SoundCloud sign-in and transactional verification email require explicit server configuration. Checkout, cash withdrawal, marketing email and automatic SoundCloud engagement remain inactive.
  • You can clear your server workspace in Workspace copies without changing the browser copy or published community content. You can delete your own published requests and feedback in Community. Deleting a request also deletes its received feedback and related reports; deleting a response deletes reports about that response. Moderator removal hides content but does not itself erase it. My data offers permanent deletion for eligible ordinary Community-only accounts with a reviewed snapshot and either their current password or fresh SoundCloud confirmation for a passwordless account. It deletes the account and supported server records, including owned requests with responses and discussions, authored feedback/messages, settings, Activity, invitations, reports and owned support tickets. Financial, legacy and staff records require support review. Independent support and appeal records owned by other people may remain, including correspondence and conflict exclusions. Browser-only plans, downloaded copies and backups are not erased. Backup retention and a final retention schedule remain separate work. This page is an informational summary, not final legal policy.

Optional Discover observation

Account settings offers a default-off choice to help understand reported standard Discover displays and later participation. A card at least half visible for one continuous second in a foreground tab can produce one record per account, task and consent period. It stores account/task references, consent revision, server time and any later original assignment reference/link time, with original campaign, execution and quote references for server-side source checks. This is reported display, not attention, listening, completion or causality. Records expire after 90 days and immediately leave history, exports and summaries; physical removal runs when internal cleanup is next available. At most 1,000 unexpired records are retained per account; withdrawal deletes optional observations and links, while original assignments, financial records and the consent setting remain. Own history and account export include retained records. Internal reporting uses combined counts. No anonymous ID, browsing path or third-party service is used. Manage observation consent and history.

Preserved backend analytics models and admin foundations are not approval to collect browser events. Any collection beyond this narrow optional scope requires a founder-approved privacy/security scope covering event purpose, notice, data minimization, retention, access, deletion/export, and testing before browser collection can be enabled.

Cookie summaryRead first-run help