Trust / draft local disclosures

Cookies and privacy choices

Understand the data boundaries and release prerequisites before considering AGINDOW. No operative legal policy is published here.

Draft disclosure

Not effective. No approved legal entity.

Version: draft-1
Source inventory reviewed: 2026-10-22
Effective date: Not effective; no approved policy date.
Responsible entity: Legal entity: unconfirmed. AGINDOW is the project name.
Contact: Legal contact: unconfirmed. General project contact: support@agindow.com; not a verified rights-request channel.

No deployed inventory approval, policy approval or provider/transfer approval is recorded. These pages describe project implementation boundaries, not an operative privacy policy, binding terms or a production assurance. The public site may be served while this record stays incomplete; trust paths stay noindex until a source-reviewed release replaces the draft.

Privacy choices

Optional tracking is off. The public site is usable with JavaScript disabled and loads no optional analytics script, advertising, cookies or browser storage. Contact, demo and launch-interest forms include an unchecked, per-submission conversion-analytics choice; it may send only the form type, never the page URL, email, message or other field value. No analytics provider is configured, so no event is sent today. This page writes no consent receipt and stores no preference.

There is no site-wide optional tracking switch to enable today. Introducing optional processing requires reviewed purposes/providers and a qualified consent mechanism that prevents loading before applicable consent and supports withdrawal. The form choice is not a tracking cookie and is never inferred from submitting the form. Privacy choices stay reachable in every footer.

Public site and dashboard have different boundaries

The private dashboard backend uses essential Better Auth session cookies configured host-only, Secure, HttpOnly and SameSite=Lax, with cookie caching disabled. Authentication cookies are not set by these public pages. Exact deployed names, lifetimes, recovery behavior and hosting request logs still require the approved inventory; no hosted login is qualified.

Authentication and cookie implementation ↗

Pre-alpha / current prerequisites

Local Rust/WASM and Node/Python SDKs; both packages are unpublished. Detection is off until you configure it. Statistical detection requires explicit scoped baseline/live windows and readiness checks. The default guest does not supply selective repair.

Verified selective repair requires an explicitly integrated trusted engine, sufficient confidence and verification gates. Installing an adapter or changing mode alone does not enable that capability.

No automatic retries or automatic write execution. Replay requires an explicit caller decision, original idempotency binding and dispatch evidence; local replay state is process-local, with no durable/distributed replay.

Response inspection can follow a completed upstream write and cannot undo it. Payload verification and HTTP acceptance do not prove write integrity. These local guard paths do not supply independent write-integrity proof.

Hosted services are not deployed. Examples and fixtures are local evidence; no production traffic or full streaming qualification is claimed.

Status and implementation boundaries ↗