Skip to content

Data Processing Terms

When one of your visitors gives you their email address through a Lanpage page, that address is yours and we are only holding it. These are the terms on which we hold it, and the list of everyone who touches it. They are part of the Terms of Service, and they apply automatically — there is nothing to sign.

What these terms cover

The personal data you put into Lanpage about people who are not you: the addresses submitted to an email capture block, and anything identifying that you write into a document or a landing page. For that data you decide the purpose and we act on your instructions. For your own account data we are the ones deciding, and the Privacy Policy is the answer instead.

Your settings are the instructions

We process that data to do what the product does: store it, show it to you, let you export it, and delete it when you tell us to. Using the product is the instruction, which is why there is no separate document to negotiate. We do not use it for anything else, we do not sell it, we do not email your visitors, and we do not use it to train models.

How long it lasts

We process this data for as long as your account exists, and the processing ends when the account does. There is no separate term to renew or notice period to serve: the agreement runs with the service, which is the same reason there is nothing here to sign.

Confidentiality

Access is limited to the people who operate the service, and only when operating it requires it. The measures are the ones described under how we protect data in the Privacy Policy, and they apply to this data identically rather than to a lesser standard.

Who else touches it

The full list, with what each one can see. Every one of them is under a written data processing agreement with us, and we remain responsible to you for what they do with this data as if we had done it ourselves. Counting page views adds nobody to the list: that runs on a server we rent and administer, so the counts never reach another company. We will tell account holders before adding a provider that touches customer data, early enough to close the account instead.

  • Paddle — payments, invoicing and tax. Sees your billing details; never your visitors' data.
  • Resend — transactional email. Sees the address we are writing to and the message itself.
  • Cloudflare — R2, where uploaded images are stored. Sees the images you upload.
  • Our hosting provider, in the United States — runs the application and the database, and therefore holds everything that is stored.

Where it goes

The database runs in the United States and the providers above operate internationally, so data you collect through a Lanpage page is transferred there. Publishing through Lanpage is choosing that. If it does not work for the data you hold, Lanpage is not the right place to hold it, and we would rather say so here than after you have imported a list.

Deletion and export

You can export captured addresses at any time. Deleting an app deletes the addresses captured through it; closing the account deletes all of it. Backups are taken nightly and pruned after 14 days, so a deleted record can persist in one for up to that long before it is gone for good.

Helping you answer a request

If a visitor asks you for a copy of their data, or asks you to delete it, the dashboard is enough to answer without involving us. When it is not, write to support@lanpage.co and we will help inside the time you have to answer, not after it. The same applies if you are working out whether what you are doing needs an impact assessment, or a regulator has asked you something about how the data is held here: what we know about our own systems is yours to use.

Checking that we do what this says

This document, plus the data processing agreements our providers publish, is what we offer as evidence. A written question about how something here works gets a written answer within a reasonable time, and if a regulator asks you something about us that you cannot answer, send it to us and we will help you answer it. We do not host on-site audits, and we say so here rather than agreeing to one and then explaining why it cannot happen — a one-person studio that promised an audit window would be promising a fiction.

If something goes wrong

If data you hold here is exposed, we tell you without delay, with what we know at the time rather than after the investigation closes — because your own deadline for telling anyone else starts running before ours does.

Effective date: 2026-09-10