Skip to content

CLEAR BOUNDARIES, HONEST ANSWERS

Documents deserve more than a reassuring badge.

Here is what the local application implements, and what still needs verification before a production pilot.

Workspace boundaries

Private reads and writes check business workspace membership on the server.

Scoped client access

Clients access a particular request using an expiring link and verification. Replacing the link invalidates previous access.

Private uploads

Files live outside the public web directory and are served through authorization checks.

Controlled uploads

The current version restricts file types and sizes, uses opaque storage keys and retains original filenames as metadata.

Review history

Replacement versions and review activity help the business understand what changed.

Separate local environment

Development uses a dedicated local database. The original product’s live data is not part of this application.

Before production

Production hosting, encrypted transport and storage configuration, malware scanning, backups, retention and deletion, incident handling and monitoring still need implementation or verification. Local access checks are not a substitute for those controls.

AI and providers

The homepage AI sequence is illustrative. Live document processing is disabled. Provider terms, processing locations and data handling need review before enabling external services.

Questions or a concern?

Use the contact page for the available contact options. Do not put credentials or confidential documents into a general message.

Contact options →