Terms of Service

Draft for human and legal review. Wording in square brackets is a placeholder that must be filled in before this page is published. See docs/legal-stance.md for the list of open points.

1. Who we are and what this agreement covers

AppFoyer (“AppFoyer”, “we”, “us”) is operated by [Operator legal name], [legal form and registration number], [registered address] (the “Operator”).

These Terms of Service (the “Terms”) govern your use of:

• the AppFoyer dashboard at app.appfoyer.com, including its API and the /mcp endpoint used by coding agents;
• the AppFoyer Claude Code plugin and any other client we publish;
• the public web pages we host for your apps on appfoyer.page subdomains (each a “Hosted Site”); and
• the website appfoyer.com

(together, the “Service”).

The Terms, together with our Privacy Policy and Refund Policy, are the whole agreement between you and us about the Service. If you purchase a paid plan, the purchase itself is also subject to the terms of our payment partner (see section 10).

2. Accepting these Terms

You accept these Terms by ticking the acceptance box in the dashboard after signing up. We record the date, the version you accepted and the IP address from which you accepted it. If we later change the Terms in a way that requires new consent, you will be asked to accept the new version the next time you sign in, and the dashboard, API and agent endpoint remain unavailable until you do.

To use the Service you must be at least 18 years old (or the age of majority where you live, if higher) and able to enter into a binding contract. If you use the Service on behalf of a company or another legal entity, you confirm that you are authorised to bind that entity, and “you” then means that entity.

The Service is a business tool for people who publish mobile applications. It is not intended for consumers or for personal, household use.

3. Your account

• Identity. You sign in through a third-party identity provider (email and password, Google, or X). We never receive or store your password. You must use an email address you control and keep it verified; account notices are sent there.
• One person, one account. Do not share your sign-in or your session with others. Each account holder is responsible for everything done through their account, including actions taken by a coding agent using one of their API keys.
• API keys. Keys you create in the dashboard are credentials. Keep them secret, rotate them if you suspect exposure, and revoke keys you no longer use. A key can draft content but can never publish a page: publishing is always a human action in the dashboard.
• Accurate information. The app name, developer name, support email and store links you enter are shown publicly on your Hosted Site and are used by our trust and abuse checks. They must be true and must describe a real app that you publish or are authorised to represent.

4. What the Service does

For each app you add, AppFoyer gives you a Hosted Site with a home page, privacy policy, terms of service, support page and account-deletion request page, plus an app-ads.txt file, all served from a subdomain of appfoyer.page over HTTPS. Hosted Sites are delivered from a global content-delivery network with locations around the world, so they load quickly for users wherever your app is distributed.

Other parts of the Service include a compliance checklist, page templates and a template generator, notification channels for account-deletion requests, optional store-listing verification, and an agent path (skill + MCP endpoint) that lets a coding agent draft your pages from your app’s codebase for you to review and publish.

Beta features. Features marked Beta in the dashboard (none at the effective date) are provided for evaluation. They may change or be withdrawn, and we do not promise that any ad network or store will accept them. Do not rely on a Beta feature for a store submission without checking the result yourself.

Changes to the Service. We may add, change or remove features. We will not remove a feature that a store requires (the five pages and app-ads.txt) from the Free plan while the Service operates, except as described in section 17.

5. Templates are not legal advice

The page templates, the privacy-policy generator, the compliance checklist and every other piece of guidance in the Service are provided for convenience only and do not constitute legal advice. You are responsible for reviewing, completing and maintaining the accuracy of every page you publish, and for compliance with the app-store policies and laws that apply to you.

We do not know what your app actually does, which data it collects or where your users are. The templates are a starting point that you must adapt. We do not monitor store or advertising policies on your behalf, and a “done” checklist does not mean a store will accept your app.

Every generated legal page on a Hosted Site carries a visible disclaimer to this effect. You may not remove or obscure it.

6. Your content and your responsibility for it

“Your Content” means everything you (or an agent acting for you) put into the Service: page text, app-ads.txt lines, the app icon, app and developer names, store links and settings.

• You own Your Content. You grant us a worldwide, non-exclusive, royalty-free licence to host, store, cache, reproduce, render and deliver Your Content, and to make derivative copies (such as rendered HTML and cached versions) solely to operate, secure and improve the Service. The licence ends when Your Content is deleted from the Service, except for backup copies kept for the period described in the Privacy Policy and copies we must keep by law.
• You are solely responsible for Your Content: for its accuracy, for having the rights to publish it, for its compliance with the laws and store policies that apply to you, and for any claim that results from it. We host it; we do not endorse it and we do not review it for legal sufficiency.
• Your app is yours. Nothing in the Service makes us a party to the relationship between you and your app’s users, an app store, an advertising network or a regulator.
• Structural limits. Hosted Sites render Markdown only. Scripts, forms, embedded frames, external images and most external links are not rendered as such, by design. These limits protect everyone who uses the Service and cannot be lifted on request.

7. Acceptable use

You may use the Service only to publish truthful compliance pages for mobile apps that you publish or are authorised to represent. In particular, you must not use the Service to:

• Deceive. Phishing, credential or payment harvesting, impersonating any company, brand, app store, government body, or AppFoyer itself, or presenting a Hosted Site as anything other than the developer page it is.
• Distribute harmful or unlawful software. Malware, spyware, cracked, pirated or repackaged apps, cheats, license-key generators, or links to any of these.
• Spam or manipulate. Link farms, doorway pages, SEO spam, mass-created apps that do not exist, or content whose purpose is to advertise something other than your app.
• Harm people. Content that is illegal where you or we operate, that infringes intellectual property, that harasses or threatens, that sexualises minors, or that promotes violence or discrimination.
• Misuse the platform. Circumventing rate limits, moderation or plan limits; scraping other Hosted Sites; probing or attacking the Service; reselling Hosted Sites as generic web hosting; submitting other people’s personal data to the Service without the right to do so; entering, or asking your users to enter, passwords, codes, card numbers or identity documents on a Hosted Site.

How we enforce this. Every publish passes an automated screening for the patterns above. If a page is held, nothing public changes: your live page stays as it was and you can fix the text. Where we find abuse, we may, at our discretion and depending on severity, hold a page, unpublish a page or an app, disable an app, or suspend or terminate your account — at best the offending page comes down; at worst your account is closed. In serious cases (phishing, malware, content harmful to children, legal orders) we act first and notify you afterwards, and we may report the matter to the relevant authorities or affected parties. Fees already paid are not refunded when an account is terminated for a breach of this section.

A page that was held or removed by mistake is restored when you tell us; a false positive delays publication, it never deletes anything. Contact abuse@appfoyer.com to report abuse on any Hosted Site, and support@appfoyer.com if you believe an action against your account was wrong.

8. Account-deletion requests are relayed, not fulfilled

Google Play requires a public URL where your users can ask you to delete their account. The account-deletion page on your Hosted Site collects such requests and notifies you on the channels you configure (email, Telegram or Slack). We store each request so that you have an audit trail.

We do not have access to your systems and we never delete anything in them. You alone are responsible for acting on each request within the time the law and the stores give you, and for telling your users what will happen. Our notifications are best-effort: we retry failed deliveries and show failures in your dashboard, but you should check the request list in the dashboard rather than rely on notifications alone. Requests are stored regardless of your plan or payment status.

9. Addresses on appfoyer.page

• Every app receives a permanent random address of the form app-xxxxxx.appfoyer.page. It never changes and is never given to anyone else.
• Paid plans may add a custom subdomain, subject to our naming rules (reserved words, brand names, structural words such as login or verify, and a requirement that the name relates to your app or company). A custom subdomain that you release, or that lapses when a plan ends, redirects to your permanent address and is never made available to another account, because an address that was ever printed in a store listing must not become someone else’s phishing page.
• You have no ownership of, or right to, any particular subdomain. We may reclaim or rename a subdomain that infringes a third party’s rights, is misleading, or is required by law, and we will redirect the old address to your permanent one where we can.

10. Plans, fees and payment

• Free plan. Everything a store requires — the five pages, app-ads.txt and the checklist — is available on the Free plan for one published app, without a card.
• Paid plans. Paid plans add capacity and convenience (more published apps, custom subdomains, additional notification channels). Current plans and prices are on the pricing page. Plan limits are applied by our servers when you publish, never by the app on your device.
• Merchant of record. Paid plans are sold by our payment partner, Paddle, acting as the merchant of record. Paddle handles the checkout, collects applicable taxes, issues your invoice and processes refunds. By purchasing you also agree to Paddle’s buyer terms, which are shown at checkout. No card data ever reaches our systems.
• Subscriptions renew automatically monthly or annually until cancelled. You can cancel at any time in one click from the customer portal linked in your dashboard; your plan remains active until the end of the period you paid for.
• Price changes. If we change the price of your plan, we will tell you by email at least 30 days before the new price applies to your next renewal. Where our pricing page says that early customers keep their price, we honour that through your account settings.
• Taxes. Prices are shown exclusive of VAT, GST or sales tax where the law allows; Paddle adds the applicable tax at checkout based on your location.

11. If a payment fails or a plan ends

Our rule is that non-payment is never punished with a store rejection. Pages above your plan’s limit do come down, but slowly, with warning, and never before the payment has genuinely failed.

While a payment is being retried, nothing changes at all. Our payment partner retries a failed charge for two to four weeks; no countdown of ours runs during that time. The timeline below starts only when the subscription is actually cancelled.

Situation	What happens
A renewal payment fails	Nothing changes, for as long as the payment is being retried. You see a banner in the dashboard and receive one email.
Your subscription is cancelled or expires — day 0	Your account returns to the Free plan. You choose which one app stays published; if you do not choose within 7 days, your most recently published or edited app stays. The app-ads.txt file of every other app stops being served immediately.
Day 7	Apps above the Free limit become frozen: their pages stay online but cannot be edited or republished.
Day 21	Frozen apps are unpublished — with one exception, below. Nothing is deleted; subscribing again brings everything back with one publish.
Reminders	We email you on day 0, day 7 and day 18.
Account-deletion pages stay online	The /account-deletion page of an unpublished app remains available indefinitely, read-only and excluded from search engines. Requests submitted there are still stored and still emailed to you. Your users do not lose their route to you because of a billing problem.
Custom subdomains	Redirect permanently to the app’s random address and are reserved for you. Subscribing again re-claims them in one click.
Account-deletion requests	Always stored, on every plan and after unpublishing. Email notifications continue; Telegram and Slack pause.
Chargeback, or a refund we consider fraudulent	All your apps are unpublished immediately, without a grace period, and the account may be closed. Account-deletion pages still stay online.

app-ads.txt is treated differently from the five pages on purpose: it is required by advertising networks, not by an app store, so it is the one thing that stops at once. Nothing an app store requires of you is ever withdrawn for non-payment while your account exists.

12. Refunds

Our Refund Policy is part of these Terms. In short: a full refund, no questions asked, if you ask within 14 days of a charge.

13. “Verified” indicators

The Service may show that an app’s store listing was checked against the public store record (“listing verified”), or that we manually confirmed the listing matches the app and developer name (“Verified by AppFoyer”). These indicators mean only that the listing appears to exist and match the identity shown. They are not an endorsement of the app, its developer or its content, and they are removed automatically when the store link, name, developer or subdomain changes.

14. Our access to your account

Our operators may view, and where necessary edit, account data and Your Content to provide support you ask for, to investigate abuse reports, to keep the Service secure, and to comply with the law. Such access is logged. We do not read your content for any other purpose and we do not sell it.

15. Availability and support

We run the Service on redundant global infrastructure and aim to keep Hosted Sites available at all times, but we do not offer a guaranteed uptime level or service credits. Planned maintenance that affects the dashboard is announced in advance where practical; Hosted Sites are served as static files and are not normally affected by dashboard maintenance.

Support is provided by email at support@appfoyer.com on a best-effort basis. We cannot appeal or influence a decision by an app store or an advertising network on your behalf.

16. Ending your account

You may stop using the Service at any time. To close your account, email support@appfoyer.com from your account address (a self-service button in the dashboard will replace this). Closing your account takes all your Hosted Sites offline; if their URLs are still in a store listing, update the listing first. Your data is soft-deleted immediately and permanently removed within 30 days, as described in the Privacy Policy. Your permanent random subdomain, and any custom subdomain you held, are reserved and never given to another account.

We may suspend or terminate your account for a breach of these Terms (section 7), if we are required to by law, or if your account has been inactive and unpublished for more than 24 months — in the last case only after emailing you 30 days in advance.

17. If we shut the Service down

Your Hosted Site’s URL sits in a store listing that is slow to change, so we commit to the following if we ever decide to discontinue the Service. This commitment is the reason many developers can trust a hosted compliance page at all, and we treat it as binding.

1. Announcement. We announce the shutdown publicly on appfoyer.com and email every account holder at their account address. The announcement states the shutdown date, which is at least twelve months after the announcement.

2. Phase one — first three months. The Service continues to operate normally: Hosted Sites stay online, you can edit and republish pages, notifications continue and billing continues. The only change is that new apps and new sign-ups are disabled, so nobody starts a store submission on a URL that is going away.

3. Phase two — the following nine months. Hosted Sites remain online and account-deletion requests are still stored and relayed. The dashboard becomes read-only except for export and unpublish. No charges are made during this phase: subscriptions are not renewed, and any prepaid period that extends past the start of phase two is refunded pro rata through Paddle.

   Phase two is long because keeping the pages online is nearly free: they are static files served by a content-delivery network, with no application running behind them. What we cannot promise for a year is publishing — every publish is screened for impersonation and scams, and that screening needs people who will no longer be here. So during phase two your pages keep working and keep serving your store listing; they simply stop changing.

4. Export. From the day of the announcement until the shutdown date you can download an export of everything you put into the Service — the Markdown of every page, your app-ads.txt, your app settings and your account-deletion request log — from the dashboard, in open formats. If the dashboard export is unavailable for any reason we will send it to your account email on request.

5. Shutdown date. Hosted Sites go offline and Your Content is deleted within 30 days after, except where we must keep records by law. Subdomains are not transferred to anyone.

If the Service is transferred to another operator instead of being shut down, we will tell you at least 30 days before the transfer, and the new operator takes on this agreement and this section unchanged; you may export and close your account before the transfer if you prefer.

This section does not apply to the termination of an individual account under section 7 or 16, and we may be prevented from honouring it in full by events outside our reasonable control — a legal order, the loss of our infrastructure provider, or force majeure. In such a case we will do as much of the above as we lawfully and practically can, starting with the export.

18. Disclaimers

The Service is provided “as is” and “as available”. To the fullest extent permitted by law we disclaim all warranties, express or implied, including fitness for a particular purpose. In particular, we do not warrant that any app store, advertising network or regulator will accept a page, file or listing produced with the Service. AppFoyer is not affiliated with, endorsed by or acting on behalf of Apple, Google, or any app store or advertising network; their names are used only to describe what their consoles ask for.

19. Limitation of liability

To the fullest extent permitted by law, neither we nor the Operator are liable to you for any indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost data, or the rejection, suspension or removal of an app from a store, however caused. Our total liability to you for all claims arising out of the Service in any 12-month period is limited to the greater of the fees you paid us in those 12 months and [USD 50].

Nothing in these Terms limits liability that cannot be limited by law, including liability for death or personal injury caused by negligence, for fraud, or for wilful misconduct.

20. Indemnity

You will defend and indemnify us and the Operator against any claim, loss or expense (including reasonable legal fees) arising from Your Content, your app, your breach of these Terms, or your violation of any law or third-party right — for example, a claim by one of your users, an app store, an advertising network, a rights holder or a regulator about a page you published.

21. Changes to these Terms

We may change these Terms. For changes that affect your rights or obligations we will email you at least 14 days before they take effect and ask you to accept the new version at your next sign-in; until you accept, the dashboard, API and agent endpoint are unavailable but your Hosted Sites stay online. If you do not agree, export your content and close your account before the effective date. Corrections of typos, clarifications and changes required by law may take effect immediately and do not require new acceptance. The version you accepted is shown in your dashboard, and every version is preserved in the public change history of this website.

22. Governing law and disputes

These Terms are governed by the laws of [jurisdiction], without regard to its conflict-of-law rules. Disputes will be brought before the courts of [city, jurisdiction], unless mandatory law where you live gives you the right to a different forum. Before starting proceedings, please write to support@appfoyer.com; most issues are resolved within a few days.

23. General

If any provision of these Terms is found unenforceable, the rest remains in effect. Our failure to enforce a provision is not a waiver. You may not assign this agreement without our consent; we may assign it as described in section 17. Notices to you are sent to your account email; notices to us go to support@appfoyer.com or the Operator’s registered address.

24. Contact

• Support and account matters: support@appfoyer.com
• Abuse on a Hosted Site: abuse@appfoyer.com
• Operator: [Operator legal name, registered address]

---

Questions about this document: support@appfoyer.com. Previous versions are in the public change history of this site.