Badsky Signup Kit Privacy Policy

What is sent to badsky.net

When you connect the extension to your account, it sends only the following data:

Account data: your Badsky account identity and the connection token.
Recipes: the fields you save (name, steps, parameters with their defaults, templates and outputs), so they reach your other browsers. While "Protect secrets in recipes" is off (the default), the values a recipe remembers for its secret parameters, such as passwords, are sent and stored in plain text with the recipe. Turn the setting on to keep secrets out of recipes; turning it on deletes the remembered values from your recipes here too. The environment a recipe is linked to stays in your browser. We keep the last 50 versions of each recipe, and deleted recipes for 30 days so your devices can sync the deletion.
Recipe runs: for each run, the recipe's id, name and version, the status, start and end times, the run mode, the id of the profile it used, the random seed a table row or a "New person each run" run made its profile from, the number of the step it stopped at (cursor), the id of its table run and its row number (rowIndex), links to the run it repeated, continued or was part of, and the status message; for each step, its id and kind, its status, times, number of attempts, which matched element it used, whether it was copied from the run it continued (copied), and when it failed, the error kind and the error message. Messages are redacted first: every secret value of the run is replaced with [redacted] and every web address or page path with [url], but an error message can still quote other page text (such as the text an assertion found). Never the recipe as it ran, the values the run used or extracted, page addresses, or the sites it worked on. A parameter table run is sent as one summary with, per row, its status, seed, run id, the step it failed at (failedStep: its id, position, error kind and message) and the redacted message of a failure. Runs are kept for 30 days, and an account can start 200 runs per day.
Inbox messages: messages received by your Badsky inbox that the extension reads for verification steps.
Form structures for AI field mapping: only the structure of a form that the built-in rules could not classify, meaning field labels, input types, option texts, constraints (such as length limits and patterns) and nearby text. Nearby text is what the page shows next to a field, so it can include page content such as a name on an admin form; email addresses, phone numbers, card numbers and the values the extension fills are masked before sending. We never receive the values you or the extension type into fields, cookies, page URLs or secrets. Answers are cached by a fingerprint of the form structure for 30 days, and AI mapping is limited to 100 requests per day per account.
Encrypted vault blobs: secrets (2FA accounts, role logins, saved session snapshots, the DuckDuckGo token) are encrypted in your browser before upload, and we cannot read them. We store only the ciphertext with its item type, key-derivation settings and timestamps, never labels, names, cookies or your vault password. We also store the vault meta: the key-derivation settings and a verifier, which is a short known text encrypted with your key so a device can check the password; it reveals neither the password nor the key. The vault is limited to 200 items and 5 MB per account, and deleted items are kept briefly so your devices can sync the deletion. A vault you use without a password is never uploaded: nothing of it reaches badsky.net.
Usage counters: how many runs and mappings you used, for plan limits.

What stays in your browser

Test profiles and the per-site field memory (which form field means what on a site you filled) are stored locally in your browser and are not synced to badsky.net yet. Recipes and runs are kept in your browser first and work offline; while an account is connected, changes are sent when the connection is back. A run keeps the values it used and extracted (secrets as [redacted]) and the addresses of the pages it worked on only in your browser, for 30 days; run reports you export leave the extension only as a file you download. Recording a recipe happens in the page you record: what you type into a password or one-time code field never leaves the page, the recipe gets a parameter in its place. Secret values you type when a run starts are kept only in the browser session memory, so a failed run can be continued, and are gone when the browser closes.

Network captures (the requests, redirects, headers, request bodies, response bodies where you turned them on, and cookie changes of a tab) are made only on the sites you enabled as environments, and only while the side panel is open or while a run works in that tab. Capture stops when the panel closes; only when the extension restarts in the background does a panel that was open get 30 seconds to reconnect. A run also reads the tab's local and session storage before and after each step, to show what each step changed; those values are kept with the run. Captures are redacted before they are stored: authorization and cookie values, values under names like password, token, secret, otp, card, cvc or iban (rules you can change in the settings), and every secret a run uses. Other values, including storage values under other names, are kept as the site sent or wrote them. The cookie history never stores cookie values, only a short fingerprint that shows a value changed. The values the rules replaced are stored encrypted with a key that lives only in the browser session memory; after the browser restarts the key is gone and they cannot be read any more. Captures are never sent to badsky.net: a live tab's captures are deleted when the tab closes, and a run keeps its own redacted captures and storage changes in your browser for 30 days, deleted with the run. A HAR export of captures leaves the extension only as a file you download. Response bodies are read only on environments where you turn on "Capture response bodies", through a script the extension adds to those sites only, or during runs of the separate reliable mode build.

2FA secrets and session snapshots (cookies, local and session storage, and optionally IndexedDB data of a site) are stored only encrypted in your vault, never as plain text. With a vault password, the vault key is held in the browser session memory only and is dropped when the vault locks automatically or when you lock it. If you choose to use the vault without a password, its key is a random key kept in the extension's own storage in this browser, which web pages cannot read, next to the encrypted items, and it is never sent to badsky.net. That vault never locks and stays in this browser only, so anyone with access to this browser profile can read its secrets. You can set a password at any time in the Vault card. Your vault password cannot be recovered. "Reset vault" deletes the whole vault, in your browser and, when connected, its encrypted items and meta on badsky.net (permanently, with no copy kept), so you can start with a new password. We keep only a reset counter and its date, so your other devices learn of the reset and delete their copy instead of uploading it again. The undo history of the session tools is kept in the browser session memory only, never written to disk and never sent anywhere.

The optional cookies permission is asked for only when you open the cookie editor or use sessions and roles, and is used to list, edit, export, import, save, restore and clear (a recipe's Sign out step, a parameter table row that starts signed out) the cookies of the site you are working on, and to show when the cookies of an enabled site change in the Network tab. Cookies you export leave the extension only as a file or clipboard text you choose; they are never sent to badsky.net. To suggest values while you edit a recipe step, the extension reads the cookie names and domains and the request URLs of the tab's site in your browser; they are shown only in the editor and never stored or sent anywhere.

The webRequest permission is part of the install and sees only the sites you enabled as environments. It is used only while the side panel is open, to show the requests of those sites in the panel's window, or while a run works: to keep the requests of the tab the run works in for its timeline, to wait for, read or check them, and to follow the redirects of a page the run opens. What it sees is redacted and stays in your browser, as described above. Access to a site is asked for per environment (or when a run needs another site), never for all sites at install. The debugger permission is not part of the extension you install from the store: only a separate build with reliable mode asks for it, at install, to send clicks and typing as trusted input and to read the response bodies of the run's requests while a run works on an environment with reliable mode on.

The notifications permission shows a system notification with the address, subject and sender when new mail reaches one of your inbox addresses; you can turn it off in the extension settings. While you have an inbox address, the extension checks your Badsky inbox for new mail every 30 seconds; which messages you have read is kept in your browser only and never sent anywhere. The tabs permission lets the extension read the address and title of the tab you are on so the side panel can show which site it would fill, which session tools apply, and offer to enable it. It does not record, store or send your browsing history, and it reads or changes page content only on sites you enabled.

Third parties

The extension has no third-party telemetry or analytics.

AI field mapping is processed by Anthropic (the Claude API) on behalf of badsky.net. Anthropic receives only the form structure described above, never field values, cookies, page URLs or secrets. The extension never contacts Anthropic directly: requests go through badsky.net.

Contact

Questions or deletion requests: use the contact options on badsky.net.