AProject AnchorBack to home

TRUST CENTER

Know what Anchor can—and cannot—do.

This page summarizes the current product boundary. Contract terms, privacy notices and risk disclosures remain the controlling customer-facing documents when paid access opens.

Public pre-launch previewProduct pages are public; no application, customer account or payment is accepted.
AreaCurrent controlWhat it means

Market decisions

Customer-controlled

Anchor structures research and review. The user makes every decision.

Production orders

Not available

The initial paid product does not create, sign or submit production orders.

Funds and assets

Never held

The initial product does not receive, hold, safeguard or transfer customer funds or assets, and it does not operate a wallet, exchange or brokerage account.

Exchange credentials

Not collected

Do not enter API keys, passwords, private keys, seed phrases or authentication headers.

AI assistance

Constrained

AI may explain the workflow. Deterministic controls remain separate, and AI cannot authorize or execute a trade.

Pilot case data

Device-local by default

Detailed Pilot cases remain in the tester's browser unless the tester exports them.

Commercial feedback

Redacted and voluntary

Eligible Pilot feedback excludes instruments, hypotheses, account data, orders, balances and monetary P&L.

Fees

Fixed software scope

No performance fee, profit share, assets-under-management fee or transaction commission.

DATA FLOW

Minimum data by design.

Preview mode shows product information without collecting an application. When guided inquiries open, the form sends only the information the visitor intentionally provides through a protected relay. Payment credentials stay with the approved payment provider.

Read the Privacy Notice

FAIL-CLOSED ACCESS

Missing requirements keep features off.

Inquiry, Pilot AI, feedback, checkout and account capabilities have independent runtime gates. A marketing-page setting alone cannot open a protected workflow when its required identity, security or delivery evidence is absent.

Read the Risk Disclosure

SUPPORT & INCIDENTS

Keep sensitive material out of email.

Support and privacy channels must never receive trading credentials, seed phrases, full payment credentials, account balances, order records, identity documents or private strategy details. A working branded response path is required before public inquiries open.

Read the Website Terms

THIRD-PARTY SERVICES

Integrations do not change authority.

AI, market-data, infrastructure and payment providers may perform limited assigned functions. Connecting a provider does not give Anchor custody, discretion or permission to make or execute a customer's market decision.

Review provider status

VERIFY THE SCOPE

See the evidence and its limits.

Review evidenceView use cases