What is stored
Four tables and one option:
Plus the cartpresets_settings option, and meta on order line items — see Order line item meta.
The one row with personal data in it
A redemption records who claimed a preset, so a per-customer cap can be enforced. For a signed-in customer that is their user ID. For a guest it is a hashed fingerprint, not an email address or an IP you could read back.
Without it a per-customer limit cannot exist — there is no way to know somebody has already claimed something if you do not record that they did.
What leaves your site
Nothing, on the free build. No analytics, no phone-home, no scripts or styles enqueued on your storefront at all.
On Pro, one thing: a licence check. Your licence key and site URL go to the licensing service to activate, to verify periodically, and to check for updates. It runs from wp-admin and cron only — never from your storefront, so a customer browsing your shop never triggers it.
The Presets report reads your own WooCommerce order tables. Those figures never leave your site.
The Copy system report button on the Settings sidebar reads your install and puts the result on your clipboard. It sends nothing. It is there so you can paste it into a support thread yourself.
Uninstalling
Deleting the plugin removes nothing by default.
That is the opposite of most plugins, and deliberate: a merchant who deactivates to test something, or who deletes and reinstalls to fix a bad upload, should not lose a year of work to a routine action.
Each category has its own opt-in under Settings → Data control:
These fire on delete, not on deactivate, and they cannot be undone. Turning one on does nothing immediately — it arms the deletion for whenever you next delete the plugin.
What is never removed
Order line item meta stays, whatever you switch on. It is part of your order history, and an order that recorded which preset it came from should keep recording it after the plugin is gone.
The carrier product is also left alone unless you opt in specifically. It is a WooCommerce product that may be attached to old orders, and deleting it would damage order history.
GDPR and data requests
The only personal data is the redemption record. If you need to erase a customer’s data, deleting their rows releases any per-customer cap they were holding — which is the correct outcome: with no record of their claim, there is no claim.
Moving to a new site
Presets are database rows, so a full database migration carries them.
If you are moving between separate stores, use Import and export instead — it matches products by SKU on the way in, which a raw table copy cannot do.
