1. Current status
The diagnostic completed two matching, complete Drive listings of the designated relay folder. It did not download file contents, write to Drive, route an item, or advance handled or checkpoint state. No Google refresh credential was persisted.
2. Google access and its limit
Gal granted the existing Desktop client Google Drive’s drive.metadata.readonly permission for the bounded listing. Google classifies this as a restricted, account-wide metadata scope. The diagnostic requested only the designated relay folder, but that code-side limit does not narrow the permission Google grants.
The request could receive file IDs, names, MIME types, parents, trash status, shared status, owner email addresses, and file sizes when supplied. It did not request or download file contents, and it could not 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 one-time diagnostic identified relay-folder metadata, checked that two complete listings agreed, and returned a local aggregate result. A listing result does not make a file eligible for delivery. No item was routed, published, shared, or marked handled.
The diagnostic processed provider responses in memory and retained a local receipt of aggregate counts, hashes, and operation details. That receipt does not contain Drive item IDs, filenames, or raw provider responses. Further item validation, live retention and deletion controls, and any running mail connection remain on hold.
4. Storage, tokens, and deletion
This public website does not receive Google tokens or Drive metadata. Its source pages have 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.
The OAuth tokens from the bounded run stayed in memory; no refresh token was saved. A restricted local Windows vault has since been created, and current-user DPAPI protection passed tests with synthetic values. It contains no Google credential. Real refresh, revocation, and removal have not been validated, and coverage by backups outside the project has not been audited.
Gal can withdraw the existing grant through Google Account settings. A future persisted credential and recurring connection require a verified retention, deletion, and revocation path. The local aggregate receipt remains retained as project evidence; deleting it would be a separate owner decision.
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 recurring use of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements. A connected mail-workflow 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. Gal can withdraw the existing grant 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 revision records the bounded live diagnostic separately from the paused mail-workflow adapter. The page will be revised again before a persisted credential or recurring connection changes actual handling.