Applane terms of service

Version: terms-2026-09-04

1. Parties and definitions

1. “We”, “us” and “Applane” mean Julien Ganichot, trading as Applane, a sole proprietorship (eenmanszaak, ZZP) under Dutch law, not a company, at Faas Wilkesstraat 149G, 1095 MD Amsterdam, Netherlands, VAT id NL003642041B41.
2. “You” and “Customer” mean the company that accepts these terms by signing an order form or by paying an invoice. These terms are for businesses only.
3. “Service” means the Applane builder at app.applane.dev and its MCP bridge, the admin console, and the backend that issues licences.
4. “Order form” means the document (or the pilot email) that states your plan, seat count, fees and term. If an order form and these terms disagree, the order form wins.
5. “Seat” has the meaning in section 6. “App” means anything your users build with the Service: the Apps Script project, its files, deployments and data.

2. The service

1. The Service lets your employees describe an internal tool in the browser and have it built, previewed and deployed as a web app in your own Google Apps Script. The model runs on your Vertex AI project; the code lives in your Google Drive; the apps run on Google.
2. We provide the software and keep the licence backend running. We do not host, run, proxy or store your apps, your prompts or your data, and we have no access to them.
3. We may improve the Service at any time. We will not remove a capability your plan includes during a paid term without offering an equivalent.

3. Your Google environment

1. You supply and pay for your own Google Workspace and Google Cloud project, including the Vertex AI usage the Service generates. Google bills you directly at its own prices; we charge no usage fee.
2. You create and keep the OAuth client, the API enablement and the IAM grant the Service depends on. If you change or delete them, the Service stops working for your users until they are restored, and that is not a defect of the Service.
3. You are responsible for your Google admin settings, including who may use the builder, Drive sharing policies, and the permissions of the accounts that use the Service.

4. Ownership

1. You own everything built with the Service: every App, its source code, its data, its deployments and its configuration. They are created in your Google account and never leave it. We claim no right to any of it.
2. We own the Service: the builder, the bridge, the agent prompts and validators, the app template, the admin console and the backend. These terms license the Service to you; they do not sell it.
3. Because the Apps are yours and run on your Google, they keep running after these terms end. Only the builder stops working.

5. Licence and restrictions

1. For the term and for the number of seats on your order form, we grant you a non-exclusive, non-transferable licence to use the Service for your internal business.
2. You may not resell, sublicense or rent the Service; give access to people outside your organisation; reverse engineer, decompile or copy the Service except where the law allows; patch the builder to bypass the seat check; or use the Service to build a competing product.
3. The template code that the Service places inside your Apps is licensed to you without restriction so that your Apps remain yours and keep working without us.

6. Seats

1. A seat is one user in one of your verified domains who has signed in to the builder. People who only open a deployed App are not seats and are never counted.
2. A seat becomes active on the user’s first sign-in and stays active until an admin reclaims it or it has been idle for 60 days. Reclaimed seats free capacity at once.
3. When all seats are in use, existing seats keep working and new sign-ins are refused until you add seats. We never block an active seat because of a cap.
4. On plans with an allowlist, only listed users get seats. On open plans, any verified user in your domain does, up to the cap.
5. A Seat is one named individual with an email address at a Verified Domain of the Customer who has successfully authenticated to the Software. A Seat is created on that individual’s first successful authentication and remains active until it is released. Applane releases a Seat automatically after 60 consecutive days without authentication, and the Customer’s administrator may release one at any time. The number of Seats for an invoicing period is the number of active Seats recorded by Applane on the invoicing date.

7. Fees and payment

1. Fees are per seat and stated on your order form. Annual plans are invoiced up front for the seats you buy. Monthly plans (where offered) are invoiced for the active seats counted daily.
2. Invoices are due within 30 days. Late payments may bear the statutory Dutch commercial interest rate.
3. Prices exclude VAT. For business customers in another EU member state, VAT is reverse-charged; you supply your VAT id. Dutch customers are charged Dutch VAT.
4. If an invoice is more than 30 days overdue we may suspend the issue of new licences. Active users keep a 7-day grace period before the builder locks. We restore access when the invoice is paid.

8. Pilots

1. A pilot is a paid, fixed-fee licence for 60 days and up to 25 seats, for internal Apps in one domain. The fee is stated in the pilot order form.
2. If you sign an annual contract within 30 days after the pilot ends, the pilot fee is credited against the first annual invoice.
3. Apps built during a pilot are yours and keep running whether or not you continue.

9. Term and termination

1. The term starts on the date in your order form. Annual terms renew for another year unless either side gives written notice at least 30 days before the renewal date.
2. Either side may terminate for a material breach that is not fixed within 30 days of written notice. We may terminate at once if you breach section 5.2 or section 10.
3. At the end of the term: your users lose access to the builder, the admin console and the MCP bridge; your Apps keep running on your Google, unchanged; we delete your tenant data within 30 days as described in the privacy notice. Nothing needs to be exported, because nothing of yours was with us.
4. Fees already paid are not refunded except where these terms or the law say otherwise.
5. The licence to use the Software terminates when the subscription ends. Use of the Software to build, modify or deploy after that date is unlicensed use and a breach of this agreement. Applications the Customer has already deployed continue to operate and the Customer’s own code in them remains the Customer’s property.

10. Acceptable use

1. You will use the Service in line with Google’s terms for Workspace, Apps Script and Vertex AI, and with the law.
2. You will not use the Service to build Apps that collect passwords or other credentials, that attack or overload any system, that infringe someone’s rights, or that process data you are not allowed to process.
3. You are responsible for what your users build and for reviewing Apps before you rely on them. The Service bounds what an App can do; it does not check whether an App’s output is correct.

11. Availability and support

1. Building, previewing and deploying depend on Google’s services, not on our backend. Our backend issues licences that stay valid for 72 hours and are accepted for a further 7 days if it cannot be reached.
2. We offer no service-level agreement unless an Enterprise order form includes one. The response times on the pricing page are targets.
3. Support is by email at the address in section 16, in English, on Dutch business days.

12. Warranties and liability

1. We warrant that the Service will work materially as described on this website. Your remedy for a breach of this warranty is that we fix the problem or, if we cannot, refund the fees for the affected period.
2. Except for that, the Service is provided as is. We do not warrant that it is error-free, that Google’s services will remain available or unchanged, or that any App your users build is fit for a purpose.
3. Neither side is liable to the other for indirect or consequential loss, lost profit, lost data (other than data we hold for you), or business interruption.
4. Each side’s total liability under these terms in any 12-month period is capped at the fees you paid in the 12 months before the event giving rise to the claim.
5. These limits do not apply to death or personal injury caused by negligence, fraud, wilful misconduct or gross negligence, breach of section 13, or any liability that cannot be limited by law.

13. Confidentiality

1. Each side keeps the other’s non-public information confidential, uses it only for these terms, and shares it only with people who need it and are bound by similar duties. This lasts for three years after the term ends.
2. It does not cover information that is public, already known, independently developed, or that must be disclosed by law, in which case the disclosing side gives notice where it may.

14. Data protection

1. The privacy notice describes what we process and why. For the seat and admin records we process on your behalf, our data processing agreement applies; it is available on request and is part of these terms once signed.
2. We never receive your Google access tokens, your Apps’ source, prompts, or the data your Apps read or write. Your own Google policies and audit logs govern those.

15. Changes to these terms

1. We may update these terms. The date at the top of this page shows the current version. Changes that materially reduce your rights are announced to your admins by email at least 30 days before they take effect and apply from your next renewal.

16. Governing law and contact

1. Dutch law governs these terms. The courts of Amsterdam have exclusive jurisdiction, without prejudice to mandatory rules that give you another forum.
2. Notices and questions: hello@applane.dev, or by post to the address in section 1.