construct://updated october 19, 2026

privacy policy

construct is a private, single-user command center run by Kevin Rucker. there is no sign-up and no public service.

who this covers

construct (construct.bykevinrucker.com) is an internal tool operated by Kevin Rucker for his own businesses. Its only user is its operator. This policy explains what the tool does with data from connected accounts, including Google accounts, so the operator and the services it connects to can see how that data is handled.

what construct collects

construct reads business data from systems the operator has connected: point-of-sale and payment processors, email marketing, social media statistics, task managers, bank and accounting feeds, and the operator's own Google accounts. It stores daily snapshots and summaries of that data in a private database so it can report on trends over time.

google user data

When the operator connects a Google account, construct requests access to Gmail (read and modify) and Google Calendar (read and create events) and the account's email address. It uses that access to:
  • search and display messages the operator asks for, and show the text of a message on request
  • on the operator's instruction: archive, mark read or unread, label, or move messages to Trash
  • on the operator's instruction: save a draft in that account's Drafts folder for the operator to review and send
  • list upcoming calendar events, and create events when asked
  • identify which business account a message or event came from
construct stores the OAuth refresh token for each connected account so it can keep working without re-authorising. Message and event content is fetched on demand when the operator asks for it and is not copied into the database, except where the operator explicitly files a summary or note. construct never sends email on its own: drafts are saved, not sent, and the operator sends them from Gmail. It never permanently deletes messages and never changes account settings.

how data is used, and with whom it is shared

Data is used only to inform the operator. construct does not sell, rent, or share Google user data or any other data with third parties for advertising or any other purpose. To produce summaries and answer questions, construct may send retrieved content, including the text of emails and calendar events the operator asked about, to Anthropic's Claude API as a processor acting on construct's behalf. No human other than the operator reviews this data.

limited use

construct's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

storage and security

Data is stored in a managed Postgres database (Supabase) and served from Vercel, both over HTTPS. Access to construct requires the operator's password. OAuth tokens are stored server-side and are never exposed in the browser.

retention and deletion

Tokens are kept until the account is disconnected. Disconnecting removes the stored token; the operator can also revoke construct's access at any time at myaccount.google.com/permissions. Snapshots and notes are retained for as long as the operator finds them useful and can be deleted on request.

contact

Questions about this policy go to the operator through bykevinrucker.com.
privacytermsbykevinrucker.com