Who we are
EnKart is operated by Enstacked Technologies. For any privacy question or request, email support@enstacked.com.
What we access in Shopify
EnKart uses Shopify's Admin GraphQL API. It asks for these access scopes, each for one job:
- read_products: to read your catalogue, collections and product fields, so rules, exclusions and offers can match products.
- write_products: to save each product's offers in its own metafield, so your theme shows them with no extra network call, and to create the one hidden product that carries paid add-ons.
- read_orders: to count orders that contain an item added from an offer (your results and billing), and to read the last 60 days of orders for products bought together.
- read_themes: to check whether the app block and the cart drawer embed are placed and switched on in your theme.
- write_cart_transforms: to register the one cart transform that prices paid add-ons.
- read_shipping: to read your free shipping amount from your shipping settings, for the free shipping offer.
- unauthenticated_read_product_listings: to ask Shopify for its own related and complementary product recommendations.
- write_discounts: to create the one automatic discount that applies offer discounts at checkout.
- read_locales: to list your store's languages, so an offer's text can be translated.
We do not access your customers
EnKart asks for no customer scope and never reads a customer's name, email, phone number or address. The orders it reads are used for their line items and totals only.
What we keep, and where
Our database keeps, for your store:
- the Shopify session for this app on your store, including its access token, which never leaves our servers.
- your store's domain, currency, time zone, plan, trial and billing dates, scan status and app settings.
- a working copy of your catalogue: each product's title, handle, vendor, type, tags, collections, product fields, price, stock status and main image address.
- your collections' titles, for rules and exclusions.
- the offers you create, with their text, products, conditions, look and translations.
- the product rules you create.
- the exclusions you set.
- the product recommendations Shopify returned for your products.
- pairs of your products bought together, with how often, worked out from your orders without any customer details.
- for each order: its id, number and date, and for each line added from an offer the line's title, value and any refund, with whether the order counted and why.
- daily counts of how often each offer was seen, clicked and added, with no shopper identifier.
- the charges made through Shopify's billing.
- the results of the theme check: theme names and whether the block and embed are on.
- when the app last showed on each of your themes, sent only from the theme editor and theme previews.
- what was last written to each product's offers metafield, so only changes are written again.
What we write to your store
So that your theme can show offers without calling our servers, EnKart writes metafields in the enkart namespace on your products and on your shop. It also creates one hidden product for paid add-ons, one cart transform and one automatic discount. Cart lines added from an offer carry a hidden line property with the offer's id, which is how an order is counted.
On your storefront
The app's block and embed load only on product and cart pages. If you add the EnKart block to your Thank you page or Order status page, it shows offers for the products bought, reads nothing about the customer and sends nothing to us. To show you how offers perform, the storefront sends anonymous counts (an offer was seen, clicked or added) with no cookie and no shopper identifier, and sends nothing when a shopper declines analytics in your store's cookie banner.
If you turn on a pop-up offer, the shopper's browser remembers which pop-ups it has already shown during that visit, in its session storage rather than a cookie, so each opens once at most. This is never sent to us, and the browser clears it when the shopper closes the tab.
On the post-purchase page
If you choose EnKart as your store's post-purchase app, then after payment Shopify's post-purchase page asks our server for an offer. It sends the order's reference, the products and variants bought with their quantities, and the customer's language, never their name, contact details or address. We use them to pick the offer and keep nothing but anonymous counts of offers shown and accepted.
When the customer accepts an offer, our server signs the change Shopify makes to their order: the product added, its discount, and a note on the order naming the offer, which is how the order is counted.
How long we keep it, and deletion
We keep this data while EnKart is installed. When you uninstall, the app's access ends at once and its session is deleted. 48 hours later Shopify asks us to erase your store's data (shop/redact), and we delete every record we hold for your store.
Shopify can also ask on a customer's behalf for their data, or for its deletion (customers/data_request and customers/redact). EnKart holds no customer personal data, so there is nothing to return or delete; each request is verified and logged.
The metafields, hidden product, cart transform and discount in your store are yours to keep or remove.
Who else sees it
We do not sell or share your data. It is processed only by the providers that host the app and its database, and only to run the app. Charges go through Shopify's billing; we never handle payment details.
Security
Data is sent only over encrypted connections. Every request from your admin is verified with Shopify's session token, every webhook with Shopify's signature, and every query is limited to your own store. Our logs record events with your store's domain and, for an order, only its id: never its contents or anything about a customer.
Changes and contact
When what EnKart reads or keeps changes, this page changes with it and shows the new date. Questions and requests: support@enstacked.com.