HomeCharge Proof · DIGIDENT LTD

Privacy policy

How the beta handles optional housing-charge document extraction.

Effective: 15 August 2026

Privacy-first beta. Complete OCR text is shown on your device for editing before optional submission. Remove names, addresses and identifiers. The Worker applies a second pattern-based redaction pass and does not write document content to DIGIDENT application storage.

1. Controller

HomeCharge Proof is operated by DIGIDENT LTD. Contact digidentai@proton.me about this policy or your data-protection rights.

2. Information processed

On your device: imported images, OCR text, documents, calculations, confirmations and saved projects remain in app-controlled local storage unless you choose to send or export them.
Optional extraction: only the bounded OCR text displayed for review and module/document hints are sent when you confirm.
Security: Google Play Integrity app, licence and device signals, a per-install public key, normal network metadata and pseudonymous counters are processed to authenticate and rate-limit requests. Google receives an authentication request hash, not document text or a document hash.

3. Information you must remove

Do not submit names, addresses, postcodes, signatures, contact details, bank data, account/agreement/lease/pitch/property identifiers, tax identifiers or another person's confidential information. Automated redaction reduces risk but cannot guarantee detection of every identifier.

4. Storage and retention

DIGIDENT's Worker does not write OCR text or model output to DIGIDENT application logs, databases, caches, analytics or object storage. OpenAI Responses requests use store: false, which disables response application-state retention for later retrieval. Unless DIGIDENT's OpenAI project is confirmed as using approved Zero Data Retention or Modified Abuse Monitoring, OpenAI may retain prompts and responses in abuse-monitoring logs for up to 30 days, or longer where legally or security-required, and may retain documented encrypted prompt-cache state. Cloudflare may process network and security data under its applicable terms. The rate gate clears active UTC-daily counters. The authentication store retains an app-scoped pseudonymous subject, its public key and revocation epoch for the security life of the service; single-use proof hashes expire shortly after the access credential. These records contain no document text, Play verdict, name, email address or advertising identifier.

5. Providers and transfers

Cloudflare delivers and protects the Worker. Google Play Integrity verifies the Play-installed app, licence and device. OpenAI performs optional Luna extraction. Providers may process data outside the UK subject to applicable contractual and transfer safeguards.

6. Purpose and legal basis

We process optional OCR text to provide the extraction you request and limited pseudonymous/security data to protect the beta. Relevant UK GDPR bases may include performance of the requested service and our legitimate interests in security and abuse prevention.

7. Choices and rights

AI extraction is optional. You can edit the entire OCR block, use manual entry, delete local projects and uninstall the app. Subject to UK law, you may ask about access, correction, deletion, restriction, objection or portability and may complain to the Information Commissioner's Office. Because DIGIDENT does not retain document content in its application storage and rate keys are pseudonymous and short-lived, we may be unable to link a Worker event to you. Provider-held security or abuse-monitoring records are governed by the provider controls described above.

8. Beta feedback

The app can open your email application with the DIGIDENT support address and a generic subject. HomeCharge Proof does not add a message body, logs, records or attachments. Do not send bills, source documents, full addresses, account or title numbers, names or residents' data. If you choose to email us, we receive your email address and the content you decide to send and retain it only as needed to respond, improve the beta and meet legal obligations.

9. Security and children

Controls include encrypted transport, Play Integrity attestation, non-exportable per-install signing keys, short-lived credentials, one-use signed request proofs, bounded requests, local redaction, evidence-span verification, HMAC pseudonymisation and layered rate limits. No system is completely secure. The beta is intended for adults handling records they are authorised to use.