Privatar Chrome Publisher privacy policy
This policy applies to Privatar Chrome Publisher, the private tool used by authorized administrators to maintain Privatar’s Chrome Web Store extension. It does not replace the separate wallet privacy disclosures.
Google data and permissions
The tool requests the Google OAuth scope https://www.googleapis.com/auth/chromewebstore. This allows it to see, edit, update or publish Chrome Web Store items that the authorizing Google account can manage. The tool uses access and refresh tokens, publisher and item identifiers, package upload results and release status information. It sends extension packages and publishing requests to Google when an administrator requests those operations.
Purpose and limited use
Google data is used only to manage authorized Chrome Web Store releases and check their status. The tool does not request Gmail, Drive or Google profile scopes. Google data is not sold, used for advertising or used to train general-purpose AI models. Privatar Chrome Publisher’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Storage and security
The current administration setup stores the OAuth client secret and refresh token in the administrator’s macOS login Keychain. Access tokens are used to authenticate requests to Google. Credentials are not bundled in the wallet, published on this website or committed to source control. Local release records may contain package versions, publisher identifiers and upload status; credentials should not be included in those records.
Sharing and service providers
Google processes OAuth authorization, token exchanges and Chrome Web Store API requests. During setup, the administrator may use Google’s OAuth Playground with this app’s own client credentials. If an administrator chooses to use an AI assistant for publishing work, that assistant may process the release instructions, extension package and API results needed for the requested operation under its own service terms. Publishing credentials should be passed through protected local storage rather than included in messages. This website is hosted by Vercel, which processes technical requests needed to deliver and secure these pages.
Retention, revocation and deletion
Local credentials remain in the administrator’s Keychain while publishing access is needed. An administrator can revoke the app through Google Account connections and remove its local Keychain entries. Revocation prevents subsequent authenticated operations; it does not delete extensions or records Google already holds. To request deletion of information held by Privatar or ask about this policy, contact admin@privatar.app.
Wallet data
This publisher authorization does not provide access to wallet recovery phrases, wallet private keys or permission to move wallet funds.
Contact and changes
Privacy contact: admin@privatar.app. Material changes to the publisher tool’s data practices will be reflected on this page. Never send credentials or wallet secrets to support.
Publisher tool · Privacy policy · Terms of use
Effective and updated October 12, 2026