Privacy Policy

Last updated: 2026-08-04

webclaw3 is built around a simple privacy principle: your browsing happens on your machine, with your own login state, and stays there. This policy explains what limited data we do and do not handle.

What runs locally

Skills execute on your own computer inside your own browser session. When a skill needs to be logged in to a site, it uses your existing browser login state. We never receive, store, or transmit your website usernames, passwords, cookies, or session tokens.

What we collect

Account information. If you sign in, we use Google OAuth to obtain your name, email address, and profile image solely to create and identify your account and to track your generation quota.

Site structure telemetry. When you choose to contribute, a skill may send back the public page structure of a site (such as element selectors and layout) to improve reliability and shared skills. This never includes your personal data, the contents of your accounts, or anything you typed.

Usage records. We keep minimal records needed to operate the service, such as how many skill generations an account has used.

What we do NOT collect

We do not collect your credentials, your cookies, the private contents of the sites you automate, your keystrokes, or your browsing history. Skills do not exfiltrate personal data.

How we use information

Information is used only to provide and improve webclaw3: to authenticate you, enforce fair-use quotas, generate and repair skills, and improve the reliability of shared site skills. We do not sell your personal information.

Data sharing

We rely on Google for authentication. Aside from such essential service providers, we do not share your personal information with third parties. Contributed page-structure data may be incorporated into shared skills, but it contains no personal information.

Your choices

Contribution is optional. You can stop using the service at any time, and you may request deletion of your account data by contacting us.

Contact

Questions about this policy? Open an issue on GitHub.