Security and privacy
Data kept on the computer
Section titled “Data kept on the computer”Cantero Madera stores profile state, managed Chrome data, run records, and allowed run artifacts locally. Secrets such as proxy passwords, OAuth grants, generated Amazon passwords, and billing payloads use operating-system-backed encrypted storage rather than ordinary SQLite fields.
Sensitive values generally cannot be read back into forms. Billing edits require complete re-entry;
saved proxy passwords appear as [saved].
Central analytics
Section titled “Central analytics”The product can send limited pseudonymous, typed operational milestones used to understand product health. This is not a complete record of browsing actions. Local run events, messages, arbitrary page data, artifacts, passwords, proxy secrets, mailbox contents, and payment data are not general analytics payloads.
Review the current Privacy Notice and Notice at Collection for the controlling description and privacy-request process.
Safe support requests
Section titled “Safe support requests”Share only the minimum sanitized evidence needed:
- app version;
- profile display name;
- run ID and final status;
- sanitized error code; and
- exported run ZIP after you inspect it.
Never send a license key, Amazon password, full mailbox address when unnecessary, OAuth token, proxy password, card number, CVV, or unredacted account screenshot.
Billing-data warning
Section titled “Billing-data warning”Local encryption reduces casual exposure but does not by itself determine payment-card compliance. Use Billing Profiles only after your organization and Cantero Madera support have approved the payment-data handling for the release you are using.