Google connection · privacy policy
Your data.
Your workspace.
Effective November 12, 2026
LurkCrew is a personal application operated by its owner, Jeffry Matesevac. This policy describes its Google Calendar and Gmail connection, the resulting task context, and this informational website.
What the Google connection accesses
- Basic account identity: the verified email address identifying the signed-in account.
- Google Calendar: calendar names and identifiers, plus events from calendars the owner selects. Cached event fields include title, start and end times, time zone, location and a Google Calendar link. The app requests read-only Calendar access.
- Gmail: recent inbox message identifiers, thread identifiers, subject, sender, date, label/unread status and inbox unread count. The app requests Gmail metadata access and does not request or fetch message bodies or attachments.
- Authorization credentials: OAuth access and refresh tokens needed to maintain the connection.
Why and how the data is used
Calendar and Gmail data populate the owner’s dashboard. While the PC and local server run, LurkCrew refreshes the dashboard approximately once per minute. The current cache holds up to 1,000 events in the configured time window and twelve recent inbox headers. The application does not send mail, delete mail or modify calendar events.
Agents, model providers and sharing
The Google connection does not automatically pass the inbox or calendar cache to agents. The owner can explicitly create a task from a dashboard item. This copies the selected title, source information and metadata into the local task record. When the owner asks an agent to work on that task, its context can be sent to the chosen local or cloud model and any enabled independent reviewers.
Cloud processing is governed by the configured provider’s terms and data controls. The owner should choose providers and controls appropriate for any Google data included in a task. This connection has no feature for selling Google data, advertising, credit decisions or training generalized AI models. Google credentials are not included in model prompts.
Storage and protection
The desktop application stores Google authorization credentials and its dashboard cache on the owner’s PC, encrypted with Windows user-scoped Data Protection API (DPAPI). API traffic uses HTTPS. The browser dashboard is served locally; optional remote access uses the owner’s private Tailscale connection.
Tasks and conversation history are separate local records and are not protected by the Google cache’s encryption. The private image vault protects its own image content; it is not encryption for all workspace records. Owner-created backups may retain copies of local records.
Retention, disconnection and removal
The Google cache is replaced as successful syncs retrieve current data. Disconnecting Google in LurkCrew removes the account’s tokens, email identity and Google cache from the active local Google store; the desktop OAuth client configuration is retained for a later connection. Disabling a service removes that service’s active cache.
Disconnection does not delete tasks or conversation history the owner already created from Google items, or copies in backups. Those records must be managed separately. Google consent can also be revoked through Google account connections. Revocation stops future authorized retrieval but does not erase data already copied locally.
This information website
These static information pages do not connect to Google accounts, receive workspace data, use analytics scripts or set application cookies. The hosting service may process normal request information, such as IP addresses, requested URLs and browser headers, to serve and protect the site.
Questions and changes
For questions about the personal application or this policy, contact jeffmatesevac@gmail.com. This policy will be updated when the connector’s data access or use materially changes.