EnKart Docs Add EnKart free

Permissions and privacy

Each permission EnKart asks for and why, what it never reads, and what it keeps.

EnKart asks for nine permissions, each for one job, and none about your customers. The full policy is EnKart's privacy policy, linked from the App Store listing.

Permissions#

PermissionWhat it is for
read_productsTo read your catalogue, collections and product fields, so rules, exclusions and offers can match products
write_productsTo 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 priced add-ons
read_ordersTo 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_themesTo check whether the app block and the cart drawer embed are placed and switched on in your theme
write_cart_transformsTo register the one cart transform that prices priced add-ons
read_shippingTo read your free shipping amount from your shipping settings, for the free shipping offer
unauthenticated_read_product_listingsTo ask Shopify for its own related and complementary product recommendations
write_discountsTo create the one automatic discount that applies offer discounts at checkout
read_localesTo list your store's languages, so an offer's text can be translated

What EnKart never reads#

EnKart asks for no customer permission. It never reads a customer's name, email, phone number or address. The orders it reads are used for their line items and totals only.

Offers that show only for some shoppers, by customer tag, country or market, are checked in the shopper's browser from what your theme already knows. That never reaches EnKart.

On your storefront#

  • The block and embed load only on product and cart pages.
  • To show you how offers perform, the storefront sends anonymous counts: an offer was seen, clicked or added. No cookie, no shopper identifier, and nothing at all when a shopper declines analytics in your cookie banner.
  • A pop-up offer is remembered for the browser session so it opens once at most, in the browser's session storage, never sent.
  • During an A/B test, the version a shopper sees is kept in their browser's local storage, never sent.

What EnKart writes to your store#

Metafields in the enkart namespace on your products and shop, so your theme can show offers without calling EnKart's servers; one hidden product for priced add-ons; one cart transform; and one automatic discount, Enkart offers. Cart lines added from an offer carry a hidden line property with the offer's id.

These stay yours to keep or remove after you uninstall.

What EnKart keeps, and deletion#

While it is installed, EnKart keeps your offers, rules and exclusions, a working copy of your catalogue, your settings, daily offer counts and the attribution log, among the other records the privacy policy lists. None of it is about your customers. When you uninstall, its access ends at once. 48 hours later Shopify asks EnKart to erase your store's data, and every record is deleted. Before that, you can export everything; see Your data and export.