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-11-17
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.
SoundSync
Choose a role and the products it can access
The team workspace brings members, invitations, roles and product-access choices together. Personal fields are blurred. No invitation was sent or membership changed for this image.
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 aim to acknowledge privacy requests within five business days and respond without undue delay, ordinarily within one calendar month of receipt. We explain any legally permitted extension, identity checks, retained records, and next steps within the applicable deadline; verification is not a blanket reason to restart the clock. 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.
Financial participation does not expose customer records
Affiliate and collaborator agreements do not grant developer workspace access, reseller privileges, or unrestricted customer information. Recipients receive the agreement, referral activity, allocation, and payout information needed for their own participation. Team access is assigned separately. Neither a click count nor an agreement gives access to a public customer list.
Contact records and permission
When a customer purchases a product, SoundSync automatically adds them to that developer's marketing list for product news, offers, and related updates. Eligible account and serial activity can also automatically enroll contacts for the associated developer. Existing unsubscribes, complaints, and suppressions remain protected; a new purchase does not re-subscribe an opted-out customer. Marketing messages include an unsubscribe option, separate from necessary receipts, account security, and access messages. Automatic enrollment is not evidence of affirmative consent: developers must follow the consent or other permission requirements that apply to their audience and location, and must not treat their list as an unrestricted platform-wide audience.
SoundSync
How new workflows use information
Customer details belong to the relevant store
Authorized developers can correct customer names, email and phone and, for a linked customer account, set a password for their own storefront relationship. These edits do not change the shared SoundSync login, another developer storefront, shared verification, or shared account recovery.
A changed store email or password invalidates earlier sessions and reset links issued for that store credential. The customer signs in using the corrected email in that storefront. Store-only sessions cannot manage global account security or use another store; the shared SoundSync account remains the route for platform-wide settings and integrations.
Email corrections update the store marketing contact, supported pending email work and current store contact references, including support, serial and order contact fields. Later marketing activity and imports retain the corrected store details. Customer edits to the shared SoundSync profile update shared contact records without replacing separate store details. Sent email, issued invoices and payment-provider history remain historical records.
First and last names can be cleared independently. Workspace-wide contact editing requires the existing customers.manage permission and all-products scope. Contact corrections do not transfer purchases, rewrite issued invoices, change refund eligibility or clear marketing restrictions. Last Login records sign-in activity, not a support edit.
Product access and private business information
The product overview separates product access from sales results, private reviews, delivery-file details and integration configuration. Each section follows the relevant team permission. Restricted information is unavailable to that role, not evidence that no sales, reviews or files exist.
Sensitive dashboard sections stay permissioned
Analytics access does not grant private customer snapshots, billing charges, settlement balances or reseller administration. Those dashboard sections follow the matching record permission. Goal editing requires owner or administrator settings access; read-only analysts retain their permitted analytics.
Connection diagnostics respect record permissions
Permission to inspect a product integration does not grant access to customer identities or serial keys. Diagnostics require credential-viewing access and an assigned product. Customer and device-linked information also requires customer-viewing access; serial information requires serial-viewing access. Restricted values are not returned.
Failure explanations and nested diagnostic details can repeat private information, so they require both customer and serial access. Otherwise those details are omitted. Customer-specific connection history additionally requires customer-viewing access across all products. Permitted users can still see the event type, status, package version, environment and timestamp.
Separate billing reports from payment-method management
Team members with billing-viewing permission and all-products workspace scope can read billing reports, invoices, statements and their CSV downloads. Opening the editable Stripe billing portal additionally requires billing-management permission because it can change payment methods and billing contact details.
A read-only billing viewer cannot open the editable portal. This is separate from owner-only Stripe Connect payout onboarding, the customer subscription portal and payment execution. Existing role definitions are unchanged.
Closing one store account is not deleting SoundSync
The developer customer-removal action closes and blocks the customer account at that store and stops supported pending marketing and measurement. Required purchase and financial history remains. Access through that closed store is blocked; the shared SoundSync identity and unrelated stores are not deleted.
Account closure, a refund, unsubscribing and a privacy-erasure request have different effects. For broader privacy requests, contact support@soundsyncsolutions.biz. Existing retention and legal obligations still apply.
SoundSync suspension and store restrictions
A SoundSync-wide customer-account suspension blocks customer library and download authorization, including requests made with an existing signed-in session. A restriction imposed by one store remains scoped to that store; unrelated stores remain available unless the SoundSync account is also suspended.
Suspension does not delete purchase history or create a refund. Contact SoundSync support about a platform restriction and the developer about a store restriction. A previously issued storage link can remain usable until it expires; already downloaded files cannot be recalled by an account restriction.
Private setup does not become public content
Payout-email verification, team invitations, private upload links and protected-content device proof serve their specific account or delivery purpose. They do not grant customer-table access to collaborators, marketing authority to a payment recipient or workspace authority to a customer account. Existing role and product restrictions still apply.
Activity stays within the teammate's permitted records
The combined analytics activity feed follows assigned products, including its counts and product filters. An empty assignment returns no activity. Productless website events and workspace-wide email events are not included in a product-filtered feed; a mixed-product sale shows only its selected item amount.
Customer and visitor identity, serial details and private order references follow their separate record permissions. Free-text diagnostics and nested metadata need the complete supporting record permissions. Search runs after those fields are filtered, so a hidden email address cannot be used to identify activity. Authorized analytics remain available.
Workspace-wide revenue reports and their analytics aliases require all-products access. Aggregate totals do not grant access to customer lists, subscription identities, order references or individual refund records. Refund details require refund access; private customer/order searches also require those record permissions.
