Security and data privacy

Your building's financial data belongs to its owners and residents. We protect it with role-based access, a no-delete ledger, a full audit log and per-building data isolation.

A building management platform handles data that is both financial and personal: unit balances and payments, residents' contact details, and staff and contractor contracts and bank details. To us, security isn't only about keeping intruders out; it also means no number ever changes silently.

Role-based access

Every user has a role, and every role a set of permissions: management, board, staff (lobby staff, caretakers, guards) and residents, who see only their own unit. Roles are fully configurable per building; an auditor, for example, can be given view-only access. Our principle is least privilege.

A ledger with no deletions

No financial record is ever deleted: not charges, payments, expenses or fund transfers. A mistaken record is voided with a reason, the voided record stays visible with its user and time, and a correct record is entered separately. Past reports never change silently.

Full audit log

Important actions are logged: who recorded, approved, voided or changed what, and when. The log supports audits, dispute resolution and accountability.

Per-building data isolation

The platform serves many buildings, but each building's data is isolated at the database level using row-level security. Even if an error occurred in a higher layer of the application, the database would not return one building's data to users of another.

Sensitive data

Sensitive settings, such as credentials for messaging providers, are stored encrypted. Counterparties' bank details are visible only to authorised roles.

Backups

Data is backed up regularly so it can be restored after a technical problem. We are happy to walk through backup arrangements during onboarding.

Hosting

The platform can be hosted on infrastructure inside Iran. If your organisation has specific data-location requirements, let's discuss hosting options.

Shared responsibility

Define access by real need, review access promptly when the board or staff change, never share passwords, and review the audit log periodically.

Questions or a security questionnaire? Contact us.

See it with sample data

In a short session we walk you through this part on a sample building.