Privacy Policy
Privacy Policy
How SoundSync Solutions uses personal information, shares it for services, honors marketing choices, and handles privacy requests.
Updated 2026-11-17
Who is responsible
SoundSync Solutions is registered in Michigan, USA. Our business address is 2632 Crossing Circle #1010, Traverse City, Michigan 49684, USA. Contact support@soundsyncsolutions.biz for support, billing, privacy, or security questions.
SoundSync Solutions operates the platform and its managed-commerce, account, security, support, and related data processing. Developers also have responsibilities for information they use in their own product, support, and marketing relationships.
SoundSync
Information and purposes
Information is used for the service or obligation it supports.
| Information | Purpose |
|---|---|
| Account and contact details | Account access, developer identity, support, and necessary communications |
| Orders, payment references, refunds, disputes, and payout details | Purchase fulfillment, reconciliation, settlement, and legal obligations |
| Customer location and tax information | Applicable checkout tax and supporting tax records |
| Licenses, serials, entitlements, and device identifiers | Product ownership, claims, activation, validation, and device limits |
| Download and service activity | Authorized delivery, troubleshooting, operation, and security |
| Campaign contacts, consent, suppression, and engagement | Permitted marketing, preference enforcement, and reporting |
| Support correspondence | Responding to requests and resolving product or account issues |
| Demo booking contact details, messages, meeting times and calendar references | Scheduling requested calls, sending invitations and booking messages, and handling meeting-related support |
| Team roles, invitations, agreements, referral activity, and recipient allocations | Scoped workspace access, intended-recipient onboarding, accepted terms, permitted attribution, and financial settlement |
Why information is processed
Where applicable, processing is based on providing the requested service or contract, meeting legal obligations, legitimate interests such as service security and fraud prevention, or consent for activities requiring it. Purchases automatically enroll eligible customers in the relevant developer marketing list, subject to protected preferences and applicable permission requirements.
Sharing for the relevant service
Relevant product developers receive the information needed for their products, customer support, and permitted customer relationships. Stripe, PayPal, and providers supporting hosting, storage, delivery, email, security, or requested assistance process information needed for those functions.
SoundSync does not sell personal information or provide unrestricted customer lists for unrelated third-party advertising. Information may also be disclosed where legally required or necessary to address a dispute or protect lawful rights.
Purchases and automatic marketing enrollment
When a customer purchases a product, SoundSync automatically adds them to that developer's marketing list for product news, offers and related updates. Eligible storefront signups, account and serial activity can also enroll contacts for that developer. These flows do not currently offer a separate marketing opt-out at collection or require a separate marketing opt-in checkbox.
Saved unsubscribes, complaints, refusals and suppressions remain protected. Signing in, correcting an email or buying again does not silently clear them. Marketing messages include an unsubscribe link; minimal preference records can remain to honor that choice. Receipts, account security and necessary purchase or access messages are separate from promotional campaigns.
Automatic enrollment is not evidence of affirmative consent, advertising-measurement permission or unrestricted access to a platform-wide audience. Being on a list does not establish sending permission for every audience or location. A later unsubscribe link is not evidence that a choice was offered when details were collected. Developers must establish the applicable permission and keep its evidence before sending where permission or a collection-time choice is required. No universal marketing-law compliance is promised.
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.
Email measurement follows sending readiness
Branded email tracking is separate from storefront Google Analytics. Supported sends can proceed with open/click tracking disabled while tracking TLS is not ready only where the configured provider can enforce it; otherwise sending remains blocked. This safeguard does not replace marketing permission, unsubscribe choices or applicable privacy requirements.
Advertising measurement is separate from email enrollment
Meta forwarding uses its existing advertising-measurement permission and respects the supported Global Privacy Control, Do Not Track and visitor suppression checks. Purchasing or joining a developer email list does not supply that advertising permission. Declining measurement must not block ordinary browsing or checkout.
When enabled and permitted, events can include event/time/URL, product or order value, currency, browser matching identifiers and hashed customer matching fields. Hashing is not anonymization. Keep destination tokens private. A disconnect stops pending forwarding and removes saved destination credentials and supported checkout measurement snapshots; it does not erase history already held by Meta.
This integration does not change GA4 behavior or email preferences. Provider-side processing follows the developer destination and applicable provider terms. Use the existing privacy-request procedure for account-related requests; no new universal retention or delivery promise is made.
SoundSync
Providers used by the relevant features
This identifies the integrations for these functions, not a claim that every provider is used for every account or request.
| Provider | Function | Relevant information |
|---|---|---|
| Stripe and PayPal | Payments and related financial processing | Payment, transaction, refund/dispute, and applicable account information |
| Railway | Platform hosting and operation | Information processed or stored by the hosted application |
| Cloudflare R2 | Product and media file storage/delivery | Uploaded product files, media, generated assets, and authorized retrieval requests |
| Elastic Email | Marketing campaign and growth-flow delivery and reporting | Recipients, message content, sender details, and delivery/engagement events |
| Google Gemini | Enabled product, storefront, marketing and operational AI assistance | Submitted instructions, support messages/notes and relevant product or campaign context; authorized analytics requests can include 30-day order, gross, refund/dispute totals and supplied dashboard metrics |
| Google Analytics | Developer-configured storefront analytics | Relevant page-view and browsing context when the integration is enabled |
| Google Calendar and Google Meet | Requested demo scheduling, calendar invitations and meeting links | Name, email, optional company and message, meeting type, time zone and selected meeting time |
| Resend | Transactional account, purchase, licensing, program-verification, and subscription notices | Necessary recipient, brand, verification/security, transaction/access, subscription/recovery, and message information |
| Meta | Developer-configured advertising measurement | Permitted event/time/URL, product or order values, browser identifiers and hashed customer matching fields; hashing is not anonymization |
SoundSync
Email and import processing
| Provider / function | Information used |
|---|---|
| Elastic Email / marketing campaigns and growth flows | Recipient details, content, sender identity, delivery and engagement events for the relevant message |
| Resend / transactional delivery | Necessary recipient, brand, account verification/security, purchase/redemption, licensing/activation, program verification, subscription/recovery, and message information |
| Google Gemini / enabled catalog assistance | Public page context for extraction, or export column headers for mapping; header matching does not send customer CSV values or private download links |
| Private delivery storage / catalog uploads | Authorized source links, files, upload-session details, and attachment checks; signed URLs can temporarily grant access |
Programs and connected reseller stores
Affiliate and collaborator recipients see their own relevant terms, referral activity, allocations, and payment information; participation alone does not grant customer-table or developer-team access. Invitation links and verification tokens are private access material.
An approved WooCommerce integration uses store-level provider permissions and can receive whole-order webhooks. SoundSync limits fulfillment to approved relevant product lines and the customer/order information needed for them. Provider transmission and SoundSync's retained fulfillment records are different scopes; review the integration before authorizing it.
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.
Requested operational AI assistance
When an authorized workspace user requests assistance, submitted support messages, notes and relevant product context can be processed by Google Gemini. Analytics access is required for 30-day order counts, gross, refund/dispute totals and supplied dashboard metrics; marketing access is required for deal context. Support-only requests do not query or send those financial aggregates.
Operational tools require all-products scope and the permission for that tool. Generated drafts, related record references, provider/model, context permissions and review status can be stored for later authorized review. Draft access also requires its recorded context permissions; older drafts with unknown context require analytics and marketing access. Changing a draft status does not send a customer reply or execute its suggested action. Do not submit credentials, full serials, payment details or unnecessary personal information.
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.
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.
Customer identity in redeemed-serial imports
Redeemed-serial import tools reuse the existing customer identity matched by normalized email without replacing its shared name, verification, account status or marketing preferences. A new identity is created only as part of a successful imported serial row. The serial can retain its developer-specific imported name snapshot; that snapshot is not a shared account-profile edit.
Unknown or unowned products, invalid required input and duplicate serials are skipped. A duplicate race or failed serial insert rolls back any customer created for that row. Earlier successful rows can remain imported if a later row fails; review the result and retry deliberately. A serial import is not a paid checkout, inbox verification, login transfer or permission to bypass an unsubscribe.
Country and branded contact details
Country information can be supplied through billing, a customer profile, or a serial claim, with approximate observation used where available. Automatic IP-to-country inference is not currently configured. These reports are not GPS tracking.
Developers control optional public support details and help content. A private contact-form delivery address is used for routing, not exposed as a public contact field. Editing an email address does not rewrite issued invoices or sent messages and does not erase an opt-out.
Source imports and assistance
A developer can submit a public product page, export, media, and private delivery source for catalog preparation. Public-source discovery requests source pages, and authorized delivery copying requests the selected file host. AI-assisted extraction uses the relevant public page context or export-header names; private download links and unrelated customer CSV values are not needed for header matching.
Provider use depends on the feature. This policy does not promise that a provider never retains data or uses it for training without a separately verified applicable arrangement.
Payout setup and protected-content records
Payout setup processes registered-business and destination country, provider account references, the proposed payout email and verification status. Payout and reconciliation records include eligibility, quotes, fees, provider references and payment status. SoundSync uses these to verify the destination, operate settlement, prevent misuse and reconcile statements; financial-record retention remains governed by the existing retention policy.
Protected-content delivery and licensing process product, content and release identifiers, software compatibility, customer access and device/session proof. Signed grants and download authorization are used to deliver permitted content and enforce its access terms. Private upload/download capabilities, invitation tokens and verification codes must not be published.
Notice and advertising records
Plugin Notices records product/recipient identity, editor events, delivery leases, display/action receipts and campaign dismissal. Anonymous notice identity is not an email marketing subscription. Display and dismissal records help enforce frequency and prevent repeatedly showing the same campaign; they are separate from license and purchase records.
Notice maintenance supports pruning expired sessions, old editor events and short-lived content requests while retaining the delivery/frequency/receipt records. Meta delivery cleanup clears terminal or expired payloads and ages out event/source history. These are maintenance mechanisms, not a new guarantee that every copy or provider record disappears immediately. Existing privacy requests, purpose-based retention, backup handling and legal record requirements still apply.
Developer inbox read markers
The developer interface stores notice ID/revision/severity read markers in browser local storage for the relevant account and workspace, or the account-only workspace warning. These support the unread badge; they are not marketing consent, a permission grant or a server-side record that an issue was resolved. Different browsers can show different unread states.
Retention and security
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.
Access restrictions and scoped permissions help protect information, but no service can promise absolute security. Credentials, full serials, and sensitive personal information should not be exposed in public examples or screenshots.
Import jobs, media, and deleted campaign reports
Import jobs keep source provenance, proposed product data, warnings, mappings, and progress needed for review and recovery. Raw export rows are discarded from completed job data after a successful commit; mappings, provenance, and reviewed product data remain. Unfinished jobs can retain source material while unresolved. Copied or staged media can remain until reviewed or cleaned up. No automatic all-import deletion deadline is promised.
Deleting a campaign removes its recipient report, not the usage and financial record, suppression history, or the ability to unsubscribe through an earlier message. Request account-specific deletion through support; necessary financial, security, and preference records can remain.
Replacing media is not immediate file erasure
Older product versions, published pages, branding and previously sent messages can refer to an asset after its current reference is replaced. A retention review must consider those uses; replacement is not a promise of immediate deletion. Necessary download and access checks remain in place.
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.
Access, deletion, and other rights
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.
Depending on applicable law, individuals may request access, correction, deletion, portability, restriction, or objection; withdraw consent; and complain to the appropriate regulator. We explain applicable retention exceptions, verification requirements, and effects on purchased access.
SoundSync
Retention periods and request timing
Retention and deletion
Support tickets, routine security logs, backup boundaries, legal holds, and privacy requests.
Providers and international processing
SoundSync is operated from the United States and may use providers operating in other countries. The safeguards required for a particular transfer depend on the provider, data, and applicable law. Contact support for information about the processing relevant to your account; this page does not assert an unverified transfer certification or universal data-residency guarantee.
Policy changes and contact
Material changes to the use of personal information will be communicated as appropriate. Contact support@soundsyncsolutions.biz with privacy questions or requests. A revised policy must reflect actual processing rather than introduce incompatible uses retroactively.
Connected external purchase records
Configured external checkout connections can process provider order references, purchased product/quantity, buyer email and event/refund state to issue and reconcile the relevant licenses. Provider credentials and generated webhook/fulfillment secrets are private integration data, not public product credentials. The external provider or store retains its own payment and tax responsibilities.
The notification alone is not verified account sign-in or marketing enrollment. Use the existing account verification and claim flow. An independently hosted customer portal also has its own server session storage and privacy responsibilities; the website key must not be exposed in its browser code.
Operational notice records and local read markers
Operational incidents and achievements can be recorded server-side to distinguish ongoing issues from later recovery. Separately, the header keeps bounded browser-local read markers for the relevant account and workspace. These markers do not resolve incidents, change permissions or represent marketing consent. The Activity view is limited to recent grouped updates, not a complete account audit log.
Recover delivery problems without clearing customer choices
Verified historical temporary or sender-side failures can be distinguished from permanent recipient restrictions. A full mailbox, deferral or sender configuration failure is not automatically a customer unsubscribe. Unknown failures, invalid recipients, hard bounces, complaints and opt-outs stay protected; a later purchase must not erase them.
The eligibility read does not itself rewrite a contact. An ordinary eligible activity/enrollment write may clear a proven stale recoverable provider restriction after all identity and historical checks pass. Sender-side failures also have operational notices. Recovery does not resend an already accepted message, guarantee inbox delivery or change automatic enrollment policy.
