Privacy Policy

Last updated: October 26, 2026

Who we are

This app is operated by Goodevas (the app developer), acting as data processor for the merchant's store data. The merchant remains the data controller for their store and their customers' data.

What data we process

Store data: the store's myshopify domain, the offline API access token issued by Shopify at installation, the merchant's widget, playlist, appearance and app settings, the store's published languages, and links to media files the merchant selects from their Shopify Files (the app never stores the media files themselves). To attribute sales the app also keeps, per product the merchant attached videos to, the product id, handle and title.

Creator records: the people the merchant collaborates with — handle, platform, country, languages, usage rights and notes — together with the deals under them (date, type, optional cost, promo code, link code) and the links to their posts. The merchant enters them by hand or connects a feed of their own; for a connected feed the app stores its address and, encrypted at rest, the key the merchant provides. These are business contacts of the merchant, not shoppers.

Shopper data: the app does not collect names, email addresses, phone numbers, physical addresses, or any other directly identifying shopper information. If the merchant enables statistics or A/B testing, the app processes pseudonymous usage events (video impressions, clicks, watch time, player sessions, the slot a video was shown in, and whether a video block stayed on screen for ten seconds) keyed by a random first-party identifier. Each event carries the page context the storefront reports: the device class (mobile, tablet or desktop), the storefront market (the two-letter country of the storefront being browsed, as the theme reports it — not a geolocation of the shopper) and the storefront language. Usage events are kept in raw form for four months, then deleted; daily totals derived from them are kept while the app is installed.

Creator-link visits: independently of the statistics toggle, when a visitor lands through a creator link the app stores one row per creator reference, per random visitor identifier, per day, so the merchant can see how many people a creator sent. The row holds the reference, that random identifier and the date — no order data, no page history and nothing identifying.

Orders: to attribute sales to videos, creators and A/B test groups, the app receives order, cancellation and refund webhooks. It keeps an order only when one of its own marks claims it — a video that was watched or bought from, a creator link or promo code, or an A/B test group; every other order is acknowledged and discarded. For a kept order the app stores: the order id, its total, currency and creation time; per line, the line and product ids with the line total; refund ids and amounts; the discount codes used; the app's own cart attributes and line-item properties (only those whose name starts with the app's own prefix), which say which video, playlist, creator link or test group led to the sale, on which device class and in which storefront market. Customer fields — names, addresses, emails, phone numbers, payment data — are neither read nor stored. The order id is what keeps Shopify's webhook redeliveries from counting the same sale twice, and it is removed when Shopify asks the app to redact that customer.

Cookies and storefront storage

The app's storefront widgets (added to the theme by the merchant) set first-party cookies and browser storage only after the shopper's consent where Shopify's consent management applies:

• _vaw_vid — a random first-party identifier (UUID, up to 365 days) used to count unique visitors and keep A/B group membership stable. It contains no personal data and is not shared with third parties. Written when statistics or A/B testing is enabled, or when a visitor lands through a creator link.
• _vaw_ab — the shopper's A/B test group (up to 180 days), so the storefront renders consistently during a test. Written only while a test is running.
• _vaw_ref — the creator reference a visitor arrived with (6 days), so the creator can be credited for the order. A landing carrying only a discount code is remembered by that code.
• _vaw_click_map and _vaw_dwell_map — browser storage entries (6 days) remembering the last video a shopper interacted with and the video blocks they kept on screen, so a later purchase can be credited to them.
• _vaw_stats_carryover, _vaw_tracked_…, _vaw_abview_… and _vaw_dc:… — short-lived browser storage entries that hand pending analytics events to the next page, de-duplicate A/B enrollment and product views per test, and avoid re-applying a discount code twice in one session.

With statistics and A/B testing disabled (the default) and no creator link in play, the widgets set no cookies. Authentication inside the Shopify admin uses Shopify session tokens, not cookies.

Where data is stored

The admin app runs on Fly.io (region: London, UK) and keeps its session records in a database hosted by Supabase on AWS in eu-west-1 (Ireland). The library, playlists, statistics, orders, creators and A/B data are processed by our backend service and its managed PostgreSQL database, both hosted on DigitalOcean. Scheduled work (daily statistics roll-ups, creator feed syncs, catalog refreshes) is coordinated through Temporal Cloud, which receives job names and record ids only, never shopper data. Application logs go to Better Stack and contain store domains and request metadata, no shopper data. Currency conversion for the merchant's own reports uses public exchange-rate feeds (European Central Bank, open.er-api.com); nothing about the store or its shoppers is sent to them. Video files always stay in the merchant's own Shopify Files — the app stores links to them, never copies.

Data retention and GDPR requests

• App uninstall: the Shopify access token and the session records are deleted immediately; a lapsed plan never deletes merchant data.
• customers/data_request: acknowledged. The app holds no directly identifying shopper data; what it holds for a shopper's orders — the A/B group an order was attributed to, its product lines and amounts, the videos credited with its revenue and the creator reference or code it arrived with — is described to the merchant on request within 30 days.
• customers/redact: the Shopify ids of that shopper's orders, their lines and refunds are cleared, and the order's storefront market is forgotten, so nothing left in the database points back to the person. The amounts and what each order was credited to remain, because they identify nobody and the store's past results must not change retroactively.
• shop/redact (sent by Shopify ~48 hours after uninstall): all remaining data stored for the store — configuration, products, statistics, orders, A/B results, creators and their deals, the creator feed and its key, creator-link visits — is permanently deleted. Library videos shared with other stores of the same merchant group stay with that group.

Contact

Questions about this policy or your data: y.vasin@goodevas.com