About this page
How RentCloud protects partner and end-customer data. This page is the public summary; the contractual commitments live in the Terms and the DPA.
1. Hosting and data residency
Hosted on AWS in eu-central-1. Frontend delivery via Vercel, file storage via Supabase.
2. Encryption
Data is encrypted in transit (TLS 1.2+) and at rest (AES-256 on S3 and RDS). Passwords are hashed with bcrypt.
3. Access control
Access to production data is restricted to a small set of named operators via SSO, MFA and an SSM-only bastion.
4. Tenant isolation
To be written: how one partner’s data is separated from another’s, and what enforces it.
5. Backups and recovery
To be written: backup frequency, retention window, and the tested recovery objectives (RPO/RTO).
6. Logging and monitoring
To be written: what is logged, how long audit logs are kept, and who can read them. Privacy states audit logs are kept 2 years.
7. Vulnerability management
To be written: patch cadence, dependency scanning, and whether third-party testing is performed.
8. Sub-processors
AWS, Resend, Stripe, Supabase, Vercel and Anthropic. The current list is maintained in the Privacy Notice.
9. Incident response
To be written: detection, the notification window to partners, and who leads the response.
10. Reporting a vulnerability
To be written: the disclosure address and the response commitment.