OAuth app purpose

ComplyEaze Pack Release Automation

ComplyEaze Pack Release Automation is the Google OAuth app used by ComplyEaze maintainers to authenticate the protected Chrome Web Store release workflow for ComplyEaze Pack. It is not the Pack browser extension runtime and is not used to access GST Portal accounts.

What this app does

Release submission

Authenticates the Chrome Web Store API call that uploads or publishes a ComplyEaze Pack release package.

Maintainer-only use

Used by ComplyEaze maintainers and the protected GitHub Actions environment for the Pack publisher account.

Release artifacts

Submits release ZIPs from the source-controlled release workflow and records release evidence when available.

No GST Portal access

Does not sign in to GST Portal, read taxpayer records, download GST files, or run inside the Pack extension.

OAuth scope

The Google OAuth consent flow authorises the Chrome Web Store API scope needed to manage Pack releases in the publisher account.

OAuth app name: ComplyEaze Pack Release Automation
Google API: Chrome Web Store API
Requested scope: https://www.googleapis.com/auth/chromewebstore
Release support contact: [email protected]

Data boundary

Release automation is separate from the local-first browser extension workflow.

It does not request, collect, store, or transmit GST Portal credentials, OTPs, CAPTCHA responses, cookies, or session tokens.
It does not read GST Portal pages, taxpayer identifiers, GST PDFs, portal HTML, browser download paths, or local extension storage.
It does not add extension analytics, advertising, session replay, or runtime telemetry.
Its release inputs are source-controlled release artifacts: extension ZIP, release tag, publisher configuration, and any checksum or provenance evidence recorded for that release.

Release controls

The release workflow is intentionally narrower than normal extension runtime behavior.

Protected workflow

Chrome Web Store submissions run from a restricted GitHub environment with publisher credentials stored as GitHub secrets.

Package evidence

Release records link the extension package to the source tag and include checksum or provenance evidence when available.

Limited credential use

OAuth credentials are used only to obtain an access token for the Chrome Web Store API release request.