Last updated 6 October 2026
Who provides CollectionPilot
CollectionPilot is provided by David Duff, trading as Studio8022, Asprou Potamou 1, Oikia 2, Agios Georgios Peyias, 8570, Cyprus. Contact support@studio8022.com about privacy, access, export or deletion. Studio8022 is independent of Shopify.
We act as processor for information handled on a merchant’s instructions and as controller for our own merchant relationship, support and service-security records. Merchants control their storefront notices and analytics choices. The app-specific data-processing agreement explains these roles.
Information used to provide the app
Shopify supplies the shop domain and timezone, authentication credentials and sessions, and the store-owner identity fields supplied during authentication, which may include name, email address, user ID and locale. We store subscription/access status, trial expiry, catalogue and collection identifiers, titles, product images, tags, variants, inventory availability, location information, arrangement settings, previews and publishing history. When you enable Product insights, we record the accepted agreement version, acceptance time and authenticated owner ID.
These records authenticate the owner, apply plan limits, import collections, arrange products, run requested schedules and verify or restore Shopify collection order. We do not request customer-profile or order permissions and do not handle payment-card credentials. Shopify handles subscription billing.
Optional product insights
Recording is off until the merchant enables it. A Shopify app pixel respects Shopify’s analytics consent signals. It sends product-view and add-to-basket event names, product IDs, timestamps, an event ID and a shop routing identifier to our service. Event IDs are hashed for duplicate detection. We do not send customer names, email addresses, customer or persistent visitor IDs, browsing URLs, complete carts, order details or payment data in that payload. No persistent visitor profile is created.
Counts describe recorded actions for imported products across the storefront, not unique shoppers, purchases, conversion rates or attribution to a particular collection. Consent choices, blockers and paused periods can leave gaps. Earlier Shopify history is not imported. A limit of 50,000 recorded actions per shop per rolling 24 hours protects service capacity; a reached limit is shown in the editor.
Turning recording off stops new counts. If Shopify cannot immediately update a pixel on an already-open page, incoming events are discarded locally. Merchants should explain optional analytics in their storefront privacy information and configure Shopify’s consent controls appropriately.
Purposes and lawful grounds
For our controller activities, we process information to provide and support the requested business service and administer the agreement, meet applicable legal duties, and pursue legitimate interests in securing the service, preventing abuse and responding to support requests, balanced against individual rights. Where consent is required for analytics, recording depends on Shopify’s analytics consent signals. Merchant-directed processing follows the merchant’s documented instructions and lawful basis.
We do not sell personal information or use these product events for advertising, cross-store customer profiles or automated decisions with legal or similarly significant effects. Supplying necessary shop and authentication information is required to use the connected app; optional insights can remain off.
Providers and international processing
Application data is hosted on Studio8022’s existing OVHcloud VPS. Shopify supplies platform data, authenticates access and processes requested collection changes and subscriptions. OVHcloud also supports business email used for support. UptimeRobot checks a public health endpoint containing service status, without merchant records.
We operate from Cyprus. Provider processing may involve other countries; we do not claim that all information stays in the EEA. Required transfer safeguards and processor arrangements depend on the relevant service and destination. Contact us for applicable locations and safeguards. Provider privacy links alone are not transfer safeguards. Information is disclosed only for providing and protecting the service, following authorised instructions, or meeting legal obligations.
Retention, uninstall and deletion
Daily product counts are retained for 31 days. Hashed event receipts are retained for up to two days, subject to the hourly cleanup run. Expired previews are removed after one day. Full arrangement data is retained for up to 30 days and the latest 100 arrangements per collection; completed run summaries remain for 90 days. Unfinished or unresolved publishing records remain until resolved.
Authenticated uninstall processing stops background work and deletes authentication sessions. The saved trial cutoff prevents repeated trials after reinstalling. Shopify’s shop-redaction event removes stored shop records. Processing failures can delay automated cleanup; an authorised merchant can request export or earlier deletion directly. Export is also available in Plans and settings.
Support correspondence and records required for legal obligations are retained only as necessary for those purposes. Restricted recovery copies follow the existing provider retention cycle and are not used for ordinary operations; deletion instructions must be reapplied before recovered records return to service. Contact us for the applicable retention information.
Your rights and requests
Depending on applicable law, individuals may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. Consent can be withdrawn without affecting the lawfulness of earlier processing. Storefront visitors should contact the merchant first about merchant-controlled processing; we assist the merchant with verified requests. We may need proportionate information to verify authority.
You may complain to the Office of the Commissioner for Personal Data Protection in Cyprus or your competent supervisory authority. Contact support@studio8022.com if you believe we have not handled a request appropriately. This notice does not limit mandatory rights.
Security and changes
We use encrypted transport, Shopify-authenticated shop-bound access, restricted administration and protected credentials. No security measure guarantees absolute protection. Do not send passwords, API keys or unnecessary personal records in support messages.
This notice was updated on 6 October 2026. We will publish material changes and provide additional notice where required. Publishing a notice or approving Shopify billing does not record acceptance of Studio8022’s separate service terms.