SECURITY AND TRUST · PRIVATE PREVIEW

The security posture, stated plainly.

Requirements the code enforces, work in progress labeled as such, and nothing dressed up as a certificate.

ArkLegacy is read-only by design. It never trades, transfers money, takes custody, or stores wallet recovery phrases; credentials that could are refused. Access is controlled by the family.

01 · ENFORCED BY THE PRODUCT TODAY

Restraint, written into the architecture.

These are requirements the shipped implementation enforces in the current private preview, not aspirations. Connector code is fixture-tested server-side and activation-gated; live provider activation happens with each family during onboarding.

Read-only architecture, no money movement

Connections can read balances, positions, and transactions. Nothing in the product can trade, transfer, initiate payments, or change anything at an institution. API keys carrying trade or transfer power are refused before they are stored, and re-checked on every sync.

PRODUCT REQUIREMENT

No custody, ever

ArkLegacy never takes custody of assets and never asks for, accepts, or stores a wallet seed phrase or private key. Watch-only wallet tracking uses the public address alone.

PRODUCT REQUIREMENT

Permission-scoped access

Every family member, professional, and operator sees a defined slice of the record. Grants and revocations are explicit, role-scoped, and logged.

PRODUCT REQUIREMENT

Append-only audit logging

Authentication, membership, billing, and operational events are written to an append-only audit table; the database layer itself rejects updates and deletes to audit rows. Details pass through redaction before they are written.

PRODUCT REQUIREMENT

Credential encryption at rest

Provider credentials are sealed with AES-256-GCM authenticated encryption under a dedicated data key, with key versioning for rotation. Without the key, encryption features fail closed and stay off; there is no insecure fallback.

PRODUCT REQUIREMENT

Encrypted backups, isolated restore

Backups are AES-256-GCM encrypted under a dedicated backup key and restore into isolation for verification, never directly over live data.

PRODUCT REQUIREMENT

Hardened first-party sign-in

Passwords are hashed with scrypt using self-describing parameters; unknown accounts pay the same hashing cost so timing cannot enumerate users. Reset tokens are single-use, short-lived, and hashed at rest.

PRODUCT REQUIREMENT

Provenance on every value

Every number keeps its institution, owner, owning entity, valuation basis, as-of date, and evidence status. Stale evidence and broken feeds identify themselves instead of quietly presenting unreliable information.

PRODUCT REQUIREMENT

Family records are not training material

The record is context for answering the family's own questions, never material for training models. No external AI provider is active in the current preview, and the product says so wherever intelligence appears.

PRODUCT REQUIREMENT

02 · IN BUILD AND PLANNED, LABELED HONESTLY

What is not finished says so.

  • IN BUILD
    Strict per-family tenant isolationProductizing the single-family system into strict per-family isolation, with tenant-scoped storage and access boundaries throughout, is the core of the current engineering phase.
  • PLANNED
    Passkeys and multi-factor sign-inPasskey and MFA enrollment for family and professional accounts.
  • PLANNED
    SSO / SAML for office teamsIdentity-provider sign-in for family-office and professional deployments.
  • PLANNED
    Third-party penetration testingIndependent testing of the production platform, with findings tracked to closure.
  • PLANNED
    Self-service retention and deletionFamily-controlled export, retention windows, and verified deletion of the record.

03 · WHAT WE DO NOT CLAIM

A short list, kept honest on purpose.

  • ArkLegacy does not hold third-party compliance certifications today, and this page will never imply one before it exists.
  • No completed independent penetration test is on file yet; when one is, its status will be stated here rather than implied.
  • The public demo contacts no financial institution and holds no real family data: every surface runs on labeled synthetic fixtures about a fictional family.
  • ArkLegacy is organizational and decision-support software. It is not legal, tax, accounting, or investment advice, and consequential actions always stop and wait for a person.

Boundaries you can read. Then verify in the demo.