CARAWAI

This notice covers the private beta version of CARAWAI Capture BETA used by approved testers, collaborators, and project operators. It is not a public consumer service.

CARAWAI collects data only for approved testing and only while capture is active or while the tester is using CARAWAI controls.

• Browsing activity during an active capture session, including page URLs, domains, titles, tab state, and navigation timing.
• Interaction events such as clicks, scrolls, selections, copy-event metadata, capture controls, notes, and export actions.
• Visible page content needed to describe the workflow, such as rendered text, page structure, selected text, and optional screenshots when enabled for an approved test.
• Technical metadata such as extension version, session identifiers, diagnostic events, and export receipts.

CARAWAI is not designed to collect passwords, payment information, private tokens, cookies, or unrelated personal content. Because it records browser workflows, testers should use a dedicated Chrome profile and avoid unrelated sensitive pages during capture.

• Evaluate whether CARAWAI can accurately record browser workflow traces during approved tests.
• Debug capture reliability, export behavior, privacy controls, and tester setup issues.
• Prepare session exports, workflow summaries, and research handoff materials for approved CARAWAI collaborators.
• Improve the prototype's safety, usability, and trace quality before any broader study use.

CARAWAI does not sell tester data, show advertising, mine cryptocurrency, or use browsing data for credit, lending, employment, insurance, or unrelated profiling decisions.

CARAWAI uses tester data only for consented browser workflow capture, export, provenance, approved workflow summarization, debugging, security, retention, and policy enforcement.

• No sale of tester data.
• No advertising or personalized-ad use.
• No credit, lending, employment, insurance, housing, or eligibility decisions.
• No unrelated profiling, data brokerage, or model training on raw session evidence.

CARAWAI stores capture state in the tester's browser profile and can create local export files for review. Approved tests may also send selected session evidence to a configured research backend for workflow analysis, summaries, and debugging.

Access is limited to approved CARAWAI project collaborators and test facilitators who need the data for beta evaluation, research validation, debugging, or safety review.

Approved backend, infrastructure, or LLM providers may process selected session evidence only for the configured CARAWAI run. They must not retain, train on, or reuse raw session evidence for unrelated model training, advertising, profiling, analytics, resale, or product development.

Local browser state remains until the tester or project operator clears CARAWAI data, removes the dedicated Chrome profile, or uninstalls the extension. Exported test artifacts are retained only as needed for approved beta evaluation, debugging, and research validation, then deleted or de-identified when no longer needed.

Testers can request deletion or correction by contacting andrew@andrewnordstrom.com.

• Use a dedicated Chrome profile for CARAWAI testing.
• Pause or stop capture before visiting unrelated or sensitive pages.
• Avoid entering passwords, payment information, private tokens, or unrelated personal content during capture.
• Ask for test data to be deleted or corrected by contacting the project owner.

This notice may be updated as CARAWAI changes. Material updates will be reflected on this page before the private beta expands to additional testers.