Privacy Policy

Effective date: 4 October 2026

1. Scope

This Privacy Policy explains how Aapview Labs ("Aapview Labs," "we," "us," or "our") processes information when a Shopify merchant installs or uses Reelmerce (the "App") and when shoppers interact with Reelmerce experiences on a merchant storefront.

Reelmerce turns merchant-owned product videos into shoppable reels, provides storefront engagement analytics, supports performance-based merchandising and Conversion Lab reporting, and can attribute paid merchandise sales to qualifying Reelmerce cart lines.

2. Merchant and store operational data

Reelmerce processes merchant/store operational data needed to provide the App, including:

• Shop identity and authorized Shopify session data.
• Product, variant, file/video, and app-owned metaobject references used by Reelmerce.
• Widget Studio, Saved design, Theme Editor, storefront configuration, and plan/entitlement state.
• Shopify App Pricing subscription state used to verify plan entitlements.

3. Storefront analytics

For storefront analytics, Reelmerce may process:

• Shop identifier.
• Reelmerce video handle.
• Optional product or variant identifier.
• Event type, including storefront view, play, product click, and successful add-to-cart activity.
• Optional cart-value amount associated with a successful Reelmerce add-to-cart event.
• Placement identifier.
• Optional Conversion Lab experiment context.
• Event timestamp.

4. Paid-order attribution data

Reelmerce uses a filtered Shopify orders/paid webhook to attribute paid merchandise sales to valid Reelmerce-attributed order lines. For this purpose, Reelmerce may process:

• Shop domain.
• Shopify order and line-item identifiers.
• Product and variant identifiers.
• Quantity.
• Merchandise subtotal and discount amounts.
• Presentment currency.
• Order timestamp.
• Reelmerce video handle.
• Placement identifier.
• Optional Conversion Lab experiment context.

Attributed paid sales use paid merchandise subtotal allocated to valid Reelmerce lines. Shipping, tax, and duties are excluded. Reelmerce does not calculate advertising spend or ROAS.

5. Browser-local state

Reelmerce currently stores two types of shopper-side state in browser localStorage:

• Liked/favorited Reelmerce video handles. The current Like control is a browser-local favorite only; there is no server-side global like count or like analytics.
• For Conversion Lab, the A/B letter assigned to a specific experiment. The assignment is random when first encountered and is then stored for that experiment. Reelmerce does not create a visitor identity for this purpose.

If browser storage is unavailable for Conversion Lab, the storefront safely falls back to Variant A.

6. Data Reelmerce does not request or store for paid-sales attribution

Reelmerce's paid-order attribution does not request or store:

• Customer name.
• Customer email address.
• Customer phone number.
• Postal address.
• IP address.
• Payment credentials or payment-card data.

7. Purpose and use of data

Reelmerce uses the data described above only to provide merchant-requested Reelmerce functionality, including:

• Creating and delivering shoppable-video storefront experiences.
• Product-aware and inventory-aware merchandising.
• Storefront engagement analytics.
• Performance-based video ordering.
• Attributed paid-sales reporting.
• Conversion Lab experiment reporting.
• Plan verification and entitlement enforcement.

Reelmerce does not sell this data or use it for third-party advertising.

8. Retention and deletion

• Storefront analytics and paid-order attribution records are retained for no more than 365 days for active App usage.
• Expired VideoEvent and RevenueAttribution rows are pruned as Reelmerce processes analytics and paid-order activity.
• On uninstall, Reelmerce deletes app-side revenue attribution, analytics events, legacy video records, and sessions when available.
• Shopify shop/redact cleanup deletes remaining app-side revenue attribution, analytics events, legacy video records, and sessions for the shop.

9. Shopify permissions and platform access

The current production App uses Shopify GraphQL Admin APIs and the following OAuth scopes:

10. Infrastructure and storage

Production uses PostgreSQL. Reelmerce is hosted on Google Cloud Run and is configured for a production PostgreSQL / Cloud SQL deployment model.

App-owned Shopify metaobjects and app-installation metafields are also used for storefront content, design configuration, entitlement state, and performance-ordering snapshots.

11. Security

• Application traffic uses HTTPS/TLS.
• Production App data is stored in managed database infrastructure that supports encryption at rest.
• Access is limited to services required to operate Reelmerce.
• Reelmerce does not create a cross-store or cross-experiment customer profile for storefront analytics.
• Storefront analytics and paid-order attribution use validation and deduplication safeguards.

12. Shopify privacy lifecycle

Reelmerce implements Shopify's mandatory privacy webhook routes for:

These routes are used to support Shopify privacy requests and shop cleanup when applicable.

13. Current product boundaries

The current production release does not include third-party social-media account integration or Instagram, TikTok, or YouTube import. If future releases add new persistent shopper identifiers, global like analytics, social integrations, or materially different data processing, this policy should be updated before those features are publicly claimed or released.

14. Contact

For privacy questions about Reelmerce, contact Aapview Labs:

hello@aapviewlabs.com ↗