Clear boundaries for product data and optional analytics.

We handle account and contact information you provide, workspace and billing records, and the URLs, goals, scenarios, test results, screenshots, and API-test configuration needed to provide the service. Security records can include IP-derived rate-limit identifiers, device or browser information, timestamps, and audit logs.

Optional analytics uses page groups, interaction names, plan category, browser or run type, outcomes, performance measurements, and a pseudonymous identifier. We designed the analytics boundary not to send names, email addresses, phone numbers, raw account identifiers, prompts, screenshots, request bodies, credentials, payment identifiers, or precise location to Google Analytics.

We use necessary information to provide and secure the product, run requested tests, retain evidence under the applicable plan, process billing, prevent abuse, support customers, meet legal obligations, and improve reliability. With your permission, we use optional analytics to understand acquisition, activation, feature use, and whether product journeys are working.

Depending on the context and applicable law, we process necessary account and product data to perform our contract with you, protect the service and our legitimate interests, comply with legal obligations, or respond to your request. Optional Google Analytics is based on your consent where consent is required. You can withdraw that consent at any time through Cookie settings.

Google Analytics is off until you choose Accept analytics. If you accept, the browser can load Google's analytics script. We may also use Google Analytics Measurement Protocol to report server-confirmed lifecycle outcomes such as a trial start, checkout completion, subscription start or cancellation, and payment failure. Those events use a pseudonymous identifier and a restricted parameter list.

Rejecting or later withdrawing analytics permission prevents subsequent optional browser and server analytics events. Necessary service, fraud-prevention, security, support, and billing records are separate and are not controlled by this optional analytics choice. We do not enable user-provided data collection or send hashed contact details to Google through this implementation.

Google explains how it uses information from sites and apps that use its services in its notice, How Google uses information from sites or apps that use our services.

Necessary cookies support authentication, security, preferences, and requested product functions. The first-party analytics preference cookie stores only whether analytics is granted or denied and the current notice version. It lasts up to 12 months unless you change it or clear browser storage.

We use service providers for hosting, databases, browser-test execution, payments, email, observability, AI model routing, and—when allowed—Google Analytics. These providers process information only for their contracted role and may operate in other countries, including the United States. Where required, we rely on appropriate contractual and organizational safeguards for international transfers. Public evidence pages are shared only through customer-controlled, token-gated links; the badges described below appear only when you create one.

Tested badges are opt-in. A badge shows the verdict and the last-run date only — never the token-gated share URL or run detail.

Revoking a badge delists its slug so it no longer updates. Third-party image caches outside our control, such as GitHub's camo proxy, may retain the last badge image briefly after revocation.

Weekly scheduled tests are available to signed-in accounts. We store your account email to deliver the summaries, and every email carries an unsubscribe link. If a watch's URL fails three weeks in a row, we pause the watch and email you once about the pause. Hard bounces and spam complaints suppress further delivery to that address automatically.

Anyone can report misuse of a public proof page or badge to [email protected]. We handle the report, the reported address, and any enforcement decision — such as delisting a badge or suspending access — for as long as needed to keep the service safe, subject to the retention rules below.

Google Analytics event and user-level data is configured for a maximum retention period of 14 months. Aggregated reports may remain after user-level data expires. Test evidence follows the retention period of the customer's plan. Account, transaction, security, and audit records are retained only as long as needed for the service, dispute prevention, legal obligations, and legitimate security purposes. Badge and weekly-watch rows are deleted with the run or account they belong to.

We delete or de-identify information when it is no longer needed, subject to backups, fraud prevention, accounting, tax, and other legal requirements. You can request account or personal-data deletion using the contact below.

Depending on where you live, you may have rights to access, correct, export, restrict, object to, or delete personal data, and to withdraw consent without affecting earlier lawful processing. You may also complain to your local data-protection authority. We will verify requests proportionately before acting on account data.

We do not sell personal information. This analytics implementation does not enable ads personalization, Google Signals, or automatic user-provided data collection. Well Tested is a business software service and is not directed to children under 18.

Pyramid Works LLC is responsible for Well Tested. For access, correction, objection, withdrawal, or delete requests, email [email protected]. Include the account email and the type of request, but do not send passwords, API keys, or payment-card information.

We may update this notice when the product or applicable requirements change. Material changes will receive a new effective date and an appropriate notice.