Rentals369 does not sell personal information. We use service providers only as needed to operate, secure, measure, bill, and support the platform.
This Privacy Policy describes how Rentals369 collects, uses, shares, and protects information when you visit our website, create an account, subscribe, contact support, or use the Rentals369 property management platform.
1. Information You Provide
We collect information you provide directly, such as name, email address, phone number, company or portfolio details, account credentials, billing selections, support messages, and the property, unit, tenant, lease, rent, repair, notice, document, photo, vendor, and workflow records you choose to enter.
2. Billing and Payment Information
Subscription checkout and payment processing are handled by Stripe. Rentals369 receives subscription and billing status information needed to activate, manage, reconcile, and support your account. Rentals369 does not store full payment card numbers.
3. Automatically Collected Information
We collect technical and usage information such as device and browser details, pages visited, referral and campaign parameters, session activity, security events, and approximate interaction timing. This helps us operate the service, troubleshoot issues, improve product flows, and measure advertising effectiveness.
4. Cookies, Analytics, and Advertising Measurement
Rentals369 uses essential cookies for security, sessions, checkout, and preferences. We also use analytics and measurement tools, which may include Google Analytics, Google Ads conversion measurement, Ahrefs analytics, and Microsoft Clarity, to understand site usage and whether advertising leads to completed subscriptions. Browser settings and available privacy tools may let you limit or block non-essential cookies and tracking technologies.
5. How We Use Information
We use information to provide and secure Rentals369, create and manage accounts, process subscriptions, provide support, communicate service notices, prevent abuse, improve product workflows, maintain audit and security records, and comply with legal obligations.
6. How We Share Information
We share information with service providers that help us operate Rentals369, such as hosting, payment, analytics, security, email, customer support, and optional integration providers. We may also share information when required by law, to protect rights and safety, or as part of a business transaction such as a merger or acquisition.
7. Optional Integrations
If you connect optional integrations, such as accounting or email services, Rentals369 processes the data needed to provide those connected features. You should connect only services you are authorized to use and review each provider's terms and privacy practices.
8. Data Security
We use administrative, technical, and organizational safeguards designed to protect information, including encrypted transport, access controls, and activity/audit records for sensitive workflows. No online service can guarantee absolute security.
9. Android App and Phone Sign-In Approvals
The Rentals369 Android app provides access to supported portfolio information. When the relevant server capabilities and rollouts are enabled, landlord administrators can create and edit properties; eligible administrators and managers can add or rename units, create tenants, and edit supported tenant profile and lease fields, including custom display name, phone, current rent, last-increase date, move-in date, and lease start and end dates; eligible administrators and managers can also review a tenant rent ledger and record a reviewed manual payment entry; and authorized staff can create repair requests, update repair status, and add repair photos. A last-increase date may be changed but cannot be cleared through the app. Rentals369 records manual payment entries for property-management accounting but does not process or move those funds. These write features are disabled by default and may be enabled globally or for configured pilot users.
The app keeps previously synchronized portfolio information and in-progress property, unit, tenant-create, tenant-edit, repair, and manual-payment work in encrypted local storage so supported information and unfinished work can remain available offline. Offline drafts are never submitted automatically; submission and retry require an explicit user action and network access. Android backup and device-to-device transfer are disabled for the app. Local sign-out removes the protected mobile session and ordinary offline portfolio data from that device.
If the server may have accepted a manual payment but the app has not yet stored the receipt, the app keeps a narrow encrypted reconciliation record containing the exact account and tenant identifiers, draft, request, and duplicate-prevention context. It remains bound to the same user and company, is considered only after that same account is authenticated again, and never submits automatically. It can remain after local or all-device sign-out only when a protected copy has been safely verified; otherwise a voluntary sign-out or authentication transition stops so the app does not discard uncertain recovery information.
If receipt cleanup fails or a security event requires local data removal, the app disables the entire local payment-recovery set, blocks its restoration or submission, and attempts to remove its protected recovery material. This can also affect other unresolved device handoffs. The safety step does not contact or change the backend and, while the current session remains healthy, keeps the local receipt available. The app directs you to the canonical ledger or support before entering another payment. If the app cannot safely prove that recovery has been disabled, it requires Android Clear storage and support. Clear storage or uninstall removes local recovery state but does not remove canonical server records.
Production enablement and approval of the final Google Play Data Safety declaration remain separate release-owner and privacy-reviewer tasks. This policy does not by itself approve or establish production release readiness.
If you choose to enroll a phone for sign-in approvals, Rentals369 processes the approval-device name, app and platform version, a device-generated public key, Android key-attestation certificate metadata, an approval-device identifier, and a Firebase Cloud Messaging registration token. We use this information to verify the app and device, deliver a generic notification that a sign-in request is available, validate your signed approve or deny response, prevent replay, investigate security events, and let you revoke enrolled phones. Notification payloads do not include your account details, the number-match choices, browser or network details, cryptographic signing material, or an approve action. You may deny notification permission and use the authenticated in-app approval inbox instead.
Local sign-out does not by itself remove an enrolled approval phone from the server. You can remove an enrolled phone from Security settings or use all-device sign-out. Rentals369 automatically clears stale notification tokens after 35 days, revokes approval phones after 90 days without activity, and retains expired enrollment, delivery, challenge, and revoked-device security records for the limited periods needed to operate and protect the feature. Uninstalling the app removes its local data but may not immediately delete server-side account or security records.
10. Data Retention
We keep information for as long as needed to provide the service, support your account, comply with legal obligations, resolve disputes, maintain security, and enforce agreements. You may request account or privacy help at contact@rentals369.com.
11. Your Choices
You may update account information in the product where available, contact us for support, unsubscribe from non-essential emails where an unsubscribe option is provided, and manage cookies through your browser or device settings. Privacy rights can vary by location.
12. Contact
For privacy, support, or account questions, email contact@rentals369.com.