Data processing addendum
Last updated November 5, 2026
This data processing addendum ("DPA") is part of the LeaseDash™ terms of service between your agency ("you") and LeaseDash CRM LLC ("LeaseDash", "we", "us"). It explains how we handle the customer data your agency keeps in LeaseDash. It applies automatically while your agency uses LeaseDash. If this DPA and the terms disagree about customer data, this DPA wins.
1. Words we use
- Customer data: information your agency or your users put into LeaseDash about people, such as leads, customers, co-signers, your own staff and drivers, and the messages, deals, lease returns and schedule entries about them.
- Sensitive data: the most protected part of customer data: Social Security numbers, dates of birth, driver's license details and income.
- Security incident: a confirmed breach of our security that leads to customer data being lost, changed, disclosed or accessed without permission.
- Subprocessor: another company we use to run LeaseDash that may handle customer data.
2. Your data, your instructions
Your agency decides what customer data goes into LeaseDash and why, and owns it. We handle it only on your behalf, to provide, secure, support and improve the LeaseDash service for you. Your use of LeaseDash, your settings, and your written requests to us are your instructions. We will tell you if we believe an instruction breaks the law.
For U.S. privacy laws we act as your service provider (in California, a "service provider" or "contractor" under the CCPA as amended by the CPRA). That means we will not:
- sell or share customer data, including for targeted (cross-context behavioral) advertising;
- keep, use or disclose customer data for any purpose other than providing LeaseDash to you, or outside our direct business relationship with you;
- combine customer data with data we get from other sources or other agencies, except as the law allows a service provider to;
- use customer data to train artificial intelligence models.
We will tell you if we can no longer meet these obligations. You may take reasonable steps to stop and fix any use of customer data that breaks this DPA.
We may use information that is truly de-identified or combined so it can't identify any person or agency (for example, counts of how many features are used) to run and improve LeaseDash. We will not try to re-identify it.
3. Your responsibilities
You are responsible for having the right to collect and use the customer data you put into LeaseDash, for giving people any notices and getting any consents the law requires, and for the permissions you give your users. If you turn on automatic emails, we send them for you, as your processor, only to customers and leads you record as having given permission. You are responsible for that permission, for what the emails say and for the mailing address in them. We add an unsubscribe link to every email, honor unsubscribes, bounces and spam complaints by not emailing that address again for your agency, and keep a send log that holds no email text. If a mailbox is connected, the emails go out from that mailbox through Google or Microsoft; the connection is send-only, the sign-in token is stored encrypted and never shown to any user, and disconnecting removes it. A bounce from a connected mailbox arrives in that mailbox, not in LeaseDash. Under the FTC Safeguards Rule (16 CFR Part 314), you remain responsible for overseeing your service providers. This DPA and the security summary below are meant to help you do that.
4. Who can see customer data
- Your agency's users see what their role, permission groups and data scope allow, as set up by your administrators.
- Other agencies never can. Every agency's data is separated by rules enforced in the database itself on every read and write.
- LeaseDash staff see your agency's data only through a support session that an administrator or supervisor of your agency approves, for 1 hour, 2 hours or 1 day, or that you invite us into. A support session is view-only unless you allow "view and fix", and support staff can never delete records. Every support session is recorded in your activity log, and your administrators get a summary when it ends.
- Emergency access: only a LeaseDash executive can open it, only with a written reason your agency can see, and your administrators and supervisors are emailed straight away. We use it only to protect the service, your data, or the law, when waiting for approval would cause harm.
- Everyone at LeaseDash who can reach customer data is bound by confidentiality and gets only the access their job needs.
5. How we protect customer data
We keep a written information security program designed to meet the FTC Safeguards Rule, led by David Sutton, Founder. It includes:
- Encryption: data is encrypted in transit (HTTPS/TLS) and at rest (AES-256 by our hosting provider). Backups are encrypted again with a passphrase only LeaseDash executives hold.
- Two-step sign-in is required for every user, using an authenticator app, an emailed code or a texted code.
- Separation between agencies enforced by database rules on every table, and links between records that can only point inside the same agency.
- Permissions and data scope by role and group, set by your administrators, and checked again on our servers.
- Sensitive data is stored apart from the rest of a customer's record, can be hidden until a permitted user chooses "Reveal", and every reveal is recorded in the activity log.
- Activity log of sign-ins, changes, reveals and support sessions that your administrators can review.
- Backups of the whole database every night, kept for 14 days, with an automatic restore test each night.
- Session timeouts and limits on repeated sign-in and code attempts.
- Vendor review: we choose subprocessors able to protect the data and bind them by contract (section 6).
- Updates and testing: we apply security updates promptly and test changes before release.
We may change these measures as long as overall protection does not go down.
6. Subprocessors
You allow us to use the subprocessors below. Each one is bound by a written agreement that protects customer data at least as well as this DPA, for what it does. We stay responsible for their work.
| Company | What it does for LeaseDash | Customer data it handles | Where |
|---|---|---|---|
| Supabase | Database, sign-in, file storage, server functions | All customer data | United States (AWS, Virginia) |
| Vercel | Hosts and delivers the LeaseDash web app | Passes through it in transit; not stored | United States and global network |
| GitHub (Microsoft) | Stores encrypted nightly backups for 14 days | All customer data, encrypted | United States |
| Resend | Sends emails (invites, sign-in codes, notices) and the automatic emails your agency sets up for its customers and leads | Names and email addresses of your users, and of the customers and leads your agency emails; email content | United States |
| Google (Gmail) | Sends the automatic emails from a mailbox the agency or a rep connected, where mailbox connect is used (send-only access) | The names and email addresses of the customers and leads emailed, and the email content | United States and global network |
| Microsoft (Outlook) | Sends the automatic emails from a mailbox the agency or a rep connected, where mailbox connect is used (send-only access) | The names and email addresses of the customers and leads emailed, and the email content | United States and global network |
| Telnyx | Sends sign-in codes by text message, if a person chooses text codes | The phone number and the code | United States |
| Anthropic | Dash Bot (the AI assistant), when the built-in reader can't answer, after each person allows it | The question typed. For the schedule assistant, the day's schedule details (customer names, towns, times). Never sensitive data. Not used to train AI models. | United States |
| Cloudflare | Relays in-app audio calls and screen shares between your users | Call audio and screen video, encrypted in transit; not recorded or stored | United States and global network |
| Apple, Google (Firebase) | Deliver phone app notifications | A device token and the notification text, which can include a customer’s name | United States |
| Meta (Instagram) | Delivers Instagram messages to the agencies that connect Instagram | Instagram username and messages sent to the agency | United States |
| Stripe | Bills your agency's subscription | None (only your agency's own billing contact and payment details) | United States |
AI tools you connect. If your agency or one of your users connects an AI tool (such as Claude, ChatGPT or any other tool that uses an API key or a webhook) to LeaseDash, that tool acts on your behalf. It is your choice and your instruction, not our subprocessor. LeaseDash does not send customer data to any such tool unless you connect it, and then only what that connection asks for and your user may see. Sensitive data and documents are never available to a connected AI tool. Once data reaches a tool you connected, that tool's own terms and privacy practices apply, and you are responsible for choosing tools you trust. You can disconnect any tool at any time in Settings, and every action a connected AI tool takes is recorded in your activity log. Webhook messages go to the address you give us and carry names, ids and links, never sensitive data.
We will email your account owner at least 30 days before adding or replacing a subprocessor that handles customer data. If you have a reasonable data-protection objection, tell us within that time. If we can't resolve it, you may end your subscription and get a refund of any prepaid fees for the unused time.
7. If something goes wrong
If we become aware of, or reasonably suspect, unauthorized access to your customer data, we will tell your account owner and administrators without undue delay, and no later than 72 hours after we become aware of, or reasonably suspect, unauthorized access to your customer data. We will share what we know (what happened, what data and roughly how many people are involved, what we are doing about it, and who to contact), and update you as we learn more. We will help you meet your own legal duties, such as notifying affected people, state regulators, or the FTC under the Safeguards Rule (for incidents involving 500 or more consumers, within 30 days of discovery). Telling you about an incident is not an admission of fault.
8. Helping with people's requests
If someone asks to see, correct or delete their information, your agency can do this in LeaseDash. If a request about customer data comes to us directly, we will send it to you and not answer it ourselves unless the law requires it. We will give reasonable help with requests you can't handle in the app.
If a government agency or law enforcement asks us for customer data, we will tell you first unless the law forbids it, so you can respond yourself. Before answering, we review whether the request is lawful and valid and challenge it if it is not, disclose only the minimum the law requires, and keep a record of the request, our response and the legal reasoning. Our full policy is in the Privacy Policy.
9. Keeping and deleting data
- While you subscribe, you decide what to keep and can delete records in the app (subject to your permissions).
- When your subscription ends you can export your data for 30 days. After that we delete your customer data from our live systems within 30 days.
- Copies in backups disappear as the backups expire (14 days), and are never restored for any other purpose.
- We may keep the minimum needed to meet legal, tax or accounting duties (for example, invoices), protected as described here.
10. Showing that we comply
Once a year, or after a security incident, we will answer a reasonable security questionnaire and give you a summary of our security program. If the law requires more (for example, an audit by a regulator), we will cooperate at your cost, with reasonable notice, during business hours, and in a way that protects other agencies' data.
11. Where data is kept
Customer data is stored in the United States. We will tell you before that changes.
12. How long this DPA lasts, and liability
This DPA lasts as long as we hold any of your customer data. Each party's liability under it is subject to the limits in the terms of service, except where the law does not allow a limit.
Questions
Email support@leasedashcrm.com, or write to LeaseDash CRM LLC, 6 Arlington Street, Oakhurst, NJ 07755. To sign a copy of this DPA for your records, ask us at the same address.