Privacy policy

Effective 2 September 2026 · Applies to the AppMama Android application (dev.appmama) and this website

The short version. AppMama has no servers, no accounts and no analytics. We — the people who write it — receive no data from you at all. What the app does do is act on your behalf: it stores your credentials encrypted on your device, and it sends your prompts to the AI provider you chose to connect. This document explains exactly where every byte goes.

01 Who is responsible

AppMama is free software published by its contributors at github.com/hsyvy/appmama under the GNU General Public License v3.0. For the purposes of data protection law, the project maintainers are the controller for this website only. For the application, you are the one deciding what to send and to whom; the AI provider you connect is the controller for the prompts it receives, under its own policy.

02 What we collect

Nothing. There is no AppMama backend, no account system, no telemetry SDK, no crash reporter, no advertising identifier, no analytics of any kind — in the app or on this site. This is verifiable rather than promised: the source is public, and the app declares only the permissions listed in section 05.

Because we collect nothing, there is no profile to export, correct or delete, and no data-sharing or data-selling arrangement of any kind.

03 What stays on your device

All of the following is stored in the app's private storage and never leaves the device unless you deliberately export or share it:

Provider credentials. API keys and subscription (OAuth) tokens for Claude, ChatGPT, Grok or OpenRouter, held in Android's EncryptedSharedPreferences (AES-256).
Your projects. Every file the agent writes, the Gradle caches and the APKs it produces.
Session history. Your prompts, the agent's replies and the terminal output for each project, so a conversation can be resumed.
Preferences. Which provider is active, which model, reasoning effort, onboarding state.
The Linux environment. The downloaded toolchain and any packages you install into it.

Android's cloud backup is disabled for this app (allowBackup="false"), so none of it is copied to Google Drive. Uninstalling removes all of it, including your keys.

04 What your device sends, and to whom

The app makes network requests only in the situations below. In each case the connection is between your device and that third party; it does not pass through anything we operate.

The AI provider you connected

When you send a prompt, the agent CLI transmits your message and whatever parts of the project it needs to read — file contents, command output, error text — to that provider's API, authenticated with your key or subscription token. If a project contains something you would not want a model provider to see, do not build it here. What the provider does with it is governed by their agreement with you:

GitHub

Everything the app needs to build with is bundled in the install, so nothing is downloaded on first run. At every launch it fetches a small model catalogue from raw.githubusercontent.com so newly released models appear without an app update. GitHub sees what any file download reveals: your IP address, the time, and the file requested.

Package and dependency repositories

Building an Android project makes Gradle fetch its dependencies — typically from Google's Maven repository and Maven Central. Installing extra tools into the environment contacts the corresponding package mirrors. These requests come from your device and are visible to those hosts.

Sign-in flows

Choosing a subscription login opens the provider's own website (claude.ai, ChatGPT or accounts.x.ai) in your browser. You authenticate there, with them. The app never sees your password — only the token the flow returns, which it then stores as described in section 03.

The agent runs with broad permissions inside its sandbox. To build software it must be able to read and write files and run commands in the Linux environment. It cannot reach your photos, contacts, messages or other apps — Android's app sandbox prevents that, and AppMama requests no permission that would change it.

05 Permissions, and why

Permission	Why it is needed
INTERNET	Let the agent reach its provider, and let a build fetch the dependencies a project needs.
WAKE_LOCK	Keep a build running when the screen turns off.
FOREGROUND_SERVICE FOREGROUND_SERVICE_SPECIAL_USE	Run the build you started to completion instead of being killed in the background.
POST_NOTIFICATIONS	Show the ongoing-build notification, which Android requires for that service.
REQUEST_INSTALL_PACKAGES	Hand the APK you just built to Android's installer. This is the app's whole purpose; you still confirm every install.

There is no location, camera, microphone, contacts, SMS, or storage permission, and none is planned.

06 How the sensitive parts are protected

Keys and tokens are encrypted at rest with a key held in the Android Keystore, and are passed to the build session as environment variables — they are never written into the Linux environment's filesystem.
Cloud backup is off, so credentials are not synced off the device.
All provider and download traffic uses HTTPS.
No security measure is absolute. Rooting the device, or installing software that abuses accessibility or debugging access, defeats these protections — as it would for any app.

07 Your control and your rights

Remove a credential: clear the key or sign out in the app's provider settings.
Revoke access entirely: delete the key or session from the provider's own dashboard — that is the authoritative place.
Delete everything: uninstall AppMama. Projects, history, credentials and the Linux environment all go with it.
Provider-held data: requests to access, correct, export or erase what a provider holds go to that provider; we hold no copy and cannot act on your behalf.

Where the GDPR, UK GDPR, CCPA/CPRA or similar law applies, the rights they grant are exercised against whoever holds the data. For this project, that is nobody: we neither collect nor process personal data, and we do not sell or share it.

08 Children

AppMama is a developer tool and is not directed at children. We do not knowingly collect information from anyone, children included. The AI providers it connects to set their own minimum age; check theirs before signing in.

09 This website

This site is static. It sets no cookies, runs no analytics, embeds nothing from another domain, and loads its fonts from its own server — so visiting it does not tell any third party that you did. The only script it runs is a small file that animates the page; it stores nothing and sends nothing.

The host that serves the site (GitHub Pages, unless stated otherwise on the page you are reading) keeps ordinary web-server logs, including IP addresses, as described in GitHub's privacy statement. Links out to GitHub, the AI providers or other sites are governed by those sites' policies.

10 Data-safety summary

The same facts in the form app stores ask for.

Question	Answer
Data collected by the developer	None
Data shared with the developer or third parties by the app	None
Data sent at the user's direction	Prompt text and project file contents, to the AI provider the user connected, to fulfil the user's request
Data encrypted in transit	Yes — HTTPS
Credentials encrypted at rest	Yes — AES-256, Android Keystore
Deletion	Uninstalling removes everything; there is no server-side copy
Analytics, ads, tracking, ad IDs	None
Account required	No AppMama account. An AI provider account is required to build.

11 Changes to this policy

If the app's behaviour changes, this page changes with it, and the effective date at the top moves. Because the page lives in the project repository, every revision is a commit you can read and diff. Material changes will also be noted in the release that introduces them.

12 Contact

Questions, corrections, or a privacy concern about this project:

Open an issue at github.com/hsyvy/appmama/issues — public, and usually the fastest route.
By email: hsyvy7@gmail.com

This document describes how the software behaves. It is not legal advice, and it does not replace the policies of the AI providers you connect to.