Privacy policy

1. Who is responsible

Snoozemode, operated by an individual in New Zealand operates Product Forms for Wix and Catalog Feed Sync for Squarespace. “We” and “us” refer to the Snoozemode operator as an individual. This policy covers these apps, this developer website, and communications with us.

Snoozemode is the privacy contact: [email protected]. Launch detail required: postal contact address for the operator.

We are responsible for personal information used to manage our relationship with merchants and support correspondents. Merchants remain responsible for their own store and form privacy notices. Where we handle personal information solely on a merchant’s instructions, the applicable data-processing terms also govern that handling. Wix, Squarespace, and Meta have their own responsibilities and privacy policies.

2. Catalog Feed Sync: information and purpose

The planned connection obtains information from the Squarespace store you authorize: product and variant identifiers, names, descriptions, SKUs, images and image URLs, product URLs, prices, currencies, and availability. Site identifiers and basic site details associate the feed with the correct store. Authorization tokens maintain the connection. Feed settings and synchronization results support updates and troubleshooting. The updated backend also stores complete product/store-page snapshots in Cloudflare D1, manually supplied Google product details, verified variant links and merchant-confirmed pricing/tax settings. Credentials are encrypted; product snapshots are not encrypted at the application layer.

This information is used to generate and refresh the product feed you request. The intended scope is read-only catalog access; the feed does not need shoppers’ order histories, payment-card information, or contact lists. Credentials must never be placed in the feed.

Launch detail required: verify exact API permissions and stored fields, including any separate inventory access, account profile information, webhook payloads, and logs. Confirm the feed’s access controls and expiry behavior.

When you give its feed URL to Meta Commerce Manager or Google Merchant Center, that destination retrieves the included product data. A feed can expose its contents to anyone who can access its URL, depending on its access controls. Only include information intended for catalog publication; do not place private customer information in product descriptions or feed fields. Removing our connection does not remove copies already imported by a destination.

3. Product Forms: information and purpose

Product Forms is designed to use Wix site/app-instance identifiers, product and category identifiers, form links or references, and assignment settings such as priorities and default rules. These enable the app to select and display the appropriate Wix Form on a product page.

A shopper who completes the selected form provides information to the form’s receiving service and the merchant. The merchant determines the fields, purpose, and recipients, and must provide a suitable notice at the form. Displaying a form is distinct from storing its answers.

Launch detail required: confirm whether this app or its logs access, relay, or store form answers, attachments, contact details, visitor identifiers, or submission metadata. Identify the actual recipient, storage location, permissions, and retention for each. Until verified, this draft does not claim that the app never handles form submissions.

We do not use merchants’ customer or visitor information to build our own marketing lists, sell it, or advertise to their customers. Any processing on a merchant’s behalf must be limited to the requested service.

4. Website visits, support, and billing

This website’s source contains no analytics scripts, advertising pixels, or application cookies. Its intended host is Cloudflare. Hosting infrastructure can process request information such as IP address, requested URL, timestamp, and browser details to deliver and protect the site. Hosting configuration and log retention still need verification.

If you email us, we receive your email address, message, and any attachments you choose to send. We use them to answer your request and keep necessary correspondence. The proposed support mailbox is hosted by Google’s Gmail service. Do not send passwords, access tokens, full feed URLs containing secrets, payment details, or unnecessary customer records.

Launch detail required: disclose the payment provider and transaction/account fields received if paid plans are introduced, and the actual app logging or monitoring services and fields.

5. Reasons for handling personal information

We use information to supply the requested app functionality, administer connections, answer support requests, protect the service, and meet applicable legal duties. If GDPR applies to processing for which we are a controller, the relevant basis is contractual necessity for a service requested by an individual; legitimate interests for business-contact support and proportionate service security, subject to the individual’s rights; legal obligation where a specific duty applies; or consent where required. Merchant-directed processing depends on the merchant’s lawful instructions and applicable processing agreement.

Providing support information is voluntary, but we may be unable to investigate without a site identifier and description of the problem. Declining required platform permissions prevents the corresponding feature from working. We do not treat installation as consent to unrelated marketing. Optional marketing, if introduced, requires a separate opt-in with an unsubscribe option.

6. Recipients and service providers

Information is available to the operator and authorized service providers only as needed for hosting, storage, security, communications, and any disclosed billing. Providers acting on our behalf must be subject to appropriate confidentiality and data-protection terms. Squarespace and Wix supply authorized platform data; Meta or another destination receives feed data when you configure that destination.

We do not sell or rent personal information. We disclose information to authorities only where legally required, and notify the affected merchant before disclosure unless prohibited. A merchant’s instructions to publish a product feed do not authorize disclosure of unrelated personal information.

Launch detail required: publish the confirmed app hosting, database, backup, monitoring, email, and billing providers, their functions, and processing countries. Cloudflare is configured for the reference website; that does not establish where either app processes store data.

Connected platforms’ notices: Squarespace, Wix, Meta, Cloudflare, and Google. These notices supplement, and do not replace, our explanation of our own handling.

7. Retention, disconnection, and deletion

We keep personal information only for the period needed for its stated purpose or an applicable legal requirement. When you withdraw permission for a Squarespace connection, we stop accessing the store’s data immediately. Stored connection data and generated feeds must then be removed under the completed schedule below, except for records that law requires us to keep. Removing an app, cancelling payment, and deleting data are separate actions.

• Connection credentials, feed files, product caches, and assignment settings: Launch detail required: deletion trigger and maximum time after disconnection or a verified deletion request.
• Request, security, and synchronization logs: Launch detail required: fields retained and maximum retention period.
• Support correspondence and any billing/legal records: Launch detail required: retention period, start event, and any statutory exception.
• Backups: Launch detail required: expiry period and process for preserving deletions if a backup is restored.

Contact us to request deletion or an explanation of any necessary retention. We explain what was deleted, what must remain and why, and its expected deletion date. For copies held by Wix, Squarespace, Meta, or a merchant, use their applicable account controls or contact them; we cannot erase their independent records.

8. Security and overseas processing

Safeguards must be proportionate to the information handled, including restricted access, protected credentials, secure transport, and appropriate provider arrangements. No service can promise absolute security. If an incident affects personal information, we will notify affected people and relevant platforms or authorities as required by applicable law and platform agreements.

We operate from New Zealand. Providers may process information elsewhere. Launch detail required: verify implemented safeguards, storage/access countries, and the lawful protection used for each overseas transfer. Identify any applicable adequacy decision or contractual transfer mechanism and how a person can obtain information about it. Do not infer these from a provider’s brand name.

9. Cookies and visitor choices

The reference website has no application-level tracking code. This statement does not cover cookies or storage used by Wix, an embedded form, or another connected service. Launch detail required: verify the installed apps and forms, list any cookies or similar storage with purposes and durations, and explain consent controls. Non-essential tracking must respect applicable consent choices, including Wix visitors’ consent policies.

10. Requests and complaints

Email [email protected] with the app name, relevant site URL or identifier, and what you are requesting. You may request access to or correction of personal information. Depending on applicable law, you may also request deletion, portability, restriction, or object to processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.

We acknowledge requests, verify identity or site authority using only necessary information, and respond within applicable legal deadlines. For Wix-related access, correction, and deletion requests, our service commitment is completion within 30 calendar days, or sooner where law requires it. We explain any lawful refusal. See request instructions.

If your request concerns answers submitted to a merchant’s form, contact that merchant first. We will assist with information we hold or process rather than suggesting the merchant can erase records outside its control. You may complain to the New Zealand Privacy Commissioner or the relevant privacy authority in your location, including an EU supervisory authority where applicable.

11. Children and policy changes

Our merchant apps are intended for adult business operators. Merchants control their forms’ audience and must consider any additional protections required for children’s information.

We will publish updates here with their effective date. For material changes, we will provide a prominent in-app notice or email affected account holders before the change takes effect, unless an urgent legal or security reason requires earlier action. New uses requiring consent will not begin without that consent.

Launch detail required: set the effective date after all details and notification mechanisms are confirmed.