--- title: "Terms & Conditions" description: "Last updated October 22, 2026" canonical: https://landtest.dev/terms last-updated: 2026-10-30 --- # Terms & Conditions Last updated October 22, 2026 ## 1. Agreement These Terms govern your use of Landtest: the website, dashboard, Test Studio, Autopilot, the tracking script, the REST API, the MCP server, the CLI and any related services (the "Service"). By creating an account, joining the waitlist, connecting a repository or calling the API, you agree to these Terms, our [Privacy Policy](https://www.landtest.dev/privacy) and our [Refund Policy](https://www.landtest.dev/refund). If you use Landtest for a company, you confirm that you can bind that company, and "you" means the company. ## 2. The service Landtest runs A/B tests on landing pages that live in your GitHub repository. It generates page variants with AI, commits them to your repository with routing middleware and a tracking script, and reports results. Your own hosting provider serves your pages to your visitors; Landtest does not proxy your traffic. Landtest currently supports Next.js (App Router) and Vite + React projects hosted on GitHub. Features in beta, early access or the sandbox may change or be removed, and may be less reliable. ## 3. Eligibility and accounts - You must be at least 18 and able to enter a binding contract. - Give accurate account information and keep your sign-in credentials, API keys and MCP tokens secure. You are responsible for activity under your account and workspace. - Workspace admins control roles, billing, integrations and BYOK keys, and are responsible for the teammates they invite. - Joining the waitlist does not guarantee access, a launch date, features or pricing. - We may reclaim workspace names that are misleading, infringing or unused. ## 4. GitHub access When you install the Landtest GitHub App on a repository, you authorise Landtest to read its contents and to create branches, commits and pull requests in it. Landtest uses this to add test variants, routing middleware and the tracking script; to publish splits and change weights; and, when a test ends, to commit the winning variant and remove its own test code. - You must have the right to grant this access to every repository you connect. - Depending on your publish settings, Landtest may commit to the branch you deploy from, which can trigger a production deploy through your hosting provider. - Every change is a normal git commit. Review pull requests, protect important branches, and keep backups as you normally would. - You can revoke access at any time in GitHub. Tests that are running when you do so may stop being tracked or cleaned up. ## 5. AI-generated variants Variants, copy, names, plans and analyses are produced by AI models and can be wrong, broken, off-brand, or similar to material elsewhere. Landtest shows a preview before you publish, but you are responsible for reviewing what goes live on your site, including its claims, accessibility and legal compliance. As between you and Landtest, you own the code and content generated for your project, to the extent the law allows ownership of AI output. Landtest does not use your code or prompts to train AI models. If a workspace admin opts in to the insight network, you grant Landtest a perpetual, worldwide licence to use de-identified, aggregated test results (as described in the [Privacy Policy](https://www.landtest.dev/privacy#ai)) to improve the service, publish anonymous benchmarks and train Landtest's own models. Opting out stops new contributions and deletes your raw records; models already trained on pooled data are not retrained. We will not identify you in any published material without your written approval. ## 6. Autopilot Autopilot is off by default. If you turn it on, you authorise Landtest to act on running tests without asking each time, within the guardrails you choose: shipping winners, stopping losing tests, and, if you enable it, planning, generating and launching the next test. These actions commit to your repository and use AI credits like any other. You can use a veto window or require approval for each action, and you can turn Autopilot off at any time. Actions it has already taken are not reversed automatically, but each one is a git commit you can revert. ## 7. Visitor tracking on your site While a test runs, your site serves a Landtest cookie and the `lt.js` script, which send visitor events to Landtest as described in the [Privacy Policy](https://www.landtest.dev/privacy#visitors). You are the party in control of your visitors' data, and you are responsible for: - telling visitors about the experiment and the data collected, in your own privacy notice; - getting consent where your visitors' laws require it. Landtest can wait for consent with `data-lt-await-consent="1"`; - not placing personal data (such as names or emails) in page paths, link text, button labels or form IDs that the script reads. We process visitor data only to provide your experiment results. ## 8. Plans, credits and limits Current prices are on the [Pricing](https://www.landtest.dev/pricing) page. Each plan includes a number of active tests, a monthly AI credit allowance, and a monthly analytics-event allowance per project: Plan Active tests AI credits / month Analytics events / project / month PlanFounder (invite) Active tests5 AI credits / month50 Analytics events / project / month100,000 PlanStarter Active tests5 AI credits / month100 Analytics events / project / month500,000 PlanPro Active tests20 AI credits / month200 Analytics events / project / month3,000,000 PlanMax Active testsUnlimited AI credits / month1,000 Analytics events / project / month15,000,000 PlanLifetime Active testsUnlimited AI credits / monthYour own key (BYOK) Analytics events / project / month5,000,000 - One AI credit equals US$0.10 of AI model cost. Credits are measured from the real cost of each AI call in the current UTC calendar month, reset at the start of each month, and do not roll over. - Running tests and collecting analytics do not use credits. Generating, revising, naming and planning variants does, including calls made by Autopilot. - When you reach your credit or active-test limit, Landtest pauses the action and offers an upgrade. It does not charge overages. - When a project reaches its event allowance, your pages keep working and visitors still see their variants, but further events may not be recorded until the next month. Pageviews and goals are kept before other events. - We may change plan contents for future billing periods with notice, as described in "Changes". ## 9. Payments - Payments are processed by Dodo Payments, which acts as the merchant of record and handles checkout, invoicing, payment methods and applicable sales tax or VAT. Its terms also apply to your purchase. - Subscriptions are billed in advance for each billing period (monthly, or annual where offered) and renew automatically until cancelled. - Workspace admins can cancel at any time from **Settings → Billing → Manage billing**. Cancellation takes effect at the end of the current period, and you keep paid features until then. - Lifetime is a one-time payment for continued access to the Service for as long as we operate it, with AI calls made on your own key. It is not a perpetual licence to the software, and it does not cover the cost of your AI provider. - If a payment fails or a subscription ends, the workspace returns to the free allowance. Running tests keep running, but you may not start new ones above the free limits. - Refunds are covered by our [Refund Policy](https://www.landtest.dev/refund). ## 10. Bring your own AI key On the Lifetime plan, a workspace admin can add an Anthropic or OpenAI API key. Landtest then makes AI calls with that key and does not meter credits for them. You are responsible for that provider's charges, rate limits and terms. Keys are encrypted at rest, and you can remove yours at any time. ## 11. API, MCP and agents - You may use the REST API, MCP server and CLI to automate your own workspaces, including through AI agents you control. Actions taken with your tokens are your actions. - Respect rate limits and do not try to get around them, plan limits or access controls. - The sandbox and its demo key are for trying the API. Sandbox data is not private and may be reset at any time. - We may change or retire API versions with reasonable notice, except where a change is needed for security. ## 12. Acceptable use You agree not to: - test pages that are illegal, deceptive, or that infringe others' rights, or use variants for phishing, fake reviews or misleading claims; - connect repositories or sites you are not authorised to change; - send fake, automated or inflated events to the ingest endpoint, or tamper with other customers' results; - probe, overload or disrupt the Service, or bypass authentication, rate limits or plan limits; - reverse engineer the Service except where the law allows it, or resell it without our written agreement; - use the Service to collect sensitive personal data, such as health or financial data, from visitors. ## 13. Your content You keep all rights to your repositories, pages, brand materials, Memory and data. You give Landtest a limited licence to host, copy, process and display that content only as needed to run the Service for you, including sending it to the service providers listed in the Privacy Policy. If you send us feedback, we may use it without obligation to you. ## 14. Our property The Landtest name, logo, website, dashboard, tracking script and software belong to us. These Terms give you a right to use the Service, not ownership of it. The runtime code Landtest adds to your repository during a test may be used in that repository for as long as you need it. ## 15. Test results Results use statistical methods (including mSPRT confidence and sample-ratio checks) that estimate, and do not guarantee, which variant performs better. Low traffic, tracking gaps, bots, ad blockers, consent settings and seasonality can all distort results. You are responsible for decisions based on them. We do not promise any increase in conversions or revenue. ## 16. Availability and support We work to keep Landtest available, but we do not offer an uptime guarantee and the Service may be interrupted for maintenance, provider outages or reasons outside our control. Because your host serves your pages, a Landtest outage should not take your site down, but events sent during an outage may be lost. Support is by email and the in-app feedback form. ## 17. Suspension and ending - You can stop using Landtest at any time: end your tests, uninstall the GitHub App, and ask us to delete your account. - We may suspend or close an account that breaks these Terms, puts the Service or others at risk, or has unpaid fees. Where reasonable, we will warn you first and give you time to fix the problem. - When an account closes, we delete its data as described in the Privacy Policy. Code already committed to your repository stays there. Before you leave, end running tests so Landtest can clean up its code, or remove it yourself. - Sections that by their nature should survive (such as payments owed, disclaimers, liability and indemnity) survive the end of these Terms. ## 18. Disclaimers To the fullest extent the law allows, the Service is provided "as is" and "as available", without warranties of any kind, including merchantability, fitness for a particular purpose, non-infringement, or that the Service, generated code or results will be accurate, error-free or uninterrupted. ## 19. Limitation of liability To the fullest extent the law allows, Landtest is not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, conversions or data, even if we were told they were possible. Our total liability for all claims relating to the Service is limited to the amount you paid Landtest in the 12 months before the claim, or US$100 if that is greater. Nothing in these Terms limits liability that cannot be limited by law, or any non-waivable rights you have as a consumer. ## 20. Indemnity You will defend and compensate Landtest against third-party claims arising from your pages and content, your repositories, your handling of your visitors' data, or your breach of these Terms. ## 21. Disputes If something goes wrong, email us first at [hello@zerocost.app](mailto:hello@zerocost.app)and we will try to resolve it informally within 30 days. If we cannot, the dispute will be handled by the courts that have jurisdiction where Landtest's operator is established, unless the law where you live gives you the right to bring it elsewhere. ## 22. Changes We may update these Terms. We will change the date at the top and, for material changes, tell account holders by email or in the dashboard at least 14 days before they take effect. Continuing to use Landtest after that means you accept the new Terms. If you do not, cancel before the change takes effect. ## 23. Contact [hello@zerocost.app](mailto:hello@zerocost.app)