LOCAL AGGREGATES
Local aggregates
On your Mac, Keydance turns logical keyboard actions, clicks, and pointer movement into daily aggregate counts, time periods, and trends for Overview, Statistics, and historical dates. Pointer movement is a screen-projected estimate, not a physical trail.
This product data is stored in the macOS sandbox container and stays on your Mac by default.
NOT PART OF THE RECORD
Not part of the record
The Keydance macOS app does not save typed text, clipboard contents, screenshots, app/window/URL context, file paths, raw keyCode sequences, per-event timing or order, original coordinate trails, prompts, replies, or Agent conversation content.
Keyboard actions are counts of logical actions, not words, output, or productivity. Heatmaps and trends are not used to infer what you were doing.
PERMISSIONS
Permissions and optional connections
Recording keyboard actions, clicks, and pointer activity requires macOS Input Monitoring. If you revoke it, Keydance stops recording those aggregates. Accessibility permission is not required.
When macOS enables Secure Input in a password field or another protected context, Keydance pauses keyboard, click, and pointer aggregation. Recording resumes only after that context ends, and raw input from it is not saved.
Optional Agent edit aggregates are created locally only for sources you choose to connect and that the app currently shows as available; Codex is one example. Authorization follows what the app currently shows for each source. After connection, Keydance converts successful text additions and changes into aggregate counts without saving text, file paths, prompts, replies, or conversation content.
WEBSITE ACCESS
Website access
keydance.app introduces the product, provides support, and publishes this policy without requiring an account. Website analytics is separate from the Mac app. Visiting the website does not give Google or the website access to input activity, Agent aggregates, or ranking identities in the app.
Only after you explicitly allow website analytics do we load Google Analytics 4 (GA4) to measure page visits, traffic sources, displayed page language, and App Store link clicks. A click does not mean an installation or purchase. We do not record screens or replay browsing sessions, collect text you type, or link website analytics to app data.
Before a choice is made, or if you decline, GA4 is not loaded and no cookieless visit or consent-status signals are sent to Google Analytics. Declining does not affect browsing, viewing rankings, or visiting the store. Use Analytics settings on any page to change your choice. Withdrawal stops subsequent analytics and clears this website's analytics cookies; it does not automatically delete data already sent.
If allowed, GA4 uses first-party analytics cookies to distinguish browsers and sessions. It receives page information, referring domains, browser/device information, and related network requests, and can derive statistics such as approximate location. This does not identify real people precisely. We do not enable advertising links, Google Signals, or personalized advertising. Sent page addresses include only public pages and agreed campaign labels, without other query contents or URL fragments.
Your analytics choice is saved in this browser for 180 days, after which we ask again. This website's analytics cookies are set to a maximum of 180 days. GA4 user- and event-level retention is set to 14 months; monthly aggregate reports without browser identifiers may be kept longer. Google processes data under its policies, which may involve servers outside your region. Clearing browser storage resets your local choice.
Google Search Console is used to review search impressions, clicks, and indexing; it does not require an additional visitor-tracking script on the website. Hosting, CDN, DNS, and similar infrastructure may still keep limited technical logs, such as request times, addresses, status codes, or network addresses, for security, reliability, and troubleshooting. These logs are separate from optional analytics and follow the respective service policies.
Google Privacy Policy · How Google uses information from partner sites
YOUR CONTROL
Your control and contact
In Keydance you can view local records, use Clear All Data, turn off recording at login, or pause, leave, and delete ranking data. You can also revoke Input Monitoring in macOS Settings. Clear All Data first handles the ranking identity and upload queue, then removes local records. If network deletion fails, the app keeps the minimum retry state and does not claim that everything is complete.
Ranking uses an access token and recovery code linked to the pseudonymous participant identity; no Apple, WeChat, or other account login is required. In ranking management you can choose to view and save the participant ID and recovery code. Both are sensitive credentials. After reinstalling a device, if you do not have them and cannot prove the original participant identity, the service will not restore old data to a new identity.
If you have a question about data handling, contact Keydance through the support page. Before sending anything, remove original input content, file paths, prompts, replies, and conversation content.