Clerk authentication
User identity is handled through verified authentication tokens and protected routes.
Loading the latest property data and media.
Security and trust
EstateAI applies layered authentication, ownership checks, secure storage access, verified billing events and auditable activity.
Security foundations
The platform is designed around least privilege and verified server-side decisions.
User identity is handled through verified authentication tokens and protected routes.
Backend services validate ownership and organisation permissions instead of trusting frontend identifiers.
Property media is stored in Cloudflare R2 with controlled access patterns and signed delivery where required.
Checkout, recurring billing and customer portal activity use Stripe rather than storing raw card details in EstateAI.
Billing events are signature-verified, idempotently processed and logged.
Important property, organisation, notification and billing actions are persisted for operational traceability.
Archived, deleted and excess-storage data follow defined retention and cleanup workflows.
EstateAI describes implemented controls without presenting unverified certifications.
Configuration validation, structured logging, rate controls and readiness checks support reliable deployment.