Privacy Policy generator for FlutterFlow apps

FlutterFlow makes it easy to ship a real native app without writing Dart — but the App Store and Google Play still expect a fully-compliant privacy policy before they'll approve the app. BaseTerms generates one that matches exactly what most FlutterFlow apps actually do, including Firebase, user accounts, and the monetization options FlutterFlow exposes out of the box.

What FlutterFlow apps typically collect

Most FlutterFlow projects use Firebase under the hood: Firebase Auth for sign-in, Firestore for data, Firebase Analytics for usage tracking, and Firebase Storage for user uploads. Many also use Google Mobile Ads or RevenueCat for monetization. All of these collect data categories that Apple and Google require you to disclose.

FlutterFlow also ships with a built-in integration for Algolia (search), Stripe (payments), and Branch (deep linking and attribution). Each of those adds its own data category — Stripe handles payment data directly, but Branch collects device identifiers for attribution, which needs disclosure.

Why the default FlutterFlow template isn't enough

FlutterFlow's built-in privacy policy template is a generic starting point but doesn't automatically update to match which Firebase services you've enabled. Apple's reviewers specifically check that the policy mentions every data category declared in App Store Connect, so a template that says 'we may collect data' without specifics often gets flagged. A generator that updates the policy text based on which services you toggled is a much safer default.

Using BaseTerms with FlutterFlow

In BaseTerms, toggle on analytics (Firebase Analytics), accounts (Firebase Auth), location if you use it, and ads/payments if your app monetizes. The generated policy references each service appropriately and is hosted at yourapp.baseterms.com/privacy. Paste the URL into App Store Connect and Play Console.

You can also paste the same URL into FlutterFlow's in-app settings screen so users can access the policy from inside the app — both stores prefer this, and it's required by some newer Google Play policies.

Common questions