Contact security and privacy

Our public contact form accepts selected topics, not written messages or attachments. Google sign-in is required to reduce anonymous abuse. Google sign-in confirms access to an account; it does not verify a person's legal name, customer status or intentions.

What this contact system processes

When you start secure contact, Google handles sign-in and Cloudflare performs security checks. We receive the email address associated with the signed-in Google account and a protected account identifier. We do not request access to your Gmail messages, contacts or payment accounts. Accounts using non-Google-hosted email can be held for manual review before we contact the address.

Cloudflare sees the network address used for the connection. Our contact application converts it to a keyed security identifier and does not put the raw address, Google profile name, identity token or browser user-agent into the request spreadsheet or notification email. Cloudflare and Google process data under their own service terms and privacy policies.

Cookies and retention

Starting secure contact creates a first-party security cookie lasting up to 30 minutes. It is used for the contact session, not advertising. The application clears network and browser security identifiers from its new request records after 30 days and deletes those request records after 90 days. A scheduled maintenance task carries this out while the deployment is active. Historical records in earlier versions' spreadsheets are not modified by this update. Account block identifiers remain until our team removes the restriction.

Request limits and review

One request per account every 10 minutes and up to three per 24 hours are permitted. High-volume network activity may result in review; a shared network address is not proof of misconduct. The system also limits overall intake and email notifications. Accepted requests may be held or queued for review instead of immediately generating an email.

Access to records

Request information is used for responding, managing abuse and supporting the service. Internal emails include a fixed inquiry topic, a request reference and a link to a private record, rather than visitor-written material. Access to the record must remain restricted to authorized staff. For the general policy, see our Legal and Privacy page.