Privacy Policy

Last updated 10 August 2026 · Insertly is operated by Found.

The short version. Insertly reads a merchant's orders so it can print a personalised card for each one. It never sees payment or card details. It stores nothing about a buyer beyond what is needed to render that buyer's card. It never sells data to anyone.

1. Who this covers

This policy covers Insertly, an application for OpoShop stores that generates print-ready package inserts — thank-you cards, care cards and reorder offers — from a store's orders. It applies to the merchant who installs Insertly. Insertly has no storefront widget and no buyer-facing web page: buyers only ever encounter it as a printed card in their parcel.

2. Merchant store data

When a merchant installs Insertly, OpoShop grants it an access token scoped to that one store. Insertly uses it only for the following, and requests no permission it does not use:

Orders (read). Order number, date, item count and the buyer's name, so a card can say “Thanks for your order, Jane!” instead of “Dear Customer”, and so the packer can match a card to a box.
Discounts (write). Only when a merchant switches on unique reorder codes: Insertly creates one discount in the merchant's store per order, so the code printed on the card actually works at checkout. This is the only write Insertly ever makes to a store.
Discounts (read). To read a code back after creating it and confirm it exists before it is printed on a physical card.

Insertly does not request or use access to products, customers, collections, or webhooks.

3. What Insertly stores

In its own database (a dedicated database used only by this app, with every record scoped to a single store), Insertly keeps:

The store id, subdomain, store name, and the OpoShop access token — used only to call OpoShop on that store's behalf.
The store owner's identity as supplied by OpoShop during install, so the app can authenticate them.
The merchant's brand settings (business name, logo image, accent colour, storefront URL, sign-off) and card designs.
A ledger of every reorder code Insertly created: the code, the order number it belongs to, the percentage, the expiry, and whether it was successfully created.

4. Buyer data — what we do not keep

To personalise a card, Insertly reads a buyer's name, order number and item count from the order at the moment the card is generated. That information is used to render the PDF and is not stored in Insertly's database. Insertly does not store buyer email addresses, postal addresses, or phone numbers, and it never has access to card or payment details at any point — payment is handled entirely by OpoShop and its payment provider.

The only buyer-linked record Insertly retains is the reorder-code ledger described above, which stores an order number — not a person's contact details.

5. Analytics

Insertly uses PostHog for product analytics, to understand which features are used. Events are identified by an opaque, store-scoped identifier of the form store_<id>. No personal data is ever sent to analytics — no emails, no buyer names, no order contents, no addresses.

6. Sharing

Insertly does not sell data and does not share it with advertisers or data brokers. Data is processed only by the infrastructure providers required to run the app: Fly.io (hosting), MongoDB Atlas (database), and PostHog (analytics, non-personal events only). Generated PDFs are produced on demand and streamed to the merchant's browser; they are not stored on our servers.

7. Retention

Store data, brand settings, card designs and the reorder-code ledger are kept for as long as the app is installed. If a merchant uninstalls Insertly, the store is marked uninstalled and the first-run flag is cleared; the card designs and code ledger are retained so a reinstall restores the merchant's work. A merchant can request complete deletion of their data at any time by emailing the address below, and it will be removed.

8. Security

All traffic is served over HTTPS. Access tokens are stored server-side and never exposed to the browser. Every record is scoped to exactly one store, and every request is authorised against the store it belongs to — one merchant's data is never reachable from another merchant's session.

9. Your rights

You can request access to, correction of, or deletion of the data Insertly holds about your store at any time. Email brandon@tryfound.io and we will respond.

10. Changes

If this policy changes materially, the “last updated” date above changes with it.