Privacy Policy

This Privacy Policy applies to PG Owners, Managers, Tenants, invited users, users who access the RentKnock app or website, users who enable payment verification features, and users who contact RentKnock support.

RentKnock collects information needed to provide PG/rent management, tenant management, invoice generation, rent tracking, payment status tracking, reminders, receipts, reports, and smart rent payment verification.

• Account Information: name, email address, phone number, profile photo where available, Google/Firebase user ID, login provider information, account status, role, permissions, and last active workspace.
• Property Information: property name, property type, address, city, locality, state, pincode, rent settings, due date, collection window, setup progress, floors, rooms, beds, property status, and trial or subscription status.
• Tenant Information: tenant name, phone number, email, assigned room or bed, move-in date, rent start date, monthly rent, deposit, tenant status, invite status, tenancy notes, move-out information, and settlement details.
• Invoice and Ledger Information: invoice number, invoice type, billing cycle, rent period, due date, payable amount, paid amount, pending amount, UPI note/code, invoice status, payment attempt records, tenant claim information, owner review information, and verification status.

RentKnock may store information required to create and track UPI rent payment flows, such as Owner UPI ID, receiver name, UPI account label, preferred UPI app, invoice amount, UPI note/code, UPI intent URI, payment attempt status, tenant claim reference, and owner review decision.

RentKnock does not collect or store UPI PIN, bank login credentials, debit card PIN, net banking password, bank OTP for payment approval, full bank account password, card CVV, or full card details. Tenant rent payment is completed inside the tenant’s selected UPI app or bank app.

Tenant rent payments are made directly from the Tenant’s UPI app or bank account to the Owner’s UPI ID or bank-linked UPI account. RentKnock does not hold, settle, escrow, reverse, or refund tenant rent payments.

RentKnock may offer smart rent payment verification using Android Notification Access. This feature is used only on the Owner’s selected verification device and only after the Owner enables Notification Access from Android settings.

RentKnock uses Notification Access to detect supported UPI app payment notifications received on the selected Owner device and match them with RentKnock rent invoices. This helps Owners verify tenant rent payments faster and reduces manual payment review.

When Notification Access is enabled, RentKnock may process limited UPI payment notification information from supported UPI apps:

• UPI app package name
• UPI app name
• Notification timestamp
• Notification key or reference generated by Android
• Payment amount detected from the notification
• Possible transaction reference where available

Supported UPI apps may include PhonePe, Google Pay, Paytm, BHIM, and supported business UPI apps.

RentKnock does not use Notification Access to read personal chats, social media messages, emails, photos, files, contacts, passwords, UPI PINs, bank OTPs, banking passwords, or unrelated private content.

RentKnock attempts to process only supported UPI payment-related notifications for rent verification. Notification Access can be disabled anytime from Android settings. If Notification Access is disabled, automatic rent payment verification may stop and payments may require manual Owner review.

Notification Access is used for Owner-side rent payment verification only. Tenants are not required to enable Notification Access to pay rent or use their RentKnock tenant account.

If the Owner’s selected verification device receives a supported UPI payment received notification but the internet connection is unavailable or RentKnock servers cannot be reached, RentKnock may temporarily save limited structured payment verification metadata on that device and retry sending it when internet is available.

The local retry queue is used only to reduce missed rent verification caused by temporary network failure after a supported UPI payment notification was already received on the Owner’s selected verification device.

The retry queue uses Android app-private storage, also known as app sandbox storage. It is not a general user-visible file, and other normal apps cannot directly access it through standard Android app isolation.

The retry queue is designed to store only limited structured metadata, such as payment amount, UPI app package name, UPI app name, notification timestamp, Android notification reference, Owner verification device ID, transaction reference where available, payment direction, and parser version.

RentKnock does not store full raw notification title or full raw notification text in the local retry queue. The retry queue is cleared after successful sync, logout, disabling automatic verification, device change, or automatic cleanup. Very old or repeatedly failed queued events may be removed automatically.

RentKnock may collect limited device and verification status information from the Owner’s selected verification device, including device platform, device name if provided, Owner device ID, Notification Access status, supported UPI app notification status, last seen time, internet availability status, and secure device-token usage time.

This information is used to help the Owner understand whether payment verification is ready, delayed, or requires setup. Tenants do not see private Owner device details.

RentKnock may issue a device authentication token for the Owner’s selected verification device. This token allows the device to securely send UPI notification verification events to RentKnock servers.

RentKnock stores only a secure hash of the device token on the backend. The raw token is returned once and saved on the user’s device. The token may be rotated by the Owner. This token is separate from the user’s Firebase or Google login token.

We may collect device type, operating system version, app version, IP address, crash logs, error logs, API request logs, authentication logs, security logs, feature usage events, backend status logs, and time/date of actions. This helps us secure, debug, improve, and maintain RentKnock.

If RentKnock offers paid subscriptions, we may collect subscription data such as plan type, trial status, subscription status, billing period, payment provider reference, purchase token or order ID where applicable, renewal status, cancellation status, and feature access status.

Payments for RentKnock subscriptions inside the Google Play distributed app may be processed through Google Play Billing. RentKnock does not store full card numbers, UPI PINs, bank passwords, card CVV, or payment credentials used by Google Play.

Owner RentKnock subscription payments are separate from tenant rent payments. Tenant rent payments go directly to the Owner’s UPI ID or bank-linked UPI account.

• Create and manage user accounts.
• Authenticate users.
• Create and manage PGs/properties.
• Add and manage tenants, rooms, beds, and rent settings.
• Generate invoices and tenant ledgers.
• Start UPI payment flows.
• Track tenant payment status.
• Verify rent payments using supported UPI notifications.
• Show payment status to Owners, Managers, and Tenants based on role.
• Enable Owner review of uncertain payments.
• Maintain audit logs and payment verification records.
• Prevent fraud, duplicate verification, and misuse.
• Debug issues and improve app performance.
• Provide customer support.
• Manage subscriptions, trial status, and feature access.
• Comply with legal, security, and operational requirements.

We do not sell personal information. We may share limited information with trusted service providers for authentication, cloud hosting, database hosting, app distribution, payment processing, crash reporting, messaging, notifications, analytics where enabled, and customer support.

Information may also be visible within a property depending on user role and permissions. Owners may see tenant records and payment status. Managers may see information based on permissions granted by the Owner. Tenants may see their own invoice and ledger details.

We may disclose information if required to comply with law, respond to legal requests, prevent fraud, investigate misuse, enforce Terms, or protect rights, safety, and security.

We use reasonable technical and organizational measures to protect data, including authentication controls, role-based access, permission checks, secure token handling, hashed device tokens, HTTPS for API communication, server-side validation, audit logs, and limited access to backend systems. However, no system is 100% secure.

We retain data for as long as needed to provide RentKnock services, maintain property records, support dispute resolution, meet legal, accounting, security, or operational needs, prevent fraud, and comply with applicable obligations.

Some records, such as invoices, audit logs, subscription records, and payment verification records, may be retained where required for operational, legal, security, accounting, or fraud-prevention purposes.

• Update account information where supported.
• Switch property/workspace.
• Request account deletion.
• Disable Notification Access from Android settings.
• Log out.
• Contact support for data questions.
• Request correction or deletion where applicable.

Tenant data may be entered by an Owner or Manager. If you are a Tenant and believe your data was added incorrectly or without proper authorization, contact your Owner/Manager or RentKnock support. Some tenancy, invoice, ledger, and payment records may need to be retained for dispute, audit, security, accounting, or legal reasons.

RentKnock is intended for PG owners, managers, and tenants who are legally capable of entering into rental, property management, or payment-related arrangements. RentKnock is not designed for children and is not targeted to children.

• Internet: used to connect to RentKnock servers.
• Notification Access: used only on the Owner’s selected verification device to read supported UPI payment notifications for rent payment verification.
• Post Notifications: used to show important app alerts, payment updates, rent reminders, and system notifications.
• Network State: used to detect internet availability for retrying payment verification events and showing verification readiness.

UPI apps and banks may approve, reject, delay, block, or fail transactions based on their own policies and risk systems. RentKnock does not control UPI app approval, bank settlement, payment decline reasons, chargebacks, or transaction reversal.

RentKnock does not ask users to enter UPI PIN, bank password, debit card PIN, card CVV, or bank OTP into RentKnock. UPI PIN entry happens only inside the selected UPI app. Users should never share UPI PIN, OTP, password, or banking credentials with anyone, including RentKnock support.

Users may request deletion of their RentKnock account and eligible personal data. Some records may be retained where required for legal, accounting, security, payment verification, fraud prevention, audit, operational continuity, or dispute-resolution purposes.

Account deletion request page: RentKnock Account Deletion

We may update this Privacy Policy from time to time. If we make material changes, we may notify users through the app, website, email, or other reasonable means. Continued use of RentKnock after changes means you accept the updated Privacy Policy.

RentKnock Support

Operator: Dheeraj Patil

Location: India

Email: medheerajput@gmail.com