Legal readiness / counsel-review draft 0.6

Trust starts before checkout.

Owner-reported preparation scope: initial tests are planned in Israel, the United States and Australia, with intended site purchases from all 21 Eurozone states. This is planning scope, not an approved order list: actual site accessibility and country-level order acceptance are unverified, and orders are not enabled. Buyer type is unknown. Canada is not in the current first-market list, and future acceptance remains unknown. Jurisdiction-specific applicability requires professional review. A future EU post-quantum encryption service is a separate, unapproved offer.

ATACSYS is preparing a supervised role-review service. Payments, automatic subscriptions, public role-request intake and broad production deployment remain disabled until the commercial, legal, privacy and tax gates are complete.

Clear boundaries today. Complete terms before payment.

The public site explains the intended service without pretending that unfinished commercial functions are live.

Commercial

No live payments

No card collection, automatic renewal, paid entitlement, escrow or creator payout is active.

Access

Role review

A future request will be reviewed manually. A first test is designed to stay within an agreed low-risk task.

Jurisdiction

Market priorities and eligibility

The owner-reported preparation scope is initial tests in Israel, the United States and Australia, with intended purchases through the site from all 21 Eurozone states. This is not an approved market or order list. Buyer type is unknown; Canada is not in the current first-market list, and future order acceptance remains unknown. Seller, provider, tax, privacy, accessibility and jurisdiction reviews remain open, and no order is enabled. Owner intent does not prove deployed website accessibility or service availability in any territory.

Public documents in plain English.

These pages are public working drafts for role-review transparency. They do not replace a signed order form, data-processing agreement or final counsel-approved commercial terms.

Terms of Service

Service definition, role-review limits, customer responsibilities, AI limitations and suspension rules.

Privacy Notice

Proposed collection boundaries, purposes, providers, retention and rights for a future approved release; public request intake is not open in this build.

Cookie and browser storage notice

A source-only inventory of local storage, the rate-limit cookie, the disabled analytics choice, and what has not been checked in a deployed browser.

Acceptable Use

Prohibited workflows, high-impact decisions, sensitive data and actions that always require human approval.

Refunds & cancellation

Current no-payment state and the disclosures required before future paid plans are enabled.

Before you pay

The plan, employee, usage, tax, renewal and memory details a future checkout must show.

Paid-launch gates: Checkout stays closed until these decisions are real.

Technology alone does not create a responsible commercial service.

Legal identity

The legal seller, authorized business name, registration status, and service address have not been verified for publication. This public draft intentionally omits private owner details. Add seller information only after document verification, professional review, and the owner's approval for publication.

Data contract

Approve the data map, retention, transfers, processors, rights process and customer DPA.

Billing contract

Confirm the contracting seller, any payment-provider role, taxes, invoices, cancellation, refunds and signed payment-event controls.

Production controls

Complete identity, access, audit, backup, incident response, accessibility and support readiness.

ATACSYS mark

Questions about role review?

The owner intends to use hello@atacsys.com for contact, privacy and deletion requests, but the mailbox is not configured and needs setup. There is no active request-intake route in this draft. Do not send personal data, credentials or confidential information to that address until setup and the response procedure are verified. A security-reporting route also remains unverified.