Privacy policy

What Payly collects, why, who can see it and the choices you have. Payly is run by WPPlugin LLC. Last updated October 20, 2026.

The short version

We only ask for information we need to run Payly.
We never sell your information or your customers' information, and we never use it for ads or ad targeting.
Payly puts no ads or advertising trackers on payly.org or on your store.
Card numbers go straight to PayPal or Stripe and never reach our servers.
Stores count visits without cookies, and skip visitors whose browser asks not to be tracked.

1. Who we are and who this covers

Payly (payly.org) is run by WPPlugin LLC of Boulder, Colorado, USA ("we" or "us"). This policy covers:

Visitors to payly.org.
Merchants: people who have a Payly account and run stores, including their team members.
Shoppers: people who visit or buy from a store built on Payly.

For merchants' account information, we decide how it is used. For shoppers' information, Payly mostly acts for the store's owner, who decides what their store collects. Payly decides for its own uses described in this policy: the shared sign-in record, security and fraud checks, and statistics across stores. Each store should have its own privacy policy, so shoppers with questions about their information should contact the store first.

2. Visitors to payly.org

payly.org runs no ads or advertising trackers. It counts visits to its own pages the same way stores do (see How stores count visits): the page, the website you came from, an approximate location, how long the page was open and a random ID for the open browser tab. If you arrive through a link with campaign tags (such as utm_source or utm_campaign), it also records those tags for the rest of that visit, so we can see which ad, email or post brought you. It uses no cookies, and it does not run when your browser sends a Do Not Track or Global Privacy Control signal. We use these figures to see how payly.org is used and to improve it.

Like any website, our servers receive basic technical information with each request, such as your IP address, browser type and the page you asked for. Our hosting provider, Cloudflare, uses it to deliver pages and protect the site. Our server logs keep some of it for a short time, and can also record an email address, for example when someone asks for a password reset or a store sign-in link.

Your language and theme choices, and whether you dismissed the cookie notice, are saved in your own browser. See Cookies and browser storage.

If you write to us through the contact form or by email, we keep your name, email address, message and the email's headers, so we can reply and help with later questions.

3. Information about merchants

Your account. Your email address, your name if you give it, your language and theme, and when you signed up and last signed in. Your password is handled by our sign-in provider, Supabase, and stored only in hashed form. Supabase also records the IP address and browser used to sign in, for security. If you sign in with Google or Facebook, they give us your name, email address and profile picture link.
Your stores. What you build and set up: pages, designs, products, prices, settings, and your team members' names, email addresses and roles. Images and downloadable files are stored in your own Cloudflare account, not by Payly. Each design backup there records the email address of the person who made it.
Your Cloudflare connection. Your Cloudflare account ID and name, the IDs of what Payly created there, and the access tokens Payly uses, which we store encrypted.
Your payment connections. Your PayPal or Stripe account ID, the account's name and email address, and whether it is in live or test mode. We never receive your PayPal or Stripe password, and we do not store their API keys. To start the PayPal sign-up form, we send PayPal the email address you use for Payly.
Support. Messages you send us, our replies, and notes our team adds. A request sent from the dashboard is linked to your account.

4. Information about shoppers

When someone visits or buys from a store built on Payly, Payly stores this for the store's owner:

Orders. Name, email address, shipping address, the phone number and order note if the store asks for them, the items bought, prices, discounts, tax, shipping, how it was paid and its status. Also an approximate location (country, region and city) worked out from the IP address at checkout. The IP address itself is not stored.
Customer accounts. Payly creates an account with the shopper's name and email address when an order is paid or a subscription is started. Shoppers sign in to stores with a link or code sent by email, not a password. Each store has its own customer list, but Payly's sign-in system keeps one record for each email address. It is shared by every Payly store where that address has an account, and by a Payly merchant account with the same address.
Subscriptions. The plan, status, renewal dates and shipping address. PayPal or Stripe handles the billing.
Reviews. The rating, title and text, shown publicly on the store with the shopper's name (or the part of their email address before the @ if there is no name) and a "verified purchase" label if they bought the product.
Contact forms. What the visitor writes, the page it was sent from, their browser and device details (user agent) and a hash of their IP address. Their IP address is also checked with Cloudflare Turnstile to block spam.
Checkouts, if a store turned on cart recovery: the email address, name and cart from each checkout, saved when the shopper presses pay and kept even after the order is paid.
Visit statistics, described in the next section.

Download links are sent only to buyers of paid orders, by email and on their account page. Each link works for 7 days, even if the order is later refunded. Anyone with the link to an order's page can open it, so shoppers should keep that link private.

5. How stores count visits

Each store page includes a small visit counter so the store's owner can see how their store is doing. For each page view it records:

The page's address, without anything after a "?".
The website the visitor came from (its name only, not the full address).
An approximate location (country, region and city) worked out from the IP address. The IP address is not stored.
How long the page was open.
A random ID that lasts only while that browser tab is open, so pages seen in one visit can be grouped.

The counter uses no cookies and does not link visits to a name, email address or account. It does not run at all when the visitor's browser sends a Do Not Track or Global Privacy Control signal. Payly keeps these records for as long as the store exists. Our team can see visit statistics across all stores, and for each store, which we use to run and improve Payly.

6. Cookies and browser storage

Cookies and browser storage are small pieces of information a website saves in your browser. Payly uses them only to keep you signed in, remember your settings, and run the cart and checkout. We do not use advertising cookies. This is what Payly saves today.

On payly.org

Your sign-in is saved in your browser's storage, not in a cookie, until you sign out.
Google sign-in uses one cookie (__Host-payly_google) while you sign in with Google. It is deleted within 10 minutes.
Your settings, such as language and theme, and the cart in our example stores, are saved in your browser's storage until you clear them.
Visit counter: a random ID for the open browser tab, and the campaign tags of the link you arrived by if it had any, deleted when the tab closes. It is not a cookie.

On stores built with Payly

Shopper sign-in: a cookie (payly_customer) that keeps a shopper signed in to their account at that store for up to a year, or until they sign out.
Order receipt: a cookie (payly_receipt) that lets the browser that placed an order reopen its receipt for 2 days.
Cart: the cart, and a note while a payment is in progress, saved in the browser's storage until the order is placed or the cart is emptied.
Visit counter: a random ID for the open browser tab, deleted when the tab closes. It is not a cookie.

Other companies

Some store pages load tools from other companies, which may set their own cookies under their own privacy policies. Checkout loads PayPal's and Stripe's payment tools, which may use cookies for security and fraud prevention. Contact forms use Cloudflare Turnstile to block spam. Videos, maps, fonts and some template photos can load from YouTube, Google Maps, Google Fonts and Unsplash. Some Payly dashboard pages also load fonts from Google Fonts. Payly's sign-up, sign-in and password pages also use Cloudflare Turnstile to block bots.

In the future

We may add other cookies or similar tools. If we do, we will update this page first.

You can block or delete cookies and browser storage in your browser's settings, but signing in and the cart will then stop working.

7. How we use information

To run Payly: your account, your stores, checkout, customer accounts, emails and reports.
To give you support.
To keep Payly secure, and to prevent fraud, spam and abuse.
To understand and improve Payly, using statistics across stores such as visits, orders and sales totals.
To send merchants news about Payly by email (see Emails).
To meet legal obligations, and to protect our rights and the rights of others.

We may publish statistics that do not identify anyone, such as how many stores use Payly. We may also use support questions, with personal details removed, to improve our help articles.

We do not sell personal information, share it for targeted advertising, or use it to build profiles of people. We make no automated decisions about anyone that have legal or similar effects.

If you are in the European Union or the United Kingdom, our legal bases are: providing the service you asked for, our legitimate interests in running, securing and improving Payly, your consent where the law requires it, and our legal obligations.

8. Emails

Service emails, such as the welcome email, new orders, form messages, password resets, usage warnings, payment disputes, team invitations and replies to support requests.
Emails to shoppers for a store, such as receipts, sign-in links, and shipping, refund and subscription notices. They come from Payly's address under the store's name, and replies to order and subscription emails go to the store owner's Payly sign-in email address.
News about Payly. When you create a Payly account, you agree to receive marketing emails from us. We add your name and email address to our newsletter list, which runs on our own server. Every newsletter has an unsubscribe link, and you can also ask us to remove you. We never add shoppers because they bought from a store.
Whether our emails are read. Our welcome email, our reminders about building your store and the weekly store summary include a tiny image and links that pass through payly.org. They tell us whether the email was opened, whether a link was clicked and whether you unsubscribed from it, so we can see which emails help. Emails to shoppers are never tracked.

Our sign-in provider, Supabase, sends the emails that confirm a new account or a new email address.

We share personal information only in these cases:

With the store. A shopper's information goes to the store they bought from or contacted, and to that store's team.
With a store's shoppers. Emails to shoppers about orders and subscriptions show the store owner's Payly sign-in email address as the reply address.
Publicly, when a shopper posts a review, as described above.
With PayPal and Stripe, to take payments. They receive what each payment needs, such as the items, the amounts, and the buyer's email address or shipping address. They handle it under their own privacy policies.
Through WPPlugin LLC's payment servers. Payment requests and payment notifications pass through our servers at wpplugin.org on their way to and from PayPal and Stripe. These servers may keep logs to troubleshoot technical problems with payments, which can include the buyer's email address, name, shipping address and the items bought. They also count payment totals for our partnerships, using one-way coded IDs instead of names or account numbers.
With service providers that run parts of Payly for us:
- Supabase: our database and sign-in system.
- Cloudflare: hosting for payly.org, receiving email sent to payly.org, server logs, and Turnstile spam protection. Stores run in their owner's own Cloudflare account.
- Amazon Web Services (Amazon SES): sending email.
- Google: sign-in with Google, if you choose it, and fonts on some pages.
- Meta: sign-in with Facebook, if you choose it.
With the companies whose content loads on store pages, listed in Cookies and browser storage. Visitors' browsers contact them directly.
For legal reasons. When a law, subpoena, court order or government request requires it, or when we believe in good faith that it is needed to protect the rights, property or safety of WPPlugin LLC, our users or the public.
If Payly changes hands. If WPPlugin LLC or Payly is acquired, merged, sold or goes through bankruptcy, information may be transferred to the new owner, who may keep using it as this policy describes.
With your permission.

10. Who at Payly can see information

Only people who work on Payly and need it can see personal information, and they have agreed to keep it confidential. Our support team can see merchants' account details, stores, team members, store totals, visit statistics for each store and support messages. To help a merchant, our support team can also sign in to that merchant's dashboard. We keep a log of who signed in, when and why. While signed in, they cannot move money, change who has access, or change the merchant's sign-in details. For anyone who writes to us, they can see the name and sign-in dates on that person's Payly sign-in record. They can also see shoppers' email addresses on orders our payment checks flag. People who maintain Payly's systems can reach the database directly when needed to fix problems.

11. How long we keep information

Merchant accounts: while the account is open. When an account is closed, we delete it and remove it from our newsletter list, except for the records described below and anything the law requires us to keep.
Stores: while the store exists. Store owners can delete orders, reviews and form messages at any time. Deleting a store deletes its pages, products, orders, customers, subscription records, reviews, form messages and visit statistics. If Payly is still connected to the store's Cloudflare account, it also removes the store, its images and files from there.
Shoppers' sign-in records: Payly's sign-in record for an email address stays after a store is deleted, even if no other store uses it. Contact us to have it deleted. This also removes that person's customer accounts, subscription records and reviews at every Payly store.
Support messages: kept so we can help with later questions. Ask us and we will delete them where we can.
Payment notifications: we keep each notification's ID, type and status permanently, so a payment is never recorded twice. We keep a notification's full details only when it fails to process, and delete them after 90 days.
Shoppers' sign-in links and codes: stop working after 15 minutes and work only once. The record of each request, which holds the email address, is kept while the store exists.
payly.org server logs: kept for a short time.
Payment server logs at wpplugin.org: kept while we need them to troubleshoot technical problems with payments.
Newsletter list: until you unsubscribe or ask us to remove you.

Deleted information can stay in backups for a limited time before they expire.

12. Your choices and rights

Merchants can change their name, email address, password and language in Settings, export products and reports, and delete stores. To get a copy of your information, correct it, or close your account, contact us.
Shoppers should contact the store first. A store can delete your orders, reviews and messages. To delete your customer account or sign-in record, you or the store can contact us.

Depending on where you live, such as the European Union, the United Kingdom or California, you may have rights over your personal information. These include the right to access, correct, delete or get a copy of it, to object to or limit how it is used, to withdraw consent you gave, and to complain to your data protection authority. You can also ask someone you authorize to make a request for you. We will not treat you differently for using these rights. We reply to requests within 30 days, and we may need to confirm your identity first.

13. Security

Payly pages and stores are served over encrypted connections (HTTPS). Cloudflare access tokens are stored encrypted, shoppers' sign-in links and codes are stored only in hashed form, shopper sign-ins are digitally signed, and access to our database is restricted.

No system is perfectly secure. If a breach affects your personal information, we will tell you as the law requires.

14. Where information is stored

WPPlugin LLC is based in the United States. Our database is hosted by Supabase, our email is sent from Amazon's data centers in the United States, and Cloudflare serves pages from data centers around the world. Your information may be processed in the United States and in other countries outside your own. When we transfer personal information out of the European Union, the United Kingdom or Switzerland, we rely on safeguards the law allows, such as standard contractual clauses.

15. Children

Payly accounts are for adults: merchants must be at least 18. Payly is not meant for children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has given us personal information, contact us and we will delete it.

16. Changes to this policy

We may change this policy from time to time. Changes take effect when we post them on this page, and the date at the top will change. If a change is significant, we will make a reasonable effort to tell you before it takes effect, for example by email or a notice on payly.org.

17. Contact

Privacy questions and requests: use our contact form or email support@payly.org.

WPPlugin LLC
Boulder, Colorado, USA