Privacy Policy
Privacy Policy
How SoundSync Solutions uses personal information, shares it for services, honors marketing choices, and handles privacy requests.
Updated 2026-10-22
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 |
| 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.
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.
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.
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 |
| Resend | Transactional account, purchase, licensing, program-verification, and subscription notices | Necessary recipient, brand, verification/security, transaction/access, subscription/recovery, and message information |
Marketing preferences
Unsubscribe and suppression choices stop applicable marketing use. Minimal consent and suppression records may remain to honor those choices. Receipts, account security, purchase, and necessary service messages are distinct from promotional campaigns.
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.
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.
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.
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.
SoundSync
Retention periods and request timing
Retention and deletion
Support tickets, routine security logs, backup boundaries, legal holds, and privacy requests.
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 |
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.
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 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.
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.
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.
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.
Product news and marketing preferences
Eligible purchases, subscriptions, and account activity automatically add customers to the relevant developer's marketing audience. Cart, checkout review, checkout sign-in, and subscription-plan cards do not ask for a marketing choice. Standalone storefront customer sign-in and account creation retain the Do not add me to product news and offers choice.
Automatic enrollment preserves saved refusals, unsubscribes, and suppression records. Marketing messages include an unsubscribe link. Necessary receipts and account/access messages remain separate.
Customer identity and support permissions
A developer cannot use customer contact editing to replace a linked account email or password. Customers control those credentials through account recovery and verified settings. Workspace-wide contact edits, removal, imports and verification resends require all-products access; assigned-product permissions alone are insufficient.
Supported name and phone corrections can update a shared customer profile used by relevant developer relationships. Contact removal removes the requesting developer relationship, not another developer relationship, the global login or required purchase records.
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.