In short
- Greenset keeps what it needs to run your account and your ads: your email and name, a scrypt hash of your password, your Whop ad account's details, and the store listings you point it at.
- Card, bank and identity details are typed into Whop's secure frames inside Greenset and go to Whop and the providers Whop uses inside those frames (Stripe for cards, Sumsub for identity checks, Sardine for fraud checks); Greenset never sees them. For the card that pays Greenset's fee, Greenset keeps Whop's ids, a label like “Visa •••• 4242” and its billing address.
- Greenset sells no data and runs no advertising or analytics trackers. It sets five cookies: your sign-in session; for up to a day after you sign up, a check that this browser typed the account's password; for up to 7 days after you open a teammate invitation, that invitation's link; for 30 minutes while you install Greenset's Shopify app signed out, which store you're installing; and, when you open a checkout for a paid plan, a random browser id used to give one free trial per person.
- If you buy Premium or Agency, Whop takes the payment in its checkout inside Greenset. Greenset keeps your plan's status and, so each person gets one free trial, keyed hashes (HMAC-SHA-256) of your email address, Whop account, card, browser, network and store website: the one-trial records hold these hashes, never the values.
- AI images and videos are made by outside providers once Greenset switches each on: Google gets the prompts Greenset writes (and, for video, your product photos and the script); fal.ai gets what a video or creator avatar needs. Greenset may learn from ad results across all accounts to improve Autopilot and Studio; no account ever sees another account's data.
- Competitor tracking reads only what is public about the businesses you name: the ads Meta's Ad Library shows for their Facebook page, and their own website where it allows Greenset in.
- Store credentials, purchase events and webhook signing secrets are encrypted at rest (AES-256-GCM).
- Greenset keeps what it collects. Changing or removing something, or deleting your account (Account settings, once your ad balance is empty), takes it out of the app; Greenset keeps the earlier version or the removed record in its own records.
Greenset, at app.greenset.ai, is run by Greenset LLC, a Wyoming limited liability company. Greenset turns your store into ads, opens the ad account they run through on Whop, and launches them when you say so. This page says what Greenset collects, why, who else receives it, how long it is kept, and how to delete it.
What Greenset collects#
Your email address and name
- From
- You, at sign-up
- Why
- Your account, sign-in, and the emails Greenset must send you
Your password
- From
- You
- Why
- Sign-in. Stored only as a scrypt hash; Greenset can't read it back
The card for Greenset's fee
Whop's ids for the card and a label such as “Visa •••• 4242” (never the card number, which is typed only into Whop's frame); its billing address (name, street, city, state, postal code, country); and each fee charge: amount, sales tax, the card-paid spend it covers, Whop's payment id and result
- From
- Whop, from the card and address you enter in Whop's frame
- Why
- To charge Greenset's fee on ad spend paid by card, for Whop to calculate the sales tax on it, and to show you every charge
Sign-in records
When you last signed in, failed attempts, the Terms version you agreed to and when, and the devices you sign in from: the browser and system (such as “Chrome on macOS”), the first three parts of the network address (never the full address), and when each was first and last used
- From
- Greenset
- Why
- Security, the “new sign-in” email, the sign-in list in Account settings, and a record of your consent
Your Whop ad account
Its ID, status, balance, campaigns and results, and your Facebook page's name
- From
- Whop
- Why
- To show your setup, your balance and how your ads are doing
Your store's listings
Store addresses and their public product listings
- From
- The store you enter
- Why
- To draw ads from your products
Store sign-in credentials
A WordPress application password, a Shopify access token, or the access a store platform (BigCommerce, Wix, Squarespace, Etsy or Amazon) grants when you approve Greenset on that platform's own consent screen
- From
- You, only if you choose to give them or approve a connection
- Why
- To read your products and orders and install the Whop pixel. Encrypted at rest (AES-256-GCM)
What a connected store platform shares
What the access you approved covers: your products, your orders (with the buyer details the platform includes) and your store's settings
- From
- BigCommerce, Wix, Squarespace, Etsy or Amazon, only after you approve the connection there, with your consent
- Why
- To draw ads from your products, credit your ads with the sales they drive, and install the pixel where the platform allows it
Purchase events from your store
Order value, currency, and the buyer's email, phone, name, address, IP and browser
- From
- Your store's order webhooks, only if you connect them
- Why
- To credit your ads with the sales they drive. Encrypted at rest; sent to Whop only when you switch server-side conversions on
Your ads and settings
Ads you generate, drafts, spend limits and settings
- From
- You
- Why
- To run the product
Shopify app installs
The store's myshopify.com address as Shopify signed it, when, whether you were signed in, and what happened; and a hash of the gs_shopify_install cookie's random id
- From
- Shopify, when you install Greenset's Shopify app
- Why
- To finish the install once you sign in
Shopify's privacy requests
Each request as Shopify sent it (the store, and the customer and orders it names), encrypted at rest; how many of Greenset's records it touches; and what Greenset did. Greenset records deletion requests and holds them for review: it keeps what it holds (see “How long data is kept”)
- From
- Shopify, for stores with Greenset's Shopify app
- Why
- To answer a store customer's request for their data or for its deletion, and a store's deletion request
Your plan
Which plan; Whop's ids for the membership, the plan and your Whop user; the plan's status (trial, active, past due, canceled or ended); the current period's start and end; whether it is set to end, and the reason Whop records; on Agency, the number of stores and which client workspaces it covers; a change of plan waiting to start; and each checkout you opened (which plan, whether it had a trial, and when). The card is typed only into Whop's checkout; Greenset never sees it
- From
- Whop, after you buy Premium or Agency in Whop's checkout inside Greenset
- Why
- To give your workspace its plan and its limits, and to email you when the plan changes
One free trial per person
When you open a Premium or Agency checkout, a keyed hash (HMAC-SHA-256, under a secret key only Greenset's server holds) of each of: your email address in a normalized form, your browser id (the gs_dev cookie), your network (the first three parts of the network address), and each store website in the workspace. Once a trial starts, also a hash of your Whop user id and of each saved card's fingerprint, an id Whop gives each card (never the card number). Each record holds the hash, which kind of identity it is, the workspace and plan it was claimed for, and when; never the address, id or card itself
- From
- Greenset, and Whop for the Whop account and the card
- Why
- So each person gets one Premium trial
Teammate invitations
The address invited, who invited them, the role, when it was sent and when it expires (7 days), and whether it was accepted or withdrawn. The link's token is kept only as a SHA-256 hash. For each person, which workspace they last opened
- From
- The workspace owner who invites someone
- Why
- To email the invitation and let only that person join
Plan usage
How many images the workspace made each day and how many seconds of video each month
- From
- Greenset
- Why
- To apply your plan's daily and monthly limits
Businesses you track
The names, websites and Facebook pages you enter, and public information about those businesses, read once a day and when you ask for a check: the ads Meta's Ad Library shows for that Facebook page (their text, dates and where they ran; never their images or spend), and the page you gave and its public product listings, only where the site's robots.txt allows Greenset's reader. Each read is kept, with the changes found in it (new products and offers, price changes, new ads and angles)
- From
- You name them; the rest is public
- Why
- Competitor tracking: to show you what those businesses advertise and sell, and what changed
Profit tracking (Premium)
From the order webhooks: each order's amounts, currency, status, product ids, quantities and Whop's ad click ids from the landing address; never the shopper's name, email, phone, address or IP. Your products' costs (Shopify's product cost, WooCommerce's cost of goods) and the costs you type. The store check reads your store's public home, product and cart pages: their status, timing, size and what they load
- From
- The order webhooks your store already sends Greenset; your store, with the access you gave in Connections; you
- Why
- To show profit by day, campaign, ad group and ad, and to check your store's pages
AI tools you connect
Nothing beyond what the API records: a tool connected with a key reads and changes your workspace exactly as the API does with that key, and each call is in the API log (key, method, path, status, address, time). What the tool sends to its own maker is governed by that maker's terms
- From
- You, with an API key made under Developers
- Why
- So an AI terminal or editor (Claude Code, Codex, Cursor, Warp and others) can read and change your workspace
The email log
Which email Greenset sent you, when, and whether it was delivered. If an email to your address bounces or is reported as spam, Greenset records that and stops sending to the address
- From
- Greenset and its email provider
- Why
- To know an email you need actually arrived
Messages sent to Greenset
Each message exactly as it arrived, encrypted at rest (AES-256-GCM): for store orders this includes the buyer's details listed above
- From
- Whop, your store (if you connect its order webhooks), Shopify (for stores with Greenset's Shopify app) and Greenset's email provider
- Why
- To act on payments, orders and email deliveries, and as Greenset's record of what it received
Your API keys
Each key's name, permissions, expiry, and when and from which IP address it was last used. The key itself is kept only as a SHA-256 hash, plus its prefix and last four characters so you can recognize it
- From
- You
- Why
- So your own software can use Greenset for your workspace
The API call log
Which key, method, path, result, IP address and time of each call (never a request body or a secret)
- From
- Greenset
- Why
- Security, and so you can see what your keys did
Your webhook endpoints
The address, the events you chose and a signing secret (encrypted at rest), and a log of each delivery
- From
- You
- Why
- To send your workspace's events to your own server
Earlier versions and removed records
When anything above is changed or removed (by you, by Greenset, or by deleting your account), the version before it, exactly as it was (encrypted where it was encrypted)
- From
- Greenset
- Why
- So nothing you or Greenset changed or removed is lost
Your Whop account#
When you confirm your email, Greenset asks Whop to open an ad account for you, connected to Greenset's Whop platform and owned by your email address. For an address that is new to Whop, Whop also creates a Whop user for it. Greenset sends Whop your email, a name for the account (your workspace name, your name, or the part of your email before the @), and two internal references (your Greenset workspace and user IDs). From then on Whop processes data about that account under Whop's privacy policy (opens in a new tab), may email you about it directly, and runs your ads on Meta. Greenset reads the account's status, balance, campaigns and results so it can show them to you.
Changing your sign-in email (Account settings) changes where Greenset signs you in and sends its own emails. It does not change the owner email of your Whop ad account: Whop's own notices keep going to the address the ad account was opened with.
Money screens: Whop's secure frames#
Adding funds, saving a card for ad spend and confirming your identity happen in Whop's secure frames, opened inside Greenset's Setup screen; you don't leave Greenset to do them. When you open one, your browser loads Whop's Elements script and frames from cdn.whop.com, and they talk to api.whop.com directly, so Whop receives your IP address and browser details. Whop's frames collect your bank, card and identity (KYC) details directly, under Whop's privacy policy; Greenset never sees or stores them. Inside its frames Whop uses its own providers: Stripe processes card details, Sumsub runs the identity check (a photo of your ID and a selfie; your browser asks before the camera turns on), and Stripe's and Sardine's fraud checks may read your device's motion sensors. Greenset's server only asks Whop for a short-lived pass, limited to your own ad account, for each frame, and Greenset's page is told when a step finishes, for example that a deposit was started or a card was saved. Whop's address field, where you enter the billing address of the card for Greenset's fee, suggests street addresses through Google Places as you type.
Who else receives data#
- Whop: the account Greenset opens for you, your ads and their results, purchase events you choose to send, and what you enter in Whop's frames, straight from your browser. Whop's own providers inside those frames (Stripe, Sumsub and Sardine) receive what each needs, under Whop's privacy policy. If you buy Premium or Agency, Whop also receives your payment in its checkout inside Greenset, with references to your workspace, your Greenset user and the checkout, so Greenset can match the plan to your workspace.
- Google (its Gemini API), once Greenset switches AI images on: the prompts Greenset writes for a picture, built from your product's category and your brand's colors. For images it never receives your product photo: Greenset places the real product itself. Once video is switched on, Google also receives your product photos, the video's prompts, and its script, which Google reads aloud as the voiceover.
- fal.ai, only once video or creator avatars are switched on: your product photos and the prompts for that video, and for a creator video its voiceover.
- Meta (its Ad Library), when you track a business by its Facebook page: that page's id, so Greenset can read the ads Meta shows for it.
- DataForSEO, only once Greenset switches its ad research on (no feature uses it yet): the website addresses looked up, yours and those of businesses you track, to find their public Google ads and search data.
- Resend: sends Greenset's emails, so it receives your email address and each email's content.
- Hostinger: hosts the Greenset server, the greenset.ai website and the greenset.ai mailboxes.
- Your own servers: if you add a webhook endpoint, the events you chose for it are sent to that address.
Greenset does not sell data, runs no advertising or analytics trackers in the app, and uses your store's customer data only to report your own sales to your own ad account.
Learning across accounts#
Greenset may learn from ad results across all accounts, yours included, to improve Autopilot and Studio for every account: patterns such as which angles, formats and budgets work for a kind of product. What it learns is about ads, not people: it carries no account's name, store, customers or ids into another account, and no account ever sees another account's ads, numbers or data.
Cookies and browser storage#
gs_session (cookie)
- Purpose
- Keeps you signed in. Only a hash of it is stored on the server, so signing out, resetting your password or deleting your account ends it; changing your password in Account settings ends it on your other devices.
- Lifetime
- 7 days
gs_signup (cookie)
- Purpose
- Set when you sign up, or sign in before confirming your email, and sent only to Greenset's sign-in pages. It shows that this browser typed the account's password, so confirming your email here signs you in; elsewhere you choose the password again. It holds a keyed hash, never your password or email address.
- Lifetime
- 24 hours, or until you confirm your email in this browser
gs_join (cookie)
- Purpose
- Set when you open a teammate invitation link. It holds that invitation's token, so signing up, confirming your email or signing in brings you back to the invitation; it is removed when you join or when the link turns out not to work.
- Lifetime
- 7 days, or until you join
gs_shopify_install (cookie)
- Purpose
- Set when you install Greenset's Shopify app while signed out, and sent only to Greenset's Shopify install pages. A random id that remembers which store you're installing, so the install carries on once you sign in; Greenset keeps only a hash of it.
- Lifetime
- 30 minutes
gs_dev (cookie)
- Purpose
- A random id for this browser, set when you open a Premium or Agency checkout. It holds nothing else; it lets Greenset give one free trial per person, and Greenset keeps only a hash of it (see “One free trial per person”).
- Lifetime
- 400 days
gs-facebook (local storage)
- Purpose
- Passes the result of a Facebook connection from the connection window back to your Greenset tab.
- Lifetime
- Until your next connection, or until you clear it
gs-connect (local storage)
- Purpose
- Passes the result of a store connection from the store's approval window back to your Greenset tab.
- Lifetime
- Until your next connection, or until you clear it
gs-keys (local storage)
- Purpose
- Remembers whether the number keys 1 to 6 switch screens in the console, which you turn on or off in the account menu. It is set only when you change it.
- Lifetime
- Until you clear it
gs-dev-tab, gs-dev-lang, gs-dev-ai (local storage)
- Purpose
- Remember the Developers screen's last tab, the code-sample language you picked, and the AI coding tool you picked for its setup steps.
- Lifetime
- Until you clear them
Whop's frames may set their own cookies, under Whop's privacy policy, while a money screen is open.
How long data is kept#
- Everything Greenset collects is kept, with no deletion schedule. Changing or removing something, or deleting your account, takes it out of the app; Greenset keeps the earlier version or the removed record in its own records.
- Server access logs (IP address, time, the page requested, the page you came from, and your browser's user-agent): kept. Query strings, which can carry sign-in links, are not logged, for either page.
- Sign-in devices: Account settings lists the 50 most recent for each person; older ones stay in Greenset's records.
- The log of API calls made with your keys, the record of webhook deliveries, and the messages sent to Greenset: kept.
- Database backups: one a day, encrypted before it is stored, so only Greenset can read it. Greenset keeps its backups and does not delete them on a schedule, so a backup made before you deleted something still holds it.
- Money records (deposits, Greenset's fees and charges, with Whop's ids and amounts): kept, as financial records (at least 7 years in any case), including after you delete your account.
- Plan records, the checkouts you opened and the one-trial hashes: kept, including after you delete your account, so one free trial per person still holds.
- Sign-in codes and links: single use; they expire after 24 hours (email confirmation), 24 hours (email change), 1 hour (password reset) or 7 days (the undo link sent to your old address when your sign-in email changes).
Deleting your data#
Removing a store connection takes it out of the app: Greenset stops using its credentials, catalog and purchase events, and keeps them in its own records (the credentials stay encrypted). Deleting your Greenset account (Account → Delete account) takes your profile, sessions and every workspace you own (it closes for everyone in it; workspaces you were invited into stay with their owners), with all of its data, out of the app, so you can no longer sign in and the email address is free to sign up again; Greenset keeps a copy of all of it in its own records. The email log keeps which emails were sent, with your address masked in the log itself. Backups made before the deletion still hold that data (see “How long data is kept”).
If Greenset opened a Whop ad account for you, deleting your Greenset account queues that ad account to be closed at Whop, and Greenset keeps a short record of it: the ad account's ID, your email address in a normalized form (lower case, without any +tag, and for Gmail addresses without dots), and its ads status at Whop. That record lets the account be closed and stops a restricted ad account from being reopened under the same address. Greenset deletes your account only once your ad balance is empty: while the ad account still holds money, or while Greenset can't confirm its balance with Whop, deletion is refused and nothing is deleted. Write to hello@greenset.ai to have the money returned first, or try again later if Whop couldn't be reached. Deletion is also refused while a Premium or Agency plan you pay for still renews: cancel it in Plan first. Whop keeps the records it is required to keep, and the Whop user created for your email stays with Whop: Greenset has no way to delete it, so ask Whop under its privacy policy. You can also write to hello@greenset.ai.
Your rights#
You can ask for a copy of your data, a correction, or deletion by writing to hello@greenset.ai, or by post to Greenset LLC, a Wyoming limited liability company, 1309 Coffeen Avenue, STE 1200, Sheridan, WY 82801. If you are in the EU, UK or California you also have the rights your local law gives you, including the right to complain to your data-protection authority.
Security#
Passwords are hashed with scrypt. After 10 wrong passwords in a row an account is locked for 15 minutes. Store credentials and purchase events are encrypted with AES-256-GCM. Every page is served over HTTPS (plain HTTP is redirected), and the app sets a strict content-security policy that allows frames only from Whop. Each person's workspace can reach only its own Whop ad account.
Changes#
If this policy changes, the date at the top changes; material changes are emailed to you first.