Privacy Policy
Strunk Privacy Policy
Last updated: August 6, 2026
Strunk helps people publish drafts from Claude to Google Docs, bring reviewer comments back into Claude, and apply approved revisions to the same Google Doc.
Information we process
Strunk processes the information needed to provide the review workflow:
- Account and authentication information, including your Strunk account identifier.
- Google OAuth tokens after you connect Google Docs. Refresh tokens are encrypted at rest.
- Document mapping data needed to update the right Google Doc, including user id, hashed local document key, Google document id, and version.
- Document content, titles, URLs, and comment text only while handling your publish, pull, reply, resolve, or revision request.
What we do not store
Strunk does not store Google Doc bodies, document titles, document URLs, or reviewer comment text. Google Docs remains the source of truth for the published document and review comments.
How we use information
We use information only to provide and maintain Strunk, including to:
- Create or update Google Docs you ask Strunk to publish.
- Read reviewer comments from Google Docs you use with Strunk.
- Apply revisions, replies, and resolves that you approve.
- Authenticate requests and protect the service from abuse.
- Debug, secure, and improve the service.
Google user data
Strunk uses Google's limited drive.file permission so it can work with Google Docs it creates or files you explicitly open with Strunk. Strunk's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Sharing
We do not sell your data. We share information only with service providers needed to run Strunk, with Google when you ask Strunk to work with Google Docs, when required by law, or with your consent.
Security
Strunk uses HTTPS in transit. Google refresh tokens are encrypted at rest. We keep stored document metadata minimal by storing hashed local document keys rather than document bodies, titles, URLs, or comment text.
Your choices
You can revoke Strunk's Google access from your Google account settings. To request deletion of Strunk account data, contact us through the channel where you received access to Strunk.
Changes
We may update this policy as Strunk changes. If we materially change how we use Google user data, we will update this policy and request any required consent before using that data in a new way.