Privacy Policy — Sire Treasury Reporting

Operator: Squiddy.
Privacy contact: squiddy953@gmail.com.
Version: prepared for publication; effective upon publication.

Purpose

Sire Treasury Reporting uses Google Docs and Google Sheets to carry out reporting and document tasks authorized by its operator. Reporting may combine public blockchain information with data from authorized documents and spreadsheets.

Information accessed and stored

The integration may access document and spreadsheet contents, file identifiers, titles, formatting, formulas, and information returned by the Google APIs when needed for an authorized task. It stores OAuth access and refresh credentials on the operator-controlled system to support scheduled tasks without repeated sign-in. It can also store generated workbooks, report data, verification snapshots, execution logs, and backups on that system. Some artifacts may contain document or spreadsheet data.

The integration requests the Google Docs and Google Sheets scopes. It does not request Gmail, Calendar, Contacts, or Google Drive API scopes in this setup. Google handles account sign-in; this app does not need the user's Google password.

Use and sharing

Information is used to generate, read, verify, and update authorized reports and documents; diagnose failures; and maintain scheduled automation. Relevant task data may be processed by the AI service providers configured for the operator's assistant when the operator requests an assistant task. Scheduled script-only refreshes do not themselves require an AI model call.

Report status messages and, when authorized, report contents may be sent to collaboration channels chosen by the operator. Google API data may therefore be available to collaborators with access to the selected files or channels. External blockchain-data providers receive public wallet/token queries; the reporting workflow does not require sending them Google OAuth credentials or private Google documents.

Google user data is not sold or used for advertising. Google Workspace API data is not used to develop, improve, or train generalized AI or machine-learning models. Use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and retention

Data is stored on the operator-controlled system and in authorized Google files. Relevant data may also be processed by configured service providers for authorized assistant tasks. Local artifacts and backups are not currently governed by a single automatic deletion period; retention depends on the reporting task, system configuration, and the operator's instructions. The operator can remove local credentials and reporting artifacts. Revoking Google access alone does not erase existing local copies, reports, logs, or backups.

Revocation and deletion requests

You can revoke the app's Google access through your Google Account's third-party connections settings. Revocation prevents future authorized Google API access but does not delete previously generated files or stored copies. Contact the operator at the address above to request deletion of locally stored credentials or data, subject to any applicable retention obligations. Collaborator-owned copies and files may require separate action by their owners.

Security and changes

OAuth credentials and private report information should be accessible only to authorized operators and services. No storage or transmission method is completely secure. Material changes to data handling should be reflected in an updated policy on this page.

Contact

For access, privacy, or deletion questions, contact squiddy953@gmail.com.