Personal Receipts
Status: pre-launch. This page describes target design; this document does not establish a deployed service.
Scope: proposed receipt-vault capability presented through the Skyzai Personal package; any Work use needs its own scope and acceptance. Personal and Work are two app/commercial packages, not substitutes for the seven product owners. This is not a standalone SKU. See The Product Family.
Surface: receipts.skyzai.com (declarative)
Catalog route: skyzai.com/products/personal-receipts/
Status: SPEC
Evidence tier: [D] — vault encryption design ratified; sibling to OFN B2B-2; first external user is the proof gate (re-tiered [B]→[D] 2026-07-03 per TIER_MERGE_GATE: a spec/draft is not an observed run; [B] requires a dated reproducible receipt)
Source canon: (private, unpublished)
What Personal Receipts Is
Your life audit trail, without turning your life into a product. Personal Receipts is the consumer-side vault for receipts from everyday transactions — payments, tickets, agreements, signatures. Encrypted to your key. Stored on your infrastructure (or yours via Nexus). K4 export always one call away.
Same OFN receipt schema as the B2B SDK. The receipts your apps emit on B2C surfaces (Pay POS, Events, etc.) flow into your Personal Receipts vault.
What It Is Not
- Not an audited bookkeeping service
- Not a tax filing service or accountant — we provide format, not attestation
- Not a comprehensive personal-finance record — only what you choose to vault here
- No legal-binding claim on stored receipts — counsel-cleared contracts give legal force
- We do not custody money, tokens, or assets — only the receipts that record their movement
Cross-links
- Product page:
/products/personal-receipts/ - Buyer deck:
/products/personal-receipts/deck/ - Resource room:
/products/personal-receipts/resources/ - Access form:
/products/personal-receipts/access/ - Adjacent canon: OFN Receipts (P1), OFN organ (97), Nexus (P7)
- Source markdown: (private, unpublished)
Refer to the canonical
WEBSITE.mdsource for complete product spec. This wiki page exists so the .com → .org bidirectional pair resolves cleanly.