Connect FlutterFlow
Turn on GitHub Integration in FlutterFlow, then connect that repository.
How the connection works
- Turn on syncPoint your builder at a GitHub repository so it pushes your generated code there.
- Connect that repoPick it in Poliogo — the scanner reads what the generated code really calls.
- Detection stays onRegenerate in your builder and the next scan picks up what changed.
What it looks like once connected
An illustration of this connection inside your Poliogo dashboard — not live data.
Detected in this project
- Firebase Authfirebase_auth in pubspec.yaml
- Cloud Firestorecloud_firestore in pubspec.yaml
- Stripeflutter_stripe in pubspec.yaml
- PostHognew since your last scan
Exact permissions requested
Every permission this connection asks for, named as FlutterFlow names it on its own consent screen — so you can compare this table to what you are shown.
| Permission | Grant | What it is used for |
|---|---|---|
| Contents | Read | Read manifests, source text and .env.example in the repositories you select. |
| Metadata | Read | List your repositories and their default branch so you can pick one. |
| Email addresses | Read | Identify your account when you sign in with GitHub. |
| Contents — branch + pull request | Write | Create a poliogo/* branch and open a pull request on it. Changes reach your default branch only through a pull request you approve. |
Setting it up
What you do, and what you will be looking at while you do it.
Turn on GitHub Integration
In FlutterFlow, enable GitHub Integration in your project settings and push your code to a repository.
Connect that repository
Press Connect below, install the GitHub App on it, and pick the repository FlutterFlow pushes to.
Check what it found
Poliogo reads pubspec.yaml alongside everything else, so Flutter packages are detected the same way npm ones are — and Firebase, which most FlutterFlow apps use, is picked up from its config.
Generate and publish
Your policies arrive as a pull request. A mobile app still needs a reachable privacy policy URL for the app stores, and the hosted Trust Center link gives you one.
Choose how to scan your app
Pick one. We scan your code and settings to find the services your app uses — the scan keeps that list, not your files.
In FlutterFlow: Settings → GitHub Integration, then pick that repository below.
Authorise on GitHub
Granted on GitHub's own screen — this panel can show it, never widen it.
Connect GitHubSelect repositories
What Poliogo detects from FlutterFlow
The right-hand column is the part worth reading: it is what this connection cannot reach even if we wanted it to.
What it reads
- Dependency manifests — package.json, requirements.txt, Cargo.toml, go.mod, composer.json, pubspec.yaml and the rest.
- The endpoints your code actually calls. A raw fetch to api.openai.com is found even with no SDK installed.
- Environment variable names in .env.example — STRIPE_SECRET_KEY proves Stripe without reading any secret.
- Your framework and where its routes live, so generated policy pages land in the right folder.
- Cookies and tracking scripts referenced anywhere in the source.
What it never reads
- Repositories you did not select.
- The value of any secret or environment variable.
- Your default branch, except through a pull request you approve — updates arrive on a poliogo/* branch.
Ready to connect FlutterFlow?
The free plan covers one project with no credit card. You approve everything before a single document is written.
Poliogo is a compliance management platform, not a law firm. What it produces is not legal advice. See exactly what each connection reads.