SEEP Privacy Policy

Effective date: August 30, 2026

SEEP helps Shopify merchants answer storefront questions, sync catalog data, analyze store operations, and—with merchant-defined permissions—prepare or make supported Shopify changes and recurring audits. It can also collect support or shopper handoff requests when a shopper opts in.

What SEEP stores

• Merchant account and configuration data such as shop domain, plan, branding settings, prompt settings, and retention controls.
• Catalog data synced from Shopify so the assistant can answer questions about products.
• Chat history and operational analytics used for merchant reporting and troubleshooting.
• Support requests created by merchants and shopper lead-capture submissions only when a shopper voluntarily provides contact details for follow-up.
• Merchant operator goals, structured plans, approvals, permissions, scheduled jobs, audit findings, action/change history, and Designer verification or rollback records.
• Bounded Shopify store snapshots used to analyze catalog, order, inventory, content, navigation, and storefront state.

Order snapshots deliberately exclude customer names, addresses, email addresses, and phone numbers. They contain only the minimum order identifiers, timestamps, status, totals, and product/quantity line items needed for merchant store-management audits and automations.

What SEEP does not claim

• SEEP does not claim an external compliance certification or provide legal advice.
• SEEP should not be used to collect payment card details or other secrets through chat.

How data is used

SEEP uses stored merchant and storefront data to operate the assistant, answer shopper questions, generate merchant-facing reporting, enforce permissions, execute approved Shopify actions, verify or roll back supported changes, recover interrupted work, and pass relevant bounded prompt context to the configured AI provider when generating a response.

Store and customer content is treated as untrusted data rather than agent instructions. Access tokens, secrets, and raw mandatory-webhook payloads are not included in model prompts or durable operator action history.

Privacy requests and Shopify lifecycle events

• SEEP verifies Shopify webhook signatures and suppresses replayed delivery IDs.
• Customer data requests create a merchant-visible privacy task using hashed references rather than retaining the raw webhook payload.
• Customer redaction removes matching lead, chat, and analytics data only within the exact store that received the request.
• Shop redaction and uninstall processing remove the store's catalog, chat, analytics, billing, operator, audit, snapshot, Designer, and history data.

Retention and controls

• Merchants can configure retention in the dashboard and can export or delete retained chat history.
• The merchant-selected retention window removes expired chat, voluntary lead-capture, and support records, including linked analytics identifiers.
• Order-level rows in bounded store snapshots are automatically removed after 15 minutes. Non-customer catalog evidence and aggregate audit results can remain in the merchant's operational history.
• Shopify customer redaction, shop redaction, and uninstall processing remove applicable exact-store data.

Security and customer choices

• Production traffic uses HTTPS/TLS and hosted database data is encrypted at rest.
• SEEP does not sell customer data or use it for automated decisions with legal or similarly significant effects on customers.
• Where a customer privacy request applies, SEEP processes Shopify's signed privacy webhooks and removes exact-store linked data.

Contact

Questions or deletion requests can be sent to info@seep.to.