What this policy covers
This Privacy Policy explains how TagMake handles the information used to generate craft fair tags, care cards, and line sheets. The app is designed so that your working product data stays in your browser during normal editing, while a smaller set of checkout and payment records is processed only when you start a paid purchase.
Product data stays local while you edit
When you import CSV, XLSX, or saved JSON files, TagMake processes that content inside your browser on your device. Your product names, descriptions, prices, images, logos, and layout settings are also stored locally in your browser so you can keep working if you refresh or return later.
- Imported files are parsed in the browser, not uploaded to TagMake during normal editing.
- Draft settings are saved in browser local storage so your workspace can be restored.
- Language choice and free-template preference are also stored locally on your device.
What changes when you start checkout
If you choose a paid export, TagMake creates a checkout draft identifier in your browser and sends that identifier to the hosted checkout URL so the payment can be matched to your export access. After checkout, the app may call its access endpoint with that draft identifier to confirm that payment access has been granted.
- The checkout draft identifier is a random reference used to reconnect your browser to a paid batch.
- The access check endpoint uses the draft identifier to look up export access and does not need your full product catalog to respond.
- Payment processing itself is handled by Lemon Squeezy under its own terms and privacy practices.
Records TagMake stores for paid access
To activate paid export access, TagMake stores a limited record of the paid order. That record includes the checkout draft identifier, an access token, the order identifier, the plan tier, SKU limit, purchaser email supplied by the payment provider, and access timestamps.
- These records are used to unlock paid exports and support later access restoration.
- Paid access records currently expire after 30 days unless a refund or other account action ends access earlier.
- Refund webhook events can revoke export access linked to an order.
Your choices
You can clear locally stored drafts and preferences directly in your browser. You can also choose not to start checkout, in which case your working product data remains local to the browser session and storage available on your device.