Guide
Customer Information and Privacy Requests
Developer data boundaries, marketing choices, privacy requests, and retained records.
Your information has a purpose
SoundSync uses account, order, licensing, device, delivery, support, and marketing information to provide the requested service. Customer information is not a general-purpose platform audience that any developer can access.
Demo bookings and meeting invitations
When you book a SoundSync call, we use your name, email, optional company, phone and message, meeting type, time zone and selected time to arrange the meeting, respond to your request and send booking messages. Booking records include the meeting status and calendar or meeting references. Do not put passwords, full serials or payment details in a booking message.
Google Calendar receives your name, email, optional company and message, and meeting details to create the calendar event, attendee invitation and Google Meet link. Booking confirmations and organizer notifications use the transactional email service. Optional phone details are kept in the SoundSync booking record and can appear in the organizer notification; they are not added to the calendar event by this integration.
Booking information follows the purpose-based retention and privacy-request rules on this page and in the retention guide. Contact support@soundsyncsolutions.biz about a booking-related correction or deletion request. Calendar invitations and messages already delivered to recipients or held by a provider are separate copies; deleting a SoundSync record does not recall those copies.
What developers can see
A developer receives information relevant to their own products, purchases, support, and permitted customer relationships. Workspace and product permissions limit staff access. Sensitive financial and credential actions require their own permissions.
Purchases, marketing, and your choices
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 does not sell personal information or provide an unrestricted platform-wide mailing list.
Retention, deletion, and account closure
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.
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
Read the actual policies
The privacy policy covers information and rights; the retention page explains the record categories.
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
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.
Google Analytics on branded storefronts
When a developer configures GA4 for an eligible verified custom-domain storefront, this integration loads the Google tag and queues page views automatically on supported public pages. It does not wait for visitor opt-in, and a previously saved analytics decline does not disable this integration. Account, sign-in, developer and owner routes are excluded by its public-page rules.
The page URLs supplied by this integration omit query parameters except permitted catalog, product and bundle selectors; supplied referrers omit queries and fragments. This does not mean analytics is anonymous or cookie-free. Google processes information under its own terms and the configured property settings. Necessary account and checkout storage is separate.
This is not a consent-management system or a guarantee of legal compliance. The former soundsync:analytics-consent event is not a supported switch for this tracker. Developers must assess applicable notice and consent requirements before enabling analytics and arrange any required controls; a notice alone does not enforce a visitor choice.
Automatic enrollment and sending permission
Purchases and eligible storefront signups automatically add contacts to the relevant developer marketing list. These automatic account and purchase flows do not currently offer a separate marketing opt-out at collection. Saved unsubscribes, complaints and suppressions remain protected; necessary service messages are separate from marketing.
Being on a list does not establish affirmative consent or permission for every audience or location. A later unsubscribe link is not evidence that a choice was offered when details were collected. Before sending where permission or a collection-time choice is required, establish the applicable permission and keep its evidence. Automatic enrollment is not a promise of universal marketing-law compliance.
