Trust starts with proof

Security overview

How Accrod approaches the security of lease records, what exists in the current preview, and what still has to be built and verified before customers rely on it. Nothing here claims a certification or control that has not been validated.

Preview version

This overview describes the current preview. Controls are listed as implemented only once they have been built and tested; the final statement will be published before accounts open.

Security statements are promises. Publish a commitment only when it has been implemented, tested and documented. This preview deliberately avoids claiming certifications, encryption configurations, uptime levels or independent audits that have not been verified.

Design principles

  • Least privilege: users should only access the workspace and records they are authorized to use.
  • Server-side enforcement: identity, workspace isolation, subscription entitlement and destructive operations must be checked by the backend.
  • Safe document handling: document uploads require validation, size limits, access controls and a retention/deletion policy.
  • Reliable history: sensitive changes should have auditable events with appropriate access restrictions.
  • Clear recovery: account recovery, backup restore, export and incident contact paths should be documented and tested.

Current preview and browser storage

The supplied deployment is not connected to a live Supabase project. The source includes a backend foundation, but migrations, authentication, workspace access and storage have not been tested against a hosted environment. When the cloud workspace is connected, the current browser client also retains a local working copy and a pending-change recovery snapshot. Browser storage is not an encrypted backup or a substitute for a verified device and session security design. Do not enter sensitive customer records into this preview.

Before making public security claims

  • Verify TLS, storage encryption and key-management practices with the actual infrastructure.
  • Test tenant/workspace data isolation, object-level authorization and invitation flows.
  • Review session handling, password reset, sign-out, token expiry and CSRF/CORS policy.
  • Confirm backup schedules, restoration tests, deletion semantics and incident response ownership.
  • Inventory vendors, logging, access to sensitive documents and retention settings.
  • Run dependency, accessibility, application-security and cross-tenant authorization tests.

Customer controls to plan for

The product should provide understandable access to workspace membership, data export, account deletion requests, active sessions, notification preferences and billing history where relevant. A button in the interface is not a security control until the corresponding server behaviour exists and passes tests.

Report a security concern

No verified security-reporting address is configured in this preview. The operator must create, monitor and test a dedicated reporting channel before publishing instructions for reporting security concerns.