Security

Our commitment

Yarduno is built for independent yard operators who need reliable, well-protected operational and billing records. Security decisions are made with tenant isolation and data integrity as first priorities.

Tenant isolation

Each yard operator's data is logically separated from other tenants. Application-level access controls ensure a user can only reach the records belonging to their own account.

Access control and authentication

Accounts are role-aware, and MFA-ready authentication is supported to reduce the risk of unauthorized access. Users should choose strong, unique passwords and enable additional protections where offered.

Payment security

Payments are processed through Stripe. Yarduno does not store full card numbers; payment data is handled by Stripe's PCI-compliant infrastructure.

Data in transit and at rest

Traffic to and from the Service is encrypted in transit. Operational records, including gate tickets, invoices, and proof records, are stored using our hosting provider's standard encryption-at-rest practices.

Backups and availability

We maintain routine backups of operational data to support recovery in the event of a system failure. This does not replace a customer's own export of critical records.

Reporting a vulnerability

If you believe you have found a security vulnerability in Yarduno, please report it to support@yarduno.com so we can investigate promptly. Please avoid accessing or modifying data that is not your own while testing.

Subprocessors

We use a limited set of subprocessors to operate the Service, including Stripe (payments) and Resend (email delivery). A current list is available on request.

Changes to this page

We may update this page as our security practices evolve. Material changes will be reflected by an updated effective date.

Contact

Security questions can be sent to support@yarduno.com.