Limited Use clarification for accessibility OCR using BYOK Gemini API

[アスカネット]

I found the recent thread “Limited Use clarification — user-provided Gemini API keys,” but I am asking separately because my extension serves an accessibility use case and I need to distinguish Unpaid and Paid Services before submission.

I am preparing Scribe, a free image OCR extension for the Chrome Web Store. Its single purpose is to let blind and low-vision adults extract and copy text from an image they explicitly select.

The default OCR method runs locally through a Windows companion. An optional method lets an adult user enter their own Gemini API key. The key is stored locally, and the selected image is sent directly from the extension to Google's Gemini API. The extension developer does not receive the key, image, or OCR result.

Gemini API Unpaid Services may use submitted content and generated responses for product improvement, and human reviewers may process input and output. The extension can disclose this to the user but cannot currently determine whether the user's key belongs to an Unpaid or Paid Service.

Could someone from the Chrome Extensions or Chrome Web Store policy team clarify:

1. May the developer affirm compliance with the Chrome Web Store Limited Use requirements when a user explicitly chooses the Gemini method and sends a selected image through their own Unpaid Services API key?
2. If not, would requiring users of the Gemini method to use a Cloud project with an active billing account (Paid Services) resolve the Limited Use concern?
3. What disclosure or consent is required in the listing, extension UI, and privacy policy for this direct BYOK transfer?

The official Chrome Web Store contact form did not offer a human support option for this pre-submission policy question. No user data, credentials, or confidential information are included in this inquiry.