Privacy policy

Smidt Beheer, an eenmanszaak (sole proprietorship), registered with the Dutch Chamber of Commerce (KvK) under number 99124254, at Binnendelta 11M, 1261 WZ Blaricum, the Netherlands, operates PeerForge and is the controller of the personal data described here. Write to hello@peerforge.app about anything on this page.

When you publish documents that contain other people's personal data, you are the controller of that and we process it on your behalf.

We do not use advertising cookies, we do not run third-party analytics on the pages that serve your documents, and we do not sell anything to anybody.

A document owner can see how often a document was opened. If the reader was signed in, that record carries their email address, because the owner decided who was allowed to read it and can reasonably know that they did.

If the reader was not signed in, we do not store their IP address. We store a SHA-256 hash of it computed with a secret key we hold, which lets us count the same reader twice without being able to work backwards to who they are. We treat that hash as personal data anyway, because it is derived from something that identifies a person.

Publishing without an account uses the same kind of keyed hash, to enforce the hourly limit from one network.

Most of it is because we cannot provide the service otherwise — that is performance of our contract with you. Sign-in codes, notification email about your own documents, and keeping the service secure and within its limits rest on our legitimate interest in running it safely. Billing records are kept because the law requires them.

Where we ask for consent — signing in with Google or Microsoft, for instance — you can withdraw it by not using it, and by removing that connection from your account.

The people you share a document with, and nobody else. Beyond that, only the companies that run parts of the service for us, each under a data processing agreement:

Your documents and your account live in the EU. Some of these providers operate global networks, so data may be handled outside the EU in transit or for support; where that happens it is covered by the European Commission's standard contractual clauses.

We will hand data to an authority only where we are legally obliged to, and we will tell you unless we are forbidden from doing so.

The application sets one cookie, to keep you signed in, plus a preference for which workspace you are looking at and whether you chose the light or dark theme. They are strictly necessary, so we do not ask for consent to them and we do not show a banner.

The domain that serves published documents sets no cookies at all. That is deliberate and structural: it is what makes it safe to run a document's own scripts.

You can ask for a copy of your data, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, or object to processing based on legitimate interest. Write to hello@peerforge.app and we will answer within one month.

You can stop notification email at any time from the link at the bottom of any of it, without an account and without asking us.

If you think we have handled your data badly, please tell us first — and you are also entitled to complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or to the regulator where you live.

Documents published without an account are deleted automatically after 30 days unless claimed. Everything else lasts until you delete it or close your account, after which we remove your documents, comments and account within 30 days, except records we must keep for tax or accounting.

Access to documents is decided on the application domain and enforced in the database. Documents are served from a separate domain with no session cookie, inside a sandbox, so a document cannot reach your account even if it tries. API keys are stored hashed. Sign-in is a one-time code or an identity provider; we never store a password because we never ask for one.

If a breach affects you we will tell you, and the regulator, within the time the law allows.

If we change this policy in a way that matters we will say so by email or in the app before it takes effect. The date at the top always reflects the current version. Our terms cover the rest of the relationship.