Terms of Service

This page describes the current local MyVTC build and is not a final production contract. Production terms require legal review, an identified operating entity and jurisdiction, approved service levels, and a published effective date.

Do not place real sensitive, estate, minor, health, financial, or evidentiary records into this local build.

Firebase Authentication provides the account boundary. Members are responsible for protecting their credentials and for entering information they have the right to record.

Private profiles, timeline entries, wish plans, recipient records, encrypted deposits, and operational records are owner-scoped. A member must take a separate publication action before a safe profile projection becomes public.

The local sealing tool encrypts text in the browser with an AES-GCM envelope before the ciphertext is submitted. MyVTC records an immutable deposit and receipt, but the current build does not retain or recover the member's passphrase.

A lost passphrase can make a deposit unusable. Post-activation key release, recovery, recipient decryption, evidence custody, and trusted timestamping are not approved production services.

Members can record recipients, proposed triggers, and delivery plans. Recipient contact content is client-encrypted before its deposit is stored.

All delivery execution in this build is simulation-only and requires explicit administrative review. No email, secure link, postal fulfillment, human concierge action, automatic release, or legal notice is sent.

Displayed plans are product descriptions. No payment provider, recurring subscription, refund workflow, escrow, trust account, fiduciary service, or live money movement is connected in this local build.

Selecting or reviewing a plan does not charge a card, activate an entitlement, or create a paid subscription.

A production retention schedule, backup policy, restoration test, account export process, deletion workflow, and estate-handling procedure have not been approved.

Keep independent copies of important records. A recorded date or trigger is not a retention or delivery guarantee.

Do not use MyVTC to violate another person's privacy or intellectual-property rights, impersonate another person, distribute malware, evade the law, or record content you are not authorized to control.

Do not attempt to bypass authentication, authorization, rate limits, review gates, or the separation between private source records and public projections.

The live myvtc.com service remains the protected production baseline. This local rebuild has not been deployed, and its Firestore rules, indexes, environment configuration, payment integrations, and delivery systems are not production-approved.

Final production terms must be reviewed together with the privacy notice, security posture, release runbook, rollback proof, and all external provider agreements.