Your business data, protected by architecture — not promises.
PianoHelm is built as a multi-tenant platform from the ground up. This page describes how the system actually protects your data, in plain terms.
Tenant separation, enforced by the database
Every organization's data is isolated by row-level security rules in the database itself — not merely filtered in the interface. One business's records cannot be read or changed from another's account, even by accident or by a crafted request.
Role-based access control
Access is governed by roles and permissions stored in the database. Organizations can shape roles to their team, and every permission check is enforced server-side.
Authentication
Sign-in is handled by a dedicated, hardened authentication service with support for email and Google sign-in. Password reset flows follow the provider's standard secure process.
Audit history
Operational changes are recorded with who made them and when. Business and financial records are archived or voided rather than silently deleted, so history survives.
Controlled support access
When our team helps you, access happens through explicit, time-bounded support sessions that are scoped to your organization and recorded in the audit history.
Data handling principles
Your business data belongs to your organization. We don't sell it, and attachments and documents are stored privately — accessible only to members of your organization.
Questions about security?
We're happy to walk through our architecture in detail as part of a demo. If your organization has specific requirements — access policies, data handling, support access — raise them with us directly.
Security questions
Can one dealership see another dealership's data?
No. Organization boundaries are enforced in the database for operational records, not only hidden in the interface.
How is support access controlled?
Support administrators must start an explicit, time-bounded session for the selected organization. That access and resulting actions are recorded for accountability.
Can access reflect each employee's responsibilities?
Yes. Role-based permissions determine which operational areas and actions are available to each team member.