Your data, explained
Privacy policy
Project HQ Calendar is a personal, read-only Google Calendar integration within the private Project HQ dashboard.
Last updated: 18 November 2026
Your Google Calendar data is used to show your appointments and plan around busy time. You control the connection. Your calendar is not changed, sold, used for advertising or used to train AI models.
1. Who operates the app
Project HQ is operated by Louis Burrin for personal use. The dashboard is restricted to its authorised owner. These public information pages do not grant access to the dashboard.
2. What Google data is accessed
When you choose to connect, Google asks for these permissions:
- Google account identity: OpenID sign-in and your email address, to confirm that the email is verified and matches the authorised Project HQ owner. The app does not request access to your Gmail messages.
- Read-only events on calendars you own: the permission
calendar.events.owned.readonly. This permission covers owned calendars; the current integration queries only your primary calendar.
For the requested date window, Project HQ reads event identifiers, titles, start and end times, all-day status, cancellation status and busy/free status. It also checks your own invitation response to exclude declined events. The retained event view contains only identifiers, titles, times, all-day markers and busy/free status.
Event descriptions, locations, guest lists and meeting links are not requested. Project HQ cannot create, edit or delete Google events.
3. How data is used and shared
Calendar data is used only to display appointments, avoid busy time when planning work and maintain the connection you authorised. Google account information is used to verify the owner.
Google provides account sign-in, permission management and the Calendar API. Cloudflare hosts the private dashboard and processes the encrypted connection and event cache in its D1 database. Those providers process data to deliver their services under their own terms and privacy policies.
Calendar data is not sold, used for advertising, transferred to data brokers or used to train general-purpose AI or machine-learning models. Imported Google events are excluded from Project HQ workspace snapshots, exports, recovery history and planning-board backups. They are not exposed through the Project HQ Claude MCP connector. Any separate Google Calendar connection you enable directly in Claude is outside this integration.
Access to stored calendar information is restricted to operating and securing the service, resolving a specific issue at the owner's request or meeting applicable legal obligations.
Project HQ Calendar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
4. Storage, security and retention
OAuth access and refresh tokens, which keep the connection working, are encrypted in server-side storage. The single retained calendar-window cache is encrypted separately. Access to the private dashboard requires authentication, and calendar API responses instruct browsers not to store them in an HTTP cache.
- Credentials: retained while the calendar remains connected. Access tokens are refreshed as needed. Disconnecting clears the saved tokens; an invalid refresh grant detected during use also clears them.
- Server event cache: only one date window is retained per owner. A successful fetch replaces it. A normal request reuses it for five minutes; if Google is unavailable, matching cached events may be displayed for up to 24 hours, marked with their last update. These are reuse limits, not automatic deletion deadlines. An unused cache can remain stored until replaced, disconnected or cleared after an invalid refresh grant.
- Browser memory: fetched calendar windows are held in the current tab's memory, rather than saved to dashboard local storage. Closing the tab clears that memory. Disconnecting in that tab clears its calendar state; close other open dashboard tabs to clear their existing in-memory views.
- Connection metadata: an owner identifier, connection generation and request-limit counters can remain after disconnect. These do not contain event details or saved Google tokens.
The hosting provider may retain database recovery copies and operational security records under its own retention settings. Clearing the active record does not promise immediate erasure of every recovery copy. No system can guarantee absolute security.
The Google sign-in flow uses a secure temporary cookie that expires after ten minutes and is cleared when the sign-in callback completes. The private dashboard also uses authentication cookies and browser storage for its separate workspace features.
5. Disconnecting and deleting data
- In the private dashboard, open Plan your time > Schedule > Calendar.
- Choose Disconnect Google Calendar. This clears saved Google tokens and the event cache from the active Project HQ database and attempts to revoke permission at Google.
- You can also remove Project HQ from your Google Account connections. Use this if Google revocation could not be completed, and disconnect in Project HQ as well to clear its stored connection.
Disconnecting does not delete Google appointments or your separate Project HQ tasks, notes and boards. For a request to remove remaining connection metadata or for help with deletion, contact the operator below.
6. Visiting these information pages
These pages do not connect to Google Calendar or the private dashboard database. They contain no analytics scripts, advertising, tracking pixels, forms or embedded third-party media, and set no application cookies. The hosting provider receives ordinary web-request information, such as IP address, requested URL and browser information, to serve and secure the site.
If you email the operator, the address and information you send are used to answer your request. Do not email passwords, access tokens or private calendar exports.
7. Changes to this policy
This page will be updated when the integration's data practices change. A new use of Google data will be disclosed and any required consent obtained before that use begins.
8. Contact
For privacy, access or deletion questions, email Louis Burrin at louis.burrin14@gmail.com.