Privacy policy

Information we handle

• Website and security data. When you visit, we and our service providers may process your IP address, request time, requested page, browser or device details, and security signals to deliver and protect the site. Product analytics records page visits, selected button clicks, acquisition sources, coarse country information and conversion events. Signed-in analytics may include your account identifier, email address, name and access state. Analytics is processed in the EU; visitor IP addresses are used transiently for coarse location and then anonymized. Session replay and automatic capture of form inputs are disabled. Authentication codes, API keys, prompts, tool contents and generated responses are not sent to analytics. We do not use advertising trackers. The pricing page uses your browser's timezone to display local hours; that selection runs in your browser.
• Account data. If you sign in, we process your email address, name if provided, account identifier, verification status, and session information. Email sign-in uses a one-time code. If you choose an external sign-in service, we receive the basic identity and email information needed to sign you in. We do not request access to your files or repositories. We do not ask you to create a RedWatts password.
• Workspace and API data. We keep your account settings, API-key labels and security records, and any applicable subscription status. We also keep usage and diagnostic records, such as the model used, request time, token counts, technical identifiers, and whether a request succeeded or failed.
• Content you send to the API. Your prompts, tool inputs, and generated outputs are processed to deliver responses. RedWatts does not save plaintext prompts or outputs in its usage history. Service providers helping us operate RedWatts may retain request content under their own policies, so do not submit information you are not authorized to share.
• Messages to us. If you email support, we receive your address and whatever you include in the message so we can respond.

When you choose card checkout, we send Polar your account identifier, email address, optional name and selected plan to create checkout and associate access with your account. We receive customer, subscription, payment-status and order information needed to manage access and support billing. Polar acts as merchant of record and handles payment details under its privacy policy. RedWatts does not receive or store your full card details.

If you choose an agent-native wallet subscription, we process your wallet address and network, signed ownership proofs, selected access hours and timezone, payment authorizations and transaction references. Payment verification and settlement services receive the information needed to process that transfer. Wallet addresses and transfers are recorded on a public blockchain and cannot be deleted from that chain. We store API-key hashes, not your wallet private key or the agent's locally generated API-key secret. Your agent keeps its own credential and recovery file on your machine.

Why we use it

We use account and request data to provide sign-in, operate the workspace and API, deliver AI responses, show usage, and answer support requests. Where applicable, this is necessary to provide the service or take steps you request before using it. We also use technical and usage data to protect accounts, enforce rate and abuse limits, diagnose failures, plan capacity, and understand product use and conversion paths. We rely on our legitimate interests in operating a secure and reliable service where that basis is available, while considering your rights. Non-essential device tracking may require consent under applicable law; accepting our terms is not analytics consent. We may retain and disclose limited information where required by law or to establish, exercise, or defend legal claims.

Who receives information

We share information only as needed with service providers that support hosting, security, account sign-in, email delivery, payment processing, product analytics, and processing requests. If you choose an external sign-in service, that service also handles the sign-in step under its own privacy policy. Providers that process request content may have different retention and model-improvement practices; we do not promise zero retention of request content by every provider.

Only authorized personnel may access account and operational data for support, security, and service administration. We do not sell your personal information or share it for targeted advertising. We may disclose information when legally required or in a business transfer, subject to applicable safeguards.

Cookies and local storage

We use essential cookies to keep you signed in and protect sign-in attempts. Sessions last no longer than 30 days, and one-time sign-in data expires sooner. Product analytics uses cookies and browser storage to recognize visits and connect them with a signed-in account. A random sign-in-attempt identifier is stored in the current tab for up to one hour. Browser analytics respects Do Not Track; server-confirmed purchase and refund records are separate from browser tracking. We do not use advertising cookies. Your chosen time block may be saved in browser session storage so it survives sign-in. This is only a preference; it cannot grant paid access. We do not store your account session or API keys in browser local storage; an API key you create is shown once and must be stored securely in your own client.

Retention and security

Short-lived sign-in and security records expire after their purpose is served. We keep account details and usage records while your account is open and as needed to operate the service, investigate abuse, resolve disputes, or meet legal obligations. If you ask us to close your account, we will delete or de-identify data that is no longer needed, except where a legal obligation, security investigation, or legal claim requires further retention. We keep support correspondence as long as needed to handle the request and related obligations.

We use encrypted connections, access controls, and other safeguards to protect your information. No internet service can guarantee absolute security.

Processing across borders

Some service providers may process information in different locations. We do not currently offer a region-specific processing commitment. If your work requires a particular processing location or transfer safeguard, contact us before sending it through the API.

Your choices and rights

You can sign out and revoke API keys in the workspace. For access, correction, export, account closure, or deletion requests, email support@redwatts.com. We may need to verify your identity before acting. Depending on applicable law, you may also have rights to restrict or object to processing, withdraw consent where consent is used, or complain to a data-protection authority. Some data may need to be retained for the reasons described above.

Changes to this policy

We will update the date at the top when this policy changes. If a change materially affects how we handle your information, we will provide additional notice where required.