Typhoon OCR Assistant — Privacy Policy

# Typhoon OCR Assistant — Privacy Policy

Status: Draft for the developer to complete before publishing. Replace bracketed fields and confirm the actual production backend's behavior.

Effective date: [publication date]
Developer/operator: [public developer name]
Contact: [support/privacy email]

## Purpose
Typhoon OCR Assistant extracts text from images the user selects, uploads, pastes, captures, or chooses through Chrome's image context menu.

## Data processed
The extension processes selected images, screenshots or cropped regions, extracted text, image filenames, selected source-page URLs, and related result metadata. It stores the configured Apps Script URL, extension access token, preferences, and up to 50 recent OCR results in Chrome's local extension storage. A pending right-click image may also be stored temporarily until consumed by the panel. It does not continuously monitor the clipboard or crawl browsing history.

## Transfers for OCR
When OCR runs, selected image data and request metadata are sent over HTTPS to the configured Google Apps Script backend. That backend sends the image and OCR instructions to the Typhoon OCR API. The extension access token authenticates requests to the backend; the Typhoon API key is stored server-side.

The Auto-run right-click OCR preference is enabled by default. When enabled, choosing “Extract text with Typhoon OCR” triggers processing after the panel receives the selected image. Other workflows start processing when the user chooses Extract text.

## Storage outside the browser
If Save to Google Drive is enabled, the supplied bridge stores the input image and OCR Markdown in the backend operator's Google Drive folder. These files are not necessarily stored in the extension user's own Google account: ownership follows the Apps Script deployment.

[Confirm whether the production backend also saves to Google Sheets automatically. If so, identify the saved fields, account ownership, purpose, and retention/deletion process here.]

Google and the Typhoon API provider process data under their applicable terms and privacy policies. [Insert verified provider policy links and explain any retention or training controls configured for this service. Do not promise zero retention or no training without verification.]

## Retention and deletion
Users can clear OCR history in the History tab and remove extension-local data by uninstalling the extension. Clearing local history does not delete copies already saved in Drive, Sheets, backend logs, or retained by service providers.

[Specify actual retention periods and the procedure for requesting deletion of server-side files, sheet rows, or logs. Identify who operates the default backend.]

## Purpose limitations
The reviewed extension package contains no advertising or analytics integrations. [The developer must confirm that the deployed backend and business practices do not sell user data, use it for unrelated advertising, or transfer it for purposes unrelated to OCR before adopting these commitments.]

## User choices and security
Users choose the material to process, can disable automatic right-click processing, and can leave optional Drive saving disabled. Submit only material you are authorized to process. Access tokens should be kept private. A compatible configured backend and provider account are needed for OCR; this extension does not perform OCR entirely offline.

## Contact and updates
For privacy questions or deletion requests, contact [support/privacy email]. Updates to this policy will be posted at [public policy URL].