Privacy Policy

Data StoreCheck processes

Account data can include your email, optional name, authentication-provider identifiers, and securely hashed password when you use email/password sign-in. Shopify-only embedded workspaces may use the verified Shopify shop domain as the workspace identity without requiring an unrelated email login.

Catalog and scan data

Uploaded Shopify CSV files are processed in memory for scanning. StoreCheck does not persist the raw uploaded CSV. For signed-in users, StoreCheck can persist scan summaries, detected issue records, comparison information, and the original filename so history and review workflows work. Connected Shopify scans read catalog data through Shopify APIs and persist the resulting StoreCheck scan records.

Shopify connections

StoreCheck verifies Shopify OAuth/session tokens and stores the access and refresh credentials needed for connected scans in encrypted form. Disconnect and uninstall flows clear stored Shopify credentials. StoreCheck requests product access for catalog auditing and merchant-approved Safe Repairs. Scans are read-only; write-back is limited to explicitly previewed actions and is never performed silently. Revenue Exposure can optionally request Shopify order access for a maximum 60-day product-level revenue analysis; StoreCheck does not request customer names, emails, addresses, or phone fields for this feature. When an analysis completes, StoreCheck can retain a compact per-product revenue index for that analysis so later catalog regressions can be prioritized with recent product-revenue context; this is exposure context, not a claim of lost or recovered revenue. For newly saved scans, StoreCheck can also retain a compact product-level catalog snapshot (supported product content, SEO, image, variant, price and inventory-configuration fields) so Migration QA can compare a later scan against a selected baseline. These snapshots are tied to the saved scan and are deleted when Shopify shop-redaction removes that store's data. Migration QA can also generate an immutable client evidence report. If the agency explicitly creates a client sign-off link, StoreCheck stores only a SHA-256 hash of the random capability token plus the workflow response record. StoreCheck also stores a SHA-256 evidence fingerprint derived from the immutable report so the recorded response can be tied to the exact evidence version. A response can include the reviewer's name, optional note, status, response channel and timestamps. This sign-off workflow does not store the reviewer's IP address, user-agent string or a browser/device fingerprint. The plaintext capability token is returned only when the link is generated and is not stored in the database. Migration Project metadata (project name, optional target launch date/notes and references to StoreCheck baseline/evidence/sign-off records) is stored to organize an agency migration lifecycle; it does not duplicate the catalog snapshot itself. Migration Project metadata and client sign-off records are deleted with the related store during Shopify shop-redaction. Pro agencies can optionally save a client-presentation profile containing an agency display name and short intro. That text can appear on private sign-off/evidence pages only after the agency configures it; StoreCheck does not load third-party agency logo URLs in this feature. The owner-level presentation profile is removed if Shopify redaction removes the final embedded-only workspace/user. Shopify can deliver product create/update webhooks for installed stores. StoreCheck acknowledges those events, but only creates a monitor job and re-reads the changed product when you explicitly enable Catalog Regression Monitor for that connected store. Monitored events are deduplicated into an audit record. Monitor mode is read-only and does not authorize a product write. Pro users can also explicitly enable Scheduled Verification for a connected store. That feature stores cadence and recent run metadata and periodically runs the same read-only full-catalog scan pipeline; a completed scheduled scan can reconcile existing Regression Inbox findings against the fresh catalog, but it does not authorize Safe Repair or any other catalog write. Scheduled Verification records are deleted with the related store during Shopify shop-redaction.

Billing

Stripe processes checkout, payment methods, invoices, and billing portal activity. StoreCheck stores Stripe customer/subscription identifiers and subscription status needed to apply plan entitlements. StoreCheck does not store full payment-card numbers.

Product analytics and traffic attribution

StoreCheck records a small allowlisted first-party event stream to understand signup, activation, scanning, upgrade, checkout, retention, and churn paths. It can also retain bounded campaign parameters such as UTM source, medium, campaign, content, term, and the referring hostname so StoreCheck can compare traffic from channels such as TikTok, X, creators, and other campaigns. It does not store raw IP addresses, catalog content, CSV filenames, scan identifiers, email addresses, Stripe identifiers, or free-form errors as analytics properties. Browsers use a random anonymous identifier in local storage; authenticated identity comes from the server. First-party analytics events expire after 180 days.

When configured, StoreCheck also offers optional Google Analytics 4. Google Analytics is loaded only after you allow optional analytics. StoreCheck sends page activity, traffic attribution, and an allowlisted subset of product-funnel event properties; it is configured not to send email addresses, catalog content, scan identifiers, payment identifiers, or advertising-personalization signals. Google processes this data under its own terms and privacy practices.

Support requests

If you submit the support form, StoreCheck stores the contact email, topic, message, optional verified account link, status, and timestamps needed to handle the request. Support requests are configured to expire after 365 days. Do not include passwords, API secrets, or payment-card details.

Retention

Scan-history visibility depends on plan (currently 7 days for Free and 90 days for Pro), with older records eligible for the configured retention-pruning process. Billing records are retained as needed to maintain subscription state and accounting history. Authentication and workspace records remain while needed to provide the account. Retention can also be affected by backup, security, fraud-prevention, or legal requirements.

Service providers

StoreCheck relies on infrastructure and database hosting, Shopify for connected catalog access, Stripe for billing, and authentication providers such as Google only when that sign-in option is enabled and chosen, and Google Analytics only when optional analytics is configured and allowed. Those providers process data under their own terms and privacy practices.

Your choices

You can use CSV scanning without connecting Shopify, disconnect a Shopify store, manage billing through Stripe’s portal, allow or disable optional Google Analytics at any time above, and contact StoreCheck about access, correction, deletion, or other privacy questions. A request may require identity verification before account data is disclosed or changed.

Security and changes

StoreCheck uses application access controls, encrypted Shopify credentials, HTTPS in production, and server-side authorization checks. No online service can promise absolute security. This policy may be updated as StoreCheck’s features or providers change; the date above will be revised for material updates.