Privacy policy
Updated October 28, 2026 · Version 2026-10-28
Draft legal text. Legal review is pending.
This policy describes information handling in RentariIQ, operated by Rentari.ai LLC. Active financial records continue to be preserved until authorized deletion. It replaces the previous automatic three-month financial-record expiry schedule and keeps separate limits for operational information.
Financial-record preservation began with the October 26, 2026 revision. Revised terms take effect for existing accounts on November 27, 2026. For questions or privacy requests, contact [email protected]. You can also read the previous policy.
1. Scope and responsibility
This policy covers rentariiq.com and RentariIQ applications and features that link to it. Rentari.AI's property-management services and external providers have separate policies. A connection between products does not merge their accounts or deletion controls.
We determine how account administration, support and security information is used to run RentariIQ. Portfolio owners decide which rental records to enter and whom to invite. When you provide tenant, vendor or other people's information, you are responsible for having a lawful basis to do so and providing any required notices. Requests about another person's portfolio may need the portfolio owner's involvement.
2. Information we handle
- Account and sign-in information: name, email, optional phone number, password hash where a password is set, account and portfolio permissions, referral information, sign-in activity and communication preferences. Google or Apple sign-in provides a provider identifier, email and available name information. It does not give RentariIQ access to your email inbox.
- Rental and bookkeeping records: portfolio and property details, addresses, units, tenants and contacts, leases, vendors, optional vendor taxpayer IDs, account labels and last four digits, transactions, balances, rental charges and payment allocations, trust-account beneficiaries and financial activity, statement balances, loans, assets, notes, mileage and time records, uploaded documents and property photos.
- Imports: supported statement files are processed to extract rows. The original statement is not saved as an attachment by the import flow; extracted records, filenames and import history may be saved. A file you separately upload as a receipt or document is retained as an attachment. Scanned-statement recognition runs within our application infrastructure rather than being sent to a separate generative-AI service.
- Optional bank feeds: when enabled and connected, Stripe Financial Connections provides account references, institution and account labels, last four digits, balances and transaction dates, amounts and descriptions. Authorized refreshes can import available transactions automatically; you do not approve every row before it reaches the import feed. We do not receive your bank sign-in password through this connection.
- Billing: when subscriptions are enabled, Stripe processes checkout and payment details. RentariIQ stores customer and subscription references, plan status and billing-event records, rather than full card numbers or card security codes.
- Rentari.AI connections: a connection can supply identity and access references, properties, units, vendors and supported paid income and expense records. Sync history and source references help keep the connected books consistent.
- Support and technical records: messages and feedback you send, relevant page references, security and audit events, IP addresses, request and error logs, browser or device information, and email delivery or suppression records. Delivery and suppression records use an email-address hash; support mail and your active account can still contain the email address itself.
3. How we use information
We use information to create and authenticate accounts, apply portfolio permissions, maintain books and reports, process imports, operate requested connections, store documents, handle subscriptions when available, deliver account messages, respond to support requests, diagnose errors and protect the service against abuse. Operational records also help us investigate disputes and comply with applicable obligations.
We do not sell your personal information or share it for cross-context behavioral advertising. We do not use your financial records for advertising. Optional product-news email requires opt-in. Necessary account messages and the optional reminders you enable are described in your email preferences.
4. Who can access information
- Your portfolio members: people with access can see the portfolio's records according to their role. Authorized downloads leave the app's control. Consider the sensitivity of documents and taxpayer details before granting access.
- Authorized staff: support and administrative staff may access accounts and records to resolve issues, maintain the service and investigate security concerns. Staff use of the support-view feature is recorded in the audit log.
- Google Cloud: hosts the application, database, private file storage and operational infrastructure. Email delivery uses Google's mail service. Relevant account or message information is processed to provide those services.
- Cloudflare: delivers and protects the website and provides Web Analytics. Website requests expose technical information such as an IP address to the network provider.
- Google and Apple sign-in: if you choose a provider, the sign-in flow exchanges the information needed to authenticate and link your account. Provider policies also apply.
- Stripe: when payment or bank-connection features are available and used, Stripe processes the necessary customer, payment or financial-account information. See Stripe's privacy policy.
- Optional OpenAI commentary: when this feature is configured, a portfolio owner can explicitly choose to send a question and the displayed aggregate report facts, dates and bookkeeping-check counts to OpenAI. The assistant excludes source documents, transaction descriptions, bank details and tenant identities from its automatic evidence packet. Anything you type in the question is also sent, so do not include sensitive personal details or credentials. Calculated report explanations and offline statement recognition do not require this connection. The workspace does not save questions or generated answers, and requests API response storage to be disabled. The provider's processing and retention terms still apply; this is not a promise of zero provider retention. See OpenAI's privacy policy.
- Google property imagery: when Street View imagery is enabled, your browser requests an image from Google using the property's address and exposes normal connection information such as your IP address. Uploaded property photos are stored privately instead. See Google's privacy policy.
- Rentari.AI: an enabled connection exchanges supported source records and identity or access references as described above. Its source records remain governed by its own privacy policy.
We may also disclose relevant information where reasonably necessary to comply with law or valid legal process, protect rights and safety, or investigate misuse. If the business is transferred or reorganized, information may be transferred subject to the privacy commitments and applicable law governing it. Other disclosures require your direction or another lawful basis; this policy does not permit providers to use your financial records for their own advertising.
5. Cookies, device storage and analytics
RentariIQ uses cookies for sessions, form security, sign-in flows and temporary messages. Browser storage can remember a display preference, such as pausing motion. Native apps use device storage for authentication. These functions support the service; blocking or clearing them can sign you out or prevent forms and sign-in from working.
Cloudflare Web Analytics measures visits, page performance and browser or device categories. Cloudflare describes this analytics service as using neither analytics cookies nor local storage and not fingerprinting individuals. That description is separate from the security and session cookies needed to operate the website. See Cloudflare's explanation and privacy policy.
You can manage browser cookies and storage in your browser settings. RentariIQ does not currently use advertising pixels or cross-site advertising profiles. We do not change app behavior in response to a browser's Do Not Track setting. Contact support about a privacy preference or a legally applicable opt-out request.
6. Retention and account deletion
Active financial records are preserved until authorized deletion. Age, account activity, cancellation of a subscription does not by itself schedule the deletion of a portfolio's financial history. This includes journals, rental charges and payment allocations, trust-account records, reconciliation evidence, supporting attachments and portfolio-linked audit and billing evidence. This is a product retention choice, not a claim that it satisfies every legal records requirement.
The previous automatic three-month financial expiry schedule is cancelled. Earlier expiry notices do not authorize future deletion under this policy. Available records already moved to protected export-only storage are also preserved until authorized deletion. This change cannot restore records already deleted or reconstruct a stopped book's complete balances and reports. Keep independent exports and supporting files for your own records.
- Authorized deletion: deleting your account requires your password or a recent supported sign-in and confirmation. It removes your login, authentication links, email preferences and owned portfolios from the active database, including their financial records and other members' access. Contributions to portfolios owned by other people remain with those books, with applicable user references removed. Individual record-removal tools and reviewed privacy requests can also remove information within their authorized scope. Accounting corrections normally remain as reversals or void history rather than silently rewriting a posted transaction.
- Connections and holds: active subscriptions and linked banks must be resolved before account deletion. The app does not automatically cancel a provider subscription or disconnect a bank as part of deletion. Preservation holds block account deletion while a documented dispute or obligation is reviewed. Requesting a hold does not itself apply one; support must review and confirm it. A RentariIQ deletion does not delete separate Rentari.AI accounts or source records.
- Files and recovery copies: removing file records queues storage cleanup in the same database transaction. Cleanup runs after that transaction succeeds, and failed tasks remain queued for retries and support review. A file still referenced by an active or retained financial record is protected from cleanup. The current attachment provider retains deleted objects for a seven-day recovery period. Database and provider recovery copies require separate review before restoration or an erasure response.
- Operational records: app email-delivery logs and audit IP addresses normally expire after 90 days; app support messages and closed privacy requests after two years; other audit/security details and billing-event metadata after seven years. Portfolio-linked audit and billing evidence stays with active financial history rather than expiring on those operational schedules. Opaque payment-event markers remain to prevent replay. These are operational defaults, not statutory minimum periods; a preservation hold can delay cleanup.
- Necessary controls: active identity and access records, registration consent, open privacy requests, preservation holds, email opt-out hashes and pending file-cleanup controls remain while needed. Expired sign-in credentials and temporary security counters have shorter cleanup schedules. Completed maintenance and deletion-control records are normally removed after 90 days once no retained records depend on them. Opt-out hashes remain until a valid opt-in so cleanup cannot resubscribe someone.
- Account deletion and requests: deleting an account also removes linked app support messages and clears identifying audit details, IP addresses and account links. Open privacy requests continue so support can finish the request. Operational evidence, reviewed preservation obligations and recovery copies can outlast account deletion as described here.
Daily maintenance handles eligible operational records in bounded batches. Infrastructure request logs currently have a 30-day default retention period. Copies in the support mailbox and independently managed providers require separate review under their applicable schedules. The app's job does not delete messages from the shared Rentari.AI mailbox or change shared infrastructure. Support reviews these copies when responding to a privacy request.
7. Exports, email choices and privacy requests
Your data provides a JSON export of your profile, preferences and supported records from portfolios you own, including available records held in protected export-only storage. Shared portfolios include membership details only. The export excludes file contents, full vendor taxpayer IDs, security credentials and some operational records; it is not a complete response to every possible personal information request. Download attachments separately and save report CSV/PDF exports for your own records. Books already stopped under the previous policy provide available export-only fragments, not reconstructed reports. Contact support for additional records.
Use your profile and permitted editing tools to correct information. In Email preferences, choose optional reminders and product news. Where offered, an email unsubscribe link also changes optional-email preferences. Verification, password recovery and other necessary service messages cannot all be disabled while maintaining the account. Turning off optional email does not delete your account.
Depending on where you live and which laws apply, you may have rights to access, correct, delete or obtain a portable copy of personal information, object to or restrict certain uses, withdraw consent, appeal a request decision or complain to a privacy regulator. Use Privacy requests in your account to submit a request and track status and replies. You can also email [email protected] with "RentariIQ privacy request" in the subject, including if you have no account or cannot sign in. We may verify your identity and an agent's authority before releasing information or acting on a request. We will respond within applicable legal time limits and explain any refusal or limitation. Submit an appeal using the earlier request reference, or reply to support for a review of a decision.
If your information is in a landlord's or another owner's portfolio, identify that relationship so we can direct or coordinate the request appropriately. We do not discriminate against people for exercising applicable privacy rights. Never send passwords, full taxpayer IDs, complete card numbers or bank credentials in a support email.
8. Security
We use encrypted connections, account and portfolio access controls, password hashing, private attachment storage and encrypted storage for vendor taxpayer IDs. The app displays only the last four digits of those taxpayer IDs. Uploaded property photos are re-encoded to remove embedded location metadata. Ordinary document attachments may still contain the information and metadata you upload.
No system can guarantee absolute security. Protect your credentials, review access permissions and report suspected account compromise to support. This policy does not claim a particular security certification or independent audit.
9. Where information is processed
RentariIQ's primary application and database infrastructure is in the United States. Providers may process information in other locations under their applicable arrangements. The protections and rights available can differ by location. Contact us about a location-specific processing requirement before uploading information that is subject to it.
10. Children
RentariIQ accounts are intended for adults. The service is not directed to children. If you believe a child has created an account or provided information directly without appropriate authorization, contact support so we can investigate and address it. Portfolio owners are responsible for limiting personal information entered about members of a tenant's household to what they are entitled to manage.
11. Updates and contact
We will date updates and give notice of material changes in the app or by email before they take effect, obtaining additional consent where required. A policy update does not retroactively authorize a new use of previously collected information that conflicts with earlier commitments.
Contact Rentari.ai LLC about RentariIQ privacy at [email protected]. Describe the request and relevant account or portfolio. We will arrange an appropriate way to verify identity rather than asking you to email a password.