This notice covers CheckoutPilot and related support. Last updated 8 October 2026. Our website privacy and cookie notice covers visits to studio8022.com. The PostcodePilot privacy notice covers that app separately.
Who is responsible
CheckoutPilot is provided by David Duff, trading as Studio 8022, Asprou Potamou 1, Oikia 2, Agios Georgios Peyias, 8570, Cyprus. Contact support@studio8022.com for support or privacy requests.
Information we receive from Shopify
Shop/staff authentication and subscription information; merchant rules, product/variant/tag/collection references, revisions, module publication state and agreement acceptance version/time. Functions evaluate cart, product, customer-tag, delivery-address and method information inside Shopify. Checkout blocks evaluate available checkout conditions in the browser and save optional fields to Shopify order attributes. Optional analytics sends offer/variant identifiers, a checkout token transiently converted to a keyed hash, event type, quantity, observed line value and currency to our server. It does not send customer contact details, full cart contents, order IDs or payment data, and does not maintain customer profiles or a payment-card database.
Authentication sessions can include the authorised staff member’s identifier, name, email, language, role, access/refresh tokens, granted scopes and expiry. Credentials stay server-side. Do not send them to support.
Checkout and storefront processing
Authenticate access; prepare, simulate, save, publish, pause and recover merchant rules; evaluate supported conditions within Shopify; render configured checkout content; save merchant-configured optional attributes to Shopify; add an offer only after an explicit customer action; record and aggregate consent-aware offer events when enabled; assign a stable checkout to one of two offers; provide support and fulfil verified data requests. Customer-tag conditions are not available to checkout UI blocks. Observed line values precede order-level discounts, tax and shipping and do not account for refunds.
Analytics is off until enabled by an authorised merchant after acceptance of the identified service terms and data-processing agreement. Customer events also require Shopify’s analytics-consent signal. Events count once per checkout and offer for each event type; recorded purchases require an earlier recorded offer add and are capped at that one unit. Currencies are separate. Missing consent, blocked requests or an unplaced Thank you extension can leave gaps. No advertising trackers are installed.
Optional fields are saved through Shopify, not sent to the analytics endpoint. Merchants should not request sensitive personal information in these fields.
Information you provide and technical records
We receive the rules and settings you save and any information you choose to send to support. Please do not include passwords, payment credentials or unnecessary customer information in messages or rule names. Support correspondence includes your email address and message contents.
Hosting infrastructure processes connection data, including IP addresses, to deliver and protect the service. Routine HTTP access logging is not enabled for our public website or app proxy. Application diagnostic logs can contain operational events and shop identifiers; we do not intentionally record access tokens, card details or customer webhook bodies. CheckoutPilot does not use advertising analytics or sell personal information.
Why we use information
We use account, subscription and configuration information to provide the service, authenticate authorised staff, enforce plan access, apply merchant rules, recover from faults and answer support requests. We rely on the service relationship for providing the app and on legitimate interests for proportionate security, maintenance and support. Information may also be retained to meet a legal obligation.
We are responsible for our merchant relationship and support records. Where we process personal information on a merchant’s behalf to operate the integration, the merchant remains responsible for its customer notices and lawful instructions. Rules make checkout decisions according to the merchant’s configuration; we do not use this information for advertising, unrelated profiling or training AI models.
Providers and location
OVHcloud hosts the app, website and support email service. Shopify provides the platform, authentication, checkout execution and app subscription facilities. The operator is based in Cyprus. Provider services can involve processing outside Cyprus or the European Economic Area; see Shopify’s privacy policy and OVHcloud’s data-protection information. We restrict access to the people and providers needed to operate and support the service.
CheckoutPilot’s database, credentials and server-side recovery snapshots are kept on encrypted storage on our VPS. App-level snapshots and the existing OVHcloud recovery arrangements protect recovery copies under restricted access. Encryption and access controls reduce risk but do not guarantee that incidents cannot occur.
Security access records
We keep a restricted security audit trail of authenticated access and data operations. It records the time, operation, outcome and keyed references to the shop and acting account or service. It does not contain addresses, customer contact details, access tokens, checkout tokens or the contents of records. Application security records are retained for up to 90 days and reviewed for integrity. Host security logs also record privileged operator access and administration. These security records are separate from optional offer analytics and are used to protect the service.
Retention and deletion
Optional events expire after 31 days with hourly cleanup and reports cover 30 days. Turning recording off stops new events but does not immediately erase existing events. Successful authenticated uninstall or shop-redaction processing deletes sessions, Basic/Advanced drafts, module state, acceptance record and events from the active database. Customer-redaction callbacks clear all optional analytics for the shop because events do not retain customer IDs. Processing failures may delay cleanup. Existing recovery-copy controls remain unchanged; applicable deletions are reapplied before recovered data is used.
We retain support correspondence while needed for the enquiry and follow-up, normally no longer than 12 months after resolution unless a dispute or legal obligation requires longer. Contact support for verified access, export or deletion requests. The raw checkout token is not stored in the analytics database; its keyed hash remains pseudonymous data, not an assertion of anonymity.
Shopify retains its own platform and subscription records under its arrangements. Earlier versioned service terms remain available and are not retroactively accepted.
Your choices and rights
You can edit saved rules in the app and uninstall it through Shopify. Required permissions are necessary for the corresponding functionality. Depending on applicable law, you may request access, correction, deletion, restriction or a portable copy of personal information, or object to processing. We may need to verify your identity. Customers should normally contact the merchant whose store they used. You may raise concerns with the competent data-protection authority, including the Commissioner for Personal Data Protection in Cyprus.
Changes to this notice
We will update this notice when our data handling changes and communicate material changes where required. Questions can be sent to support@studio8022.com.
Your app agreement
CheckoutPilot service terms · Data-processing agreement · Providers and integrations · All app agreements
This notice explains processing; it is not blanket consent to unrelated processing or marketing. Mandatory rights are unaffected.