toT

Google OCR applies only when you choose that OCR route inside the app. Authentication happens in the system browser, and the OCR route uses the end user's Google account and requests the Google Drive scope drive.file.

toT uses an owner-provided Google Cloud project and OAuth client distributed with the app. Ordinary users do not need to manually obtain or import OAuth client credentials.

1. Data accessed

• basic Google authorization and token data needed to connect the app to your Google account for this OCR feature
• the Google Drive file access granted by the drive.file scope
• only the image or PDF files you explicitly choose for OCR
• a temporary converted Google document created during the OCR workflow so text can be exported back to the app
• the extracted text returned from Google to the app after export

2. How this data is used: the app uses this data to authenticate the Google OCR connection, upload and convert the selected file, export extracted text back to the app, reuse the saved connection for future OCR runs, and attempt cleanup of the temporary Google document after export.

3. Sharing with third parties: selected OCR files, the temporary converted document, and the related Google authorization data are shared with Google only to provide the Google OCR workflow. The app does not send OCR files or extracted OCR text to the developer. Other than Google services required for OCR and any information you separately choose to send to the developer for support, this flow does not share Google user data with other third parties.

4. Storage and protection: the app stores Google OCR token state locally on your device so the connection can be reused. Local app data and OCR results stored by the app remain in the app's local data area on your device; protection of that data depends on your device, operating system, and account security. Google OCR token state is stored locally and protected using Electron safeStorage and the operating-system protection mechanisms available to the app on your platform. The app attempts to delete the temporary converted Google document from Google after text export.

5. Retention and deletion: the local OCR token state remains until you disconnect Google OCR, remove local app data, or uninstall the app. When the disconnect action completes successfully in the app, it revokes the saved token and deletes the local token file. You can also revoke the app's Google access from your Google Account permissions/security controls. The app attempts to delete the temporary converted Google document immediately after export. The app does not send OCR files or extracted OCR text to the developer, and this OCR feature does not create a separate developer copy of that OCR content. If you want to request deletion of support messages or any data you intentionally sent to the developer, contact cibersino@gmail.com.

Last updated: April 21, 2026.