Privacy Policy
Last updated: October 9, 2026
You sign in with Google, so PressaGen never holds a password of yours.
We store your pages, your account details and the email addresses visitors leave on your pages. We count page views per day, with no visitor profiles and no advertising cookies.
You can delete any page, or your whole account, from your dashboard. Whatever you delete is gone from our backups within about three months.
The plain-language version: Your data01. What this covers
This describes what PressaGen collects from the people who build pages here and from the people who visit those pages; where something is held by an outside company, it says so by name.
PressaGen is run independently by one person and is not yet registered as a company. "We" and "us" in this policy mean that person. For any request about your personal data, write to us from the contact page.
A page owner may add their own tracking codes to their page. Those codes belong to the owner, send data straight to whoever provides them, and are outside this policy. The owner is responsible for disclosing them.
02. What we collect
- The email address, name and profile picture address Google gives us when you choose to sign in, the account identifier Google uses for you, and the fact that you signed in with Google. PressaGen has no password of its own.
- If you sign up through one of our links that carries a source tag, such as ph or hn, that tag is kept with your account so we can tell which links bring people. Nothing else about how you arrived is kept.
- Which plan your account is on, its status and renewal date, and the customer and subscription numbers Lemon Squeezy gives us.
- Card and payment details are held by Lemon Squeezy, who sell the Pro plan as the merchant of record. They never reach us.
- Your name, email address, the category you chose, the page address the message is about, the subject and the message itself.
- A ticket sent while you are signed in is linked to your account so we can check it faster; sign out first to send it another way.
- Diagnostics about the device that sent it: browser, screen size, time zone and the page you came from, together with the country the request came from and its address, stored with part of it masked.
- All of that is sent to us by email (through Cloudflare Email Routing) so that we see it and can reply. That notification is the only mail this creates; none of it is sent to you.
- A bot check from Cloudflare Turnstile runs before the message is sent.
- The email address, which page it was left on, and when.
- A bot check from Cloudflare Turnstile runs before a sign-up is accepted.
- A number per page per day. No addresses, no device information, nothing that identifies a visitor.
- An irreversible hash of the address a request came from, counted against a limit within a window of one minute to one hour, then it expires. The address itself is not stored.
- Counts tied to your account, such as how many images you uploaded today, counted against a limit within a window of up to one day, then they expire.
- When you change a page's address or delete the page, the old address is kept for 30 days: the address itself, the page it belonged to, your account id and when the hold ends. During that time no one else can take it, and if you changed the address, your old links lead to the new one while the page is published. After 30 days the address is free again; the record is deleted the next time anyone looks the address up, or when you delete your account.
- The files themselves, and which page they belong to.
- A record of each upload: where the file is stored, your account, the page it was uploaded for, its size, its type and when. Replacing a picture that none of your pages still shows, deleting the page or deleting your account deletes the file and its record together.
- Changes you make while trying out a template, the card you last copied, and interface preferences such as language. These stay in your browser and are never sent to us.
- The domain, your account id, the verification code we give you to add to the domain's DNS, and when you proved the domain, connected it and stopped using it.
- This record decides who may connect the domain next: another account must first prove it controls the domain, and the account that held it last may connect it again without that proof for 30 days after losing it, or at any time if it has proved the domain through DNS.
03. Why we use it
We use what we collect for these purposes only.
- Signing you in and keeping your account apart from everyone else's.
- Storing your pages and showing the published ones to visitors.
- Keeping each account within its plan's limits.
- Knowing which plan you are on, from what Lemon Squeezy tells us when you buy, renew or cancel.
- Reading and answering the messages you send us.
- Keeping bots and abuse out.
- Counting visits per page per day, for your dashboard and for us.
- Seeing which links bring people to sign up, and how many pages are still in use, in totals for the person who runs PressaGen.
- Finding and fixing errors.
- Sell personal data, or share it for advertising.
- Build profiles of you or your visitors.
- Use your content or your visitors' data to train AI models.
- Send you marketing email. The service sends account holders no email of its own; receipts and billing messages come from Lemon Squeezy, and if we need to reach you personally, we write to the email address of your Google account.
04. Automated decisions and AI
We use no AI to read or process your pages, your images or your visitors' data.
Some things happen automatically: your plan is set from what Lemon Squeezy reports, and requests that go over a limit are refused. The automatic checks are the bot check on the contact form and on newsletter sign-ups, the request limits, and the checks on uploaded images. If one stops you by mistake, wait a little and try again.
Suspending a page is always a decision made by a person.
05. Your Google account data
- Your email address, your name, the address of your profile picture and the identifier Google uses for your account.
- To sign you in and tell your account from every other one, to fill in your email address on the payment page when you upgrade to Pro, and to write to you when we need to reach you personally, for example about a problem with your data. No page on PressaGen shows your name or picture; your email address is shown only to you, while you are signed in.
- Only the services listed under "Who else is involved", as far as running the site needs. We do not sell it, and we do not use it for advertising.
- Delete your account from your dashboard. Everything stored from your Google account goes with it.
06. Where it is kept
Your pages, your account details, your pages' sign-ups, the messages you send us, visit counts and the images you upload are kept in Cloudflare's database and storage in the Asia-Pacific region and sent out through Cloudflare's global network, so a request may be handled in a country other than yours. Sign-in sessions are kept on Cloudflare's network too.
Payment data is held by Lemon Squeezy, on their own systems. Google and Lemon Squeezy keep what they hold in their own locations, under their own policies.
Backups are kept on an encrypted device of the person who runs PressaGen and in private storage at Cloudflare in the Asia-Pacific region, each for up to about three months.
07. How we protect it
- Every page and request travels over an encrypted connection (HTTPS), and browsers are told to use nothing else.
- You sign in with Google, so there is no PressaGen password to steal. A sign-in lasts 7 days, and Sign out everywhere on your dashboard ends it on every device at once.
- We do not store the address a request comes from: abuse limits keep only an irreversible hash of it, and the contact form keeps it with its last part masked. The bot check passes it to Cloudflare, which uses it to tell people from bots.
- Photos uploaded from October 7, 2026 on have their location and camera details removed before they are saved. To remove them from an older photo, upload it again.
- Images are stored at a public web address as soon as you upload them, even while your page is a draft. The address is long and random and does not contain your account's identity, so it cannot be guessed, but anyone who has it can open the image. Draft pages themselves are visible only to you.
- The account that runs PressaGen at Cloudflare is protected by two-step verification.
- No system is perfectly safe, and we cannot promise that nothing will ever go wrong.
- If personal data is leaked, lost or seen by someone who should not have it, we find out what happened and stop it.
- We tell the people affected as soon as we can and as the law requires, by email to the address of their Google account: what happened, what data was involved and what we are doing about it.
09. Who else is involved
- Google — signing in. We receive what is listed above and nothing else.
- Cloudflare — hosting, the database, storage and the network in front of them.
- Cloudflare Web Analytics — counts visits to every page served here, including pages people publish and their custom domains: page views, the referring site, country, device type and load speed. It sets no cookie and does not identify anyone; Cloudflare holds the data.
- Cloudflare Turnstile — a check that tells people from bots, used on the contact form and on a page's newsletter sign-up. When it runs, your browser loads it from Cloudflare; to confirm the result, we send Cloudflare the outcome of the check with the address the request came from.
- Lemon Squeezy — payment and tax for the Pro plan, as the merchant of record.
- YouTube, Spotify, Google Maps and similar — page owners can place these players and maps on their pages, and template demo pages include them. They load under each company's own policy; PressaGen receives none of that data.
- A court or public authority — only when the law requires it, after we check that the request is valid. Where the law allows, we tell the person concerned first.
- Whoever must act to prevent harm — only when it is needed to protect a person from serious harm, or to stop fraud or abuse of the service.
- A new owner — only if PressaGen becomes a registered company or passes to someone else. The data then moves with the service, under this policy; we will say so on this page and on the pricing page at least 30 days before, and you can delete your account before it happens.
Tracking codes a page owner adds to their own page are the owner's, not ours; we do not read what those services collect.
10. How long anything is kept
- A sign-in session: 7 days, or until you sign out, whichever comes first.
- Messages sent through the contact form: we clear old ones at least once a quarter, so a message is kept for up to about 15 months after it was sent, and in our backups for up to about three months after that.
- The hashes that keep abuse out: from one minute up to one hour. Counts tied to your account, such as today's uploads: up to one day.
- Each page keeps its last 10 published versions and one draft; they are deleted with the page.
- Delete a page and its images, subscribers, form entries and visit counts go with it.
- Records left by an older message form are kept until they are cleared; that form no longer collects anything new.
- Delete your account and every page you own goes through that same deletion, then the account itself. Messages you sent us through the contact form are kept as our record of the conversation, and whatever Lemon Squeezy holds about a customer is kept under their policy. Images you uploaded and their records are deleted with your pages and your account. Custom domain records are kept after you remove a domain and after you delete your account, because they decide who may connect that domain next; 30 days after you lose a domain, your record no longer lets you connect it again without proving it, unless you had already proved it through DNS.
- Backups: we copy the whole database once a week and keep each copy for up to about three months, and the database can also be rolled back to any moment in the last 30 days. So something you delete can stay in these copies for up to about three months before it is gone for good. We use them only to recover from our own mistakes, and we do not restore an account you deleted; if we ever roll the whole database back, something you deleted may briefly come back, and we delete it again.
- Images you delete: copies already held by Cloudflare's network or by a visitor's browser may still be shown to anyone with the image's address for up to a year.
- Request logs: we keep none. Cloudflare keeps short-lived technical records under its own policy.
11. What you can do
You can do the first two yourself, at any time, without asking us:
- Delete any page, from your dashboard.
- Delete your whole account, from your dashboard. If a Pro subscription is set to renew, cancel it first with Manage subscription.
- Ask what we hold about you, ask for it to be corrected, or ask us to stop using it — write to us from the contact page.
- Ask for a copy of your data: export your newsletter sign-ups yourself at any time, and for the rest write to us from the contact page. We send your pages as JSON files and lists as CSV files.
- Complain to the authority in charge of Taiwan's Personal Data Protection Act.
- Asking us for any of this will not change how we treat your account.
We answer requests within the periods the Personal Data Protection Act sets: fifteen days for a request to see your data, thirty days for a correction or a deletion. Either may be extended once, and we will tell you if it is.
12. Children
PressaGen is not meant for children: you must be at least 18 years old, and an adult under the law where you live, to create an account.
If we learn that an account belongs to someone younger, we may suspend its pages. Pages built here should not be aimed at collecting data from children.
13. Changes to this policy
When this policy changes, the date at the top changes too. A change that matters, such as a new kind of data or a new service that receives it, is marked on this page and on the pricing page at least 30 days before it takes effect.
We will not use data collected under an earlier version of this policy in a new way without telling you first.