Privacy policy
Last updated November 13, 2026. dingding is a personal, open-source assistant operated by its owner. This page describes how its Google-connected features use data.
Access and purpose
With the owner's authorization, dingding reads Gmail to create inbox briefs and answer questions; creates Gmail drafts; changes message labels or moves eligible messages to Trash when the owner requests cleanup; and reads or writes events in the calendar available to the app when the owner requests it. dingding does not send email or permanently delete messages.
Where data goes
Google OAuth credentials remain on the owner's computer. The local broker reads Google data and runs privacy filtering before sending selected summaries and redacted text to OpenClaw and the configured cloud AI provider for the owner's requested tasks. The owner also receives responses through Telegram. Security-code and password-reset messages are withheld from the cloud assistant. Filtering can miss sensitive details; the project is not an audited privacy guarantee.
Storage and retention
OAuth credentials are stored locally until the owner revokes or removes them. Local caches and placeholder mappings support the assistant's work; placeholder mappings are normally removed after 30 days. Service providers may retain data under their own policies. The app does not sell Google user data or use it to train a general-purpose AI model.
Control
The owner can revoke Google access in Google Account settings, stop the local service, and remove locally stored credentials and caches. Requests about this policy can be made through the project's GitHub issue tracker.