Privacy policy

Who is responsible

The controller of the personal data described here is the operator of PageForge, referred to as the PageForge operator. In this policy, "we" means the PageForge operator.

You can reach us at [email protected] with any question about this policy or your personal data.

What this policy covers

This policy covers the PageForge admin (where our customers and their staff log in to build sites), this marketing website, and the systems behind them. It does not cover the websites our customers build and publish with PageForge.

Each customer is the controller of the personal data collected through its own site, for example messages sent through a contact form. We process that data as the customer's data processor, on the customer's behalf, under our data processing agreement, and delete form submissions automatically after 180 days. If you have a question about a specific site, contact the owner of that site.

A customer's site can show images that are hosted on another website. Your browser then contacts that website directly. The site owner makes that choice, and this policy does not cover it.

Accounts and login

People who are invited to PageForge get an account. We process the email address, display name, a password stored only as a hash (BCrypt), whether the account is a platform administrator, the date the account was created, and the sites the account belongs to with its role on each.

Purpose: to let you log in and edit the sites you belong to. Legal basis: Article 6(1)(f) GDPR, our legitimate interest and the customer's in providing the service to the customer's staff. For the person who signs up an organization of their own, the basis is Article 6(1)(b), because the account is part of the agreement with that person.

You must provide an email address, a display name and a password to get an account. There is no statutory obligation to do so, but without them we cannot give you an account.

Retention: we keep the account until you, or the customer whose site you work on, ask us to delete it. You can download or delete your account yourself under My account in the admin, or by email (see Your rights).

Invitations

When someone is invited, we process the invitee's email address, the invitation's status and expiry date, who sent it, and the site and role it grants. The invitation token itself is stored only as a hash. The email is sent through Brevo. These details come from the person who invited you (a platform administrator or a site owner).

Legal basis: Article 6(1)(f) for an invitation to an existing site, where our legitimate interest, and the customer's, is giving the customer's staff access to the service the customer has contracted, and Article 6(1)(b) when a new organization is created, because that happens at the invitee's request before an agreement is made.

Retention: an invitation link is valid for 7 days. The invitation record is deleted 90 days after it was accepted or expired.

Password reset

When you ask to reset your password, we store your user id, a hash of the reset link and its expiry time. The link is sent to your email address through Brevo. The answer to the request is the same whether or not the address belongs to an account, so the feature cannot be used to find out who has one.

Legal basis: Article 6(1)(f), the same interest as for the account itself, and Article 6(1)(b) for the person who signed up an organization of their own.

Retention: a reset link is valid for 1 hour. The record is deleted 7 days after it expired.

Feedback

When a logged-in user sends feedback, we store the user id, the type, the subject and the message. Do not put sensitive information in a message. Only platform administrators can read feedback.

Legal basis: Article 6(1)(f), our interest in improving the product. Retention: we keep feedback until we delete it or you ask us to.

Server logs and security

For each request to our servers, we write the method, path, status code, response time, host name, an internal correlation id and the site and organization id to a log. We do not log IP addresses or browser identification (the user agent). Invitation tokens are removed from the log and email addresses are shortened (for example j***@example.dk). In rare cases an error message can contain an email address.

Purpose: operation, troubleshooting and security. Legal basis: Article 6(1)(f); this also serves our security obligation under Article 32.

Retention: the log has a fixed size limit (at most 30 MB per service) and is discarded whenever the service is redeployed.

Protection against abuse

To protect against abuse and password guessing, we count requests per IP address. The counters exist only in the server's memory, until 15 minutes after your last request, are never written to disk or to the log, and disappear when the server restarts. Legal basis: Article 6(1)(f).

Messages you send us

If you write to us, we process your email address, your name and your message so that we can reply. Legal basis: Article 6(1)(f), or Article 6(1)(b) if you are a customer. We keep the message only as long as needed to handle your request.

Acceptance of agreements at sign-up

When a new organization is created, or when an owner of an existing organization accepts an updated agreement in the admin, we record that it accepted the data processing agreement and this privacy policy: the user id of the person who accepted, the organization, which document and which version it was, and the time.

Purpose: to be able to show that a written data processing agreement exists (Article 28(9)) and that we meet our duty to demonstrate compliance (Article 5(2)). Legal basis: Article 6(1)(f), our interest in being able to document the acceptance.

Retention: the record is kept for as long as the organization exists, as proof of the acceptance, also after the user who accepted has been deleted. It is deleted together with the organization.

Backups

Every night we copy the database and the uploaded files so that we can restore the service after a failure. The copies are kept for 7 days on the server and for 30 days on a separate computer. Data we delete can therefore remain in backups for up to 30 days before it is overwritten. Legal basis: Article 6(1)(f); this also serves our obligation to keep the service available and resilient (Article 32(1)(c)).

Cookies and browser storage

PageForge sets no cookies, neither on this website, in the admin nor on our customers' sites, and uses no analytics, advertising trackers or external fonts.

The admin keeps data in your browser's local storage: a login token (a signed token that is valid for 8 hours and is removed when you log out) and display settings (the last site you used, editor view, layout, device preview and one dismissed tip). It also keeps which inspector tab is open in the editor in your browser's session storage, which is cleared when you close the tab. The data stays on your device, and the display settings are not sent to us. The settings are stored because you chose them and are needed for the feature you asked for.

Who receives the data

We use these service providers. We do not sell personal data and do not pass it on otherwise unless the law requires it.

• Cloudflare, Inc. (USA): provides the network edge and tunnel in front of our services, so it can see IP addresses and request details. Cloudflare also adds Network Error Logging headers, which can make your browser send network error reports to Cloudflare. The transfer to the USA relies on the EU-US Data Privacy Framework (Cloudflare is certified).
• Brevo (Sendinblue SAS, France): sends invitation and password reset emails, so it receives the email address, the subject and the link in the message.
• Our email provider, which hosts the contact mailbox: receives messages you send to us.
• The owners of a site can see that site's member list (the names and email addresses of its members).

Your rights

You have these rights under the GDPR:

• Access to your data (Article 15).
• Correction of inaccurate data (Article 16).
• Erasure (Article 17).
• Restriction of processing (Article 18).
• Data portability (Article 20).

Your right to object

You have the right to object at any time, on grounds relating to your particular situation, to processing that we base on our legitimate interest (Article 6(1)(f)). If you object, we stop the processing unless we can show compelling legitimate grounds that override your interests, or the processing is needed for a legal claim (Article 21).

How to use your rights

You can download a copy of your data and delete your account yourself at any time under My account in the PageForge admin (you confirm a deletion with your password). Deleting removes your login, your memberships and the feedback you sent. Pages and images you worked on stay with the site but are no longer linked to your name. If you are the only owner of a site, make someone else an owner first.

For anything else, or if you prefer, contact us by email. We reply within one month. For data collected through a customer's site, contact the owner of that site.

Complaints

If you think we handle your data in breach of the rules, you can complain to the Danish Data Protection Agency (Datatilsynet), Carl Jacobsens Vej 35, 2500 Valby, www.datatilsynet.dk. We would like to hear from you first, so that we can put it right.

Profiling and automated decisions

We do not use profiling and make no automated decisions that have legal or similarly significant effects on you.

Changes to this policy

We update this policy when our processing changes. The version is the date of the latest change in substance and is shown at the top. The current version is always available at this address.