Evictions API

Privacy policy

Effective November 18, 2026

Who we are

Evictions API is operated by Future Cities LLC (“we”, “us”). This policy explains what personal data the website, the signed-in app and the API handle, why, who receives it, and what you can ask us to do. It covers customers who start cases, attorneys who take them, visitors to the website, and tenants and other people named in a case.

What we collect

Account data

When you sign up we store your email address, your name, the name of your organization, your password and, if you choose to answer, how you heard about us. The password is stored only as a hash, so we cannot read it back. We store the sign-in sessions of your account and, when you ask to reset your password, a single-use reset link that expires after one hour. API keys and reset links are stored only as hashes.

Case data

The information a customer supplies to start and run a case: the property address, county and owner of record; the names of the parties, including tenants; lease terms, rent ledgers and amounts owed; details of any lease violation; the customer’s answers and confirmations; uploaded documents such as deeds, management agreements, notices and proofs of service; and messages written on the case. As the case moves, we add its status, deadlines, court case number and hearing date, and documents from the attorney. In test cases, made with a developer’s test key, customers are asked to use made-up names and details, not a real person’s.

Customers who manage property for owners can save an owner’s details to reuse on their cases: the owner’s name, whether it is a company and its legal type, the owner of record, contact address, phone and email, notes, and the management agreement. We keep them with the customer’s account and use them only to fill in that customer’s cases.

Tenants do not give this data to us directly. The customer who submits the case supplies it, and the attorney and we add to it as the case moves.

Payment data

Payments are processed by Stripe. Your card number and security code go to Stripe and are never received or stored by us. Of a saved card we keep its brand, last four digits, expiry date and the cardholder’s name as Stripe has it, with who added it and the landlord it is linked to. We keep a record of each charge: what it is for, the amount, whether it is due, paid, void or refunded, when it was paid, and the identifiers Stripe gives us for the payment.

Attorney data

For an attorney who applies to take cases or is engaged for one, we hold the attorney’s name, email address, firm, the states where the attorney is licensed and bar numbers. The name, firm, state and bar number of the engaged attorney are shown to the customer on the case.

Forms on this website

When you contact us, tell us about your properties or apply as an attorney, we store your name, email address and what you write in the form, which can include your company, role, states and bar number. These forms do not ask for tenant information.

Logs

Our servers and hosting providers keep technical logs of requests, such as the time, the address requested, the result and the IP address. We use IP addresses to limit repeated requests, for example repeated sign-in attempts. Tenant personal data is not written to application logs.

Analytics

We count our own visits, without cookies and without any analytics service. Our website’s server records the page requested, the site a visit came from, the country, whether the device is a phone, and a few events, such as a click on a call-to-action button, a submitted form, a sign-up or a visit that came from an AI assistant’s answer. In place of your IP address it keeps a token derived from it that changes every day, so visits are counted and nobody is identified. These counts are kept for three months.

Cookies

When you sign up or log in, the website sets a cookie that keeps you signed in. It is strictly necessary for that: it holds a session token, it is not readable by scripts on the page (httpOnly), it is sent only to this website, and it expires after 30 days or when you log out. It is not used for tracking or advertising, and the website sets no tracking or advertising cookies. When you pay, you do so on Stripe’s pages, which set Stripe’s own cookies.

How we use data

  • To run your account and keep it secure.
  • To run a case: to check it before submission, to engage a licensed attorney in the property’s state for it, to record its steps, and to show it to you.
  • To take payment and keep records of charges.
  • To send service emails: a welcome message, password resets, and news of a case, such as a status change, a new message or a new charge. These emails name a case by its id and do not contain tenant names or addresses.
  • To reply to you, and to assess attorney applications.
  • To keep the service working, find faults and prevent abuse.
  • To meet legal obligations.

We do not use personal data for advertising.

Who receives data

  • The attorney engaged for a case. We give the attorney the case data and documents so the attorney can review the case and do the legal work. The attorney is an independent lawyer with professional duties of confidentiality.
  • Courts, process servers and the other party, through the attorney. To serve a notice and file a case, the attorney gives information from the case to the people who serve papers and to the court. Court filings are often public records.
  • Stripe, which processes payments. Stripe receives your payment details from you and the amount and a description of the charge from us.
  • Hosting and infrastructure providers that store and process data for us under their terms: Cloudflare, which hosts the website and answers for our domain; Render, which hosts the API; Neon, which hosts the database; Resend, which sends our email; and Amazon Web Services, whose Amazon SES service can send it in Resend’s place. Mail sent to your case intake address passes through Cloudflare Email Routing. Mail our server cannot take is forwarded unchanged to our team’s mailbox (hosted by Google) and deleted once it has been handled.
  • The US Census Bureau, whose address lookup finds the county of a property. When you start a case from a lease, or enter an address, it receives the street, city, state and ZIP code of the property, without a unit or any name.
  • Google, when you pick a file from Google Drive. The new-case page loads Google’s sign-in and file-picker scripts, and Google gives your browser a permission that covers only the files you pick. Files picked in Google Drive are downloaded by your browser from Google; we never see your Drive or that permission.
  • Buildium and DoorLoop, when you connect one. Our server calls them with the key you give us, which we keep encrypted, to read the lease you pick: they receive the key and which lease or tenant name is asked for.
  • Google Maps Platform, if you use the address suggestions. As you type in the suggestion box, your browser sends what you type to Google, which answers with matching addresses; Google receives it directly from your browser, and we do not see, log or store what you type there. The suggestions are offered only where you enter the address yourself, and you can type the address in the ordinary fields instead.
  • OpenRouter, which passes files to an AI model that reads them. While a case is a draft and still lacks details your documents may state, we send the documents you uploaded to that case (the lease, the tenant ledger, a notice you already gave, and other papers; not your proof of authority, proof of service or messages) to be read, without asking you first, and fill in only the details that are empty: names, the landlord’s address and telephone, the rent, the lease dates, how the lease says notices are delivered, the ledger and the amounts it shows, and the type of the notice. We mark each of those answers as read from your documents, email you how many were filled, and you check them before you submit. In the new-case form it also receives a lease or a ledger when you click “Try our file reader”, and, in a case about a lease violation, the messages with the tenant you gave (at most 10) when you click “Draft what happened from these messages”. Nothing else from the case is sent. The model is Anthropic’s Claude, run by Amazon Web Services or Google Cloud, and we ask for endpoints that keep no data and do not use it for training. We do not store the files at OpenRouter or keep its answers there. OpenRouter also receives the messages you send us through the website’s forms or by email to hello@evictionsapi.com, with the name, email address and company you give, so that an AI model can draft our reply, on the same terms. The reply says it was written by AI, and a person on our team handles what it cannot answer.
  • Authorities and others when the law requires it, such as in answer to a valid court order, or when needed to protect someone’s safety or our legal rights.
  • A successor, if the service is transferred to another company, under this policy or one that protects the data at least as well.

We do not sell personal data. Webhook messages sent to a customer’s own systems carry identifiers and status only, never names or addresses.

Tenant information

A case contains information about tenants: their names, the address they rent, and what the landlord says about the tenancy. We use it only to run that case. We do not sell tenant data. We do not furnish it to anyone for tenant screening, and we do not build or sell lists or records of tenants or of evictions. Evictions API is not a tenant-screening service. Customers agree in our terms not to use the service for screening.

If you are a tenant named in a case and want to know what we hold about you, or believe it is wrong, write to hello@evictionsapi.com. We cannot give legal advice or change what happens in a court case, and some data must be kept while a case is open.

How we protect data

  • Case details (the parties, addresses and facts of a case), uploaded documents (their contents and their file names), messages on a case, court case numbers, the source notes on deadlines and the owner details a customer saves (with their management agreements and file names) are encrypted at rest in our database. The name of a deadline is a short label, such as “Hearing”, and is stored without that added encryption.
  • Data submitted through the website forms is encrypted at rest.
  • Data travels between your browser, our website and our API over encrypted connections (HTTPS).
  • Passwords, API keys and reset links are stored only as hashes.
  • Every change to a case is recorded in an audit log that cannot be edited, each organization can see only its own cases, and each time our own staff open a case that is recorded too.

No system is perfectly secure. If you think your account has been used by someone else, write to hello@evictionsapi.com.

How long we keep data

We keep account data, and the owner details a customer saves, while your account is open; a customer can archive a saved owner at any time. We keep case data, documents, messages and payment records while the case is open and afterwards for as long as we need them for the purposes in this policy: to give you access to your records, to resolve disputes, and to meet legal, tax and accounting obligations. Sign-in sessions expire after 30 days and password-reset links after one hour. Files and email text you send to your case intake address, and files your AI agent sends, are kept encrypted for up to 30 days unless you move them onto a case or remove them. We do not delete case data on a schedule. When you ask us to delete data, we carry out the request ourselves, case by case: we erase what identifies a person in the case (the parties, addresses and facts, the messages, and the documents with their file names) and keep the case’s identifier, status, dates and payment records, unless we must keep more for one of those reasons. Erased data can remain in our database provider’s encrypted backups for a limited period, until those backups expire. Test cases may be deleted at any time.

The attorney engaged for a case keeps the attorney’s own file under the attorney’s professional rules, and courts keep their own records. We do not control either.

Your requests

You can ask us what personal data we hold about you, ask for a copy, and ask us to correct or delete it, subject to what we must keep for a case or by law. This includes tenants and property owners whose information a customer supplied. Depending on where you live, the law may give you further rights, such as the right to appeal a refusal. We do not treat anyone worse for making a request. Write to hello@evictionsapi.com. We may need to confirm who you are before we act, and we answer by email.

Children

The service is for adults acting for themselves or a business. It is not directed to children, and we do not knowingly collect account data from anyone under 18.

Changes to this policy

We will post changes on this page with a new effective date. If a change is material, we will also email the address on your account before it takes effect.

Contact

Questions or requests about your data: hello@evictionsapi.com. Evictions API is operated by Future Cities LLC.

Questions about your data?

Write to hello@evictionsapi.com.