
Ecom OS Privacy Policy
Version 2026-11-10-billing
This policy explains what personal data Ecom OS collects, why, who receives it, how long we keep it, and the choices you have. Ecom OS is based in California, United States ("Ecom OS", "we", "us"). Contact: support@ecomos.build. This policy took effect on the version date above.
1. Who this covers and our role
- Merchants: the people who use the Ecom OS dashboard for a Whop business, and anyone who connects an AI assistant to it. For this data, Ecom OS is the controller.
- Buyers and store visitors: people who visit or buy from a store built with Ecom OS. Each store belongs to its merchant, who decides how their data is used. For this data the merchant is the controller (or "business") and Ecom OS is the merchant's processor (or "service provider"). The store's own privacy policy applies, and requests about this data are best sent to the store; we will pass them on and help.
- Visitors to our own pages, such as this one.
2. What we collect about merchants
- Whop account details: your Whop user ID and the ID of the Whop business you open Ecom OS for, which Whop sends with each request, and your name and username from Whop, which we keep for up to one hour to show in Settings.
- Whop business data: the products, plans, payments and shipments in your Whop business that Ecom OS reads and writes for you through Whop's API.
- Store setup: your store settings and content, products, images you upload, your business and policy details, and your choices in setup.
- Connected accounts: the API keys and tokens for services you connect (your Whop API key, AliExpress, CJdropshipping, Printful, Printify, Shippo, Resend, Shopify). They are kept in private storage on our Cloudflare account, which Cloudflare encrypts at rest, and are never shown back to you in full.
- AI connections: Ecom OS connection tokens are stored only as a one-way hash. Sign in with Whop connections are stored as hashed tokens and encrypted grants.
- Admin checks: which Whop users have shown they manage a business by connecting its Whop API key, kept for 30 days from the last time they did.
- Billing: whether your business is covered by an Ecom OS plan, its status and dates as Whop reports them (trial, active, paused, past due or ended), which Whop user's plan covers it, which businesses that user is an admin of, and which Whop user owns each business, so one plan can cover the stores its payer owns. Whop takes the payment and holds the card; Ecom OS never receives card details.
- Domain purchases: the registrant contact you enter when you buy a domain in Ecom OS (name, email address, phone number and postal address), sent to Cloudflare Registrar as the registration's contacts and kept with the purchase record. The registrar's privacy redaction hides it from public lookups where the registry allows it.
- Records of agreements: which Whop user accepted which version of the Terms of Service and this policy, and when (by our server's clock), with a keyed one-way hash of the IP address the request came from; each acceptance of your store's policy pages, with the details accepted and the template version; and each publish with incomplete policy pages, with what was missing.
- Technical data: Cloudflare and our servers process IP addresses, browser type and request details to deliver and protect the service, and Cloudflare keeps our service logs, which record requests and errors, for up to 7 days. We hold IP addresses in memory for a few minutes to limit how many requests one address can make, and, for a store's forms, a keyed one-way hash of the address for up to one hour.
- Error reports and usage diagnostics: to keep the service working, the dashboard sends Ecom OS a technical report when something in it fails: the error message, the script and page address without its query string, the dashboard version, a short browser and system name (such as Chrome on macOS) and, for a failed request to Ecom OS, its address and status code, never its content. What you write in Send feedback is kept with the same page, browser and version details. Email addresses, tokens and long numbers are removed before a report or a message is stored, and no IP address or cookie is kept with them. They hold no buyer personal data.
- Support: what you send when you email us or write to us from Support in the app (your message, the email address to answer, any screenshot you add, and the dashboard page you came from, your browser and the app version), and requests for a new supplier or fulfillment partner sent from the app, which we keep for up to one year. A message from Support reaches our support inbox by email through Resend.
3. Buyer and visitor data that passes through Ecom OS
- Orders: when a buyer pays on Whop, Ecom OS receives the order from Whop: the buyer's name, email address, phone number if given, shipping address, what they bought and the amount paid, and later the tracking details. We never receive full card numbers.
- Supplier orders: to fulfill an order, Ecom OS sends the buyer's name, shipping address and, where the supplier asks for them, phone number and email address to the supplier the merchant connected.
- Emails: every automatic email to a buyer is on until the merchant switches it off, in the Ecom OS dashboard or through the AI assistant they connect, except the shipping email and its new tracking number email, which are off until the merchant or that assistant approves them, after seeing the email, who it comes from and where replies go. On by default are the order confirmation and delivery emails, review requests, checkout reminders, the pop-up and Back in stock emails, the answers to a return request, and the subscription renewal, payment failed and refund emails. The merchant's email flows are off until the merchant approves them. Ecom OS uses buyer email addresses only to send the emails the merchant has on, and the answers the merchant (or the AI assistant they connect) sends to a buyer who wrote to the store, from the store's sender: the store's name at send.ecomos.build (Ecom OS's email service), the merchant's own domain once it is verified, or the merchant's own Resend account if they connected one. An email address left for a checkout reminder is kept for about 30 days. If an email bounces or is marked as spam, Ecom OS records that for the store and stops sending to that address.
- Email links: links in a store's marketing emails (campaigns, flows, review requests and their reminder, checkout reminders, the pop-up and next order code emails, and Back in stock emails) pass through the store's own address on the way to their page. The unsubscribe link and the links to the store's policy pages are left as they are, and order emails carry no such links. When someone follows one, Ecom OS records which email it was, when, and a one-way code of the page it led to, under a one-way code made from the store and the email address, never the address itself. If the person is on the store's list, Ecom OS also notes the day of their latest click on their subscriber record. Ecom OS uses this to show the merchant which emails led to orders: an order placed within 5 days of a click is counted for the last email its buyer clicked, and the order record keeps which email that was. For each email Ecom OS also counts how many were delivered and how many people clicked it, as totals only. Ecom OS does not store the IP address or the browser details of a click and sets no cookie for it. It uses the browser name and the network a click came from only to leave out link checks by mail security scanners, where it can tell them apart.
- Reviews and returns: what a buyer sends through a store's review or return form, checked against their order.
- Newsletter signups: the email address a visitor gives a store's signup form, with when they signed up, the page they were on and the consent wording they were shown. It is kept for the store's merchant, who sees the list in the dashboard, can export it, and can email it: a campaign goes only when the merchant presses Send, and a flow only once the merchant approved it, from the same senders as above. Every such email carries an unsubscribe link, which removes the address. Whop does not receive these addresses.
- Contact messages: the name, email address, order number if given and message a visitor sends through a store's contact form. The merchant reads them in the dashboard. If the merchant set it up, the message is also emailed to them through their own email account, and Whop shows the merchant's team a notification with the sender's name and the start of the message. The page never shows the merchant's own email address.
- Customer replies: the emails a buyer sends to the store's reply address (the reply address of the store's emails once the merchant switches on the Ecom OS inbox), received through Resend on Ecom OS's account: the sender's name and email address, the subject, the text of the email and its attachments (images, PDFs and text files, up to 3 MB each and 5 an email). The merchant reads and answers them in the dashboard, or through an AI assistant they connect.
- Notify me: the email address a shopper leaves to hear when a sold out option is back, which the store offers while the merchant has the Back in stock email on. It is used for that one email and does not add the shopper to the store's newsletter. Once the email is sent, only a record without the address stays.
- Order checks: the merchant's hold rules can compare orders before a supplier order is placed, for example several orders from one email address in a day.
- Store analytics: Ecom OS counts page views, checkouts and purchases per day, and the websites that sent visitors, as totals only. It stores no IP address, no browser details and no visitor ID, and sets no cookie for this.
- Abuse limits: a store's forms use the visitor's IP address to stop abuse, kept only as a one-way hash, for up to one hour.
- Shipping emails: once the merchant approved the shipping email, Ecom OS emails each buyer when their order ships, with the tracking details the merchant chose to show, through Resend, from the sender the merchant approved.
- Store error reports: when a script on a store page fails in a visitor's browser, the page sends a technical report to the store's own address, not to another website: the error message, the script and page address without its query string, and a short browser name. It holds no personal data, no IP address and no cookie, and sets nothing in the browser. Ecom OS uses it only to keep stores working, and Ecom OS's own store analytics never count it.
4. Cookies, local storage and Do Not Track
- The Ecom OS dashboard sets no cookies of its own. It uses your browser's local storage to remember display choices such as light or dark mode.
- Sign in with Whop, used to connect an AI assistant, sets one strictly necessary cookie for up to 10 minutes while you choose a business.
- Stores built with Ecom OS use the visitor's local storage for the cart, the visitor's privacy choice and whether a pop-up was shown. Ecom OS's own store analytics use no cookies.
- Whop's checkout and measurement pixel, and any pixels a merchant adds (Google Analytics, Meta, TikTok), can set their own cookies under those companies' policies. Whop's pixel does not load when the browser sends Global Privacy Control, and a store that sells to the UK or EU asks visitors there before loading these tools.
- Do Not Track: Ecom OS does not track people across other websites, and it works the same whether or not a browser sends a Do Not Track signal. We act on Global Privacy Control as described above. Pixels a merchant adds follow their own companies' rules.
5. How we use personal data
- To provide Ecom OS: run the dashboard, build and host stores, place supplier orders, post tracking, send the emails the merchant has on, receive buyers' replies to them and send the merchant's answers.
- To show the merchant which of their marketing emails led to orders, and to keep marketing to people who engage with it: the merchant can choose who gets an email by whether they clicked one recently, and while a store's bounce or spam rates are too high its marketing goes only to people who clicked or joined recently.
- To confirm who you are and that you manage the business.
- To keep Ecom OS secure, prevent fraud and abuse, and find and fix problems, including from the error reports and feedback described above.
- To improve Ecom OS: we use counts of feature use and setup progress, such as which setup steps a business has finished, which features it has switched on, and how many products and orders it has, to see where merchants get stuck and decide what to build. Buyers appear in these only as counts and totals.
- To support you and send service messages, such as changes to these documents.
- To keep records of agreements and of choices such as publishing with incomplete policy pages, so we can show what was agreed.
- To comply with the law.
We do not sell personal data. We do not share it for cross-context behavioral advertising. We do not use buyer data for our own marketing or to train AI models.
For people in the UK or EU, our legal bases are performing our contract with you, our legitimate interests in running and securing the service and in keeping records of agreements, complying with legal obligations, and consent where we ask for it.
6. Who receives personal data
- Our service providers: Cloudflare (hosting, storage, delivery, security, service logs, domain registration), Whop (platform, sign-in, checkout and payments), Google (Google Fonts), Resend (delivery of the emails stores send their buyers, and receiving the emails buyers send to a store's reply address), and 17TRACK (the tracking number, when a buyer follows a tracking link).
- Services a merchant connects or adds: suppliers (AliExpress, CJdropshipping, Printful, Printify), their own Resend account, email marketing tools (Klaviyo, Mailchimp, Omnisend, Kit, Beehiiv, or a webhook address), Shopify, Shippo for labels, pixels from Google, Meta and TikTok, video hosts, and AI assistants the merchant connects. They act under the merchant's own agreement with them.
- Authorities, when the law requires it or to protect rights and safety.
- A person or business that takes over Ecom OS, who must keep to this policy.
- The Data processing section of our Terms of Service, linked at the end of this page, lists what each one receives.
7. Where data is processed
Ecom OS is run from the United States. Cloudflare serves requests from data centers around the world, so data may be processed outside your country, including in the United States.
8. How long we keep it
- Merchant account data, store data and order data: while you use Ecom OS, so you can see your order history and handle refunds, returns and disputes. Delete my store data in Ecom OS Settings deletes it at once: the storefront, its addresses and images, connections and their keys, the product list, subscribers, messages and customer emails with their attachments, checkout reminders, Notify me requests, email flows and the people waiting in them, email link clicks, reviews and return requests. Order records (what was bought, by whom, the amount and where it shipped) are kept for refunds, disputes and tax records for as long as the law requires, and records of agreements and billing and domain purchase records as below. If you email us instead (support@ecomos.build), we do the same within 30 days, and we do it within 30 days after we end the service, unless the law requires us to keep it.
- Checkout reminder email addresses: about 30 days. Records that a review request was sent: one year. Abuse limit records: up to one hour. Whop name and username: up to one hour.
- Newsletter signups: until the person unsubscribes, the merchant removes them, or the merchant deletes them on the person's request (the dashboard's Delete their data deletes the signup, the messages and customer emails with their attachments, the checkout reminder, Notify me requests, waiting flow emails and email link clicks for one email address; that person's orders, reviews and return requests stay with the order records). Contact messages: up to one year, or until the merchant deletes them. Customer replies: up to one year after the latest email in the conversation, or until the merchant deletes the conversation; their attachments until the merchant deletes the conversation or the person's or the store's data.
- Notify me requests: until the Back in stock email is sent, or until the merchant deletes the person's or the store's data.
- Email link clicks: the clicks themselves for about 8 days, and which emails each person clicked for 31 days, so each person counts once for each email. The email an order is counted for stays with the order record, and the day of a subscriber's latest click stays on their subscriber record until it is deleted. The totals per email hold no personal data.
- Do not email records: when a person unsubscribes, an email to them bounces or they mark one as spam, and after their data is deleted on request, Ecom OS keeps a minimal record that the store must not email that address. It holds a one-way hash of the address, never the address itself, and is kept so that their unsubscribe is honoured.
- Error reports from the dashboard and from stores: up to 30 days. Feedback sent from the dashboard: up to one year. Service logs at Cloudflare: up to 7 days.
- Published versions of a store: the last 30.
- Backups: when we back up the stored data so a mistake can be undone, the copy is kept in private storage on our Cloudflare account and deleted after 30 days.
- Store analytics totals: as long as the store exists. They hold no personal data.
- Records of agreements (terms acceptance, policy page acceptance, publishes with incomplete policies): after your account ends, for as long as we may need them to show what was agreed, normally the time limit for bringing legal claims.
9. Security
We use encrypted connections, access checks on every request, one-way hashes for tokens we only need to compare, and storage that Cloudflare encrypts at rest. No system is perfectly secure. If a breach affects your data, we will tell you and, where the law requires, the authorities, and we report it to Whop as Whop requires.
10. Your rights and choices
- Depending on where you live, you may have the right to know what personal data we hold about you, to see it, correct it, delete it or get a copy of it, to object to or restrict some uses, to withdraw consent, and not to be treated differently for using these rights.
- To review your data, ask for a change or make any other request, email support@ecomos.build from the address on your Whop account, or tell us your Whop business. You can also correct most store and business details yourself in the dashboard. We may need to confirm who you are. We answer within 30 days, or sooner if the law requires.
- Buyers: your request is usually about a store's data, so contact the store. If you contact us, we will pass it to the store and help them answer.
- You may complain to your local data protection authority.
11. California residents
- Ecom OS is operated from California. This policy is posted under the California Online Privacy Protection Act: it lists the personal data we collect (sections 2 and 3), who receives it (section 6), how to review and ask to change it (section 10), how we respond to Do Not Track (section 4), how we tell you about changes (section 13) and its effective date (the version date at the top).
- The California Consumer Privacy Act, as amended by the California Privacy Rights Act, applies to businesses above certain size thresholds, such as annual revenue above the legal threshold or handling the personal data of 100,000 or more California residents or households a year. Ecom OS does not meet those thresholds today. We still honor the requests in section 10 from California residents, and we do not sell or share personal data as that law defines it.
- For buyers of a store, the store's merchant is the business under California law, and Ecom OS is its service provider.
- We do not disclose personal data to third parties for their own direct marketing.
12. Children
Ecom OS is for adults running a business. It is not meant for anyone under 18, and we do not knowingly collect personal data from children under 13. If you believe a child has given us personal data, contact us and we will delete it. Merchants are responsible for whether their stores comply with laws about children.
13. Changes to this policy
We may change this policy. The version date at the top shows when it last changed. When it changes, the dashboard asks you to accept the new version, and the current version is always at this address.
14. Contact
Ecom OS is operated by EcomOS, 7572 Ocean Point Drive, Huntington Beach, California 92648. Email: support@ecomos.build.