Privacy Policy
Last updated: 2026-10-29
CartPass is a Webflow app, operated by Webnotics Pvt Ltd (307, Padam Corporate Park, Sikandra, Agra, UP-282007), that adds customer accounts and order history to Webflow Ecommerce stores. This policy explains what data we handle, why, and the choices you have.
Who this covers
- Store owners who install CartPass on their Webflow site, and the team members they invite to the dashboard.
- Shoppers who create an account on a store that uses CartPass. For shoppers, the store is the party responsible for your data; we process it on the store's behalf and follow the store's instructions. Everything below about shoppers describes what we do as that processor.
What we collect
- From store owners: your Webflow account name and email, the sites you connect, and an access token from Webflow (stored encrypted). If you invite team members we keep their name, email, role and the stores they can see.
- Orders from Webflow: order number, items, totals, status, shipping and billing addresses, tracking details, and the buyer's email. For card payments we receive only the card brand and last 4 digits. We never receive or store full card numbers or CVV codes.
- From shoppers: name, email, a password (stored only as a one-way hash), and an optional phone number, saved addresses, custom profile fields the store has set up, and email preferences, including whether the shopper agreed to news and offers emails.
- On your store's pages: the account widget script CartPass adds through Webflow sends us only what shoppers type into its forms. It doesn't track visitors or read any other forms, including checkout and payment fields. See what CartPass adds to your site.
- Social sign-in, if the store turns it on: when a shopper chooses Continue with Google, Facebook, GitHub or LinkedIn, the provider tells us the shopper's name, email address and the provider's own user ID, and in some cases a profile picture. We keep the name, the email and the provider user ID (so the same person is recognised next time). We don't keep the profile picture. We never receive the shopper's password for that provider.
- Sign-in and security records: for shoppers, sign-in times and the browser type (user agent) of each active session. For store owners and team members, a sign-in log and a list of active sessions with time, email, IP address, browser type and whether the attempt worked, plus an audit log of changes made in the dashboard (who did what, and when).
- Email records: for each account email we send for a store, we keep the recipient address, subject, the message as it was sent, its delivery status and the delivery events the mail provider reports (for example delivered or bounced). One-time sign-in, confirmation and reset links are removed from the stored copy. For campaigns we keep who received each one and, only if the store owner turned tracking on for that campaign, whether the recipient opened it or clicked a link.
- Developer tools: API keys (only a one-way hash is stored; the key is shown once when created), webhook addresses and signing secrets (stored encrypted), and a delivery log of each webhook sent, including what the receiving server answered.
- Technical data: our servers log requests (including the IP address) for security and debugging. Sign-in codes and tokens in URLs are masked in those logs.
How we use it
- To show shoppers their orders, tracking, invoices, addresses and profile.
- To give store owners a dashboard of their orders and customers.
- To send account emails: email confirmation, sign-in links (for shoppers and store owners), password resets, invitations, welcome emails and order status emails (for example when an order ships). These are service messages. They carry no open or click tracking.
- To send marketing campaigns that the store owner writes, only to shoppers who agreed to receive news and offers, and never to an address that has unsubscribed, bounced or complained. Every campaign has an unsubscribe link and the store's business address.
- To let a store use connected apps: if the store owner sets up an app that signs shoppers in with their store account (OpenID Connect), the app receives the shopper's ID and, depending on what it asks for, their email and name. See Connected apps below.
- To send order and customer events to the store owner's own systems, when the owner sets up webhooks or API keys (see below).
- To email store owners about their account, such as new-customer alerts and weekly summaries, if they turn those on, and notices about billing or this service.
- To keep the service secure and prevent abuse, including rate limiting and, when a store turns it on, bot checks at sign-up and sign-in.
We don't sell personal data, and we don't use it for advertising.
Connected apps and the developer tools
- Connected apps: a store owner can register apps that let shoppers sign in with their store account. When a shopper signs in to such an app, we give the app a sign-in token and, within what the app requested and the shopper allows, the shopper's ID, email address (already confirmed) and name. We don't pass on their password, orders, addresses or phone number this way. The app's owner is responsible for what the app does with the data.
- API keys: a key lets the store owner's own server read customers, orders and roles for that store, and update customer details if the key has full access. Keys are limited to 600 requests per minute. A key shown to you once cannot be recovered by us.
- Webhooks: each webhook we send contains an event ID, type, time, store ID, the customer's ID and email address, and event details (for example an order ID, total or tracking link). Payloads are signed so the receiver can check them. We keep a delivery log, with the response your server gave, for 30 days.
Who we share it with
Only service providers that help us run CartPass, under contracts that require them to protect it:
- Cloud hosting and database provider (servers that store the data).
- Stripe, which processes subscription payments. Card details go to Stripe directly and never reach our servers; we keep only your Stripe customer and subscription IDs and your plan status.
- Email delivery provider, the SMTP service we send account and campaign emails through. It receives the recipient address and the message, and reports delivery events back to us.
- Webflow, to read orders and add the account widget to your site.
- Google, Meta (Facebook), GitHub and LinkedIn, only when a store has turned that sign-in method on and a shopper chooses it. The shopper is sent to that provider to sign in, and the provider sends back the details listed above. Their own privacy policies apply to what they do with the shopper's use of their service.
- Cloudflare, only when a store turns on bot protection (Turnstile). Cloudflare checks the visitor's browser when a shopper signs up or signs in, and may receive the visitor's IP address and browser details for that check.
- Services chosen by the store owner. Store owners can set up webhooks and connected apps that send customer and order data to addresses they choose. We send the data there, and the owner is responsible for what the receiver does with it.
We may disclose data if the law requires it.
Tracking in emails
- Account and order emails sent by CartPass contain no tracking pixel and no tracked links.
- Campaign emails are not tracked unless the store owner switches tracking on for that campaign. Opens use a tiny image and clicks use a redirect link; each is tied to the recipient so the store can see results. If tracking is off, nothing is recorded. Shoppers who don't want to be tracked can block remote images in their mail app or unsubscribe.
Cookies and storage
The store owner dashboard uses one essential sign-in cookie. On stores, the account widget keeps a sign-in token in the browser's local storage so shoppers stay signed in. When a shopper uses a social sign-in, a short-lived (10 minutes) security cookie protects that one sign-in attempt. Bot protection, if a store turns it on, loads Cloudflare's check on the sign-up and sign-in forms. We don't use tracking or advertising cookies.
How long we keep data
- While a store uses CartPass, we keep its data so the service works.
- If a store uninstalls CartPass, we delete all of that store's data within 30 days.
- A shopper who deletes their account is removed right away; the store keeps its own order records. See Data deletion for what stays and for how long.
- Email history (the message and its delivery events): 90 days, or sooner if the shopper's account is deleted.
- Webhook delivery logs: 30 days.
- Expired shopper and store-owner sessions and one-time tokens are cleared automatically every day.
- Sign-in log and audit log entries for a store owner's account are kept while the account is active and deleted with it.
- Addresses on a store owner's suppression list (people who unsubscribed, bounced or complained) are kept so they aren't emailed again.
Security
Data travels over HTTPS. Passwords are hashed, Webflow access tokens, social sign-in and webhook secrets are encrypted, and API keys, email links and sign-in tokens are stored only as hashes. Store owners can protect the dashboard with two-factor authentication (an authenticator app) and see their active sessions. Team roles limit what each person can see or change. Each store's data is kept separate from every other store's.
Your rights
You can ask to see, correct, export or delete your personal data. Shoppers can edit their profile or delete their account from My account on the store, or contact the store. Because the store decides how shopper data is used, requests about a shopper's data are best made to the store; if you contact us we will pass the request to the store or act on its instructions. Store owners and anyone else can email support@webnotics.solutions. You can stop marketing emails at any time with the unsubscribe link in any campaign, or by turning off News and offers in your profile. See also Data deletion.
Changes
If we change this policy in a meaningful way, we'll update the date above and tell store owners by email.
Contact
Webnotics Pvt Ltd, 307, Padam Corporate Park, Sikandra, Agra, UP-282007. Email support@webnotics.solutions.