Privacy Policy
OpenClaw. Last updated: 1 November 2026.
Who this covers
OpenClaw is a personal tool run by Dev Nambiar ("I"). In practice the only account it connects to is my own Google account. This policy explains what it does with that data anyway, because Google asks for it and because it's the right thing to write down.
What data OpenClaw accesses
When I sign in with Google, OpenClaw requests access to Google Calendar. That means:
- My calendar list and the events on them (titles, times, locations, descriptions, attendees).
- The ability to create, change and delete events when I ask it to.
- Basic account identity (my email address), so it knows which account is signed in.
It doesn't request access to Gmail, Drive, Contacts, or any other Google service.
How the data is used
- To show me my schedule and answer questions about it.
- To create or edit events when I request it.
That's all. Calendar data isn't used for advertising, profiling, analytics or training any model, and no human reads it except me.
Sharing
I don't sell calendar data, and I don't give it to third parties. It's sent only to the services needed to carry out my own requests, and only for that purpose. It may be disclosed if the law requires it.
Storage and retention
- Google sign-in tokens are kept only so OpenClaw stays signed in for me. They live on infrastructure I control and aren't shared.
- Calendar content is fetched when needed. It isn't kept as a long-term copy beyond what running a request requires.
- Tokens are protected using access controls on the systems I run it on.
Deleting your data and revoking access
- Revoke OpenClaw's access any time at myaccount.google.com/permissions. Stored tokens stop working immediately.
- To have stored tokens or any saved data removed, email devacc.sif@gmail.com. I'll delete it.
Google API Services User Data Policy
Children
OpenClaw isn't aimed at children and doesn't knowingly collect their data.
Changes
If this policy changes, the date at the top changes with it.