Privacy Policy
Privacy Policy
1. What this policy covers
This policy explains how ScanSnap Automatic Renaming accesses, uses, stores and shares data obtained through Google APIs. The app is operated by Hidenobu Nagai for his own personal use and for a small number of people he knows personally. It is not a commercial service.
2. Google user data the app accesses
The app acts on the Google Account that authorized it. It requests these Google OAuth scopes:
https://www.googleapis.com/auth/drivehttps://www.googleapis.com/auth/documentshttps://www.googleapis.com/auth/script.external_requesthttps://www.googleapis.com/auth/script.scriptapphttps://www.googleapis.com/auth/spreadsheetshttps://www.googleapis.com/auth/script.send_mail
Concretely, this gives it access to:
- Names and contents of the scanned PDFs in one configured Drive folder
- Drive file metadata needed to process them (file ID, created and modified dates, parent folder IDs)
- A temporary Google Doc holding the Drive OCR text of each PDF, created and deleted inside a single run
- Rows that the app itself writes to its Google Sheets log (timestamps, file IDs, original and chosen names, document date, issuer, document type, subject, error messages)
- If a notification address is configured, a failure email sent to that address only when a run has errors
3. How the data is used
Each PDF is OCR'd, and the extracted text plus the PDF are sent to an AI model only to obtain a descriptive filename; the file is then renamed and copied inside the owner's own Drive and the outcome is recorded in the log spreadsheet.
4. Storage and retention
- The original, renamed and archived PDFs stay in the owner's own Google Drive
- The rename log is a Google Sheets spreadsheet created in the owner's own account
- Configuration, including the AI API key, is kept in Apps Script script properties
- The app has no server and no database of its own
5. Sharing and disclosure
The app does not sell, rent or trade Google user data, and it does not transfer it to anyone except the services listed below, which are the technical providers the app depends on.
- Google Gemini API — The PDF and its OCR text, sent to generate a filename suggestion.
- Optional OpenAI-compatible endpoint (only if configured) — The same OCR text, sent to generate a filename suggestion when the owner selects that provider instead of Gemini.
No Google user data is used for advertising or re-targeting, and none of it is used to determine creditworthiness or for lending purposes.
6. Limited Use
The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
7. Who can see the data
Only the owner, who reads his own files. No one else has access, because all of the data stays inside the owner's own Google Account.
8. Security
- The app runs under a Google Account with the authorizations that the owner granted.
- Credentials and API keys are kept in server-side secret storage or Google-managed storage, never in public files.
- Network requests are made over HTTPS.
9. Revoking access and deleting data
- Revoke the app's access at any time at myaccount.google.com/permissions. The app stops working immediately afterwards.
- Delete the app's data in the app itself, or in the storage listed in section 4.
- Data the app stored inside a Google Account is deleted by deleting it there; there is no separate copy held by the operator.
10. Changes to this policy
If the app's data handling changes, this page is updated and the "Last updated" date above changes with it. The current version is always this page.
11. Contact
Operated by Hidenobu Nagai. The support address for the app is set as the support address on the app's OAuth consent screen. You can also reach the operator through https://github.com/hidenobunagai.