1. Overview
This Privacy Policy explains how the Forrest AI Assistant (“we”, “us”, “the App”) collects, uses, stores, discloses, and protects personal data when you install, authorize, or
use the App (including Google Calendar integration and WhatsApp messaging features). It is written to meet Google Cloud verification and listing requirements.
2. Data collected and purpose
We only request and store the minimum data required to provide the service.
- Google account data
- OAuth tokens (access and refresh tokens) for Google APIs used to access Google Calendar for configured accounts.
- Google account identifiers (email addresses associated with authorized accounts) and calendar IDs you configure.
Purpose: read/write calendar events, create reminders, and perform calendar management on your behalf. - WhatsApp / Messaging metadata
- Phone number IDs and message contents required to send replies via the WhatsApp Business API.
Purpose: deliver messages and notifications requested by you. - User-provided content and profile data
- Names, email addresses, and any calendar event content you or other authorised users provide.
Purpose: populate events, reminders and perform requested actions. - Operational data and logs
- Minimal operational metadata (timestamps, request success/failure, non-sensitive telemetry). PII is redacted where feasible.
Purpose: debugging, reliability, and security monitoring.
3. Legal basis for processing
For EU/UK users: processing is necessary to perform the contract (provide the service you requested) and for legitimate interests (service reliability and fraud prevention).
Consent is obtained during OAuth authorization for Google and during any WhatsApp linking. You may withdraw consent at any time by revoking access (see section 7).
4. OAuth tokens and Google-specific details
- Scopes: the App requests only the Google Calendar scopes required to operate (e.g., calendar read/write). Exact scopes are shown on Google’s OAuth consent screen at
authorization time. - Refresh tokens: stored to allow the App to act on your behalf without repeated consent. Note: Google’s testing/unverified apps may issue refresh tokens that expire after 7
days; publishing the app to production and verification by Google removes that limit. - Token lifecycle: refresh tokens are used to request new access tokens from Google as needed. If a refresh attempt fails (e.g., token revoked, invalid_grant), the App logs
the failure and will prompt re-authorization. - Limits and rotation: Google may limit refresh tokens per user/client (e.g., 50-token limit); issuing a new token may invalidate older tokens.
5. Storage, retention & deletion
- Secrets & tokens storage: OAuth tokens and other secrets are stored in Azure Key Vault. Tokens and stored data are retained only as long as necessary to provide the service
or to comply with legal obligations. - Logs: operational logs are stored in Application Insights / the hosting environment; PII is redacted by a logging processor before telemetry export where feasible.
- Retention periods:
- OAuth tokens and calendar configuration: retained while the account is active and authorized; removed upon revocation or deletion request.
- Logs and telemetry: retained according to platform defaults (or shorter where configurable) and removed on request when feasible.
- Deletion requests: Email pete@itzalive.co.uk to request deletion/export of your data. Typical response and completion window: 30 days. Critical data tied to backups or
legal holds may require additional time.
6. Data sharing and third parties
- We do not sell personal data.
- Third-party processors:
- Google (Google Calendar APIs) — processes data per its policies when you authorize the App.
- Meta / WhatsApp — processes messages/phone metadata to deliver messaging features.
- Microsoft Azure (Key Vault, Container Apps, Application Insights) — hosts and stores secrets, runtime, and logs.
- Access to your data is limited to the App’s runtime and the account owner/maintainers for support and operation. No external marketing or analytics vendors are given
calendar content access.
7. User controls, revocation & portability
- Revoke access: Revoke the App in your Google Account → Security → Third-party apps with account access. Revoking stops future access immediately.
- Re-authorise: Re-run the OAuth flow to generate a new refresh token if needed.
- Data export: You can request an export of stored calendar configuration and non-sensitive logs by emailing pete@itzalive.co.uk.
- Data deletion: Submit deletion requests to pete@itzalive.co.uk. Once processed, keys/tokens are removed from Key Vault and backups are purged according to retention policy.
8. Security measures
- Secrets encryption: Tokens and secrets are stored in Azure Key Vault (encrypted at rest) and accessed by the running service under restricted identities.
- Transport security: All network traffic to Google, Meta, and Azure uses TLS.
- Access controls: Runtime access to Key Vault and other services is restricted to the deployed service principal and the owner’s admin accounts.
- Logging privacy: PII scrubbing is performed on application logs where possible; sensitive data is never logged in plaintext by design.
- No guarantee: While reasonable technical and organisational measures are in place, no system is completely secure; breaches will be reported per applicable law.
9. International data transfers
Data will be processed and stored in the cloud provider regions used by Azure and Google. Transfers outside your country may occur for API processing. The App relies on
processor standard contractual clauses and provider safeguards where applicable.
10. Children
The App is not intended for use by children under 13 (or the applicable local age). Do not provide children’s personal data; if provided, a parent or guardian must consent.
11. Changes to this policy
The policy may be updated to reflect changes in practice or law. Material changes will be posted on the website with an updated effective date.
13. Contact & dispute resolution
Questions, deletion/export requests, or privacy concerns: pete@itzalive.co.uk. This policy is not legal advice. For legal disputes, the owner’s jurisdiction is the UK.
Google/Meta verification teams may contact the owner for additional documentation during OAuth verification.
Appendix
- Purpose of access: The App uses Google Calendar API to read and write calendar events for configured family calendars to provide reminders, scheduling, and
message-triggered actions. - Data stored: OAuth refresh/access tokens (in Azure Key Vault), calendar IDs, minimal user profile metadata (email/name), and operational logs (redacted).
- How users revoke access: Google Account → Security → Third-party apps.
- Data deletion process and contact: pete@itzalive.co.uk (completion within ~30 days).
- Contact for privacy verification: pete@itzalive.co.uk / https://itzalive.co.uk