Skip to content

Free, no account needed

Free terms and conditions generator for apps

Generate plain-language terms of use for your mobile app, in English or French. Copy them, or host them at a stable URL you can link from your paywall and your App Store description.

  • Can people create an account?
  • Does it collect usage analytics?
  • Does it show ads?
Language of the page
Host it on AppTap with Pro

Get it at apptap.me/yourapp/terms, ready to paste into App Store Connect and Play Console.

Preview

Terms of Use

Accepting these terms

By using Your app you agree to these terms. If you do not agree, please do not use the app.

Using the app

Your app is provided for personal use, for the purpose described in its store listing.

What we ask of you

You agree to:

  • Use the app within the law
  • Not reverse engineer or modify the app
  • Not use the app for anything unauthorised or illegal
  • Respect intellectual property rights

Intellectual property

The app and everything in it, from text and design to features, remain ours and are protected by copyright. Your use of the app is personal and non-commercial.

No warranty

Your app is provided as is. We cannot promise it will run without interruption or without fault, or that it will suit a particular purpose.

Liability

To the extent the law allows, we are not liable for damages arising from your use of the app.

Changes to these terms

We may update these terms. Continuing to use the app after a change means you accept the new version.

Contact

For questions about these terms, contact the developer through the app's store listing.

Does your app need terms and conditions?

Not every app does. On the App Store, Apple's standard end user license agreement (EULA) applies to every app by default, in every country and region. Google Play has no terms field at all. A simple utility with no accounts and nothing to sell can live without its own terms.

Three situations change that:

  • Auto-renewable subscriptions. Apple's rejection notices under guideline 3.1.2 ask for a functional link to the Terms of Use (EULA) both in the app and in your App Store metadata. In practice, that means a link on the paywall and one in your description.
  • User-generated content. When people can post in your app, Apple's guideline 1.2 rejections ask that users agree to terms making clear there is no tolerance for objectionable content or abusive users. Google Play's user-generated content policy also requires users to accept your terms of use or user policy before they can create or upload content.
  • Accounts and paid features. Terms are where you set the rules: what people may do with the app, what you can do when they break those rules, and what you are not responsible for.

A terms and conditions generator for apps gives you a sensible base for all three. You then add the clauses that are specific to your business.

Apple's standard EULA or your own terms?

On the App Store side, you have two options:

Apple's standard EULA Your own terms
Setup Nothing to do, it applies by default A custom EULA in App Store Connect, or a terms page you publish and link
What it covers The license to use the app, in general terms Your service, your rules, your subscription and content policies
On your App Store page No license agreement link A link appears when you add a custom EULA
With subscriptions Link to Apple's standard EULA in your description Link to your terms in your description, or use the custom EULA field

The custom EULA lives in App Information, next to License Agreement. It is plain text only (formatting is stripped), it applies to the countries or regions you select, and Apple's standard EULA covers the rest.

If your terms are short and you want them readable on the web too, a hosted terms page linked from your description and your paywall is the simplest route. You can update the text without touching App Store Connect, and the same page serves your Android version.

What the generated terms cover

The generator above writes short, readable terms around your app name and contact email:

  • Accepting the terms: using the app means agreeing to them.
  • Using the app: personal use, for the purpose described in the store listing.
  • What you ask of users: use the app within the law, don't reverse engineer or modify it, don't use it for anything unauthorised, respect intellectual property.
  • Intellectual property: the app and its content remain yours.
  • No warranty: the app is provided as is.
  • Liability: excluded to the extent the law allows.
  • Changes to the terms, and how users accept them.
  • Contact: where to send questions.

They deliberately leave out what depends on your business model:

  • Subscriptions: what's included, price and renewal, and how to cancel through the App Store or Google Play.
  • User content: what people may post, the licence you need to display it, a clear ban on objectionable content and abusive behaviour, and what happens when someone breaks the rules.
  • Refunds, commercial use and governing law.

If any of these apply, copy the generated text, add your clauses, and publish the result as your own text.

Where to link your terms

Terms only work if people can find them before they agree to anything:

  • On the paywall, next to the subscribe button, together with your privacy policy.
  • On the sign-up screen, if your app has accounts.
  • In settings or on the about screen, next to the privacy policy.
  • In your App Store description, if you sell auto-renewable subscriptions and don't use the custom EULA field.

Google Play has no field for terms, so link them from inside the app and from your support page.

Wherever the link sits, it has to keep working. A paywall link that 404s after you rebuild your website is exactly the kind of thing App Review notices. Hosting your terms on AppTap gives you apptap.me/yourapp/terms, next to your privacy policy and support pages, with text you can update while the URL stays the same. The generated terms open in English or French, depending on the visitor's language.

Before you rely on them

Generated terms are a starting point, not legal advice. Consumer protection rules in many countries limit what terms can exclude, which is why the liability clause applies only "to the extent the law allows". If you sell to businesses, take payments outside the stores or run a marketplace, have your terms reviewed.

Terms don't replace a privacy policy either. Both stores require a privacy policy for every app, while terms are optional. Start with the privacy policy generator if you haven't yet, and check the App Store submission links checklist for every other URL the stores ask for. Hosting is free for one app: get started.

Questions

Not by default. Apple's standard EULA applies to every app unless you provide your own, and Google Play has no terms field. Subscriptions and user-generated content are the usual reasons to publish your own.

On iOS, yes in practice. App Review asks for a working Terms of Use (EULA) link in the app and in the metadata, which can point to your own terms or to Apple's standard EULA.

Terms set the rules for using the app. A privacy policy explains what data the app collects and what happens to it. Both stores require a privacy policy for every app, while terms are optional.

Yes. One set of terms at one URL works for both, as long as it explains how subscriptions are managed on each store if you sell them.

Yes. Generating and copying the text is free. Hosting it at apptap.me/yourapp/terms is part of Pro, from $4 a month billed yearly.

Your app’s links, sorted before lunch.

Free for your first app. No card, no code, nothing to host.