Small attack surface. Honest limits.

Local-first architecture

Operational data and imported certificate or report PDFs are written to the app's private container on the iPhone. The app uses iOS file protection, atomic workspace writes and a recovery copy so an interrupted save does not silently replace a good record with a partial one.

No hidden transfer

There is no app account, remote database, analytics SDK or background customer-data upload in the founding beta. Leccy does not store a scheme password or MFA code. A file leaves the app only through a share or export action that you start. Your Apple device-backup settings may separately include app data; Caversham Digital does not control or have access to those backups.

Your part

• Use a device passcode and current supported iOS release.
• Review recipients before sharing customer or commercial data.
• Keep independent records for statutory and contractual duties.
• Create readable exports where useful; this beta cannot restore them into the app.

Reporting a problem

Send security concerns to security@getleccy.com. Do not send live customer data or an exploit in the first message.

Before cloud features

Any later team sync will require tenant-isolation tests, encryption and key-management decisions, retention and deletion controls, audited subprocessors, restore testing and an updated privacy assessment before release.