Terms of service are the page nobody reads and every app needs. Founders usually think about them the night before submitting to the App Store, copy a template, swap in their app's name, and hope for the best. That works until a user disputes a charge, a reviewer flags your subscription screen, or someone posts something on your app that you would rather not be responsible for. Good terms of service for an app are not about legal decoration. They set the rules of the relationship with your users and protect you when something goes wrong.
This guide explains in plain language why terms matter, what they should cover, the special rules for subscription apps, and how to get a solid version without a big legal bill. It is general information, not legal advice. Laws differ by country and change over time, so for anything important, especially if you handle health data, payments outside the stores, or content created by users, have a lawyer review your final version.
Terms of service vs privacy policy
These two documents are often confused, and you usually need both.
- The privacy policy explains what personal data you collect, why, who you share it with, and what rights users have. It is required by law in many places and by both app stores.
- The terms of service, also called terms of use, terms and conditions, or an end user license agreement (EULA), set the rules for using your app: what users may and may not do, how payments work, what you are and are not responsible for, and what happens in a dispute.
The privacy policy is about data. The terms are about the relationship. Link to both from your app, your website, and your store listing.
Why you need terms at all
The stores expect them for many apps. Subscription apps in particular must link to their terms of use and privacy policy in the app and in the store metadata. A missing or broken link is a common, avoidable reason for rejection.
They set expectations about payments. Clear terms about billing, renewals, trials, and refunds reduce disputes and give you something to point to when a user asks why they were charged.
They limit your liability. No app is perfect. Terms can state that the app is provided as is, limit how much you can be held responsible for, and exclude certain kinds of damages, within the limits the law allows.
They let you act against misuse. If someone abuses your app, harasses other users, or tries to break it, your terms give you a clear right to suspend or close their account.
What to include
Every app is different, but most terms of service for an app cover the following sections.
Who you are and acceptance
Name the legal entity or person providing the app, how to contact you, and how users accept the terms. For most apps, users accept by creating an account or using the app. Showing the terms at sign-up with a clear link, and ideally a checkbox or an explicit statement, makes acceptance much stronger than a link hidden in a menu.
Eligibility and accounts
State the minimum age and any other requirements. If your app is not meant for children, say so clearly, and make sure that matches your store age rating and privacy policy. Explain that users are responsible for their account and password, and for keeping their information accurate.
License to use the app
Explain that you grant users a personal, limited, revocable permission to use the app, and that you keep ownership of the app and its content. This is the core of what a EULA does.
Acceptable use
List what users must not do: break the law, harass others, try to hack or reverse engineer the app, scrape data, spam, or use the app in ways that harm other users or your service. Keep it short and readable.
User content
If users can post, upload, or share anything, such as photos, comments, profiles, or messages, you need a section on it. Typically users keep ownership of what they create, but grant you the permission you need to store, display, and process it to run the app. Explain that you may remove content that breaks the rules, and give users a way to report problems. Apps with significant user content have extra obligations in many places, and Apple's guidelines require a way to report and block abusive content, so this area is worth legal review.
Payments and subscriptions
Describe what is paid, how billing works, and how cancellations and refunds are handled. More on this below, because subscription apps have specific rules.
AI features
If your app uses AI to generate text, images, advice, or recommendations, say so, and explain that outputs may be inaccurate and should not be relied on as professional advice. If user inputs are processed by third-party AI providers, make sure your privacy policy explains that too.
Disclaimers and limitation of liability
State that the app is provided as is, without guarantees that it will always work or be error free, and limit your liability to the extent the law allows. Be careful here: many countries, especially in Europe, do not allow businesses to exclude certain consumer rights, and overreaching clauses may simply be unenforceable. If your app touches health, fitness, finance, or mental wellbeing, include a clear statement that it is not a substitute for professional advice.
Termination
Explain that users can stop using the app and delete their account at any time, and that you can suspend or close accounts that break the terms. Describe what happens to their data and any active subscription when an account is closed.
Changes to the terms
Say how you will notify users of meaningful changes, such as by email or an in-app message, and when they take effect.
Governing law and disputes
State which country's or state's law applies and how disputes are handled. Some consumer protection laws let users bring claims where they live regardless of what your terms say, so treat this section as a default, not a guarantee.
Special rules for subscription apps
If your app sells subscriptions, your terms and your paywall have to work together. Both app stores require that users understand exactly what they are buying before they subscribe. In practice, your paywall should show the subscription name and length, what it includes, the full renewal price, and how a free trial converts, plus links to your terms and privacy policy.
Your terms should then explain, in plain language:
- That subscriptions renew automatically until cancelled, and how far in advance of the renewal date users must cancel to avoid the next charge.
- Who handles billing. For in-app purchases, payment is processed by Apple or Google, charged to the user's store account, and managed or cancelled in their store account settings, not inside your app.
- How free trials work, including when the trial converts and what happens to any unused trial time if the user subscribes early.
- How price changes are handled. The stores have their own rules for notifying subscribers and, in some cases, asking for consent. Your terms should not promise anything that conflicts with them.
- Refunds. For store purchases, refunds are generally handled by Apple or Google under their policies. Do not promise refunds you cannot process yourself.
Beyond the stores, many places have laws on automatic renewals that require clear disclosure, consent, and an easy way to cancel. California's automatic renewal law is a well known example, and rules at the federal level in the United States and in other countries have been changing. If you sell subscriptions on the web, outside the app stores, these laws apply to you directly, so get proper advice.
Apple's standard EULA vs your own terms
Apple provides a standard license agreement that applies to apps by default. If you do not upload a custom one, Apple's standard EULA covers the basic license between you and the user. That is helpful, but it is generic. It does not cover your subscription details, your content rules, your AI features, or your account policies.
Many developers keep Apple's standard EULA and publish their own terms of use on their website, linked from the app, the paywall, and the App Store description, where reviewers check for it on subscription apps. Google Play does not provide an equivalent standard agreement, so your own terms do that job there.
How to get your terms without a big bill
Start from a reputable generator or template. Several services generate terms tailored to apps based on a questionnaire. They are a reasonable starting point for a simple app.
Edit them so they match reality. The biggest risk with templates is that they describe a different app. Remove sections that do not apply, add the ones that do, and make sure every promise in the document is something you actually do.
Get a review when the stakes rise. Before you handle sensitive data, take payments outside the stores, host significant user content, or start growing quickly, pay a lawyer for a review. A focused review of an existing draft costs far less than writing from scratch.
Keep versions. Date every version and keep a copy of old ones, so you know which terms applied to which user at which time.
Common mistakes
- Copying another company's terms
- Terms that promise things the app does not do, like refunds you cannot issue
- A privacy policy and terms that contradict each other
- No working link in the app or on the paywall
- Ignoring user content and AI features because the template did not mention them
- Never updating the terms as the app changes
The bottom line
Terms of service for an app do not need to be long or intimidating. They need to be accurate, readable, and easy to find. Cover who you are, how the app may be used, how payments and subscriptions work, what happens to user content, and the limits of your responsibility. Make sure your paywall and terms tell the same story, link them everywhere the stores expect, and update them as your app grows. An afternoon spent on this now saves far more time when the first difficult situation arrives.
Launch with the paperwork already handled
Foundyra is the AI cofounder for non-technical founders: it validates your idea, then builds and launches your app with you, including the store requirements, policies, and launch checklist.
Get Foundyra →