Skip to content
Privacy & records

Know where a record goes before entering it.

This notice describes the pilot reviewed on 8 October 2026. Private email-code sign-in has been verified for the pilot owner; there is no open registration. The fictional demo remains available to explore the application without entering real household records.

Reading the public guides

Reading these pages does not require a household account. Cloudflare provides the website hosting and may process connection information under its own service arrangements. No advertising or third-party analytics integration is currently included in the application.

Public guides and examples do not contain real helper payroll records. Do not place personal or payroll details in a public URL.

The fictional browser-local demo

Demo profile and financial changes are saved in this browser’s local storage. Other people using the same browser profile may be able to view them. Resetting the demo removes its saved demo record and starts again with fictional data.

Expense-receipt metadata is saved locally. Uploaded demo receipt and signed-copy file bytes last only the current browser session. After a page reload, receipt bytes are unavailable; file bytes are excluded from the demo JSON export. Demo mode is intended for fictional data; avoid real names, addresses, signatures or wage records.

The private workspace design

The private pilot is designed to store household and helper profiles, contract and compensation history, calendar events, expenses and optional receipt files, statements, actual payments, audit entries and retained original or signed statement files in Cloudflare services. Access depends on an active household membership. Active owners and editors may download private files; viewers may see receipt metadata. Owner-only ZIP export includes receipt bytes with verified hashes.

Receipt uploads preserve their saved expense context and actual upload date. Marking a file Not applicable retains its bytes and history rather than deleting it. Basic file-type and signature checks do not provide malware scanning.

The passwordless email flow uses Resend to send a sign-in code to an authorized address. Sender verification, inbox delivery and sign-in were tested for the pilot owner; open registration is not available. Email-code login is a single factor. Authentication codes and session tokens are stored as hashes rather than plaintext.

Keep the household record proportionate

Collect only the details needed for the stated payroll purpose and protect access to them. The PCPD principles address necessary collection, appropriate retention, security and access or correction.

  • Do not use uploads to store passports, identity documents or medical records.
  • Use a payment reference where it explains the payment; avoid unrelated bank details.
  • Keep signed evidence and receipts accessible only to the authorized household people who need them.

Source: PCPD: the six data protection principles

Decisions required before real household use

The operator identity, dedicated privacy contact, provider processing terms, data location, payroll retention schedule and deletion process remain under review. No unverified retention period or contact address is promised here.

The owner export workflow is implemented. Recovery of financial records and original and signed statement files was tested in a separate Cloudflare D1 database using fictional data. Real household recovery, retention and deletion arrangements still need review before inviting households to store personal payroll records.

CHECK THE ORIGINAL

Sources & review dates

Official sources were checked on the dates below. Later changes and individual cases may require a fresh review.

  1. PCPD: the six data protection principlesChecked 5 October 2026
A PLACE FOR THE WHOLE MONTH

Put the plans, pay and receipts together.

Explore the fictional demo to see how the supported household workflow fits together. The pilot does not execute bank transfers or certify legal compliance.

Open the workspace