How EstateLedger handles personal information.

Account information such as name, email address, phone number, profile photo, password credentials, organization, and assigned estate role.

Estate and resident records such as estate name, units, resident names, resident contact details, occupancy status, service-charge amounts, invoices, receipts, arrears, expenses, maintenance requests, reports, uploaded proof files, and attachments.

Payment and billing information such as payment references, transaction status, amount, channel, invoice balance, and payment provider metadata needed for reconciliation.

Usage and technical information such as device type, browser, IP address, authentication events, pages visited, consented analytics events, error logs, and security audit events.

To create and manage estate workspaces, user accounts, roles, invoices, receipts, payment records, arrears, expenses, maintenance requests, and reports.

To authenticate users, protect accounts, prevent unauthorized access, troubleshoot errors, and keep audit records.

To send operational notifications such as payment confirmations, reminders, invitations, password resets, maintenance updates, and report links.

To improve product reliability, support users, understand feature usage, and maintain the security and performance of the platform.

With authorized users in the same estate or organization, according to their assigned role and permissions.

With residents through limited invoice, receipt, and report links intended for the specific resident-facing record.

With service providers that help us operate the platform, such as hosting, storage, email, SMS, payment processing, security monitoring, and support tools.

When required by law, regulation, court order, valid government request, fraud investigation, dispute resolution, or to protect the rights and safety of users and estates.

EstateLedger may integrate with payment processors to initialize, verify, and reconcile payments. Payment processors may process transaction details according to their own terms and privacy notices.

We do not need residents' full card numbers to operate the dashboard. Card and bank processing details should be handled by the payment provider where online payment is enabled.

We use technical and organizational controls designed to protect personal information, including authentication controls, role-based access, audit records, encrypted transport, and restricted administrative access.

We retain information for as long as needed to provide the service, maintain estate accounting records, resolve disputes, comply with legal obligations, and enforce agreements.

When information is no longer needed, we will delete, de-identify, or archive it according to operational, legal, and backup requirements.

Depending on your location and relationship with an estate or organization, you may request access to your personal information, correction of inaccurate information, deletion, restriction, objection, portability, or withdrawal of consent where consent is used.

Residents should first contact their estate manager for estate-specific records. You may also contact EstateLedger for platform privacy requests, and we may need to verify your identity before acting on a request.

Some requests may be limited where we need to keep records for accounting, security, fraud prevention, dispute resolution, or legal compliance.

EstateLedger may use cookies, local storage, and similar technologies to keep users signed in, remember theme preferences, protect sessions, measure product reliability, and improve the service.

Where you accept optional cookies, EstateLedger may use privacy-conscious analytics providers such as PostHog to understand public landing and waitlist page usage.

You can control cookies through your browser settings, but disabling required cookies may prevent authentication and workspace features from working correctly.

We may process and store information using infrastructure or service providers located outside your country. Where required, we use appropriate safeguards for cross-border processing.

Estate organizations remain responsible for confirming that their own resident communications and record processing comply with applicable local obligations.

We may update this Privacy Policy as the product, legal requirements, or operational practices change. The latest version will be posted on this page with the effective date.

Material changes may be communicated through the dashboard, email, or another appropriate channel.