Skip to content
SoundSyncAudio software platform

Developer Data, Privacy, and Team Access

Developer Data, Privacy, and Team Access

Workspace separation, product assignments, sensitive permissions, staff sessions, and customer-information use.

Updated 2026-10-02

Separate businesses stay separate

Developer workspaces scope products, customers, orders, credentials, and operational information to the relevant business. Team membership in one workspace does not confer access to another developer's customer records.

Roles and product assignments

Team invitations and assigned roles determine permitted actions. Product scope limits which products a staff member can manage. Finance, credentials, customer access, and publication actions need their applicable permissions rather than one shared owner login.

Sessions and accountability

Revoking a staff session or changing access should affect subsequent authenticated requests. Activity records support review of sensitive changes. A visible menu or hidden button is not the authorization boundary; the service must enforce the permission.

Customer data and marketing

Access to customer records is for the developer's products and permitted business purposes, not unrestricted reuse of a platform audience. Imported contacts still require a lawful basis for marketing and must respect suppressions and unsubscribe requests.

Privacy requests and retained records

Send access, correction, export, deletion, or account-closure requests to support@soundsyncsolutions.biz. We verify the requester, review the affected information and access, and explain what can be removed and what must be retained. Closing an account, unsubscribing from marketing, and deleting personal information are different requests. No instant, all-record deletion is promised.

SoundSync retains information for the purpose it serves: operating accounts and purchased access, handling support, honoring marketing preferences, securing the service, and meeting applicable tax, accounting, dispute, and legal obligations. Unnecessary information should be deleted or anonymized. There is not one blanket retention period for all information.

SoundSync

Policies and permissions

Read the applicable privacy policy and implementation guide.

Privacy policy

Information, purposes, sharing, and rights.

Team accounts

Invitations, roles, and product scope.

Retention and deletion

Record categories and request handling.

Financial participation does not expose customer records

An affiliate or collaborator agreement does not grant developer workspace access, reseller privileges or unrestricted customer information. Team access is assigned separately. Initial referral previews retain aggregate click counts, not a public customer list or an automatically payable conversion record.