Privacy policy
The short version
Emberbase reads your Firebase project data directly from Google, on your device. That data never travels through an Emberbase server, and none of it is stored on your device or anywhere else.
What Emberbase stores on your device
- Your Google refresh token, in the iOS Keychain or Android Keystore.
- The list of Firebase projects you chose to track — project IDs only.
- Your settings: theme, biometric lock, telemetry preference.
That is the complete list. Signing out revokes the token at Google and deletes all of it.
What Emberbase never stores
Your project data. Not documents, not user records, not files, not configuration values, not environment variable values, not analytics figures. It is fetched when a screen needs it, held in memory while that screen is open, and gone when the app closes.
There is no server-side cache, no local database, and no export.
What Emberbase sends anywhere
If anonymous usage data is enabled in Settings, Emberbase reports:
- which screens were opened, by name
- how long requests took
- the CATEGORY of an error, such as "permission denied"
It never reports project IDs, document contents, user records, email addresses, file names, paths, query text, or error message bodies. This is enforced in code, not by policy: every telemetry payload is checked against a denylist before it is sent, and anything outside the declared shape is dropped.
You can turn this off in Settings at any time.
What Emberbase asks Google for
Read access, to browse your projects. Emberbase never creates, modifies, or deletes anything in them; every write operation in the app is disabled.
Where Google publishes a read-only permission, Emberbase asks for that one. For Firestore, Authentication, and Cloud Functions no read-only permission exists, so the permission Google grants for those is broader than the use Emberbase makes of it. We would rather say so here than imply a restriction Google is not actually enforcing.
The permissions, and what each one is used for:
- openid, email, profile: to show which Google account is signed in, in Settings.
- cloud-platform: to read your Firestore data, Authentication users, Cloud Functions, Storage files, Realtime Database, Remote Config and Hosting releases. Requests are reads only. Google offers no read-only version of this permission that covers those services.
- firebase.readonly: to list the Firebase projects you can access, and the apps registered to each one.
- analytics.readonly: to show active users and sessions for a project's linked Google Analytics property. No other analytics data is read.
"What we access" in Settings shows the same list inside the app.
How Emberbase uses Google user data
Emberbase's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The policy is published at developers.google.com/terms/api-services-user-data-policy.
Data read from Google is used only to show it to you, in the app, on your device. It is not sent to Emberbase or anyone else, not sold, not used for advertising, not used to train AI or machine-learning models, and not read by people other than you.
Third parties
Google, because that is whose API your data lives behind.
If usage data is enabled, an analytics provider receives the events described above. No other party receives anything.
Your choices
- Turn off usage data in Settings.
- Sign out, which revokes Emberbase's access at Google and wipes local storage.
- Revoke access yourself at myaccount.google.com/permissions.
Contact
Questions about this policy: app@aplicadom.com