Disconnecting takes only what it brought

Disconnecting stops every watch channel, revokes the token with Google, deletes the pulled personal events, and leaves the platform's own bookings intact.

What it is

A teardown that stops channels, revokes the access token, deletes the connection row, removes the appointments that were pulled from Google, and clears the Google event ids from the platform's own bookings so they simply stop being mirrored.

Also called: revoke Google access · unlink calendar · remove my personal events

See it
Disconnecting takes only what it brought
🔒ridgelinepostframe.com/project/google718
Riding Arena
Framing · on schedule
A disconnect confirmation listing exactly what will be removed and what will be kept. Sample data — no customer information appears here.
How it works
  1. 1Watch channels are stopped best-effort.
  2. 2The token is revoked at Google.
  3. 3The connection row is deleted.
  4. 4Appointments sourced from Google are deleted.
  5. 5Platform-owned bookings keep their data, with the Google event id cleared.
Why we built it

The rule is written in the function: 'Their pulled personal events leave with them; our own bookings stay (just no longer mirrored).'

The problem
  • A disconnect that removed everything would have destroyed real work.
  • Leaving pulled personal events behind would keep private data in the system.
Sound familiar?
What you get
Personal calendar data leaves cleanly.
Business bookings survive the disconnect.
The token is genuinely revoked, not just forgotten.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →