This policy covers the CartClip service and the CartClip WordPress plugin. It describes exactly what the software sends and stores, because that is the only description worth publishing.
1. Account data
When you sign up we store your email address and a display name. Authentication is handled by Supabase; we never see or store your password.
2. Data from a connected store
When you connect a WordPress store, the plugin sends us:
- the store's domain and URL
- its WordPress and WooCommerce version numbers
- the CartClip plugin version
This is used to lock your access key to that domain, to show the store in your dashboard, and to warn you about version incompatibilities. We do not read your orders, customers, posts, or database.
3. Product data
When you tag a product, CartClip stores that product's ID and a snapshot of its name, image, price, and URL so the dashboard can render without contacting your store. On your storefront, the plugin ignores that snapshot and uses live WooCommerce data instead, so shoppers always see current prices and stock.
4. Storefront analytics
When a shopper views a page containing a CartClip video, the player records anonymous events: a video being seen, played, a product being clicked, and a product being added to cart. Each event carries a random per-tab session identifier, the video and product involved, and a device category (mobile, tablet, or desktop) derived from the browser's user-agent string.
When an order completes, your store sends us the order total, currency, order ID, and which video the purchase is attributed to, so revenue can be reported back to you.
We do not set cookies on your storefront, and we do not collect names, email addresses, or any other shopper identity. The session identifier is random, scoped to one browser tab, and is not linked to a person.
IP addresses are used transiently for rate limiting and are hashed before use. They are never written to our database.
5. Retention
- Raw events — 90 days on the free plan, 365 days on paid plans, then deleted automatically.
- Daily aggregated counts — kept for as long as your account exists. These contain no session identifiers.
- Account, video, and tag data — kept until you delete it or close your account.
6. Processors we use
- Supabase — database and authentication
- Vercel — application hosting
- Upstash — rate limiting and short-lived tokens
- Razorpay — payment processing for paid plans. Card details go directly to Razorpay; we never receive them.
7. Your rights
You can access and correct your data from the dashboard, and export or delete it by deleting your account. Depending on where you live, you may also have the right to object to processing or to lodge a complaint with a data protection authority. To make a request, email us.
8. For merchants
If you operate a store using CartClip, you are the controller of your shoppers' data and we are a processor acting on your instructions. Because CartClip sets no cookies and collects no shopper identity, it does not by itself require a cookie banner — but your own privacy policy should mention that a third-party analytics service records anonymous interaction events.
9. Changes
We will post updates to this page and change the date above. Material changes will be announced in the dashboard before they take effect.
10. Contact
Privacy questions or requests: support@cartclip.app.