1. Current status
No Google account has authorized this app, no OAuth client has been issued, and the current build does not collect live Google user data. Its 69 automated tests use fabricated metadata and page tokens.
2. Access proposed for a later connection
If Gal approves and activates a future connected version, it is intended to request Google Drive’s drive.metadata.readonly permission and use files.list. Google classifies this as a restricted scope. It can expose file metadata across the authorized account.
The intended request may receive file IDs, names, MIME types, parents, trash status, shared status, owner email addresses, and file sizes when supplied. It is not intended to request or download file contents, and it cannot write to Drive.
Solaria’s code is designed to accept results only for the designated 00_To_Scotty relay folder. That is a code-side safeguard. It does not reduce the account-wide metadata permission granted by Google.
3. How the metadata would be used
The proposed use is narrow: identify owner-only relay items, verify that two complete listings agree, and return a local metadata result for Solaria’s bounded mail workflow. A listing result would not make a file eligible for delivery, and the adapter would not route, publish, share, or mark a file as handled.
The adapter’s validation design returns the source response bytes and SHA-256 hashes to its local caller as evidence. Live retention and deletion rules for that evidence have not yet been approved or implemented, so live connection remains on hold.
4. Storage, tokens, and deletion
This public website does not receive Google tokens or Drive metadata. It has no accounts, forms, analytics, advertising, or tracking scripts. The web host may process standard request logs such as IP address, browser information, requested URL, and time of request as part of serving the site.
For a future Windows desktop connection, PKCE with a loopback redirect and current-user Windows DPAPI token storage are proposed. They are not implemented or tested. Token exclusion from source files, logs, receipts, manifests, and backups is also a requirement that has not yet been demonstrated.
Before any live connection, Solaria must approve and test a specific local retention and deletion procedure. If access is later granted, Gal can revoke it from her Google Account’s third-party connections. Removal of any local token and retained metadata evidence must also be verified as part of that procedure.
5. Sharing and Limited Use
Google user data is not sold, used for advertising, offered to the public, or used to train a general-purpose artificial-intelligence model. The planned desktop adapter is for Gal’s private Solaria workflow. The static website host does not need Google tokens or Drive metadata to serve these pages.
Any future use of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. A connected version will not be activated until its actual handling matches this policy and this page is updated where necessary.
6. Your choices
Google authorization is optional. No sign-in is offered on this website. If a future desktop version is connected, access can be withdrawn through Google Account settings. Questions or deletion requests for locally held adapter evidence may be sent to successisus@gmail.com.
7. Changes to this policy
This page will be revised before the adapter’s behavior changes materially or before a live Google connection is activated. The effective date at the top will change when the policy changes.