Skip to content

Terms of Service

The agreement between you and Lanpage: what the service does, what we ask of you, and what happens when a plan ends. Plain language, and short on purpose. Where a topic has its own policy, this points at it rather than restating it.

Who you are agreeing with

The service is published under the name Lanpage and is operated by an independent software studio. You do not pay us directly: Paddle sells the subscription to you as merchant of record, which is why your invoice and your card statement carry Paddle's name rather than ours, and which is what the section on plans and payment describes. For anything about the service itself, support@lanpage.co reaches the person who operates it.

Who can use it

You need to be old enough to enter into an agreement where you live, and you need to give us an email address that actually reaches you — it is the only channel we have for a notice about your account. One person or organisation per account. You are responsible for everything done under yours, including by anyone you hand access to, so keep the password to yourself and tell us if it stops being a secret.

What the service does

Lanpage hosts a small set of web pages for each app you publish, at a subdomain of lanpage.co, and keeps them served from an immutable snapshot so that editing in the dashboard cannot take a live page down. On paid plans it also re-evaluates your app against the catalogue of store requirements we maintain, so that an item that stopped being satisfied shows up as out of date rather than silently staying green. That is the whole of what we undertake to do, and the next section says what the second half of it is not.

The checklist, and what it does not promise

The live checklist is the thing paid plans are actually sold on, so it is worth being exact about what it is. These are the limits, and none of them is fine print — they are how the feature works.

  • We track a catalogue of store requirements that we maintain ourselves. It is not everything either store publishes, and the checklist answers for the requirements we track rather than for the whole of a store's rules.
  • We review store policies periodically and publish changes as we find them. We do not monitor stores continuously, and we do not undertake to reflect a change within any particular time.
  • Stores change what they ask for without notice, sometimes with retroactive effect, and reviewers apply the same rule differently. An item shown as met is our reading at the last time your app was evaluated.
  • We do not monitor your app, your store listing or your review status, and we never act on your behalf with a store.
  • A notice that an item went out of date is sent to the address on your account as a convenience. Meeting a store's rules is yours to do whether or not our notice arrived, or was sent at all.
  • The checklist is not a certification of anything. Completing it is not a prediction that a store will approve your app.

What the service is not

The templates, the wizard and the checklist are informational tools that help you structure content and keep track of what stores ask for. They are not legal advice, we are not a law firm, and we do not review what you publish. Whether a document is adequate for your app, your users and your country is your call, and whether a store accepts your app is the store's. None of it is a certification of compliance with anything, and nothing in the product should be read as one.

Your subdomain

Your pages are served at a subdomain of a domain we own, and you are almost certainly going to type that address into a store listing that is hard to change later, so here is where you stand. The subdomain is licensed to you for as long as your account has it: you do not acquire rights in the name, and it cannot be moved to another provider. We treat the public addresses of published apps as something we keep working, and we design releases around not breaking them. We can still reclaim or change a slug where it infringes someone's rights, impersonates a person or product, is on the reserved list, or where a legal or technical reason leaves us no choice — and where we do, we tell you first and help you move if there is a way to. Deleting an app releases its content but keeps its address reserved to you, so that a link already printed in a store listing cannot be claimed by somebody else.

Your content is yours

You keep every right to the content you write and the images you upload. You grant us only what we need in order to store, serve and back up that content while your account exists, and nothing beyond it. You are responsible for the content being accurate, lawful and yours to publish — which is why publishing a document asks you to confirm exactly that, and why the confirmation is recorded.

What you may not publish

The Acceptable Use Policy lists what may not go on a Lanpage subdomain, what we do about it, and how you get a decision reversed. It is part of this agreement and it binds every account, paid or free.

Covering us for what you publish

Your pages sit on our domain, under our name, at addresses stores index — so a claim about your content arrives at our door as well as yours. If someone brings one against us because of what you published, what you collected through your pages, or because you broke this agreement, you cover us for it: the claim itself, and what it reasonably costs to deal with. We will tell you promptly when one arrives, we will not settle it behind your back, and you can take over defending it. This does not apply to a claim that is about something we did rather than something you published.

Plans and payment

Publishing one app is free, with platform branding and one language. Paid plans are quoted per month and billed yearly by default; the pricing page is the price. Paddle is the merchant of record: it sells the subscription, issues the invoice and collects whatever tax applies where you are, so the amount that leaves your account can be higher than the figure we quote. Payment methods, invoices and receipts live there, reachable from the billing page in your dashboard.

If a payment fails

Paddle retries a failed charge for a few days and tells you it is failing. During that window your published sites stay online and stay reachable — a card that expired is not a reason for a store link to break — but publishing new changes is paused until the payment clears. If it never clears, the subscription ends the way any other ending does: the account returns to the free plan and the section below is what happens next.

Renewal, cancellation and what comes after

A subscription renews for the same period unless you cancel before that period ends. On a yearly plan we write to you 14 days before a renewal charges, saying the date and the amount, so a renewal you did not want is one you can stop before it happens. Cancelling stops the next charge and nothing else: your URLs stay online until the end of the period you already paid for. After that the account returns to the free plan and keeps one published app — by default the one you published most recently, because that is almost always the one a store is linking to, and you can switch which one it is from your dashboard at any time. The others go offline. None of the content is deleted.

Refunds

The Refund Policy says what we refund, in what window and how to ask. Paddle also has its own buyer terms. A chargeback is not a substitute for an email and it is slower than one.

Price changes

We can change what a plan costs. A change never applies to a period you have already paid for, and we tell account holders by email before the first renewal that would charge the new price, early enough to cancel instead.

Changes to the service

The product changes: we add features, remove ones nobody uses, and occasionally move what belongs to which plan. If we remove something a paid plan sold you, we tell you before it happens and you can cancel with the unused part of the period refunded, as described in the Refund Policy.

Availability

We aim to keep published sites reachable at all times, and we design for it — published content is served from an immutable snapshot rather than from live editing, so an outage in the editor is not an outage on your site. We do not promise uninterrupted service and we do not offer an uptime guarantee.

Fixing things that break

Software breaks, and what matters is what happens next. We keep the service and the sites published through it in working order, and we fix defects as soon as we reasonably can, giving priority to anything that leaves a published page unreachable, wrong, or serving something it should not. We do not commit to a time by which a particular fix will land, and a defect is not a breach of this agreement while we are working on it. Planned maintenance is done at low-traffic hours, and where it would take published sites offline we say so in advance. Backups exist so that we can recover from a disaster of our own; they are not an undo button for you, and we do not restore an individual account, app or document from one — a deletion you asked for is meant to be final, and the Privacy Policy says so on purpose.

Things outside our control

Part of this service is other people's: the company that runs the servers, the network in front of them, the payment processor, the mail provider. When one of them fails, or when something further out fails — a cable, a certificate authority, a government, a disaster — pages can go down for reasons no amount of care on our side would have prevented. We chase those failures as hard as we chase our own, and we tell you what we know while it is happening. We are not liable for them, and neither of us is in breach of this agreement for a delay caused by something genuinely beyond our control.

Suspension and closing an account

You can delete your apps and close your account whenever you like; closing it takes your published sites offline. We may suspend a site or close an account that breaks this agreement or the Acceptable Use Policy, and you get an email saying what we saw and why — except where content is unlawful or the service itself is at risk, in which case we act first and write immediately after. If we ever discontinue the service, account holders get notice and time to export.

Accounts nobody is using

A free account holds a subdomain, and a subdomain is a name only one person can have. If a free account goes 24 months with nobody signing in, we write to the address on it, and if nobody answers we may take its site offline and release the subdomain for someone else. We write first, always, and we never do this to an account with a paid plan. If your app is simply parked between releases, signing in is enough to reset the clock.

How we reach you

Several parts of this agreement are promises to tell you something before it happens. All of them go to the email address on your account, and a notice counts as given when we send it — we cannot make a mailbox accept it, and an address that has stopped working is the one thing here we have no way to notice. Keeping it current is yours to do. If you would rather hear about something in the product as well as by email, tell us; if you would rather hear less, we will still send the ones this agreement requires, because they are the ones you would want.

Ideas you send us, and showing your work

If you tell us what the product should do, we may build it, and we will not owe you anything for the idea. That is not us claiming your work — it is so that a feature request cannot turn into an argument about who thought of it. Separately: your published pages are public, but we will not use your app, your name or your screenshots as an example in our own marketing without asking you first. If you say yes and change your mind later, tell us and we take it down.

No warranty

The service is provided as it is. We do not warrant that it will be uninterrupted or free of defects, and we do not warrant that any document, page or checklist item will satisfy a particular store, a particular law, or a particular reader.

Liability

We are not liable for indirect or consequential loss, for lost profit or revenue, for a store's decision about your app, or for what you or your visitors published. To the extent the law allows, our total liability is limited to what you paid for the service in the 12 months before the claim. Nothing here limits liability that cannot lawfully be limited — including for death, personal injury or our own fraud — and nothing here reduces the rights you have as a consumer where you live.

If we disagree

Write to us first. Almost everything is a misunderstanding an email settles faster than anything else, and we would rather refund you than win an argument. Billing disputes go through Paddle, which issued the invoice. Nothing in this agreement takes away a right the consumer law of the country you live in gives you, including the right to bring a claim there.

Changes to these terms

A new version is published here with a new effective date, and for anything material account holders hear about it by email before it applies. Continuing to use the service after that is how you accept it. If you would rather not, cancel and we refund the unused part of the period you are in.

The rest of it

If part of this agreement turns out to be unenforceable, the rest of it still stands, and the unenforceable part is read as narrowly as it needs to be rather than thrown out. The sections on your content, on covering us for what you publish, on liability and on no warranty stay in force after your account closes, because those are the ones that matter afterwards. We may transfer this agreement to whoever takes over the service, and we will tell you if that happens; you may not transfer your account to someone else without asking us first, which matters more than it sounds like when an app changes hands. Not enforcing something once does not mean giving it up. This document, together with the Privacy Policy, the Cookie Policy, the Acceptable Use Policy, the Fair Use Policy, the Refund Policy and the Data Processing Terms, is the whole agreement between us.

Effective date: 2026-09-10