Pilot privacy notice

Who operates Restock

Timur Mirsaidov operates Restock under the working developer label Variant Harbor. Contact Restock about privacy. The merchant's own privacy policy separately covers its store, shopping and checkout services.

This notice concerns the hosted Shopify pilot. The separate local simulator uses synthetic data; its local outbox is not email delivery.

Information handled

• Alert requests: the submitted email address, store and selected variant, product names and link, consent and confirmation state, request status and relevant dates. Stored addresses are encrypted, with a protected matching reference used to find related requests.
• Shopify connection: store, installation, session and subscription information needed to authenticate and control access, plus supported catalog, inventory, location and publication information. Shopify session records can contain merchant staff identity fields supplied during authentication. Restock does not request access to Shopify customer profiles or order history.
• Message operations: provider message identifiers, attempt and delivery-status metadata, quota/reservation records and protected retry content. Protected email references also support suppression and abuse prevention. Matching references remain personal-data-related records rather than anonymous information.
• Support and privacy correspondence: information you choose to send and the minimum verification or follow-up needed to handle the request. Shopify privacy notifications can also supply information used to locate a matching request.
• Technical operation: requests to the service include network information used for rate limits and protected anti-abuse references. Infrastructure and service providers also process technical information under their own service arrangements.

Restock does not collect payment-card details through its alert form. Merchant app billing is handled by Shopify.

Why information is used

The pilot uses this information to confirm a requested alert, check availability, send the requested message when enabled, manage cancellation and delivery failures, prevent abuse or duplicate work, show the merchant request status, control subscription access and investigate support or privacy requests. An alert request does not subscribe the address to a general marketing list.

Ordinary merchant tables mask email addresses. An authenticated merchant export can contain retained personal data; the merchant is responsible for handling that export securely and verifying any requester before delivering it.

Services involved

• Shopify: store authentication, app installation, product/inventory information and merchant subscription management.
• DigitalOcean: hosting for the current Shopify pilot. See DigitalOcean's privacy policy.
• Resend: the selected provider for new pilot email processing once the restricted connection is enabled. Sending a message discloses its destination, sender, content and product or signed control links to the provider. See Resend's privacy policy.
• Zoho: the support mailbox and historical ZeptoMail pilot messages and delivery records. Moving new sending to Resend does not itself delete earlier provider records. See Zoho's privacy policy.

A selected sending region does not establish every storage or support-processing location. This pilot does not promise processing exclusively in a particular country. Exact production processing arrangements and international-transfer terms must be resolved before general enrollment.

Retention and deletion limits

Email confirmation is available for 24 hours. A request is eligible for an alert for at most 90 days from signup. These are service deadlines, not automatic deletion deadlines.

The implemented ordinary cleanup rule becomes eligible 30 days after a recorded terminal transition, subject to maintenance and safety checks. Open privacy cases, uncertain delivery, reserved usage or unresolved installation/removal events can prevent ordinary cleanup. A legacy record without a reliable terminal date uses the first recorded maintenance observation rather than an invented earlier date. The pilot has not established a guaranteed cleanup-completion deadline.

After ordinary address cleanup, minimal protected request and cancellation references can remain until the original request expiry plus 60 days, and longer where an unresolved protected case prevents removal. Suppression references are kept separately to prevent unwanted sends.

Backups, support correspondence, audit records, suppression references and email-provider copies have separate retention. Finite expiry and deletion propagation for all of these categories have not yet been finalized for public launch. Deleting a live request does not instantly erase a backup, a provider record or a recipient's mailbox. Do not submit general customer lists to this development pilot.

Your choices and requests

Use an item's cancellation page to stop that request. For a store-wide stop, access, correction or deletion request, email Restock and identify the store. We may need limited verification before disclosing or changing records. Do not send passwords, provider keys, signed email links, payment details or identity documents in an initial message.

The support page explains the manual stop-all route. Contact is available without payment or reinstalling. A webhook acknowledgement, a downloaded export or a support email alone does not establish completed fulfillment; applicable rights depend on the circumstances and law.

Security and changes

The application uses HTTPS, signed confirmation/cancellation links, protected credentials and encryption for stored addresses and retry content. Authorized processing still requires decryption to send a message or create an export; this is not end-to-end encrypted email. No service can promise absolute security.

The storefront alert block does not add advertising cookies or pixels. Shopify, the merchant and infrastructure services have their own technologies and notices. We will review this notice against the accepted provider configuration and operating procedures before a public launch.