Sample data only
Sample organisations, generated traveller identities and mock document records. No production identity provider or customer data.
Security & privacy
Trust starts with
honest boundaries.
Document workflows need more than a login. Our production design makes every access decision explicit.
This public demo is not a secure document service. Browser role controls are simulations. No security certification, completed penetration test or legal compliance is claimed.
What exists today
A deliberately isolated demonstration.
No external transactions
Reminders, notifications, invoices and document reviews are simulated. No messages, payments or document uploads are sent.
Browser-local files
Sample file bytes are inspected only in memory. No filenames or file contents are persisted. Sample workflow metadata may remain in this tab session.
Planned production controls
Designed in. Still to be implemented.
Privacy by design
Minimise personal fields, document legal purposes, support data subject requests and assess applicable jurisdictions before launch.
Secure document storage
Private encrypted object storage, dedicated keys, quarantine scanning, lifecycle rules and no permanent public document links.
Role-based access
Server-side identity, active membership, resource ownership, trip assignment and explicit scoped grants checked on every request.
Corporate and agency isolation
Tenant-scoped queries and PostgreSQL row-level security as defence in depth. Cross-company access requires an explicit shared trip assignment.
Encrypted communication
TLS transport, secure cookies, CSRF controls, MFA for privileged users, revocable sessions and established identity providers.
Access history and audit trails
Record uploads, views, decisions, exports, grants and deletions in protected logs without document contents or signed URLs.
Document retention
Customer-specific retention deadlines, legal holds, authorised deletion, backup expiry and accountable deletion events.
Security monitoring
Rate limits, suspicious access detection, operational alerts, incident response and independently reviewed security tests.
Responsible data handling
Privacy notices, processing agreements, subprocessor review and cross-border assessments. Sri Lankan PDPA applicability and other legal duties require qualified review.
A controlled lifecycle
Quarantine first. Authorise every view.
Submission design
Authenticate → authorise → scoped upload → private quarantine → size, signature and malware checks → protected storage → metadata and audit event.
The demo only validates sample size/type/signature locally. It cannot scan for malware, and local files remain quarantined and unrendered.
Viewing design
Authenticate → check membership and trip assignment → check explicit document scope → audit → short-lived viewer session or signed URL.
Signed URLs are bearer credentials. Keep them out of logs and notifications. Watermarks cannot prevent screenshots or copying.
Before real documents
Production launch requires independent assurance.
- Deploy and test backend authorisation, tenant isolation and secure identity.
- Provision private storage, malware scanning, key management and restricted support access.
- Complete privacy, retention, transfer and contractual assessments with qualified advisers.
- Run independent penetration testing, restore exercises and incident response rehearsals.
- Verify actual control operation and evidence before making security or compliance claims.