Peci: Persistent Cart · Legal

Version rev17-2026-10-28 · In effect from 2026-10-28 · Version history

PRIVACY POLICY

Peci: Persistent Cart — Privacy Policy

Effective date: 2026-10-28

This Privacy Policy applies to the Peci: Persistent Cart Shopify application ("App") published on the Shopify App Store, and to visits to the App's page on the Shopify App Store that we measure (Section 3c). It is operated by PÉCI Kft., Aradi utca 5., 2119 Pécel, Hungary (Cg. 13-09-089813; EU VAT HU12761609) ("Company", "we", "us", "our"). The Company is established in the European Union.


1. Who this policy applies to

This policy covers three distinct categories of people:

Merchants — Shopify store owners and their admin users who install and configure the App. Merchants are the primary account holders and pay for the service.

Customers — end-users who browse and purchase from Merchant stores where the App is installed. The App processes limited pseudonymous data about Customers on behalf of Merchants.

Visitors to the App's Shopify App Store listing — anyone who views the App's page on the Shopify App Store. Section 3c covers them.

Throughout this policy we label our role by capacity — as Controller or as Processor — wherever the distinction affects your rights or our obligations.


2. Our role under GDPR

For Merchant data (as Controller): The Company acts as data Controller (GDPR Art.4(7)). We determine the purposes and means of processing Merchant account and billing data.

For visits to the App's Shopify App Store listing (as Controller): The Company also acts as data Controller for the data about these visits described in Section 3c.

For Customer data (as Processor): The Company acts as data Processor (GDPR Art.4(8)) on behalf of the Merchant, who is the data Controller. Merchants are responsible for their own legal basis for processing Customer data and for informing Customers that their store uses this App. If you are a Customer with questions about your data, contact the Merchant directly.

Scope of this notice, stated explicitly. This notice governs the App and the visits to its Shopify App Store listing that we measure. Within it we hold two distinct roles and they do not overlap: we are Controller for Merchant data (Section 3a) and for visits to the App's Shopify App Store listing (Section 3c), and Processor on the Merchant's documented instruction for Customer data handled through the App (Section 3b), including the data generated when a person who has no prior relationship with that Merchant opens a Share a Cart link to that Merchant's store. Two records that concern requests are our own, as Controller, and we keep them solely to be able to show how a request was handled: the GDPR compliance rows of the app event log, which carry no customer identifier, and a request a Customer sends us directly, with our reply (Section 3a, Correspondence; Section 5).

A full Article 28 Data Processing Agreement ("DPA") governing the processor relationship is published at https://peci.io/persistent-cart/dpa, is incorporated by reference into the Terms of Service, and is accepted together with the Terms of Service in the App's acceptance step, before the App is first used (Terms of Service, Section 3A). The DPA prevails over the Terms of Service and this Privacy Policy on any question of data protection (see Terms of Service, Order of Precedence).

EU representative (Art.27). Not applicable. The Company is established in the European Union (Hungary), so the Article 27 requirement to designate an EU representative does not apply.


3. Data we collect and why

3a. Merchant data (as Controller)

CategoryExamplesSourcePurposeLegal basis (GDPR Art.6)
Shop identityShopify shop domain (mystore.myshopify.com)Shopify OAuthService delivery, billingArt.6(1)(b) — contract
Store contact e-mailThe store's contact e-mail address or, where the store has none, the e-mail address of the shop owner's account (Merchant record)Shopify Admin API, read at installation or when we first need to send one of these e-mailsSending the Merchant what it must receive from us: the customer data e-mail when Shopify forwards a customer's access request (Section 8c); the copy of its data it asks for (DPA, Section 9.5); our notices as processor (a legal requirement to process otherwise than instructed, an instruction we consider unlawful, a new or replacement sub-processor, a request a Customer sent us directly, a personal data breach, a transfer or US state law obligation we can no longer meet; DPA, Sections 4.1, 4.2, 6.4, 7.2, 8.1, 11.4, 12.5); notice of changes to this policy (Section 13); and service notices (plan-limit and billing-grace e-mails). Matching an e-mail the store sends to our support address to the store and its plan, and showing the address to our staff in our internal admin view. Upgrade suggestions in the plan-limit and billing-grace e-mails, which you can stop at any time (Section 8b)Art.6(1)(b) (contract) for the e-mails we owe the Merchant and for handling its support requests; Art.6(1)(c) (legal obligation, GDPR Art.33(2)) for the notice of a personal data breach; Art.6(1)(f) (legitimate interest) for upgrade suggestions
Authentication tokensShopify offline access token and refresh token (Session)Shopify OAuthAPI access to merchant storeArt.6(1)(b) — contract
Billing and usageTier name, monthly cart/link/click counts, generated revenue estimate, plan cost, usage period dates, the dates on which usage and billing-grace notices were sent, link-quota and subscription-freeze flagsApp internalBilling enforcement, usage dashboards, suggesting a suitable App planArt.6(1)(b) — contract
Shop subscription planShopify plan display name of the Merchant's store (e.g. Basic, Grow, Advanced, Plus)Shopify Admin API, read live when the page loadsSuggesting a suitable App plan to the MerchantArt.6(1)(f) — our legitimate interest in offering the Merchant a plan that fits its store
ConfigurationRedirect-to-checkout toggle, cart icon display and icon type, cart-conflict dialog toggle, cart expiry days, share button and dialog CSS classesAdmin UIPersonalised App behaviourArt.6(1)(b) — contract
App event logAction type, timestamp, optional structured detail (AuditLog)App internalDebugging, GDPR webhook compliance, merchant analyticsArt.6(1)(f) — our legitimate interest in running, debugging and securing the App and in demonstrating that GDPR requests were handled
Terms acceptance recordShop domain, the versions of the Terms of Service and the Privacy Policy accepted, time of acceptance, method (the in-app button), time of uninstall (TermsAcceptance)App internal, when you click "I accept"Proof of the contract and of the version acceptedArt.6(1)(f) (legitimate interest: establishing, exercising or defending legal claims)
Uninstall recordShop domain, last plan name, uninstall timestamp (UninstalledRegistry)App internalRecognising a returning store: if the store reinstalls within 30 days, the installation record notes the reinstall and the previous planArt.6(1)(f) — legitimate interest
CorrespondenceThe name, e-mail address and content of e-mails you send to persistentcart@peci.io, privacy@peci.io or legal@peci.io, or that a Customer sends us directly, and our repliesYou, or the Customer who writes to usAnswering support, data-protection and legal requests, and passing a request a Customer sends us on to the Merchant (DPA, Section 7.2); afterwards, keeping the exchange to show how a request was handled (Section 5)Art.6(1)(b) (contract) for support; Art.6(1)(c) (legal obligation) for a Merchant's request under data protection law; Art.6(1)(f) (legitimate interest) for passing a Customer's request on to the Merchant and for keeping the exchange after the matter is closed

At installation, or when we first need to send one of the e-mails listed above, we read this address from Shopify and keep it with the shop record; it is deleted with the shop record on uninstall (Section 5).

Plan suggestion. To help the Merchant pick a suitable App plan, the App may mark one plan as suggested. Immediately after installation, when no usage history exists yet, this suggestion is derived from the Shopify plan display name of the store, which is read live from the Shopify Admin API and is not stored. Once usage history exists, the suggestion is derived from the Merchant's own monthly cart and link counts already listed above. This is a display of data we already hold or read on the Merchant's behalf, involves no additional collection, and concerns the Merchant's own account only — no Customer data is used.

Providing the Merchant data above is a condition of using the App: without it the App cannot be installed or run.

3b. Customer data (as Processor — on behalf of Merchant)

We process the minimum data necessary to provide cart persistence and the Share a Cart feature. We do not store customer names, email addresses, postal addresses, phone numbers, payment information, or device fingerprints. We do not persist customer IP addresses in application data; routine processing of IP addresses may occur at the hosting/edge layer (Vercel/Neon) as an ordinary and unavoidable part of routing an internet request, and the App itself holds the requesting IP address briefly in memory to rate-limit requests that open shared links; no IP address is written to the App's database or retained by us.

CategoryField(s)SourcePurposeLegal basisRetention
Shopify customer identifierShopify customer ID (numeric, pseudonymous)Supplied by Shopify with each storefront request of a logged-in customer; customer webhooksKeying a saved cart and cart token to a customer accountArt.28 — on documented Merchant instruction; Merchant's basis Art.6(1)(b)/(f)Deleted at cart expiry (plan-dependent, see Section 5) or on shop/customer redact webhook
Cart token (stored hashed)The one-way SHA-256 hash of the Shopify cart token; the raw token is never stored at rest (data minimisation, Art.5(1)(c))Storefront widget, from the store's cartRetrieving the correct cart on any deviceArt.28 — Merchant instructionSame as above
Cart contentsProduct variant IDs, quantitiesStorefront widget, from the store's cartRestoring the cart on loginArt.28 — Merchant instructionSame as above
Share a Cart link contentsProduct variant IDs, quantitiesCustomer action in storefrontGenerating a shareable short URLArt.28 — Merchant instructionDeleted at link expiry (plan-dependent, see Section 5)
Link click eventShop domain; reference to the short link, or the cart token for a click through a cart-token link, or, for a checkout-direct link, the checkout token (each token stored only as its one-way SHA-256 hash, never raw); referring channel (a category: WhatsApp, Facebook, Instagram, other social, or direct; the web address itself is not stored); variant IDs; click timestamp (LinkClick)Storefront widget or, for a checkout-direct link, a Shopify Web Pixel at checkout, in each case only when the Customer allows marketing in the store's consent settingsAttribution (recorded on all plans that offer Share a Cart); the analytics dashboard shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and aboveArt.28 — Merchant instruction; recorded only with the Customer's marketing consent as signalled by Shopify's Customer Privacy APIA click through a share link is kept while the link is live and, after the link expires, until 31 days after the click, so that the analytics dashboard's 30-day view still shows it; it is then deleted by the daily cleanup. A click through a cart-token link is deleted by the daily cleanup once that cart token has expired. All clicks are deleted on uninstall and on the shop/redact webhook; on the customers/redact webhook, the clicks set out in Section 8c
Daily click totalsShop domain, day (UTC), referring channel category, number of clicks (LinkClickDaily). No click-level record, token, customer or link referenceCounted by the App when it records a link clickThe analytics dashboard's click figures: the conversion rate, the daily trend and the breakdown by channelArt.28 — Merchant instruction; computed from the link clicks aboveKept for 31 days after the day they count, then deleted by the daily cleanup; not changed by a customers/redact request; all are deleted on uninstall and on the shop/redact webhook
Order attributionShopify order ID, order name, total price, attribution method, cart token, referring channel, link-click reference, conversion timestamp (OrderConversion — no Shopify customer ID is stored; the order ID is a pseudonymous identifier and the cart token is stored only as its one-way hash)Shopify order webhookOrder attribution (recorded on all plans); the analytics dashboard shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and aboveArt.28 — Merchant instructionDeleted on the shop/customer redact webhooks (on customers/redact: the rows matched by the customer's cart tokens or by the orders Shopify lists in the request); otherwise deleted after 365 days, or 30 days after the uninstall for an uninstalled shop
Restored-cart orderWhen a logged-in Customer restores a saved cart on a device and an order is placed from that cart: the order ID, its total, the hash of the cart token and the restore timeShopify order webhook and the storefront widget, only when the Customer allows marketing in the store's consent settingsShowing the Merchant the orders and revenue from restored carts (Pro and Advanced)Art.28 — Merchant instructionDeleted with the saved cart, and on the shop/customer redact webhooks

Links that go straight to checkout. When a Share a Cart link sends its recipient straight to checkout, the App adds two cart attributes to the Shopify cart that the link opens: _pc_link, the short code of the link, and _pc_ch, the referring channel category (as in the Link click event row above). They carry no customer data, and Shopify does not show them to the Customer at checkout. Shopify keeps them with the cart and the checkout, as it does any cart attribute. The App's Web Pixel reads them at checkout and records the click only when the Customer allows marketing. The attributes are added whether or not the Customer allows marketing, because the link is resolved on our server, where that choice is not known; without consent, nothing is recorded from them.

The Shopify customer ID is a numeric platform identifier. It does not by itself reveal identity, but it constitutes pseudonymous personal data under GDPR Art.4(1) because it can be linked back to an individual by Shopify or by the Merchant. We process it solely to match a logged-in session to a saved cart.

Referring channel. The LinkClick record stores only a category for where a Share a Cart link was clicked (WhatsApp, Facebook, Instagram, other social, or direct, which also covers every other source), derived from the referring address the browser sends with the request; the address itself is not stored. It is used solely to attribute a recovered cart to the correct sharing channel in the Merchant's analytics. It is not used to profile individuals, is not enriched, and is deleted together with the click record (see the table above). An attributed order keeps the channel category of its click (Order attribution, in the table above). The daily totals keep only the number of clicks per channel and day.

Attribution data is recorded on all plans, for Customers who allow marketing in the store's consent settings. The App logs link clicks (LinkClick) and attributes completed orders back to shared/recovered carts (OrderConversion) regardless of the Merchant's plan (on every plan, the App also uses it to recognise when it first produced an order for the Merchant); the analytics dashboard that surfaces this data shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and above. This data is used only for attribution and is never used for advertising, resale, or profiling. See the "Shopify Protected Customer Data" section below.

Attribution and consent. Cart persistence is strictly necessary to deliver a service the Customer has actively requested, and it does not depend on consent. Link clicks and the order attribution built on them are marketing measurement: the storefront widget records a click only when the Customer allows marketing in the store's consent settings, as signalled by Shopify's Customer Privacy API, and records nothing where the store asks for consent and the Customer has not given it. An order is attributed to a shared link only through the cart or checkout token recorded with the click, and only while the share link is live; orders of Customers whose click was not recorded are not attributed. For a Share a Cart link that takes the Customer straight to checkout, where the storefront widget does not run, the click is instead recorded by a Shopify Web Pixel at the start of checkout, on the same condition: only where the Customer allows marketing. The pixel reads the link code from the checkout attributes and the checkout token to attribute the resulting order, and holds no other personal data about the Customer. Wherever we store a cart token, we store its one-way SHA-256 hash and never the raw token, so the value at rest cannot serve as a live cart token (data minimisation, Art.5(1)(c)). Where the Merchant's jurisdiction requires consent for other processing through the App (e.g. under ePrivacy Directive Art.5(3), whose technical scope the EDPB addresses in its Guidelines 2/2023), the Merchant, as Controller, is responsible for obtaining it.

The person who opens a shared link. Someone who opens a Share a Cart link need not be a customer of that store, and may never have visited it before. We treat the data that click generates as Customer data under this Section: it is processed on the Merchant's documented instruction, solely so that the Merchant can attribute a recovered cart to the correct sharing channel, and never for a purpose of our own. The record holds no name, no email address, no postal address and no customer identifier, and we hold no other data about that person; it is deleted by the daily cleanup once the share link has expired and 31 days have passed since the click, or, for a click through a cart-token link, once that cart token has expired.

Shipping calculator. If the Merchant adds the shipping calculator to the cart page (Terms of Service, Section 2), the address details a Customer uses there (postal code, country and, if entered, state or province) are sent from the Customer's browser directly to the store's own Shopify shipping-rate service. They do not reach our servers, and the App does not store them.

3c. Visits to the App's Shopify App Store listing (as Controller)

The App's page on the Shopify App Store is run by Shopify. On that page, Shopify loads Google Analytics 4 with a measurement ID that belongs to us, so that we can see how Merchants find the App. Where the law requires your consent for this, Shopify asks for it on its page; without it, nothing is sent to our Google Analytics property. Shopify is responsible for its page and for the cookie consent step on it.

CategoryExamplesSourcePurposeLegal basis (GDPR Art.6)Retention
Listing visitThe listing pages you view, how far you scroll and the buttons and links you click (for example Install, or a link that leads off the page); the Shopify App Store page you came from, the language you selected there and, if you came from a search, your search query; the approximate location, device and browser that Google Analytics derives from the visit; a random identifier that Google Analytics stores in your browserThe App's Shopify App Store listing page, through Google AnalyticsMeasuring how Merchants find and install the App, to improve the listingArt.6(1)(a) (consent, given in Shopify's cookie settings) where the law requires consent for the analytics identifier; otherwise Art.6(1)(f) (legitimate interest in understanding how our listing performs)Visit-level data for 2 months; data linked to the browser identifier for 14 months after your last visit to the listing. After that, only totals remain in the reports. The identifier itself stays in your browser for up to 2 years after your last visit, unless you delete it

We use this data only in aggregate, to see which pages and searches bring Merchants to the App. We do not use it to contact you or to advertise to you, and we do not combine it with the data the App holds about your store. Google signals is switched off for our property, so our reports do not draw on data from your Google account.

Where you gave consent in Shopify's cookie settings, you can withdraw it there at any time, through the "Your privacy choices" link at the bottom of the page; this does not affect the processing before the withdrawal. We cannot link this data to your name or e-mail address. To exercise your rights over it, send us the identifier stored in your browser's _ga cookie for shopify.com; with it we can find and delete the data in Google Analytics. Without it we cannot identify you (GDPR Art.11(2)), and we will tell you so.


4. How we use data

We do not sell, rent, or share personal data with third parties for advertising or marketing.


5. Data retention

The three retention descriptions in this policy — this Section 5, the "Shopify Protected Customer Data" section, and the webhook mapping in Section 8 — describe the same rules; this Section 5 states them in full. For Customer data, the DPA prevails (Terms of Service, Section 20).

Customer data

PlanCart persistenceShare a Cart linkNotes
Free2 days2 daysOn every plan, expired records are deleted by the first scheduled cleanup after expiry
Basic7 days7 days
Pro30 days30 days
Advanced60 days60 days

These are the defaults, and on two plans the Merchant can change them. On Pro and Advanced the Merchant may select a retention window from 7, 14, 30 or 60 days in the App settings; the value is validated against that list and anything else falls back to 7 days. So a Pro shop may run on 60 days and an Advanced shop on 7 -- the plan sets the default, not a ceiling. On Free and Basic the plan value is fixed and cannot be changed. 60 days is the absolute maximum on every plan, which is what makes the "2-60 days" figure used elsewhere in this document an outer bound rather than a range of defaults. The Merchant, as Controller, therefore determines the retention period within that bound.

A saved cart's expiry is set when the cart is saved and moves forward each time it is saved again, so the window runs from the Customer's last cart activity; a share link's expiry is set when the link is created. A temporary link record, created when a shopper opening a cart-token link has to choose between merging and replacing their cart, expires after one hour. Scheduled cleanup runs daily (Vercel Cron, approximately 03:00). On expiry, CartToken and SavedCart records are deleted. ShortUrl records are deleted at expiry; a LinkClick record made through a share link is kept while its link exists and until 31 days after the click, whichever is later, and is then deleted. LinkClickDaily totals are deleted 31 days after the day they count. LinkClick records made through a cart-token link are deleted in the same run once that cart token has been deleted. OrderConversion records are deleted on a redact webhook, and otherwise 365 days after they were created.

Merchant data — and what happens on uninstall / shop redaction

When a Merchant uninstalls the App, or when Shopify sends the shop/redact webhook, we purge all merchant and shop personal data and all Shopify access tokens promptly — within 30 days of the triggering event, and typically within 48 hours of receiving the webhook. On uninstall we delete the Session (offline access token, refresh token), the Merchant record (including the store contact e-mail), the shop's Customer data (CartToken, SavedCart, ShortUrl, LinkClick) and its daily click totals (LinkClickDaily). When Shopify's shop/redact webhook follows, we repeat those deletions, delete the operational AuditLog rows, and delete the OrderConversion records. If shop/redact does not arrive (a reinstall within 48 hours cancels it, or the webhook is lost), the scheduled cleanup deletes the operational AuditLog rows and the OrderConversion records itself, 30 days after the uninstall. Operations-monitoring entries are not stored per shop: they are kept under a shared system key and may name the shop domain in their details, so shop/redact does not reach them; the 90-day cleanup deletes them. AuditLog is the one exception and it is split: the operational rows (installs, quota events, billing changes) are deleted, while the GDPR compliance rows (customers/data_request, customers/redact, shop/redact) survive, as set out below. Access tokens are not retained after uninstall.

Records that survive uninstall: the UninstalledRegistry entry (shop domain, last plan name, uninstall timestamp), retained for 30 days so that a reinstall within that period is recognised and recorded with the previous plan, and then deleted by the scheduled cleanup; and a per-shop usage summary (MerchantUsageArchive: shop domain, plan tier, aggregate usage counters and revenue totals) together with the shop's plan/settings rows (MerchantUsage, MerchantSettings), retained for 30 days after uninstall for billing reconciliation and the prevention of plan-quota abuse through repeated reinstalls (legitimate interest, Art. 6(1)(f)), then deleted by the scheduled cleanup; and the GDPR compliance AuditLog rows (customers/data_request, customers/redact, shop/redact), retained for 3 years; and the Terms acceptance record (TermsAcceptance: shop domain, the accepted document versions, the times of acceptance and uninstall, the method), retained for 5 years after uninstall as the proof of the contract for the general limitation period (Hungarian Civil Code (Ptk.), Section 6:22), not deleted on shop/redact, and then deleted by the scheduled cleanup. Thirty days is the period within which the Shopify API License and Terms of Use (Section 6.2.3) require Merchant Data to be deleted after an uninstall. The compliance rows exist to prove that an erasure we performed was in fact performed: shop/redact arrives roughly 48 hours after an uninstall, so deleting them here would destroy, within two days, the record of an erasure carried out earlier. They hold Shopify's own request ids and row counts; they carry no customer identifier. The shop domain does stay in them, which is a business identifier. None of these records contains customer personal data or access tokens.

Invoices and payout records for paid plans are issued and held by Shopify and kept in our accounting records, outside the App, for the period required by Act C of 2000 on Accounting (Art. 6(1)(c)); the App itself retains no billing record beyond the 30 days above. No customer personal data and no access tokens are retained for accounting purposes.

AuditLog entries for active Merchants are retained for 90 days, then purged by the scheduled cleanup. The single exception is the GDPR compliance rows named above (customers/data_request, customers/redact, shop/redact), which are retained for 3 years; 90 days remains the default, and any action nobody has classified keeps the short window.

Application logs. We log the App's operation to maintain the quality and availability of the service. The App writes application logs at the hosting provider (Vercel); request addresses are logged there with their query string, and for a logged-in customer every storefront request to the App carries the Shopify customer ID there. Some log lines can also contain an e-mail address, or a Shopify customer or order ID, where one appears in an error message. Vercel keeps these logs for up to 30 days. A copy of the production logs is forwarded to our own server in the European Union, which removes the IP address, the user agent, the referrer and any query string, and masks the e-mail addresses it detects, on receipt and keeps the rest for 14 days; the rest can include such an ID. We use the logs only to maintain the quality and availability of the service, that is, to detect errors, crashes and timeouts, to follow request volumes and response times, and to investigate faults. We do not use them for any other purpose.

Backups. The database provider keeps a point-in-time restore history of 24 hours, so data deleted under this Section can remain restorable for up to 24 hours after its deletion.

Correspondence. E-mails sent to our addresses and our replies are kept until the matter is closed and then for the general limitation period of 5 years (Hungarian Civil Code (Ptk.), Section 6:22), so that we can show how a request was handled. Customer data we send to a Merchant ourselves (a copy under the DPA, Section 9.5, or a customer's data under Section 8c) is not kept in our mailbox after it is sent.

Listing visits

Google Analytics keeps the data about visits to the App's Shopify App Store listing (Section 3c) for 2 months at visit level, and the data linked to the browser identifier for 14 months after the last visit to the listing; after that, only totals remain in the reports. The identifier itself stays in the browser for up to 2 years after the last visit, unless it is deleted.


6. Shopify Protected Customer Data

The App accesses Shopify Protected Customer Data. Specifically, it processes order data (Shopify order ID, order name, total price via the OrderConversion model; no Shopify customer ID is stored in OrderConversion; the order ID is a pseudonymous identifier and the cart token is stored only as its one-way hash) and the Shopify customer ID used to key a saved cart. We acknowledge this and comply with Shopify's Protected Customer Data requirements as set out below.

Protected scopes requested and why (minimum necessary).

Data / scope accessedWhy it is necessaryPlans that use it
Shopify customer ID (supplied by Shopify with each storefront request of a logged-in customer; not a separate access scope)Keys a saved cart and cart token to a logged-in customer so the cart can be restored on another device. Without it, cross-device persistence — the App's core function — is impossible.All plans (for persistence)
Order data — id, name, total price, attribution fields (read, via order webhook)Attributes a completed order back to a recovered or shared cart so the Merchant can see, in analytics, whether the App produced revenue.Recorded on all plans; the analytics dashboard shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and above

Access scopes. The App requests these Shopify access scopes: read_orders, write_pixels, read_customer_events. read_orders is used to attribute an order to a Share a Cart link (Section 3b, Order attribution). write_pixels and read_customer_events are used to activate the App's Web Pixel, which records the click of a link that goes straight to checkout (Section 3b, Link click event).

We do not request or store Shopify Protected Customer Data Level 2 fields — customer name, email address, or physical/mailing address are neither requested nor stored by the App.

Mapping to Shopify's Level-1 requirements.

RequirementHow the App meets it
Data minimizationWe store only the identifiers and order fields listed above. No Level-2 PII (name/email/address). Attribution data is recorded on all plans that use Share a Cart; the analytics dashboard shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and above.
Purpose limitationData is used only for cart persistence and order attribution (recorded on all plans; the analytics dashboard shows link clicks and matched orders on every plan; their revenue and the daily trend are a paid feature on the Basic plan and above). It is never used for advertising, resale, or profiling.
TransparencyThis policy, the Cookie Policy, and the DPA disclose exactly what is accessed, why, and for how long. Merchants must in turn disclose the App's use in their own customer-facing privacy policy.
Customer consent decisionsThe App reads the Customer's marketing consent from Shopify's Customer Privacy API and records Share a Cart link clicks, and the order attribution built on them, only when marketing is allowed. Saving and restoring carts do not depend on it. Obtaining consent (the store's consent banner) is the Merchant's responsibility as Controller.
Optional processingLink-click recording and order attribution, only for Customers who allow marketing. An order is attributed only through the cart or checkout token of a recorded click, and only while its share link is live; there is no other matching mode.
EncryptionAll data is encrypted in transit (HTTPS/TLS, with sslmode=require and channel_binding=require set on the database connection) and at rest, the latter provided by the database Sub-processor (Neon). Shopify access tokens are stored in the database and are therefore covered by that at-rest encryption. They are purged on uninstall and on shop redaction.
Retention limitsData is retained only for the plan-based cart/link windows (a click made through a share link until 31 days after the click, if that is later), or 365 days for order attribution, and is deleted on redact webhooks — see Section 5. Application logs at the hosting provider, which can contain the Shopify customer ID, are kept for up to 30 days and are not deleted on a redact webhook (Section 5, Application logs).

Protected data is processed only to deliver the features the Merchant has enabled and is deleted on the customers/redact and shop/redact webhooks as described in Section 8.


7. Sub-processors and platform providers

Shopify is not our sub-processor. Shopify Inc. is the independent e-commerce platform and app marketplace on which both the Merchant and the App operate. In respect of storefront customer data, Shopify acts as an independent controller / platform under its own terms and privacy policy, not as a sub-processor engaged by us. Data reaches the App from Shopify; Shopify does not process on our instruction.

We engage the following sub-processors to deliver the service:

Sub-processorRoleData sharedRegionSafeguard
Vercel Inc.Application hosting and edge deliveryAll data in transit; transient IP at edge; request logs, including the IP address and user agent of each request, kept for up to 30 days (Section 5)United StatesVercel is certified under the EU–US Data Privacy Framework; SCCs stand as a fallback (see Section 8 international transfers)
Databricks, Inc. (Neon)PostgreSQL database hosting (Neon, provisioned via Vercel Marketplace)All persisted dataUnited StatesDatabricks is certified under the EU–US Data Privacy Framework, and its certification covers Neon; SCCs stand as a fallback. Databricks Data Processing Addendum, which applies to the Neon service; sub-processor list at neon.com/subprocessors
Amazon Web Services (Amazon Simple Email Service)Delivery of the customer data e-mail to the Merchant when Shopify forwards a customer's access request (customers/data_request)The data the App holds about the requesting customer, in transit onlyeu-west-1 (Ireland, EU)Processed within the EU; no third-country transfer for this processing
Zoho Corporation B.V., the Netherlands (Zoho Mail)E-mail hosting for our persistentcart@peci.io mailbox and its addresses privacy@peci.io and legal@peci.ioThe content of e-mails sent to or from these addresses: Merchant correspondence, the notices we send from them, any request a Customer sends us directly (kept as our own record, Section 5), and the data we send to a Merchant ourselves (a copy under the DPA, Section 9.5, or a customer's data under Section 8c where the store has no contact e-mail address), which may contain Customer dataEuropean Union (Zoho's EU data centre)Processed in Zoho's EU data centre; any access from outside the EEA is covered by Zoho's intra-group agreement and data processing addendum based on the European Commission's Standard Contractual Clauses

Other service providers (Merchant data and listing visits). For the Merchant data in Section 3a and the listing visits in Section 3c we also use the following providers, which process that data on our behalf:

ProviderRoleData sharedRegionSafeguard
Amazon Web Services (Amazon Simple Email Service)Sending the App's e-mails to the Merchant (plan-limit and billing-grace notices, with the upgrade suggestions they carry) and operations alerts to the Company, which may name the affected shop domainStore contact e-mail address, shop domain, plan and usage figureseu-west-1 (Ireland, EU)Processed within the EU; no third-country transfer for this processing
Telegram (Bot API)Internal operations alerts to our own staffError counts and event type only; no shop domain, no Merchant or Customer identifying dataNot applicableNo personal data is sent to Telegram (the shop domain is stripped from the alert; it stays in our own e-mail and logs)
Google Ireland Limited (Google Analytics)Analytics for the App's Shopify App Store listing (Section 3c), on our behalf under Google's data processing termsThe listing visit data in Section 3cProcessed by Google, including in the United StatesGoogle LLC is certified under the EU–US Data Privacy Framework; SCCs stand as a fallback

The e-mail host in the first table also holds the e-mails Merchants send to these addresses and the e-mails we send to Merchants from them.

We will notify Merchants of any new or replacement sub-processor at least 30 days in advance by email to the store's contact e-mail address, and Merchants may object as set out in the DPA (Section 6.4).


8. International transfers and data-subject rights

8a. International transfers

The App's application hosting (Vercel) and its database (Neon) are located in the United States, and Google Analytics, which we use for the listing visits in Section 3c, also processes data there. Because the Company is established in the European Union and processes personal data covered by the GDPR, transfers of that data to the United States are safeguarded as follows:

A copy of the Standard Contractual Clauses we rely on is available on request at privacy@peci.io.

United Kingdom. For transfers subject to the UK GDPR, the UK International Data Transfer Agreement (IDTA), or the UK Addendum to the EU SCCs, applies to UK–US transfers, alongside the UK extension to the DPF where the sub-processor or service provider participates in it.

Canada. If Canadian privacy law (PIPEDA) applies to you, the rights described in this policy are available to you as well; write to privacy@peci.io.

Australia. If Australian privacy law (the Australian Privacy Principles) applies to you, the rights described in this policy are available to you as well; write to privacy@peci.io.

8b. Merchant and listing visitor rights (as data subjects of Controller processing)

Merchants and visitors to our listing (Section 3c) may exercise GDPR rights (access, rectification, erasure, restriction, portability, objection) by contacting privacy@peci.io. We will respond within one month of receiving the request; where necessary, taking into account the complexity and number of requests, this may be extended by two further months, in which case we tell you within the first month (GDPR Art.12(3)).

Your right to object. Where we process your data on the basis of our legitimate interests (Section 3a: the upgrade suggestions, the plan suggestion, the app event log, the Terms acceptance record, the uninstall record and keeping correspondence after the matter is closed; Section 5: the usage summary; Section 3c: listing visits), you may object at any time, on grounds relating to your particular situation, by writing to privacy@peci.io. For listing visits, you can also stop the collection at any time by refusing analytics in Shopify's cookie settings; deleting the cookies in your browser removes the identifier, but a new one is set on your next visit unless you have refused analytics.

Upgrade suggestions by e-mail. You may object at any time, without giving reasons, to upgrade suggestions by e-mail. They appear in our plan-limit notices, as text about our higher plans and a button to our plans page, and in our billing-grace notice, as a button to our plans page; every e-mail that carries them contains a link to stop them. Stopping them does not stop the notices themselves, which we owe you under the contract: they still reach you, without the suggestions. The billing-grace notice still tells you how full service can be restored, including by choosing a higher plan. We keep the date you stopped them with the shop record, and it is deleted with that record on uninstall.

Right to complain (Art.77) and supervisory authority. You have the right to lodge a complaint with a supervisory authority. The Company's lead supervisory authority is:

Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH) 1055 Budapest, Falk Miksa utca 9-11, Hungary Postal: 1363 Budapest, Pf. 9. Phone: +36 1 391 1400 Email: ugyfelszolgalat@naih.hu Web: naih.hu

You may also complain to a supervisory authority in the Member State of your habitual residence, your place of work or the place of the alleged infringement (GDPR Art.77(1)).

8c. Customer rights (Processor context)

Because we act as a Processor for Customer data, Customers should direct data requests to the Merchant (the Controller). The Merchant is responsible for responding. A request you send us directly is passed on to the Merchant; we keep it, with our reply, as our own record as Controller (Section 2; Section 5, Correspondence), and you may exercise the rights in Section 8b over that record, including the right to object, at privacy@peci.io. Shopify automatically routes the following mandatory privacy webhooks to us on Merchants' behalf, and we act on them within the timelines below:

customers/data_request — When a customer exercises their right of access. The App compiles the data it holds about that customer (saved carts, cart references, the links they shared and, while a link exists, its openings, orders attributed to a shared link, and the event-log entries naming them) and sends it by e-mail to the store's contact e-mail address, so the Merchant can include it in their answer to the customer; if the App holds nothing, the e-mail says so. Where the store has no contact e-mail address, we are alerted and send the data to the Merchant ourselves. The request is recorded in AuditLog with Shopify's request id and the outcome -- that entry is one of the GDPR compliance rows retained for 3 years (see Section 5), and it carries no customer identifier. Completed within 30 days.

customers/redact — When a customer exercises their right to erasure. We delete: all CartToken records for the customer ID on that shop; the SavedCart record for that customer; ShortUrl records created by that customer (customerId match); and the LinkClick records made through that customer's short URLs or cart tokens, or attributed to the orders Shopify lists in the request. Once an expired share link has been deleted by the daily cleanup, a click made through it keeps no reference to the link or to the customer who shared it, so that customer's erasure request no longer reaches it; the click keeps the product variant IDs, the channel, the time and the hashed token of the person who opened the link, and is deleted under the rule in Section 5. OrderConversion records matched by the customer's cart tokens, or by the orders Shopify lists in the request (orders_to_redact), are deleted. AuditLog entries referencing the customer are deleted (matched on the customer id inside the entry, in both the string and numeric form the different code paths write). One new compliance AuditLog row IS written to record that the erasure happened: it holds Shopify's request ids and the row counts, and no customer identifier; it is retained for 3 years (see Section 5). Completed within 30 days, typically within 48 hours of receiving the webhook.

shop/redact — When a Merchant uninstalls and Shopify requests shop-level deletion (Shopify sends this typically 48 hours after uninstall). We delete all data associated with the shop: Session (including the access tokens), Merchant, CartToken, SavedCart, ShortUrl, LinkClick, LinkClickDaily, and the operational AuditLog rows. The GDPR compliance AuditLog rows are retained for 3 years (see Section 5) -- they carry no customer identifier and are the proof that the erasure took place. OrderConversion records are deleted. The Terms acceptance record is retained for 5 years (see Section 5). The UninstalledRegistry entry and the usage-summary records (MerchantUsageArchive, MerchantUsage, MerchantSettings — no customer data, no tokens) are retained as described in Section 5. Completed within 30 days, typically within 48 hours of receiving the webhook. The UninstalledRegistry entry (non-personal, no tokens) is retained for 30 days after the uninstall, then deleted, as described in Section 5.


9. United States State Privacy Rights

This section is for residents of United States states with comprehensive privacy laws (such as California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon and Montana).

Customers of a Merchant's store. When you use a Merchant's store, the App processes your personal information on that Merchant's behalf. Under these laws we act as the Merchant's service provider / processor / contractor, not as a "third party", and the Merchant is the business responsible for your request. To access, delete, correct or port your data, or to exercise any other right your state gives you, contact the Merchant whose store you used. The Merchant will instruct us, and we will help the Merchant respond (see the DPA, Section 7).

Merchants and listing visitors. For the account and contact data we hold about Merchants and their staff, and for the data about visits to the App's Shopify App Store listing (Section 3c), contact us at privacy@peci.io. The process in Section 8b applies.

We do not sell or share personal information as those terms are defined by the CCPA/CPRA. We do not use personal information for cross-context behavioural advertising, and we do not disclose it for monetary or other valuable consideration.

Sensitive personal information. The App does not seek to collect sensitive personal information (e.g. precise geolocation, government IDs, health, biometric, or protected-class data), and does not use any data to infer characteristics. We process only the data described in Section 3; for visits to our listing, the location is approximate only (Section 3c).

Minors (US). The App is a B2B tool directed at Merchants and is not directed to children. We do not sell or share personal information (see above), and so do not sell or share the personal information of consumers under 16.

De-identified data. Where we use de-identified or aggregated data (e.g. for service metrics), we maintain it in de-identified form, do not attempt to re-identify it, and contractually require the same of any recipient.


10. Article 28 DPA summary and where to find the full DPA

The full Data Processing Agreement under GDPR Art.28 is published at https://peci.io/persistent-cart/dpa, is incorporated by reference into the Terms of Service, and is accepted together with them in the App's acceptance step. It also contains the US service-provider/contractor terms referenced in Section 9. The DPA prevails over the other documents on any data-protection question. Key terms:


11. Security

We implement appropriate technical and organisational measures including:

We will notify affected Merchants without undue delay if we become aware of any personal data breach affecting personal data we process on your behalf. (As a processor, Article 33(2) GDPR imposes no risk threshold on this notification to the controller; the risk assessment governs only the Merchant-controller's own notification duties.)


12. Children

The App is directed at Shopify merchants (business users). We do not knowingly process personal data of children. Where the App operates on storefronts across the EU, the age of digital consent varies by Member State (between 13 and 16); the Merchant, as Controller of storefront customer data, is responsible for the applicable age threshold and for any parental-consent requirements. If you believe we have inadvertently processed a child's data, contact privacy@peci.io.


13. Changes to this policy

We review this policy at least once a year. A change that limits your rights under this policy, that is materially adverse to you (Terms of Service, Section 14), that changes who the controller is, that extends a retention period, that adds a recipient or a transfer outside the EEA for data we already hold, or that uses data we already hold for a new purpose, takes effect no earlier than 30 days after we publish it on this page and notify Merchants of it by email. Any other change, such as the description of a new optional feature, a correction, or a change required by law, takes effect when we publish it, and we notify Merchants of it by email no later than that day. This Section does not affect the notice of new or replacement sub-processors in Section 7 and the DPA, Section 6.4. The version of this policy in force when you accept the Terms of Service in the App is recorded with your acceptance (Terms of Service, Section 3A). The effective date at the top of this document is updated on each revision.


14. Contact

For privacy questions, data-subject requests, or the full DPA:

PÉCI Kft. Aradi utca 5., 2119 Pécel, Hungary Data / privacy matters: privacy@peci.io Legal notices: legal@peci.io Full DPA: https://peci.io/persistent-cart/dpa

We have not appointed a data protection officer, as GDPR Art.37 does not require one for our processing; privacy@peci.io is the contact for every data-protection matter.

Version history

Each version of this document is listed with the period it was in effect. Every version is kept unchanged at its own permanent address.

VersionIn effectWhat changedCopy
rev17-2026-10-28 2026-10-28 – current Section 13 sets out how changes to this policy take effect. A change that limits your rights, is materially adverse to you, changes the controller, extends a retention period, adds a recipient or a transfer outside the EEA for data we already hold, or uses that data for a new purpose takes effect no earlier than 30 days after it is published and notified by email; any other change takes effect when published, with notice by email no later than that day. The notice of new or replacement sub-processors is unchanged. Section 3a lists notice of changes to this policy, not only material ones, among the uses of the store contact e-mail address. Permanent copy
rev16-2026-10-27 2026-10-27 – 2026-10-28 The App's page on the Shopify App Store is covered: where a visitor consents to analytics in Shopify's cookie settings, we measure the visit with Google Analytics as controller (Section 3c), with the data collected, the legal bases, the retention and how to withdraw consent or object. Google Ireland Limited (Google Analytics) is listed among the recipients, and the transfer section names Google LLC with its Data Privacy Framework certification and Google's data processing terms. The rights and United States sections include listing visitors. The shipping calculator is described: the address details a Customer uses there go from the browser to the store's own Shopify shipping-rate service and do not reach our servers. Permanent copy
rev15-2026-10-17 2026-10-17 – 2026-10-27 A click made through a share link is kept until 31 days after the click once the link has been deleted, and the App keeps daily click totals for its analytics. The purposes of the store contact e-mail address are listed in full, correspondence with us is described with its retention and legal bases, and the application logs, the 24-hour restore history and the two records we keep as controller are set out. The database provider is named as Databricks, Inc. (Neon), and Vercel's transfer basis as its Data Privacy Framework certification. The Canada and Australia paragraphs state the rights available there. Upgrade suggestions in the plan-limit and billing-grace e-mails can be stopped at any time with the link in each of them; the notices continue without them. Permanent copy
rev14-2026-10-15 2026-10-15 – 2026-10-17 The mail host behind our privacy@, legal@ and persistentcart@ addresses (Zoho Corporation B.V., Zoho Mail) is listed among the sub-processors. A separate paragraph sets out the right to object to processing based on our legitimate interests. A copy of the Standard Contractual Clauses is available on request. Permanent copy
rev13-2026-10-02 2026-10-02 – 2026-10-15 The App is named Peci: Persistent Cart. The access scopes listed are the three the App requests (read_orders, write_pixels, read_customer_events), each with its use; the Storefront Access Token is no longer listed, as the App no longer keeps one. Two records added: an order placed from a restored cart, and the two cart attributes a link that goes straight to checkout adds. Analytics shows link clicks and matched orders on every plan, their revenue and the daily trend from the Basic plan. Customer cart data is stated as coming from the storefront widget. Permanent copy
rev12-2026-10-01 2026-10-01 – 2026-10-02 First published version. Permanent copy