Data Processing Addendum
This addendum sets how Zrico handles the personal information a property management company puts into Zrico. The company decides what is kept and why; Zrico acts only on its instructions, protects the information, and deletes it when the agreement ends.
1. Parties, scope and order of precedence
This Data Processing Addendum (the "Addendum") is part of the agreement between Zrico and each property management company or owner-operator that uses the Zrico platform (the "Company"). The agreement is made up of Zrico's Terms of Service, any order form, and this Addendum (together, the "Agreement").
This Addendum applies whenever Zrico processes Customer Personal Data to provide the service. It takes effect when the Company accepts the Terms of Service and lasts as long as Zrico processes Customer Personal Data for the Company.
If this Addendum and another part of the Agreement disagree about personal information, this Addendum controls. Anything it does not cover is governed by the rest of the Agreement.
This is version 2026-11-17. The same Addendum, with the same version number, is shown inside the Zrico app.
2. Definitions
In this Addendum, these words have these meanings:
- Customer Personal Data: personal information that the Company, its staff or the people it invites put into Zrico, or that Zrico collects for the Company while providing the service, to the extent Data Protection Laws protect it. It does not include Zrico Account Data.
- Zrico Account Data: the central login (a person's email address, password, two-step sign-in settings, sessions, and which companies the login belongs to), and Zrico's own account, support and billing records with the Company.
- Processing: any operation on personal information, such as collecting, recording, storing, using, sending, correcting or deleting it.
- Data Protection Laws: the United States privacy and data security laws that apply to the processing. These include the New Jersey Data Privacy Act (P.L.2023, c.266, N.J.S.A. 56:8-166.4 et seq.), the California Consumer Privacy Act as amended by the California Privacy Rights Act (Cal. Civ. Code 1798.100 et seq.) and its regulations (Cal. Code Regs. tit. 11, section 7000 et seq.), other state consumer privacy laws with similar processor rules, and state data breach notification laws.
- Controller, processor, business, service provider, consumer, sale, sharing, sensitive data and deidentified data: the meanings the applicable Data Protection Law gives them.
- Subprocessor: a company Zrico engages that processes Customer Personal Data to help Zrico provide the service.
- Security Incident: a breach of security that leads to the accidental or unlawful destruction, loss or alteration of, or unauthorized access to or disclosure of, Customer Personal Data in systems run by Zrico or a Subprocessor. Unsuccessful attempts that do not compromise the data, such as blocked sign-in attempts or network scans, are not Security Incidents.
- Company admin: a member of the Company's staff with the admin role in Zrico.
3. Roles of the parties
- The Company is the controller (a "business" under the California law). It decides what information it keeps about its people and what that information is used for.
- Zrico is the Company's processor (a "service provider" under the California law). It processes Customer Personal Data only to provide the service, on the Company's instructions.
- Zrico is responsible on its own account for Zrico Account Data. The central login lets one person use one login with several companies. Zrico never tells a company which other companies a person belongs to. Zrico's privacy policy explains how it handles Zrico Account Data.
4. Annex: nature, purposes and duration of the processing
Subject matter: the personal information needed to run the Company's property management business in Zrico. Zrico processes it only for these specific business purposes:
- Keeping the Company's records of properties, units, leases, tenants, owners, vendors and staff.
- Accounting: ledgers, trust accounting, bank feeds and reconciliation, owner statements, budgets and tax forms such as Form 1099.
- Collecting rent, fees and application fees, and paying owners and vendors, through the payment providers the Company turns on.
- Leasing: listings, inquiries, tours, applications, the screening the Company orders, and lease signing.
- Communication: email, text messages, phone calls, voicemail, call recordings and transcripts, mailed letters and notifications.
- Documents and e-signatures, maintenance requests, work orders, inspections and smart lock access codes.
- Resident, owner and vendor portals.
- The optional features the Company turns on, including Zrico AI.
- Keeping the service secure, preventing fraud, fixing errors, backing up and restoring data, and giving support the Company approves.
- Meeting Zrico's legal obligations.
Nature of the processing: hosting, storing, organizing, displaying, sending, calculating, searching and backing up the data; AI drafting, summaries and document reading when the Company turns AI on; and deleting the data as this Addendum says.
Duration: for as long as the Agreement lasts, and then until the data is returned or deleted under the section on return and deletion.
5. Annex: whose information is processed
- Tenants, residents and household members.
- Applicants, guarantors and leads.
- Owners and investors.
- Vendors and their staff.
- The Company's staff and other people it gives a Zrico login.
- Visitors to the Company's listings, web chat and self-tour pages.
- Anyone who writes, texts or calls the Company through Zrico.
6. Annex: kinds of personal information
- Names, contact details and mailing addresses.
- Lease, rent, payment and accounting records.
- Owners' and vendors' bank account details for payouts, stored encrypted.
- Application and screening information, including the reports the Company orders and the results of identity and income checks.
- Messages, texts, emails, call recordings, voicemail and transcripts.
- Documents, photos, signatures and the audit details of each signature.
- Maintenance and inspection records, and smart lock codes and door events.
- Information a person gives in a request for a reasonable accommodation.
- Sign-in, device and network details, such as IP addresses and browser type.
- The last 4 digits of social security and tax ID numbers.
Not stored in Zrico: full card numbers, which people type into the payment provider's own pages; full social security and tax ID numbers (a full tax ID typed in for an IRS e-filing is used for that filing and not kept); and the photo ID and selfie from an identity check, which go straight to the identity provider.
Some of this can be sensitive data under Data Protection Laws, for example financial account details, health or disability information in an accommodation request, and information about a household member who is a child. The Company decides whether to collect it and is responsible for any consent the law requires before it is processed.
7. The Company's instructions
The Company's instructions are this Addendum, the rest of the Agreement, and what the Company sets up and does in Zrico: its settings, the features it turns on, and what its staff do. Zrico follows those instructions.
Zrico will tell the Company if it believes an instruction breaks a Data Protection Law. Zrico does not have to follow an instruction it reasonably believes is unlawful. Instructions outside the service as described need both parties' written agreement.
8. The Company's responsibilities
- Collecting Customer Personal Data lawfully and giving its people the privacy notices the law requires.
- Getting and keeping any consent the law requires, for example for text messages, call recording and sensitive data.
- Making sure its instructions to Zrico are lawful, and keeping its data accurate.
- Managing its own users, roles and permissions, and keeping sign-in details safe.
- Answering its people's privacy requests, using the tools Zrico provides.
- Not putting into Zrico information it was not built to hold, such as protected health information under HIPAA, or full card numbers, social security numbers, bank passwords or other credentials typed into notes or free-text fields.
9. What Zrico will not do
Zrico will not:
- Sell Customer Personal Data, or share it for cross-context behavioral (targeted) advertising.
- Keep, use or disclose it for any purpose other than the business purposes listed in this Addendum, including any commercial purpose of its own.
- Keep, use or disclose it outside the direct business relationship between Zrico and the Company.
- Combine it with personal information Zrico receives from or for other companies, or collects from its own contact with people, except the central login described above and what keeping the service secure and preventing fraud require, as the law allows.
- Try to re-identify any deidentified data it receives.
- Use it to train AI models. When the Company turns AI on, the AI provider receives it under commercial terms that forbid training on it.
Zrico will comply with the Data Protection Laws that apply to it as the Company's processor, and give Customer Personal Data the same level of privacy protection those laws require of the Company. Zrico will tell the Company if it decides it can no longer meet these obligations.
The Company may take reasonable and appropriate steps to make sure Zrico uses Customer Personal Data in line with the Company's obligations. After telling Zrico, it may take reasonable and appropriate steps to stop and fix any use this Addendum does not allow.
Zrico keeps these promises for every Company. Where the California Consumer Privacy Act applies to the Company, they are also Zrico's service provider terms under Cal. Civ. Code 1798.100(d) and 1798.140(ag) and Cal. Code Regs. tit. 11, section 7051.
10. New Jersey and other state processor terms
This Addendum is the contract between controller and processor that section 13 of the New Jersey Data Privacy Act requires (N.J.S.A. 56:8-166.16). The same terms meet the processor rules of other state privacy laws built on the same model. In particular:
- Instructions and the nature and purpose of the processing: set out in the sections on the Company's instructions and the Annex.
- The type of personal data and the duration of the processing: set out in the Annex.
- The rights and obligations of both parties: set out throughout this Addendum.
- Confidentiality: everyone who processes Customer Personal Data for Zrico is under a duty of confidentiality.
- Subcontractors: Zrico engages Subprocessors only under written contracts that require them to meet Zrico's obligations for the data, after giving the Company notice and a chance to object.
- Delete or return: at the Company's choice, Zrico deletes or returns Customer Personal Data at the end of the service, unless the law requires it to be kept.
- Showing compliance: Zrico makes available the information the Company needs to show that the obligations of the Act are met.
- Assessments: Zrico allows and contributes to reasonable assessments by the Company or its chosen assessor, or, with the Company's consent, arranges its own independent assessment, as the section on assessments says.
- Help with the Company's duties: Zrico helps, through suitable technical and organizational measures, with people's requests, the security of the processing, breach notices, and the information the Company needs for its data protection assessments.
Nothing in this Addendum relieves either party of the obligations or liability that come with its own role under Data Protection Laws.
11. Zrico AI
- AI is off until a Company admin turns it on in Zrico's AI settings, after reading and accepting the data sharing notes. While it is off, nothing is sent to the AI provider.
- When AI is on, the AI provider (Anthropic) receives the question asked and the records the AI looks up to answer it, such as names, addresses, amounts, dates, messages, and the documents or photos a feature reads.
- Before anything is sent, Zrico removes full social security and tax ID numbers, bank account, routing and card numbers, passwords and keys.
- Anthropic's commercial terms forbid it from training models on this content. It deletes inputs and outputs within 30 days, except where it must keep them longer to enforce its usage policies or by law.
- Zrico does not use Customer Personal Data to train AI models.
- The Company sets each area of work to Off, Assist or Autopilot. Anything with money over the Company's limit or legal weight waits for a person to approve it, and the AI never makes the decision on a rental application.
- Zrico keeps a log of everything Zrico AI did, which the Company can review.
12. Confidentiality and support access
Everyone at Zrico who can reach Customer Personal Data is bound to keep it confidential, and access is limited to the people who need it to provide, secure or support the service.
Zrico's support team sees the Company's tenants, owners, vendors and other people only when a Company admin approves a support access request on the Support access page in Settings. Each approval is limited in time and scope, can be revoked at any moment, and is recorded in both the Company's and Zrico's audit logs.
The people who run Zrico's hosting and database can reach stored data in the course of that work. They do so only to keep the service running, secure and backed up, or when the law requires it.
13. Security measures
Zrico maintains reasonable administrative, technical and physical safeguards suited to the nature of the data. These are built into Zrico and apply to every company:
- Separation by company: every record carries its company, and every request is limited to the signed-in person's company. Row-level security in the database checks that again inside the database itself, so one company's request cannot read another company's rows.
- Encrypted connections: every page is served over HTTPS, and browsers are told to use only HTTPS (HSTS).
- Sealed secrets: bank feed logins, owners' and vendors' bank account numbers, and each company's keys for outside services are encrypted at rest with AES-256-GCM and tied to their use. Staff only ever see the last 4 characters. Passwords are stored only in hashed form.
- Two-step sign-in: an authenticator app or passkeys for staff, and an authenticator app or a code by email or text for tenants, owners and vendors. The Company can require two-step sign-in for its staff.
- Permissions by role: staff see and change only what their role allows.
- Audit logs: an append-only log records important changes, with who made them and when. The Company can turn on a tamper check that links each entry to the one before. A separate log records everything Zrico AI did.
- Limits on repeated sign-in attempts and on the public forms.
- Backups: a daily copy of the database in file storage, plus the hosting provider's daily database backups and point-in-time restore. Zrico runs restore drills, and a weekly automatic restore test can check that the newest backup loads and balances.
- Error reports with personal details and secrets filtered out before they leave.
- Checked connections: messages from payment, text, email, mail and lock services are verified by their signatures, and requests to addresses a company types in cannot reach private networks.
- Export and per-person tools: the Company can export its records at any time, and can find, export, correct and erase one person's records. Retention schedules the Company sets erase old records only after an admin approves the list.
- Physical security of the servers is provided by the hosting provider's data centers.
Zrico may change these measures over time, but will not make a change that lowers the overall protection of Customer Personal Data. Zrico does not hold, and this Addendum does not claim, any third-party security certification.
14. Subprocessors
The Company authorizes Zrico to use the Subprocessors listed on the Subprocessors page (/legal/subprocessors), which says what each one receives, why, and where. Zrico uses each one only to provide the service, under written terms that protect the data at least as much as this Addendum does, and stays responsible to the Company for their work.
- Notice: Zrico will email the Company's admins and update the Subprocessors page at least 30 days before a new Subprocessor starts receiving Customer Personal Data.
- Objection: the Company may object on reasonable data protection grounds within those 30 days, by email to support@zrico.com. Zrico will work in good faith to resolve it, for example by not using that Subprocessor for the Company's data.
- Remedy: if it cannot be resolved, the Company may stop using the part of the service that needs that Subprocessor, or end the Agreement, and get back any fees it prepaid for the unused time.
- Services the Company connects itself, with its own account (for example screening, listing sites or accounting software), are the Company's own providers under its own agreements with them, not Zrico's Subprocessors. Zrico sends them only what the connection needs, on the Company's instruction.
15. Requests from people
Zrico gives the Company the tools to answer people who ask to see, correct, get a copy of or delete their information, and helps when asked. If Zrico receives a request about the Company's records, it sends the request to the Company and does not answer it on the Company's behalf unless the Company asks or the law requires it.
A person can ask once, from their Zrico account page, to be erased everywhere. Zrico turns that into a separate request at each company the person belongs to. Nothing is erased at a company until that company's admin approves it on the Account deletions page in Settings. Approving removes the person's personal details there while keeping the records the books and the law need, such as payments, the lease and signed documents. A company may decline, for example under a legal hold, and then keeps its records.
When every company has decided, or 30 days have passed, the login itself is erased. Companies should decide within that time: most state privacy laws give the Company 45 days to answer a person.
When one person merges two logins, a company that knew only one of them keeps writing to the address it knew, and is not told about the other. If both logins already belong to the same company, the person must agree before that company sees them as one.
16. Security incidents
- Zrico will tell the Company immediately after discovering a Security Incident, and never later than 48 hours after discovery, by email to the Company's admins.
- The notice says what happened and when, what kinds of information and roughly how many people are affected, what has been done, and whom to contact. More follows as Zrico learns it.
- Zrico will investigate, contain the incident, keep records of it, and help the Company meet its own duties to tell people and regulators. Examples: New Jersey requires a report to the Division of State Police before people are told (N.J.S.A. 56:8-163); Pennsylvania requires notice to the Attorney General when more than 500 residents are notified (73 P.S. 2301 et seq.); Ohio requires notice to residents within 45 days (Ohio Rev. Code 1349.19).
- The Company decides on notices to its people. Zrico will not send them on the Company's behalf without its agreement, unless the law requires it.
- A notice from Zrico is not an admission of fault or liability.
- The Company can report a suspected incident to security@zrico.com.
17. Assessments and audits
Zrico will make available the information the Company reasonably needs to show this Addendum and Data Protection Laws are being met. That includes a written description of Zrico's security, answers to a reasonable security questionnaire once a year, and help with the Company's own data protection assessments.
The Company, or an independent assessor it chooses who agrees to keep things confidential, may carry out a reasonable assessment of Zrico's compliance. The Company gives 30 days' notice, bears its own costs, and assesses no more than once a year, or again after a Security Incident. Assessments take place during business hours, avoid disrupting the service, and never give access to other companies' data.
With the Company's consent, Zrico may instead arrange for a qualified and independent assessor to assess its policies and its technical and organizational measures, at least once a year and at Zrico's expense, using an appropriate and accepted control standard or framework. Zrico will give the Company the report on request.
18. Data location and transfers
- Customer Personal Data is stored in the United States.
- Where each Subprocessor processes data is shown on the Subprocessors page.
- One service can receive a small amount of data outside the United States: address suggestions from komoot GmbH's Photon service, in Germany. It receives only the address text being typed, to return suggestions. On staff forms that means property and vendor addresses. On the public rental application and W-9 forms, suggestions are off unless Zrico turns them on. If Zrico runs its own Photon server, no address text leaves Zrico.
- Browser notifications pass through the push service of the person's browser maker, encrypted so that service cannot read them.
- Zrico will give the same 30 days' notice before it stores Customer Personal Data outside the United States.
19. Return and deletion
- The Company can export its data at any time.
- If an invoice goes unpaid, the account stays fully usable for 7 days, then read-only for 30 days with export still on, before it is canceled.
- After cancellation, Zrico keeps the Company's data for 90 days so it can still be exported, then erases it from the live systems. The Company can ask Zrico to return or delete it sooner, at its choice.
- Copies in backups are erased as those backups are deleted on the backup schedule (daily copies are kept for 35 days, plus the first copy of each month for 12 months). The hosting provider's own database backups age out on its schedule. Until then, the copies stay protected by this Addendum.
- Zrico keeps only what the law requires it to keep, protected as this Addendum says, and Zrico Account Data, including its own billing records with the Company.
- On request, Zrico will confirm in writing when the erase is done.
20. Liability
Between the parties, claims under this Addendum are subject to the limitations and exclusions of liability in the Terms of Service, to the extent the law allows. This Addendum does not relieve either party of the obligations or liability that Data Protection Laws place on it in its own role.
21. Term and changes
- This Addendum lasts as long as the Agreement, and its protections continue for as long as Zrico or a Subprocessor holds Customer Personal Data.
- Zrico may update this Addendum to keep up with the law or the service, with 30 days' notice to the Company's admins by email. Each version is shown on this page with its date.
- A change that lowers the protection of Customer Personal Data needs the Company's agreement.
22. Notices and contact
- Zrico sends notices under this Addendum by email to the Company's admins.
- Questions and objections: support@zrico.com.
- Security incidents: security@zrico.com.
- By mail: Zrico, 1600 NJ-70, Lakewood, NJ 08701.
This page is the Addendum itself. It is not legal advice to the Company about its own obligations, and the Company should get its own advice on how Data Protection Laws apply to its business.