Your data, explained
Privacy policy
Last updated: 31 August 2026
144 is a private personal dashboard operated by Tom Petrie. This policy covers the public information site and the private dashboard at 144.lansdell-petrie.uk. Questions or deletion requests can be sent to tompetrie4@gmail.com.
What we access and why
- Google Calendar: with the owner's permission, 144 reads the account's calendar list (identifiers, names, colours and access roles) so the owner can choose calendars, and reads events from the selected calendars to show a combined schedule and daily summary. It requests read-only calendar-list and calendar-events permissions, not permission to edit calendars. Selected calendar identifiers, names, colours and selection state are stored with their imported events. The integration does not access Gmail, Google Drive or financial accounts.
- Stored event data: event identifiers, titles, start and end times, all-day status, source information and synchronisation timestamps. Event descriptions, attendees and attachments are not imported.
- Calendar subscriptions: an iCalendar feed URL supplied by the owner is stored on the server and used to fetch calendar events. A published feed may also be readable by anyone who has its original URL; treat that link as private.
- Authentication and operation: the private dashboard uses the owner's email identity, authentication cookies, connection state and operational audit records. Browser storage may hold dashboard preferences and locally saved planning data.
Storage and protection
The private application and its database are hosted on Cloudflare. Google refresh tokens are encrypted before storage, with the encryption key held separately as a server secret. Tokens and subscription URLs are not embedded in this public site. The private dashboard and its APIs require owner authentication.
Calendar synchronisation normally imports a rolling window from 30 days in the past to 180 days ahead. A successful refresh replaces the stored event snapshot for that source. If a refresh fails, the last successful snapshot can remain until a later successful refresh or disconnection; this window is not a guaranteed deletion deadline.
Sharing and use of Google data
Google data is used only to provide the connected calendar and planning features. It is not sold, used for advertising or used to train general-purpose AI models. This public website does not display private event data.
Google processes the connection and calendar requests; Cloudflare processes and hosts application data on our behalf. These providers may process request, device and security metadata under their own policies. Data is not shared with other parties except where required by law or necessary to protect the service.
144's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Disconnecting and deleting
Disconnect Google in the private dashboard's Settings to delete its stored connection credentials and imported Google events. 144 also attempts to revoke the Google token; if revocation fails, access can be removed directly in Google Account connections. Revoking access at Google stops further authorised access but does not itself delete the existing snapshot in 144; disconnect in 144 or contact the operator for deletion.
Deselecting a Google calendar stops its sync and deletes its imported events from 144; its calendar identifier, name and selection setting remain until Google is disconnected. Removing a subscribed calendar deletes its imported events and stored feed connection. Operational audit records may remain after disconnection; they are separate from imported calendar content. For other stored information or a complete deletion request, contact the operator using the email above.
Public pages, cookies and changes
The public information pages contain no application analytics, advertising, forms or tracking scripts. Cloudflare may process ordinary request and security metadata when serving them. The private dashboard uses authentication-related cookies; Google's consent pages are governed by Google's own policies.
This policy describes the current service. Any new data integrations or materially different uses will require an updated policy and any necessary permission before they are enabled.