Legal
Privacy Policy
What Plug collects from creators and their customers, what it is used for, and who else sees it.
Version 0.2 · effective 21 October 2026
This document describes what the product does today, not what it is planned to do. Anything material will be announced rather than quietly changed.
01Who this covers
Plug is a platform where creators publish a storefront and sell digital products. Three kinds of people appear in this policy: creators, who hold an account and publish a page; customers, who buy or download something from a creator; and visitors, who open a storefront without buying.
Plug and the creator each hold information about a customer, for different reasons. Plug runs the platform. The creator runs their own business. When you buy something, both of them end up with your email address.
02What Plug collects
From a creator, when they sign up and set up a page: email address, a password (stored only as a hash, never in readable form), the handle they choose, and whatever they add to their storefront — display name, bio, profile photo, product titles and descriptions, prices, cover images, and links.
From a creator who signs in with Google: the email address, name and profile picture Google returns. Plug asks Google for nothing else, and cannot see your Google password.
From a customer, at checkout: the email address you enter — it is what the product is delivered to and what proves the purchase is yours later. For a paid purchase, Stripe also collects your card and billing address on its own payment page; Plug keeps the country, state or region, and postal code with the order, for the creator's tax records.
From anyone who makes an account: a record that they agreed to the Terms of Service and this policy and confirmed they are 18 or older, with the version and the time.
From a paid checkout, Stripe tells Plug the outcome: whether the payment went through, the amount, and the payment's reference, which Plug keeps with the order, together with the time you agreed to the creator's refund policy. From a creator who connects a payout account, Plug keeps only the Stripe account's ID and whether it can take payments and receive payouts.
From downloads: how many times each purchased file has been downloaded, and when. If you dispute a charge with your bank, Plug gives that record and the order to Stripe so the creator can answer the dispute.
From files a creator uploads: the file itself, its name and its size. Plug measures the size to apply the storage allowance on the creator's plan.
From visitors: a count of how many times a storefront has been opened. It is a single number per storefront. It is not tied to you, and Plug does not record who opened a page.
03What Plug does not collect
Plug never receives your card or bank details. Card details go into Stripe's own payment form, and a creator's identity and bank details go to Stripe when they connect a payout account.
There is no analytics service, no tag manager, no advertising pixel and no third-party script anywhere in Plug. Nobody is tracking you across other websites, because there is nothing in the page that could.
The only cookies are the ones that keep a creator signed in. There is no advertising cookie, so there is no cookie banner — there is nothing to consent to.
Plug does not sell personal information, does not share it for advertising, and does not build profiles or make automated decisions about anyone.
Plug does not read the contents of the files a creator uploads. They are stored and delivered, not inspected.
04What it is used for
- Running your account and your storefront.
- Delivering what a customer bought, and letting them get it again later.
- Sending transactional email — a download link, a link back to a library. Plug does not send marketing email. A creator gets one invitation to give feedback after publishing their page for the first time, and answers sent through the feedback form go to Plug's support inbox.
- Keeping the service safe. Plug's servers use your IP address briefly to slow down abuse, such as repeated checkout or sign-in attempts, and do not store it. The hosting providers keep standard request logs.
- Showing a creator how their own storefront and products are doing.
- Keeping the service working and looking into problems when something breaks.
05What the creator you bought from can see
The creator can see the email address you used at checkout, what you bought, when, and how many times you have downloaded it. For a paid purchase they also see, in their own Stripe dashboard, what Stripe shows any seller: your name, billing address, and card brand and last four digits.
That is how selling works — they are the seller and you are their customer. They can also export that list. What they then do with your address is their responsibility under their own obligations, not Plug's, and Plug does not control it.
Creators cannot see each other's customers, and no creator can see anything about a purchase made from someone else.
06Who else handles it
Plug uses a small number of services to run. Each one only receives what it needs to do its job.
- Supabase — the database, sign-in, and image storage. Holds accounts, storefronts, orders and profile images.
- Cloudflare R2 — storage for the files creators sell. Files are private and are only handed out through a signed link that expires in about a minute.
- Resend — sends transactional email. Receives the recipient address and the message.
- Vercel — hosts and serves the site.
- Stripe — processes payments and creator payouts, bills Elite and Pro subscriptions, and verifies the identity of creators who connect a payout account. Stripe handles that information under its own privacy policy.
- Google — only if a creator chooses to sign in with Google.
These providers process data outside your country in some cases, including in the United States. Plug does not disclose personal information to anyone else, except where the law requires it.
07How long it is kept, and deleting it
Account and storefront information is kept while the account exists. Purchase records are kept while they are needed to prove an entitlement — that is what lets a customer come back for a file months later.
You can ask for your information to be deleted, or for a copy of it, by writing to support@plugapp.co. Plug will act on it. This is handled by a person rather than a button in the product, so allow a few days.
One limit worth stating plainly: deleting your Plug account does not reach the copy a creator already exported of their own customer list. For that, ask the creator.
08Security
Passwords are hashed by the authentication provider and are never visible to Plug. Access to every row of data is enforced by the database itself rather than by the app asking nicely, so a creator can only read their own records.
Files for sale are never public. They are held in private storage and released only through a short-lived signed link, issued after the database confirms the purchase.
No system is perfect, and Plug is a new one. If something looks wrong, write to support@plugapp.co.
09Children
Plug is not for children. Accounts are for people aged 18 or over, and Plug does not knowingly collect information from anyone under 13. If you believe a child has given Plug information, write to support@plugapp.co and it will be removed.
10Changes
This policy will change as the product does. When something material changes, the effective date at the top changes and account holders are told. It will not be altered quietly.
11Contact
Write to support@plugapp.co with anything about this policy, about your information, or about a creator's use of your information.
Plug is operated at plugapp.co.
