Elisian Privacy Policy
This policy explains what information Elisian collects, why, who we share it with, how long we keep it, and what choices you have. It covers elisian.ai and our other marketing pages, the Elisian web and mobile applications, and our API.
Who this policy is for
Four kinds of people read this, and the answers differ for each. Find yourself here:
- Website visitors. You are reading our marketing site and have not signed up. Only Section 1 applies to you.
- Account holders ("Landlords"). Landlords, property managers, and community associations who subscribe to Elisian and run their properties in it.
- Invited users. Tenants, vendors, property owners, and association board members and members who were given access by an account holder.
- Applicants and other third parties. People who applied to rent, enquired about a listing, booked a tour, or corresponded with an account holder through Elisian, and who may never have had an Elisian login at all.
Our role, stated plainly
Most of the personal information inside Elisian is about someone other than our customer — a tenant, an applicant, a vendor, an owner. When an account holder puts that information into the Platform, they decide what is collected and why; we process it on their behalf and under their instructions. In the language of US state privacy laws, for that data the account holder is the controller (or "business") and Elisian is the processor (or "service provider").
For the information we collect about our own customers and our website visitors — account registration, billing, support, site analytics — Elisian is the controller and this policy is our own notice.
If you are a tenant, applicant, vendor, or owner: your landlord or property manager is the primary decision-maker about your records. Ask them first. Where this policy gives you rights against us directly, Section 11 tells you how to reach us.
1. Our website (visitors who have not signed up)
This section covers elisian.ai and our marketing pages only.
What we collect. Your IP address, browser and device type, the pages you viewed, referring URL, and timestamps — the ordinary server request record. If you enter your email address in a sign-up or waitlist form, we collect that email address.
Cookies and tracking. We do not set advertising or cross-site tracking cookies, and we do not run third-party advertising or analytics tags on our marketing pages. Third-party requests. Our pages load typefaces from Google Fonts, which means your IP address and browser details reach Google when a page loads. Google's handling of that request is governed Opt-out preference signals. We honour the Global Privacy Control (GPC) signal. If your browser or extension sends one, we treat it as an opt-out of any sale or sharing of your personal information and of targeted advertising. Since we do not sell, share, or target ads, there is nothing to switch off — but the signal is respected and we will say so on the page. Do we track you across sites? No.
2. What we collect in the Platform
The table below is our notice at collection: what we collect, what it is, where it comes from, and why. Retention is in Section 8.
| What we collect | Examples | Where it comes from | Why |
|---|---|---|---|
| Account and profile | name, email, phone, password, business name, role, avatar, organization and team memberships | you; the account holder who invited you | to create and secure your account and decide what you can see |
| Property and leasing records | properties, units, leases, rent schedules, deposits, renewal terms, listings, applications, showings | the account holder; AI extraction from documents they upload | to run the properties |
| People records | tenant, applicant, cosigner, vendor, owner and association-member contact and identity details, application answers | the account holder; you, if you applied or enquired | to operate tenancies, applications, work and ownership relationships |
| Financial records | ledgers, charges, rent payments, payouts, distributions, invoices, reconciliation, 1099 data | Platform activity; Stripe; Plaid | to collect rent, pay vendors and owners, and keep the books |
| Payment instrument details | card brand and last four digits, bank institution and masked account, provider tokens | Stripe; Plaid | to recognise and charge an instrument. We do not hold full card or bank numbers — our payment providers do |
| Government identifiers | SSN/ITIN (screening), EIN/TIN (tax forms) | applicants; vendors and owners on tax forms | to request a consumer report; to file required tax forms |
| Screening information | application data, your written authorisation, the consumer report result, adverse-action records | you, as applicant; TransUnion SmartMove | to facilitate a screening the account holder requested |
| Communications content | messages, emails, SMS, call metadata, notes, maintenance conversations, attachments | you; the account holder; delivery providers | to carry the conversation and keep a record of it |
| Documents and images | leases, notices, inspection and maintenance photos, invoices, insurance certificates, W-9s | uploads | to hold the records the property needs |
| AI interaction records | the prompt, the output, the model, tokens, cost, confidence, and who approved what | Platform | to keep an audit trail of every AI action (Section 4) |
| Technical and security | IP address, device and browser type, app version, push tokens, endpoints accessed, error and security logs | your device | to run, secure, and debug the Platform |
What we do not collect. We do not buy personal information from data brokers. We do not collect precise geolocation. We do not use protected characteristics — race, colour, religion, national origin, sex, familial status, disability — to make or recommend a leasing decision, and the Platform has guardrails intended to keep those characteristics out of AI-assisted leasing work. They may nonetheless appear in a document or a free-text note someone uploads.
California sensitive personal information. Some of the above is "sensitive personal information" under California law and its equivalents elsewhere: government identifiers (SSN/ITIN, driver's licence), financial account information, account log-in credentials, and the contents of your messages, mail, email, and text messages where we are not the intended recipient. We collect and use these only to provide the Platform and meet legal obligations — not to infer characteristics about you, and never to sell.
3. How we use information
- To provide the Platform and the features the account holder has turned on.
- To authenticate users and protect accounts, including two-factor authentication and fraud and abuse prevention.
- To process rent, deposits, distributions, and vendor payouts.
- To send transactional messages: notifications, digests, reminders, notices, receipts.
- To power AI-assisted features, as described in Section 4.
- To provide support, investigate problems, and maintain an audit trail of what happened in an account.
- To improve reliability, performance, and safety, including using aggregated or de-identified data that does not identify any individual, property, or account.
- To meet legal, tax, accounting, and regulatory obligations, and to establish or defend legal claims.
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We do not use it for targeted advertising, and we do not profile you to make decisions that produce legal effects without a human in the loop (Section 4).
4. AI processing — read this section
Elisian is an AI-assisted product. This section is deliberately specific, because the honest disclosure is more involved than "we use AI."
4.1 What the AI features do. We use large language models from Anthropic to triage maintenance requests, draft communications, extract structured data from documents you upload (leases, insurance certificates, W-9s, invoices), summarise screening results, answer questions about a portfolio, and run the in-product assistant.
4.2 What the model receives. When an AI feature runs, the information that feature is working on is sent to Anthropic's API. That can include personal information — names, contact details, lease terms, the text of a maintenance request, the fields of an application, the contents of a document, a message thread.
We do not apply a general-purpose redaction step to every AI request. Specific high-sensitivity paths are field-restricted — AI screening summaries, for example, are built only from result fields that may lawfully inform a screening decision and exclude identifiers such as SSN/ITIN. But there is no platform-wide scrubber, so you should assume that the records an AI feature operates on are processed by our AI provider. We would rather tell you that than imply a protection we have not built.
4.3 Our AI provider's terms. Anthropic acts as our processor and is contractually restricted to processing this content in order to return a result to us. Under Anthropic's commercial API terms, content sent through this path is not used to train models. 4.4 Human oversight and audit. Every AI action is recorded in the account's activity log with the model, inputs and outputs, confidence, and cost. AI output is decision support: it can be wrong, and a person is responsible for any decision that affects a tenant, applicant, vendor, or owner.
4.5 No automated decisions with legal effect on a tenant or applicant. The Platform does not approve or deny a rental application automatically. Screening summaries are decision support and the leasing decision is the account holder's. Formal legal notices require a named human's approval and cannot be sent automatically.
One documented exception, stated precisely because it is real: an account holder may explicitly elect automatic execution with notification for lease-renewal offers. That is an opt-in setting the account holder chooses, and it applies to renewal offers only — it is not available for legal notices, which are blocked at the policy layer.
5. Screening and consumer reports (FCRA)
Where an account holder uses tenant screening:
- The account holder is the end user of the consumer report. They are responsible for having a permissible purpose, for obtaining your authorisation, and for adverse-action obligations if they decline you based on the report. Elisian facilitates the request and delivers the result.
- The consumer reporting agency is TransUnion SmartMove. Your rights against a consumer reporting agency — to see your file, to dispute an inaccuracy, to have a dispute reinvestigated — run against them under the Fair Credit Reporting Act, and the FCRA summary of rights provided with your report explains how to use them.
- Your authorisation is recorded against the exact disclosure text you were shown. Disclosures are versioned, so we can always reproduce what you agreed to.
- Report content is access-restricted. It is limited to the requesting account holder's authorised users with leasing permissions, and it does not appear in general list, search, or export surfaces.
- Report content is disposed of on a schedule. The regulated fields are redacted after the retention window in Section 8, consistent with the FTC Disposal Rule.
6. Financial information
Payments and payouts are processed by Stripe. Where bank-account connection is used, it is provided by Plaid. Those providers collect card, bank, and credential details directly from you and handle them under their own privacy notices. We receive the identifiers, masks, balances, statuses, and transaction records we need to operate rent collection, reconciliation, distributions, and payouts.
7. Who we share information with
Service providers (subprocessors). We use the following, each for the purpose named:
| Provider | What it does for us |
|---|---|
| Amazon Web Services | cloud hosting, file storage, inbound email receipt |
| Anthropic | AI inference (Section 4) |
| Stripe | payments, payouts, platform accounts, treasury, identity verification |
| Plaid | bank-account connection and verification |
| TransUnion SmartMove | tenant screening / consumer reports |
| DocuSign | electronic signature for lease execution |
| Resend | transactional email delivery |
| Twilio | SMS delivery |
| Expo | mobile push notification delivery |
| Pusher | real-time in-app updates |
| Mapbox | maps and address display |
| Sentry | error and performance monitoring |
Also shared:
- Within a workspace. Information in an account is visible to the users the account holder has granted access, according to the roles and permissions they set. Data is isolated between customer accounts.
- With counterparties in a transaction. A vendor sees the work order assigned to them; an owner sees the reports shared with them.
- When you direct it. For example, a report you share with your accountant through a share link.
- For legal and safety reasons. When required by law or valid legal process, to enforce our terms, or to protect the rights, property, or safety of a person or of Elisian.
- In a business transfer. In a merger, acquisition, financing, or sale of assets, subject to this policy.
8. How long we keep information
| Category | How long | Why |
|---|---|---|
| Financial records — rent payments, payouts, 1099 data | 7 years | tax and financial recordkeeping obligations |
| Executed leases and signed contracts | 7 years | contractual and business record |
| Screening / consumer-report content | 365 days from completion, then regulated fields redacted | FTC Disposal Rule (FCRA) |
| Email opt-out records | indefinitely | an opt-out record has to outlive the request it came with, or the opt-out stops working |
| Unmatched inbound email held for review | 90 days after it is resolved; unresolved items are kept until a person reviews them | to identify and route legitimate correspondence |
| Other personal information with no retention basis | erased on request | none — we have no reason to keep it |
| Access to reports and data export after an account is cancelled | 30 days | so a departing customer can get their records out |
| Grace period on a deletion request, during which you can cancel it | 30 days | so a request made in error can be withdrawn |
These are our policy defaults and they can vary by jurisdiction. When we no longer need information, we delete it or de-identify it. Audit and activity logs are retained so that an action taken in an account remains reconstructible.
9. Security
Operating today: encryption in transit; encryption at rest for the sensitive fields we single out, such as tax identification numbers, account numbers, and stored access codes; per-account data isolation enforced by fail-closed query scoping with continuous automated tests; role-scoped access; signature verification on inbound provider callbacks, which fail closed; audit logging; two-factor authentication; and secret-scanning and static-analysis gates in our build.
Designed and committed, not yet operating: encryption at rest for the production data layer as a whole, using customer-managed keys for our database and file storage. It is written as infrastructure-as-code and scheduled for provisioning. We describe it as designed rather than operating because that is what is true today.
Account holders control who they invite and what permissions they grant, which is the most important security control in the Platform. No system is perfectly secure, and we cannot guarantee absolute security.
10. Your choices and rights
Everyone can:
- See and correct your own information. View and edit your profile and, within your permissions, the records in your workspace.
- Choose your notifications. Change which notifications, digests, and reminders you receive in Settings.
- Stop email. Every non-essential email carries a one-click unsubscribe. We may still send essential transactional and safety messages — an emergency work-order update, a legally required notice.
- Stop texts. Reply STOP to any message. We log opt-in and opt-out events with their source, and we honour a revocation however it reasonably reaches us.
Account holders can also:
- Export. Request a full export of your account's data, delivered as an authenticated, ownership-checked download.
- Delete. Request account deletion. Read the next paragraph first — the mechanics matter.
What deletion actually does. Because financial, lease, and screening records carry legal retention obligations, we implement deletion as anonymisation: we redact the identity fields and mark the record anonymised, while the legally retained business records — ledgers, executed leases — are preserved without your portable identity attached. We record the legal basis applied to each category so you can be told what was kept and why. If you are a tenant: deletion severs your portable identity from your profile, but each landlord's own historical record of their tenancy is retained under their obligations. An account owner's deletion requires the account to be wound down first.
If you are a tenant, applicant, vendor, or owner and you ask us to delete, correct, or give you a copy of information that sits inside an account holder's records: we will honour it where the information is ours to act on, and otherwise we will forward your request to the account holder whose records contain it and tell you we have done so. There is no self-service path for a person without an Elisian login — write to us using Section 11 and a person will handle it.
State privacy rights. Depending on where you live you may have the right to confirm whether we process your information, to get a copy of it, to correct it, to delete it, to receive it in a portable form, to opt out of sale, sharing, targeted advertising, and certain profiling, to limit our use of sensitive personal information, and to appeal a decision we make on your request. We will not discriminate against you for exercising any of them.
We respond within the time the applicable law allows — generally 45 days, extendable once where the law permits, and we will tell you if we need the extension. If we deny your request you may appeal by replying to our decision; we will respond to the appeal in writing, and if we deny the appeal we will tell you how to contact your state attorney general. We may need to verify your identity before acting, and we will ask only for what verification requires. An authorised agent may act for you with your written permission.
11. How to reach us
Questions about this policy, or a request about your information:
- Email: privacy@elisian.ai
- Post: [Elisian legal entity name, street address]
- In the app: Settings → Help and feedback
12. Children
The Platform is not directed to children under 13 and we do not knowingly collect their personal information. Lease and household records may name occupants who are minors, as entered by an account holder or a tenant. If you believe a child has provided information to us directly, contact us and we will delete it.
13. International use
Elisian is operated from the United States, and information is processed and stored there. If you use the Platform from elsewhere, you understand that your information is transferred to the United
14. Changes to this policy
We may update this policy. Every version carries a version identifier and an effective date, and the Platform records the version you accepted when you registered, so you can always tell which one you agreed to.
When we make a material change we will post the new version with its effective date before it takes effect and notify account holders.
Elisian