Acceptable Use Policy

What it applies to

Everything published through Lanpage: landing pages, documents, images, FAQ entries, the addresses you capture, and the app metadata around them. It applies to what you publish and to how you use the service itself.

Content that is never allowed

None of this survives a report, and most of it does not survive us noticing.

• Content that is unlawful where it is published or where it is read.
• Content that infringes someone else's copyright, trademark, or privacy.
• Impersonation of a person, a company or an app that is not yours.
• Malware, phishing, or anything built to trick a visitor into giving up credentials or money.
• Sexual content involving minors, which we report rather than merely remove.
• Content that incites violence against people, or targets them for harassment.
• Claims about what an app does that the app does not do.

Uses the product is not for

Lanpage publishes the web pages a mobile app needs. It is not general hosting, and these are the ways people try to make it one.

• Hosting files, redirects or endpoints unrelated to an app you are shipping.
• Using a subdomain as generic web hosting, a file drop or a link shortener.
• Reselling Lanpage subdomains as a hosting product of your own.
• Doorway pages, cloaking, or pages built for a crawler rather than a reader.
• Automated bulk creation of apps or accounts.
• Using the email capture block to collect addresses for something other than the app the page is about.
• Removing or hiding the Lanpage attribution on a free plan, which is what the free plan is paid with.

How you treat your visitors' data

If you capture addresses, the page has to say what you will do with them, and then you have to do that. This is the one rule here the product enforces rather than trusts: a landing with an email capture block and no consent text will not publish, because those addresses land in our database and the page asking for them is on our domain. Beyond that: do not upload addresses you collected somewhere else, do not sell them, and honour an unsubscribe the first time you are asked. We store them for you; what you do with them is yours to answer for.

The service itself

Do not probe, scan or load-test the platform without asking first — write to security@lanpage.co and we will usually say yes and tell you when. Do not attempt to reach another account's data, and do not automate the product in a way that degrades it for anyone else. Reporting a vulnerability you found responsibly is welcome and is not a breach of this policy.

What we do about it

It depends on what we found. Something plainly unlawful comes down immediately and the account is suspended. Everything else starts with an email from a person, saying what we saw and what we are asking for, and a reasonable period to put it right. We take a working site offline over how much you are using rather than what you published only after that conversation — see the Fair Use Policy.

When it keeps happening

A single mistake put right is the end of it, and we do not keep a tally to hold against you later. A pattern is different. An account that repeatedly publishes content infringing other people's rights is closed, and we say so here rather than deciding it case by case, because a platform that hosts what its customers write has to have an answer to that question written down before it needs one. The same goes for an account that keeps returning to something the Acceptable Use Policy already asked it to stop doing.

Getting a decision reversed

Reply to the email, or write to support@lanpage.co. A person reads it, and we restore what we took down when we got it wrong. We keep a record of what was removed and why, so there is something to check against rather than a memory of it.

Reporting something

If a site published on a Lanpage subdomain is infringing your rights, impersonating you, or being used to harm people, the page on reporting a published site says what to send and what we do with it.