Skip to content

docs(privacy): say exactly what gcal never sends to a WireCat server - #481

Merged
leemour merged 1 commit into
mainfrom
docs/privacy-gcal-narrow
Nov 1, 2026
Merged

leemour merged 1 commit into
mainfrom
docs/privacy-gcal-narrow

Conversation

@leemour

@leemour leemour commented Nov 1, 2026

Copy link
Copy Markdown
Member

Task

Follow-up to #480. The new gcal section said "Nothing goes to a WireCat server". That is too broad: a WireCat Desktop bug report can carry each installed tool's last 20 failed run records (the page's own bug-report section), and gcal is one of those tools.

What

In lib/privacy.ts, in en, ru and es, the sentence now says what never goes to a WireCat server: the events and the Google sign-in. The Drive and zm sections already say it this way.

Testing

  • biome check lib/privacy.ts passes.

🤖 Generated with Claude Code

The gcal section said nothing goes to a WireCat server. A bug report from
WireCat Desktop can carry a tool's failed run records, so the sentence now
names what never goes there: the events and the Google sign-in, as the
Drive and zm sections do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 995aa17 into main Nov 1, 2026
2 checks passed
@leemour
leemour deleted the docs/privacy-gcal-narrow branch November 3, 2026 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant