Privacy policy
Effective 12 October 2026
In force from 12 October 2026. Last revised 12 October 2026.
Two roles
PagesPrinter handles personal data in two different roles, and this policy covers both.
- As controller, Wonop ApS ("we") decides how to use the personal data of the people who use PagesPrinter itself: people who sign up, belong to a team, use the dashboard, the API or the MCP server, write to support or send us a report. Most of this policy is about that data.
- As processor, we handle the personal data of the visitors of the sites we host (people who fill in a form, sign up, sign in as a member, buy something or activate a licence key) on behalf of the site's owner. The site's owner is the controller of that data and decides what is collected and why. Their privacy page, linked from their site, explains it. We process it only on their instructions, under our data processing agreement. What we do for site owners below describes that processing so visitors can see how it works.
Our contact details: Wonop ApS, Klokagervej 26, 9800 Hjørring, Denmark, privacy@pagesprinter.com. Data protection officer: none is appointed; write to privacy@pagesprinter.com.
What we collect about you
Account. Your email address, which is also your sign-in name, the name you give, when your address was confirmed, and any change of address you ask for.
Sign-in. When you sign in we email you a one-time code. We store only a hash of the code, which expires after 10 minutes. While you are signed in, a session record keeps you signed in on that browser.
Teams. The teams you belong to, your role in each, who invited you, and invitations you send (the invitee's email address and a hashed token).
API keys and agents. Each key's name, scopes, when it was last used and who revoked it. We store only a hash of the key itself. When an AI agent connects through MCP we record the name the agent's client gives, the last tool it used and how many calls it made each day.
Activity. What was changed in your team's sites, by whom, through which channel (dashboard, API or MCP) and with which key, and a log of team events such as invitations and role changes. While you edit, we note who is looking at or writing a page so that teammates don't overwrite each other.
Your sites. The files you upload, site settings, releases, domains, brand settings, and the content you write in the apps. If you fill in the owner details for your site's privacy page or terms of sale, we store the name, postal address, sender name and reply-to address you enter, and show them on those pages.
Selling. When you connect Stripe, the ID of your Stripe account, its country and its public business name. We don't receive or store your bank details or Stripe password. We don't keep a Stripe access token for your account.
Plan billing. If you pay for a plan, Stripe processes your payment details. We receive your Stripe customer ID, your plan and the state of your subscription, and the billing details you give for invoices. We never see your full card number.
Support and reports. What you write to us and our replies. If you report a site, the address you report, what you tell us and, if you give it, your email address.
Mail we send you. A record of each sign-in code or notification we send: the address, the kind of message and whether it was delivered.
Technical data. To serve and protect PagesPrinter, our infrastructure and our network provider process your IP address, browser type and the addresses you request. We use IP addresses for rate limits, which are held in memory for minutes. Server access logs are kept for 30 days. We don't use analytics, advertising or tracking tools on pagesprinter.com or in the dashboard.
Why we use it, and on what legal basis
| Purpose | Data | Legal basis (GDPR Art. 6) |
|---|---|---|
| Creating your account, signing you in, running your teams and sites | Account, sign-in, teams, keys, sites, selling | Performance of our contract with you (Art. 6(1)(b)) |
| Showing your team who changed what, and letting you undo it | Activity, presence | Performance of contract; our legitimate interest in a reliable, accountable service (Art. 6(1)(f)) |
| Sending sign-in codes, security notices and service messages | Account, mail records | Performance of contract |
| Billing for plans and keeping accounting records | Plan billing | Performance of contract; legal obligation (Art. 6(1)(c)) |
| Keeping PagesPrinter secure, preventing abuse, handling reports and takedowns | Technical data, activity, reports | Legitimate interest in security and in keeping illegal content off the service; legal obligations under the Digital Services Act |
| Answering support requests | Support | Performance of contract; legitimate interest |
| Telling you about changes to the service or these documents | Account | Performance of contract; legitimate interest |
We don't sell personal data, we don't use it for advertising, and we don't make decisions about you based solely on automated processing that have legal or similarly significant effects. Our automated safety checks (links checked against Google Web Risk, malware scanning of uploads, pausing mail with high bounce rates) act on content and mail, and a person reviews any takedown made after a report.
Who receives it
We use the service providers listed on our sub-processors page to host and run PagesPrinter. The main ones are Scaleway (hosting, database, file storage, queues and email, in the Netherlands), Cloudflare (network, TLS certificates and protection for previews and connected domains) and Stripe (payments). Each of them may use the data only to provide their service to us.
We also share personal data:
- with your team: the people in your team see your name, email address, role and what you changed;
- with a site's visitors: if you fill in the owner details for your site's privacy page or terms of sale, they are published on your site;
- with authorities, when the law requires it, or to protect the rights and safety of people or of PagesPrinter;
- with a buyer of our business, if PagesPrinter is sold, under the same commitments as this policy.
Transfers outside the EEA
Our hosting, database, storage and mail run in the European Union. Cloudflare and Google are based in the United States and Cloudflare's network is global, so some data, such as IP addresses and requested addresses, may be processed outside the European Economic Area. Where that happens we rely on the EU-US Data Privacy Framework where the provider is certified, or on the European Commission's standard contractual clauses, with the additional measures the provider offers.
How long we keep it
| Data | How long |
|---|---|
| Account, teams, keys and sites | While your account exists. Deleted when you delete your account, as described in the terms |
| Sign-in codes | Expire after 10 minutes; the expired code's ciphertext is removed within a minute |
| Sessions | Until you sign out or after 365 days without use |
| Site releases | The newest 10 releases of each site |
| Activity and team events | While the site or team exists [retention period after deletion to be confirmed] |
| Records of mail we send | The address is removed from site mail records after 30 days; other records [retention to be confirmed] |
| Plan billing and invoices | As long as accounting law requires, [usually 5 years] |
| Reports and takedowns | [Retention to be confirmed], so that we can handle appeals and repeated breaches |
| Server access logs | 30 days |
Your rights
You can ask us for access to your personal data, to correct it, to delete it, to restrict its use, or for a copy in a portable format. Where we rely on legitimate interests you can object. Most account data you can see and change in the dashboard yourself.
Write to privacy@pagesprinter.com. We answer within one month. If you are a visitor of a site hosted on PagesPrinter, ask the site's owner first, since they control your data; we pass on requests we receive and help the owner answer them.
You can also complain to a data protection authority, in particular where you live or work. Our lead authority is Datatilsynet (Denmark).
What we do for site owners
This part describes the processing we carry out for site owners, as their processor. The site's owner decides what their site collects; their privacy page is the first place to look.
- Form answers and sign-ups. The answers given, the email address, the page the form was on and spam signals. To limit abuse we keep a code derived from the visitor's IP address with a key that changes every day, never the address itself, and remove it after 7 days. Unfinished answers are deleted after 7 days, spam after 30 days, and finished answers after the time the site owner chooses (by default 24 months, or 12 months unless the owner has said the answers are not sensitive).
- Contacts and consent. Each contact's email address, name, where they first signed up, and when they confirmed or stopped. When someone ticks or confirms a newsletter box we record the wording they agreed to, against a hash of their address.
- Members. To sign a member in to a site we email a code or link. The code, link and typed address are deleted after 24 hours, and removed from the sent message after 30 minutes. A cookie keeps the member signed in (see cookies).
- Buyers. For a purchase: the buyer's email address, the Stripe customer ID, billing country, amounts and what was bought, and their access to it. Payment is handled in the site owner's own Stripe account, under Stripe's terms with the site owner; we never see card numbers. Links in access emails stop working after 1 day.
- Courses and books. Which lessons a member has completed, and how often each file was downloaded (a count, not a log of each download).
- Licence keys. The key is stored only in encrypted and hashed form. For each activation: the name the software sends (such as a device name), a hash of the device fingerprint, and when it was activated and last seen. No IP addresses are stored.
- Mail. A record of each message sent for a site and whether it was delivered. The address is removed from that record after 30 days. If an address hard-bounces, complains or asks to stop, we keep a hash of it so that we don't mail it again.
When a site owner deletes a contact, their answers are deleted and only a hash of the address is kept so they are not mailed again. When a site is deleted, or 90 days after it closes, its visitors' data is deleted with it. The one exception is licence keys that are still in use: their records stay while the licence service keeps answering for them, for up to 24 months.
Changes to this policy
We post every new version here with its date, and email account holders about changes that matter to them.