Hello Google AI Developer team,
We are developing Bonflux, an Android receipt-reading application operated in Romania (EEA). Before public distribution, we would like written clarification of the Gemini API Additional Terms, specifically the Use Restrictions requirement concerning API Clients made available to users in the EEA, Switzerland and the UK.
Our proposed architecture is:
- Each adult end user authorizes their own Google account through Android AuthorizationClient.
- With explicit consent, the app creates/reuses a Cloud project owned directly by that user and enables the Generative Language API in that personal project.
- Receipt images are sent directly from the Android device to the Gemini API using the user’s OAuth access token and an explicit x-goog-user-project header for their own project.
- The developer does not proxy requests, collect API credentials, share an inference project, or purchase Gemini usage on behalf of users.
- The intended mode uses only the user’s unpaid/free API quota, with no linked billing account. When a usage limit is reached, the app offers local/offline OCR and does not enable billing.
Does the EEA Paid Services requirement apply to this end-user-owned project architecture as well? In particular:
- May such an app be publicly distributed to EEA users while individual users access only their own unpaid Gemini API quota?
- If not, must each user’s Gemini API project have an active billing account for public distribution in the EEA, even when no developer-funded inference is involved?
- Is there an applicable documented exception, approval process or alternative Google-supported architecture that permits free Gemini API receipt reading for EEA end users?
- Please distinguish this distribution requirement from the separate regional data-use provisions that apply to unpaid usage.
Product website: https//bonflux.ro/
Privacy policy: ..
We are keeping the OAuth integration in testing and have not enabled paid usage or released this flow publicly. We are not requesting a workaround for usage limits or terms; we need the applicable requirements before deciding whether public distribution is feasible.
Thank you.