Data & authorization
Privacy notice
This notice describes the public prudicz information website and the private Google integration operated by Andrej Kouřil.
1. Purpose and operator
prudicz is used by its operator for personal productivity and user-directed automation with his own authorized Google accounts. It is not a public account-registration service. Contact: andering@gmail.com.
2. Google information accessed
The integration receives account identity information, such as an email address, and OAuth credentials. Depending on permissions granted and the requested task, it may access:
- Email messages, attachments and mailbox metadata.
- Files, documents, spreadsheets, presentations and their contents or metadata.
- Calendar events, tasks, contacts, chat messages and related metadata.
- Forms and responses, Apps Script projects and other information available through authorized Google APIs.
Granted permissions can also allow writes, including creating, updating or deleting supported resources, or sending messages. The Google consent screen identifies the requested permissions. The integration does not collect or store Google account passwords.
3. How information is used
Information is used to authenticate the connected accounts and carry out the operator's requests, such as searching, summarizing or updating information. OAuth refresh tokens enable continued access without repeated sign-in, until the grant expires or is revoked.
Google data is not sold or used by this integration for advertising, credit decisions or training generalized AI models.
4. AI processing and service providers
When the operator uses an AI-assisted workflow, selected Google data returned by tools may be included in prompts, tool results and conversation history. That content can be processed by the AI provider selected in the client; it is not necessarily confined to the local machine.
Processing by Google, the selected AI provider and infrastructure providers is subject to their applicable service terms and account settings. The operator should choose provider settings appropriate for the sensitivity of the information being processed.
Cloudflare hosts and delivers this public information website. The static website does not receive Google OAuth tokens or the contents of connected Google accounts.
5. Storage and retention
OAuth credentials are stored persistently on the operator-controlled host with restricted filesystem permissions, separately for each account. The private integration and its client are access-controlled.
Retrieved content may remain in client conversation history, operational logs or backups. Retention depends on the client, provider and backup settings; this notice does not promise automatic deletion after a fixed period. Removing an OAuth grant prevents future authorized access but does not automatically erase previously stored conversations or backups.
6. Revoking access and deleting data
Access can be revoked at any time through Google Account connections. The operator can also remove locally stored OAuth credentials and delete relevant client conversations or logs. Backup copies may remain until their configured retention expires.
For questions about information handled by this integration or a deletion request, contact andering@gmail.com.
7. Website requests and cookies
This information website contains no application login, forms, analytics scripts or advertising trackers. The hosting provider processes ordinary request information, such as IP address, browser details and request timestamps, to deliver and protect the website. Provider-level security features may operate according to Cloudflare's privacy policy.
8. Changes to this notice
This notice may be updated when the integration or its data handling changes. The effective date above identifies the current version.