Flet Studio Terms of Service
Effective date: November 5, 2026
These Terms of Service ("Terms") form a binding agreement between you and Appveyor Systems Inc. ("AppVeyor", "we", "us", or "our") and govern your access to and use of the Flet Studio service ("Flet Studio" or the "Service"). Flet Studio is a hosted development environment for building, running, packaging, and publishing applications with the Flet framework.
Please read these Terms carefully. By accessing or using Flet Studio, you agree to be bound by these Terms and by our Privacy Policy. If you do not agree, you must not use the Service.
1. Acceptance of Terms
By creating an account, signing in, or otherwise using Flet Studio, you confirm that you have read, understood, and agree to be bound by these Terms. If you are accepting these Terms on behalf of a company, organization, or other legal entity, you represent and warrant that you have the authority to bind that entity to these Terms, in which case "you" refers to that entity.
We may update these Terms from time to time as described in Section 15.4. Your continued use of the Service after an update takes effect constitutes acceptance of the updated Terms.
2. The Service
Flet Studio provides a hosted environment that allows you to create, edit, store, run, and share applications written in Python using the Flet framework. The Service includes account management, project storage, code editing, AI-assisted development, application execution, sharing, and related features. It also lets you:
- Build your apps for Android, iOS, web, Windows, macOS, and Linux on build machines that we operate or rent
- Sign your apps with your own certificates and keys
- Publish your apps to Google Play, the App Store and TestFlight, the Mac App Store, and the Microsoft Store, using your own developer accounts
- Share builds on public download pages at get.flet.app, including install and device registration links for iOS testers
- Sync your apps with GitHub repositories in both directions
Flet Studio is currently delivered through the browser; we may also offer desktop or mobile applications in the future.
We may add, modify, or discontinue features at any time. Where a change materially and adversely affects the way you use the Service, we will use commercially reasonable efforts to provide advance notice through the Service or by email.
3. Accounts and Eligibility
3.1 Eligibility
You must be at least 16 years old to use Flet Studio. If you are using the Service on behalf of an entity, you must have authority to act on its behalf. The Service is not directed to children under 16, and we do not knowingly permit them to create accounts.
3.2 Account creation
You can create an account by signing in with a supported identity provider (currently GitHub, Google, or Microsoft) or, where available, by creating a local account with an email and password. You must provide accurate and complete information, and you must keep it accurate over time.
3.3 Account security
You are responsible for safeguarding your credentials and for all activity that occurs under your account. You must notify us promptly at legal@flet.dev if you suspect unauthorized access to your account.
3.4 One account per person
You may not create multiple personal accounts to circumvent quotas, restrictions, free trials, or suspensions, except where we expressly permit it (for example, separate personal and team accounts).
3.5 Privacy
Information you provide when creating and using an account is processed in accordance with our Privacy Policy.
3.6 Communications
We send service and transactional emails about your account and the Service (for example, security notices, billing communications, free trial reminders, and notices of changes to these Terms and our Privacy Policy); you cannot opt out of these while you hold an account. We also email account holders about new Flet Studio releases. You can unsubscribe from release emails at any time using the unsubscribe link included in each of them.
4. Acceptable Use
You agree not to use Flet Studio to do any of the following, or to permit or encourage others to do so:
- Upload, create, transmit, or distribute content that is unlawful, infringing, defamatory, harassing, threatening, hateful, obscene, sexually explicit, or that promotes violence
- Send spam, conduct phishing, distribute malware, or engage in fraud
- Build, sign, publish, or distribute apps that are malicious or deceptive, that impersonate another person, company, or app, or that collect data from people without their knowledge
- Violate the intellectual-property, privacy, publicity, or other rights of any person or entity
- Impersonate any person or entity or misrepresent your affiliation with one
- Probe, scan, or test the vulnerability of the Service or circumvent any authentication, access control, or rate-limiting mechanism
- Reverse engineer, decompile, or disassemble any part of the Service, except to the extent applicable law expressly permits
- Use automated means (bots, crawlers, scrapers) to access the Service in ways that are not expressly authorized, or to extract data at a scale or rate that interferes with normal operation
- Exceed your assigned quotas, evade rate limits, build time limits, or credit metering, or otherwise consume disproportionate resources
- Use build machines for anything other than building your apps, or run cryptocurrency miners, proxies, network scanners, denial-of-service tooling, botnet clients, or any workload whose purpose is to abuse compute, storage, or network resources
- Send device registration links to people who have not agreed to test your app
- Use the Service in a manner that violates any applicable law, regulation, or third-party agreement (including the terms of an app store or developer program), or that violates export-control or sanctions laws
We may, but are not obligated to, investigate suspected violations and may take any action we consider appropriate, including stopping builds, disabling download pages, limiting features, removing content, or suspending or terminating your account.
5. User Content and License Grant
5.1 Ownership
"User Content" means the source code, files, project metadata, store listings, build settings, the app packages and other files produced by your builds ("build files"), and any other materials you create, upload, or store using Flet Studio. You retain all ownership rights in your User Content. Nothing in these Terms transfers ownership of your User Content to us.
5.2 License to AppVeyor
You grant AppVeyor, and the service providers acting on our behalf, a worldwide, non-exclusive, royalty-free, fully paid license to host, store, transmit, display, copy, build, sign, and execute your User Content solely as needed to operate and provide the Service to you, including making backups, performing maintenance, and enabling features you have requested, such as building your apps, signing them, uploading them to the stores you choose, publishing them on download pages, and committing them to the GitHub repositories you connect. The license is limited to these operational purposes; it is not a license to publish, monetize, or repurpose your User Content.
This license terminates when you delete the relevant User Content or close your account, except that we may retain copies in routine backups for a limited period and as required by law, as described in our Privacy Policy.
5.3 No publication or sharing without your instruction
AppVeyor will not publish, share, or redistribute your User Content, or make it publicly available, except as you explicitly direct us to do. Features that do this at your direction include:
- Public apps, whose source code anyone can view
- Download pages, whose builds anyone with the link can download
- Store publishing, which sends your app, its listing, and its build files to the store you choose
- GitHub sync, which commits your app's files to the repository you connect. A public app can only sync with a public repository.
This commitment applies regardless of any other clause in these Terms.
5.4 Your responsibility
You are solely responsible for your User Content and for the apps you build, sign, and distribute with the Service, including their legality and your right to use and distribute them. You represent and warrant that you have all rights necessary to grant the license in Section 5.2, and that your User Content does not violate the Acceptable Use restrictions in Section 4.
5.5 Copyright complaints
If you believe content on Flet Studio infringes your copyright, send a notice to legal@flet.dev that includes:
- A physical or electronic signature of the rights holder or authorized representative
- Identification of the work claimed to have been infringed
- Identification of the allegedly infringing material with enough detail to locate it
- Your contact information (address, telephone number, email)
- A statement that you have a good-faith belief that the use is not authorized
- A statement, under penalty of perjury, that the information in the notice is accurate and that you are authorized to act for the rights holder
We will respond to valid notices in a manner consistent with applicable copyright law and may remove allegedly infringing material and terminate the accounts of repeat infringers.
6. AI Features
Flet Studio includes an AI agent that can read, generate, and modify your app code based on your instructions.
Third-party model providers. To generate responses, your prompts, conversation history, app file contents (including images), and basic profile information (your name, email address, and username) are sent to third-party AI model providers, as described in our Privacy Policy.
AI output. AI output is generated automatically. It may be inaccurate or incomplete, and generated code may not work or may contain security issues. You are responsible for reviewing and testing AI output before relying on it. AI output stored in your apps is treated as your User Content under Section 5.
Builds proposed by the agent. The agent can propose a build or a publishing run. It starts only when you confirm it, and it is charged like any other build (Section 8.3).
Credits. AI usage consumes credits, metered by model token usage at the rates displayed within the Service (see Section 8).
Your use of AI features is subject to Section 4 (Acceptable Use); you may not use them to generate unlawful or malicious content or attempt to circumvent usage metering.
7. Builds, Signing, and Publishing
7.1 Your developer accounts
Publishing uses your own accounts with Apple, Google, Microsoft, and GitHub, and their terms apply to your use of them, for example the Apple Developer Program License Agreement, the Google Play Developer Distribution Agreement, and the Microsoft Store App Developer Agreement. AppVeyor is not a party to those agreements. You are responsible for keeping those accounts in good standing and for everything you submit through them, including your app's store listing, privacy and data-safety disclosures, content ratings, export-compliance answers, and the outcome of store review.
7.2 Your credentials
To sign and publish your apps, you can store credentials in Flet Studio, such as Android keystores and their passwords, Apple API keys and certificates, Google Play service accounts, Microsoft app secrets, and GitHub authorizations. You authorize us to store them and to use them only to perform the actions you request. We encrypt them as described in our Privacy Policy. You can delete them at any time, and they are deleted with your account. A deleted credential stops being used right away; encrypted copies can remain in our backups for up to 90 days. You can also revoke them with the provider that issued them.
Keep your own backup of your Android upload keystores, including any keystore Flet Studio created for you, and of any other signing key you cannot easily replace. If a key is lost, you may be unable to publish updates to an app, and AppVeyor is not liable for that loss (see Section 12).
7.3 Builds
Each build runs in its own virtual machine, on computers that we operate or rent, and the virtual machine is deleted when the build ends. A build receives your app's files, build settings, and the signing material it needs. We may stop a build that exceeds its time limit or its credits (Section 8.3), or that violates Section 4. Build logs and build files are kept for the period your plan provides and then deleted (see our Privacy Policy). Keep your own copy of any build file you need to keep longer.
7.4 Download pages
A download page is public: anyone with its link can open it and download the builds published on it. Releases on a download page expire after the period your plan provides; an expired release can no longer be downloaded. A download link is not access control: anyone who has it can use it. Anyone can report a download page to us. We may disable or remove a download page, or a release on it, that we believe violates these Terms.
When you send device registration links to iOS testers, the identifiers of the devices they register (UDID, model, and name) are sent to your Apple Developer account. You are responsible to your testers for that use of their information.
7.5 GitHub sync
When you connect an app to a GitHub repository, changes are synced in both directions: changes you make in Flet Studio are committed to the repository, and changes pushed to the repository are brought into Flet Studio. A change from GitHub can replace edits in Flet Studio to the same files that have not been committed yet. Edits replaced in this way cannot be recovered in Flet Studio, so commit work you want to keep and keep your own backups of your repositories. AppVeyor is not responsible for changes made to your repository by others, or for edits replaced in this way.
7.6 Third-party platforms
App stores, developer programs, and GitHub are operated by third parties that may change their requirements, APIs, or terms, reject or remove your app, or suspend your account at any time. AppVeyor does not control them and is not responsible for their actions.
8. Plans, Billing, and Payments
8.1 Plans
Flet Studio is offered under a free plan (Explorer) and one or more paid plans (currently Creator). Paid plans can be billed monthly or annually. Some features are available only on paid plans, such as private apps, store publishing, paid code signing, and GitHub sync. The current plans, their features, limits, and retention periods, and their prices, together with the price of credit packs, are listed on our pricing page. We may change plan limits and pricing with reasonable advance notice; where we materially reduce a limit, we will provide notice through the Service or by email. A price change for a subscription takes effect at the start of a subsequent billing period, never during a period you have already paid for; for annual subscriptions, the renewal notice (Section 8.5) states the new price.
8.2 Credits and credit packs
Credits are one balance that pays for both AI usage (Section 6) and builds (Section 8.3). Your plan includes a monthly credit allowance. Monthly plan credits reset each month, including on annual billing, and do not roll over.
Credit packs are one-time purchases available on every plan. Credits purchased or granted on or after September 24, 2026 expire 12 months after they are added to your account, unless a shorter period is stated when they are granted (for example, for bonus or promotional credits); credits added before that date do not expire while your account remains active. When you use credits, those closest to expiry are used first. Credits have no cash value and are not transferable. Purchased credits stay in your account when you change plans. Unused credits end when your account is closed, except as provided in Section 8.7.
8.3 Build charges
Each type of build machine has a rate in credits per minute, shown in the Service before you start a build.
- Starting a build requires enough credits for its minimum charge (currently 4 minutes).
- The minimum is charged when the build machine starts working on your build. Time spent waiting in the queue and preparing the machine is not charged, so a build cancelled before it starts costs nothing.
- After the minimum, each minute is charged as it begins. For example, a build that runs for 6 minutes and 10 seconds is charged 7 minutes.
- If a minute cannot be paid, the build is stopped. Credits already charged for it are not returned.
Charges for builds that have started are not refunded, including builds that fail because of the app, its settings, or a third-party service. If you believe a build failed because of our infrastructure, contact us at hello@flet.dev; we may, at our discretion, return the credits it used.
8.4 Free trial
We may offer a free trial of a paid plan. The current trial gives 7 days of Creator and requires a payment card.
- One free trial is available per account and per payment card, and not to accounts that have had a paid subscription before.
- During the trial you have every Creator feature, plus any bonus credits stated with the offer. Your monthly credit allowance stays at Explorer's until your first payment.
- At the end of the trial, it turns into a paid subscription and your card is charged, unless you cancel before the trial ends. The subscription is the plan and billing period (monthly or annual) you chose when you started the trial, at the price shown at checkout. Cancelling during the trial, in the billing portal in your account settings, costs nothing.
- If you choose to start your plan before the trial ends, the trial ends at that moment and your card is charged right away.
- We email you a reminder before the trial ends.
We may refuse or end a free trial that we believe abuses this offer, for example a repeat trial under another account.
8.5 Payment processing
Payments are processed by our third-party payment processor, Stripe. By making a purchase you agree to Stripe's terms applicable to the payment. Your card details are collected by Stripe directly and are not received or stored by AppVeyor. Paid plans are billed in advance and renew automatically at the end of each billing period (monthly or annual) until cancelled. You can manage or cancel your subscription at any time, without any fee, through the billing portal in your account settings; cancellation takes effect at the end of the current billing period, and you retain paid-plan features until then. Before an annual subscription renews, we email you a renewal notice 30 to 60 days ahead, with the renewal date and price, how to cancel, and the fact that it renews if you do nothing. Switching from monthly to annual billing takes effect immediately, with the unused part of your current month credited toward the annual charge; switching from annual to monthly billing takes effect at the end of the paid annual period. When a subscription ends, your account reverts to the free plan and its limits.
8.6 Taxes
Prices shown do not include taxes. Applicable sales tax will be calculated based on your billing address and itemized at checkout.
8.7 Refunds
We do not refund monthly or annual subscription payments, except as described in this section. When you cancel, downgrade, or switch billing periods before the end of a paid period, no money is returned and you keep paid-plan features until that period ends. Credit packs and build charges are likewise non-refundable, and unused or expired credits are not redeemable for cash. The exceptions are:
- A free trial cancelled before it ends is never charged.
- Cancelling soon after an annual renewal: if you cancel an annual subscription within 30 days after it renews automatically, we refund the unused part of the renewed year, prorated by days, within 15 days of your cancellation. Later cancellations, and the first year of an annual subscription, are not refunded unless applicable law requires it.
- If we end the Service or your account without cause: if we discontinue the Service, or close your account under Section 10.2 for a reason other than your breach of these Terms, abuse, a security risk, or a legal requirement, we refund the unused part of your prepaid subscription, prorated by days, and the price of unused purchased credits.
- Where applicable law requires a refund, including consumer protection law where you live.
8.8 Non-payment and plan changes
If a payment for your subscription fails, our payment processor retries it over the following days and you are notified by email. If it still cannot be collected, your subscription is cancelled and your account moves to the free plan.
When your account moves to a plan with fewer features, your content is kept, but features of the previous plan stop: for example, GitHub sync pauses and store publishing becomes unavailable. The new plan's limits and retention periods apply from then on, so older build logs, build files, and download page releases may be deleted sooner.
9. Service Availability and Modifications
We strive to keep Flet Studio available and performant, but the Service is provided without any uptime or availability guarantee. We may perform scheduled or emergency maintenance, suspend access to all or part of the Service, or modify, deprecate, or discontinue features at any time.
Where a change materially and adversely affects how you use the Service, we will use commercially reasonable efforts to provide advance notice through the Service or by email. If we discontinue the Service, Section 8.7 describes the refund.
10. Suspension and Termination
10.1 Termination by you
You may stop using Flet Studio at any time. You may delete your account by emailing legal@flet.dev from the email address associated with your account.
10.2 Suspension or termination by AppVeyor
We may suspend or terminate your access to all or part of the Service:
- Immediately, if we reasonably believe you have breached these Terms, your account presents a security risk, you are abusing the Service, or we are required to do so by law
- With reasonable notice, for any other reason, in which case Section 8.7 describes the refund
10.3 Effect of termination
Upon termination, your right to use the Service ends immediately. Your stored credentials are deleted, your GitHub connections are removed, and your download pages stop serving. We will handle your account data and User Content in accordance with our Privacy Policy, which provides that account data and User Content are deleted or anonymized within 30 days of a deletion request, subject to backups and legal retention requirements.
10.4 Survival
The following sections survive termination of these Terms: Section 5.1 (Ownership), Section 5.4 (Your responsibility), Section 7.1 (Your developer accounts), Section 7.6 (Third-party platforms), Section 8.3 (Build charges), Section 8.7 (Refunds), Section 11 (Disclaimers), Section 12 (Limitation of Liability), Section 13 (Indemnification), Section 14 (Governing Law and Dispute Resolution), and Section 15 (General Provisions), together with any other provision that by its nature should survive.
11. Disclaimers
THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, APPVEYOR DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, ACCURACY, QUIET ENJOYMENT, AND ANY WARRANTIES ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.
WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR FREE OF HARMFUL COMPONENTS, OR THAT ANY CONTENT (INCLUDING YOUR USER CONTENT) WILL BE PRESERVED WITHOUT LOSS. WE DO NOT WARRANT THAT ANY BUILD WILL SUCCEED, THAT ANY APP STORE WILL ACCEPT OR KEEP YOUR APP, OR THAT THIRD-PARTY PLATFORMS WILL CONTINUE TO WORK WITH THE SERVICE. YOU ARE SOLELY RESPONSIBLE FOR THE CODE AND APPLICATIONS YOU CREATE WITH FLET STUDIO, FOR HOW YOU DISTRIBUTE THEM, AND FOR THE CONSEQUENCES OF RUNNING THEM.
Some jurisdictions do not allow the exclusion of certain warranties, so some of the above exclusions may not apply to you.
12. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:
- No indirect damages. APPVEYOR WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, GOODWILL, OR DATA, ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE SERVICE, EVEN IF APPVEYOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
- Aggregate cap. APPVEYOR'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR IN CONNECTION WITH THESE TERMS OR THE SERVICE WILL NOT EXCEED THE GREATER OF (a) THE AMOUNTS YOU PAID TO APPVEYOR FOR THE SERVICE IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM, OR (b) ONE HUNDRED CANADIAN DOLLARS (CA$100).
- Data loss. APPVEYOR IS NOT LIABLE FOR ANY LOSS, ALTERATION, OR DESTRUCTION OF YOUR USER CONTENT, BUILD FILES, OR STORED CREDENTIALS (INCLUDING SIGNING KEYS), EXCEPT TO THE EXTENT CAUSED BY APPVEYOR'S BREACH OF THESE TERMS, GROSS NEGLIGENCE, OR WILFUL MISCONDUCT, OR WHERE THAT LIABILITY CANNOT LAWFULLY BE EXCLUDED. YOU ARE RESPONSIBLE FOR MAINTAINING YOUR OWN INDEPENDENT BACKUPS.
These limitations apply regardless of the legal theory on which a claim is based (contract, tort, statute, or otherwise) and apply even if a remedy fails of its essential purpose. Some jurisdictions do not allow the exclusion or limitation of certain damages; in those jurisdictions, the above limitations apply to the maximum extent permitted by law.
13. Indemnification
You agree to defend, indemnify, and hold harmless Appveyor Systems Inc., its affiliates, and their respective officers, directors, employees, and agents from and against third-party claims, and the resulting damages, losses, liabilities, costs, and expenses (including reasonable legal fees), arising out of or related to:
- Your User Content
- The apps you build, sign, publish, or distribute with the Service
- Your use of the Service in violation of these Terms or applicable law
- Your breach of these Terms or of the terms of a third-party platform you publish to
- Your violation of any intellectual property, privacy, or other rights of a third party
We will notify you promptly of a claim covered by this section and give you reasonable cooperation, at your expense. You may not settle a claim in a way that admits fault for us or imposes obligations on us without our written consent. We may, at our option, assume the exclusive defense and control of any such matter, in which case you agree to cooperate with our defense.
14. Governing Law and Dispute Resolution
These Terms, and any dispute or claim arising out of or in connection with them or their subject matter (including non-contractual disputes or claims), are governed by the laws of the Province of British Columbia and the federal laws of Canada applicable therein, without regard to conflict-of-laws principles.
You and AppVeyor each consent to the exclusive jurisdiction of the courts located in the Province of British Columbia, Canada for the resolution of any dispute arising out of or relating to these Terms or the Service, and you waive any objection based on inconvenient forum.
These Terms do not require mandatory arbitration, and nothing in these Terms is intended to waive your right to participate in a class action where applicable law would otherwise permit one.
15. General Provisions
15.1 Entire agreement
These Terms, together with the Privacy Policy and any additional terms you accept at the time of purchasing a paid feature, constitute the entire agreement between you and AppVeyor concerning the Service and supersede all prior or contemporaneous agreements on the same subject.
15.2 Severability
If any provision of these Terms is held to be invalid or unenforceable, that provision will be enforced to the maximum extent permissible, and the remaining provisions will remain in full force and effect.
15.3 No waiver
Our failure to enforce any right or provision of these Terms will not be deemed a waiver of that right or provision.
15.4 Changes to these Terms
We may modify these Terms from time to time, including the Service's features, plan features and limits, prices, credit and build rates, and retention periods. When we make material changes, we will update the "Effective date" above and notify you by email, and through the Service, at least 30 days before the changes take effect, except for changes required by law or to address security risks. A change will not take away a cancellation or refund right for a billing period you have already paid for; for a paid subscription, it applies from your next billing period. If you do not agree to a change, you can cancel your subscription and stop using the Service before it takes effect. Otherwise, your continued use of the Service after the new Terms take effect constitutes acceptance.
15.5 Assignment
You may not assign or transfer these Terms or your account without our prior written consent. We may assign these Terms to an affiliate or in connection with a merger, acquisition, reorganization, or sale of assets, on notice to you.
15.6 Relationship of the parties
Nothing in these Terms creates a partnership, joint venture, agency, employment, or fiduciary relationship between you and AppVeyor.
15.7 Force majeure
Neither party will be liable for failure or delay in performance caused by events beyond its reasonable control, including acts of God, war, terrorism, civil unrest, labor disputes, internet or telecommunications outages, failures of third-party platforms, governmental actions, or epidemics.
15.8 Notices
We may give notices to you through the Service, by posting on our website, or by email to the address associated with your account. Renewal notices, notices of changes to these Terms, and other notices the law requires us to deliver to you are sent by email. You must give notices to us in writing at legal@flet.dev.
15.9 Contact
Appveyor Systems Inc. Email: legal@flet.dev