Privacy policy
How Leasevora handles account data
This policy explains the information used to operate landlord and renter accounts.
Plain-language summary
Leasevora uses account, property, lease, payment, maintenance, and document data to provide the features requested by landlords and renters. Personal rental records are not sold for third-party advertising.
Landlords control the rental records they add. Renters can review and update their own account information while landlords can manage records tied to their rental relationship.
1. Information collected
Account data may include names, email addresses, phone numbers, profile images, mailing addresses, emergency contacts, and login or verification records.
Rental records may include properties, leases, occupants, charges, payments, maintenance requests, insurance proof, uploaded files, signatures, and activity history.
2. How information is used
Information is used to create and secure accounts, deliver documents, record signatures, operate rent and ledger tools, route maintenance work, send requested notices, provide support, and protect the platform from misuse.
Operational records may also be used to diagnose errors, preserve audit trails, and meet recordkeeping obligations.
3. Landlord and renter access
Landlords can access rental records connected to properties and agreements they manage. Renters can access records connected to their own account and rental relationship.
Private landlord bookkeeping and internal notes are not shown in the renter portal unless the landlord intentionally creates a renter-visible charge, credit, document, or update.
4. Applications and screening data
A reusable application may contain identity details, date of birth, income, employment and residence history, references, household information, disclosures, and supporting files. The reusable profile is encrypted at rest and is not shared with a landlord until it is connected to a property application.
Property submissions preserve a snapshot of the information provided at submission. Files used as submitted evidence may be retained with the application audit record even if the renter later updates the reusable profile.
If paid screening is offered, the screening provider may collect additional identity data and produce consumer reports. Report access, consent, disputes, expiration, and retention are subject to the provider's notices and applicable law.
5. Service providers
Hosting, email, identity, payment, file-processing, and security providers may process the minimum information needed to perform their services. Their handling of data is also governed by their own terms and privacy practices.
Payment card and bank credentials are collected and tokenized by Stripe. Leasevora stores provider references, method type, limited display details such as brand or last four digits when supplied, authorization records, transaction status, fees, failures, refunds, disputes, and payout diagnostics, but not full card or bank account numbers.
6. Communications and delivery records
For account, agreement, payment, maintenance, and security communications, Leasevora may record the recipient, subject, notification type, delivery attempts, duplicate suppression, transport acceptance, provider message reference, failure status, and an encrypted copy of the rendered message.
Rendered copies are restricted to authorized platform staff and used to diagnose delivery issues, confirm the notice that was generated, and preserve an operational audit trail. Email previews do not include passwords or full payment credentials, and payment or signing links remain subject to their original access controls and expiration rules.
7. Retention and deletion
Records are kept while an account is active and as reasonably needed for signing history, financial reconciliation, fraud prevention, backups, disputes, and legal obligations.
Deleting or archiving an item may preserve a limited audit record when removing it entirely would damage financial or document history.
8. Security
Leasevora uses access controls, encrypted connections, protected file storage, signed links, request validation, and audit records to reduce unauthorized access or alteration.
No online system can guarantee absolute security. Users should protect their login credentials and report suspected account misuse promptly.
9. Optional analytics
With permission, LeaseVora uses the Meta Pixel to measure visits and improve outreach. Meta may receive page URL, browser or device information, IP-derived location, and its own identifiers under Meta's privacy terms. Lease, payment, application, signature, and uploaded-document contents are not intentionally sent as Pixel event parameters.
Analytics is not loaded until the visitor selects Allow. A visitor may decline it without losing LeaseVora account or rental features. Clearing site storage resets the choice.
10. Your choices
Account and notification preferences can be updated in Settings. Requests to review, correct, export, or delete personal information can be sent through the help center.
Some records may need to remain available to preserve executed agreements, payment history, security logs, or legal obligations.
11. Contact
Privacy questions and account-data requests can be submitted through the help center.