Skip to content
PIProperty Intelligence
FeaturesHow It WorksPricingFAQContactLog InGet Started

Public policy

Privacy Policy

This policy explains how Property Intelligence collects, uses, shares, and protects information when you use our web and mobile applications.

Last updatedAugust 9, 2026

Contact

Questions or privacy requests can be sent to support@propertyintelligence.app.

TermsDelete account

1. Introduction

  • Property Intelligence is a subscription-based property intelligence application that helps users connect supported property-message sources, process property messages and listings, search and review structured property information, and manage subscription access.
  • This policy explains what information we collect, how we use it, and the choices available to users of our web and mobile applications.

2. Information we collect

  • Account and contact information: we collect email addresses for registration, login, email verification, OTP/security verification, account recovery, service communications, account administration, subscription administration, and security or fraud prevention. We may collect a first name, last name, display name, username, account name, or Google account name where you provide it or use Google sign-in. A name is used for account creation, account management, identifying you within your account, customer communication, and service administration.
  • Phone numbers: we do not use a phone number as the standard email/password login field. We may collect phone-number data when you connect WhatsApp or when phone numbers appear in imported property messages, sender details, WhatsApp account identity, contacts, or extracted property-content fields. Phone numbers may be used to identify connected WhatsApp accounts, display contact or sender information, extract property-contact details, organize imported messages, detect duplicates, support account security, and troubleshoot source connections.
  • Connected source and message data: Property Intelligence may receive and process messages from sources that you connect to the service. This may include message text, sender information, recipient or group information, timestamps, and other metadata associated with those messages.
  • Property and user content: users may submit, import, store, or process property advertisements, property listing descriptions, requirements, notes, structured property information, imported text, review decisions, discarded-message records, duplicate records, source names, group names, and related metadata.
  • Identifiers: we create or store internal identifiers such as user/account IDs, workspace IDs, session IDs, subscription/customer identifiers, RevenueCat app user IDs, and source or message identifiers. These are used for authentication, account management, subscription entitlement, authorization, security, and associating stored data with the correct user.
  • Device and session information: the mobile app creates an installation identifier stored on the device. The backend stores a hashed version of that identifier with platform, app version, session status, refresh-token metadata, and push-token information where security notifications are enabled. We use this information to maintain authorized sessions, enforce device/session restrictions, protect accounts, prevent unauthorized access, prevent fraud or abuse, and troubleshoot access problems. We do not state that we collect Apple's advertising identifier unless that is separately implemented.
  • Subscription and purchase information: we may receive and store subscription-related information such as the product or subscription purchased, subscription status, entitlement status, transaction identifiers, original transaction identifiers where provided, purchase date, renewal status, expiration date, cancellation status, billing issue status, store, environment, and related platform or provider metadata.
  • Diagnostic and technical information: we may collect crash reports, application errors, stack traces, application version, operating-system version, device type or model, timestamps, request identifiers, request/error metadata, performance measurements, network/error information, and operational logs to diagnose crashes, identify application errors, monitor reliability, analyze performance problems, troubleshoot failed requests, maintain security, and improve stability.

3. How we use information

  • To create and administer accounts, verify email addresses, process OTP/security checks, recover accounts, authenticate sessions, and enforce security controls.
  • To provide property intelligence features, process imports, extract property information, organize listings and requirements, identify duplicates, support search and review workflows, and display account or subscription status.
  • To classify property-message content, including property type, society/location, block, plot number, size, price, availability/status, contact details, duplicate status, and review requirements.
  • To send service communications such as verification codes, password recovery messages, account deletion notices, account restoration notices, subscription status messages, support replies, and important security updates.
  • To operate, debug, protect, and improve the service using security events, redacted logs, operational metrics, and diagnostic information.

4. Connected sources and message processing

  • Property Intelligence processes only the sources, accounts, groups, or content that you connect, select, import, or authorize through the product. We do not claim to read every message on your device.
  • For connected WhatsApp sources, the service may process selected group/account information, message text, sender information, group/source names, timestamps, and related metadata so that property information can be extracted, organized, reviewed, searched, and displayed.
  • You can disconnect sources or disable processing where supported. Disconnection revokes active access where supported and stops future imports from that source, but third-party services may continue to keep their own records under their separate terms and privacy policies.
  • Current repository code uses in-service property extraction logic for message processing. We did not identify a production integration that sends message content to an external AI/model provider.

5. Purchases and subscription information

  • Purchases made through the iOS application are processed by Apple. Property Intelligence does not receive or store your full payment card number, bank account credentials, CVV, or Apple payment credentials when payment is processed by Apple.
  • Property Intelligence uses RevenueCat to manage iOS subscription purchases, purchase validation, entitlement status, renewals, cancellations, billing issues, and subscription synchronization.
  • RevenueCat and Property Intelligence may receive purchase information such as product/subscription purchased, subscription status, entitlement status, transaction identifiers, original transaction identifiers where applicable, purchase date, renewal status, expiration date, cancellation status, billing status where provided by the platform, store, and environment.
  • Some web or non-iOS checkout flows may use a hosted payment provider such as PayFast. In those flows, the payment provider collects payment details on its hosted checkout page, while Property Intelligence may receive payment status, checkout status, transaction identifiers, amount, currency, and subscription entitlement results.
  • Deleting a Property Intelligence account and cancelling an Apple subscription are separate actions unless a platform or provider expressly supports otherwise. You should manage Apple subscriptions through Apple App Store subscription settings.

6. Service providers and third parties

  • Apple processes iOS in-app purchases and subscription management through the App Store.
  • RevenueCat assists with subscription management, purchase validation, entitlement status, and subscription webhooks.
  • Email or SMTP providers may process email addresses and message content needed to deliver verification codes, password recovery messages, account deletion notices, and account restoration notices.
  • Hosting, cloud infrastructure, database, networking, and security providers may process information needed to host the web application, mobile APIs, backend services, databases, logs, and operational systems.
  • Expo push notification infrastructure may be used to deliver security or account notifications when push tokens are registered.
  • WhatsApp and related source-integration infrastructure are involved when you connect or authorize WhatsApp-based sources. WhatsApp and other third-party source services process information under their own terms and privacy policies.
  • PayFast may process web checkout payments where that payment flow is enabled outside Apple in-app purchase.
  • We do not sell personal information and do not use information collected through Property Intelligence for cross-app advertising tracking.

7. Data sharing

  • We share information with service providers only as needed to operate, secure, support, bill, and improve Property Intelligence.
  • We may disclose information if required by law, regulation, legal process, or a valid governmental request.
  • We may disclose information when reasonably necessary to protect users, investigate fraud or abuse, enforce our terms, secure the service, or complete a business transfer subject to appropriate safeguards.
  • We do not sell personal information.

8. Data retention

  • We keep account information, connected-source records, imported messages, property records, contacts, subscription records, audit events, diagnostics, and operational records for as long as needed to provide the service, maintain security, resolve disputes, meet legal or accounting obligations, and enforce our agreements.
  • Local mobile recent-search entries are stored on the device in secure storage and can be cleared in the app. The backend search endpoints use search/filter parameters to return results; we did not identify a dedicated backend search-history table.
  • Operational logs, backups, audit records, billing records, and security records may be retained for a period appropriate to their purpose, including legal, accounting, fraud-prevention, troubleshooting, and security needs.
  • When you request account deletion, normal product access is paused and user-owned operational data is scheduled for permanent purge after the recovery window, currently 90 days.

9. Data security

  • We use reasonable administrative, technical, and organizational safeguards designed to protect information.
  • Security controls include password hashing, token hashing, encrypted storage for selected sensitive fields, secure session storage, HTTP-only cookies in the web app where applicable, request IDs, log redaction, account/session revocation, and device/session controls.
  • No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

10. User choices and rights

  • You can update profile information, disconnect supported sources, refresh subscription status, restore purchases, and manage subscriptions through the relevant app store or payment provider where supported.
  • You can contact support to request access, correction, deletion, or other privacy help where applicable.
  • You can manage Apple subscriptions through your Apple account or App Store subscription settings.
  • Some records may be retained when necessary for compliance, accounting, security, fraud prevention, dispute resolution, or lawful recordkeeping.

11. Account deletion

  • You can request account deletion from the app or through the public account-deletion page linked from this policy.
  • The deletion workflow may require identity verification, such as email OTP verification or password reauthentication.
  • After a deletion request, account access is paused, sessions and devices are revoked, connected source access is revoked where supported, and permanent purge is scheduled after the current 90-day recovery window.
  • Permanent purge is designed to remove or anonymize account data and user-owned operational data such as connected sources, imported property/message data, contacts, dictionary entries, review tasks, requirements, sessions, devices, and related records, subject to limited legal, accounting, security, fraud-prevention, diagnostic, backup, and audit exceptions.
  • Deleting your Property Intelligence account does not necessarily cancel an Apple subscription. Manage Apple subscriptions through Apple.

12. Children's privacy

  • Property Intelligence is intended for property professionals and is not directed to children. If you believe a child has provided personal information to us, contact us so we can review and take appropriate action.

13. International data processing

  • Property Intelligence is initially intended for users in Pakistan, Saudi Arabia, the United Arab Emirates, and Oman.
  • Information may be processed and stored in countries where we or our service providers operate. Those countries may have data protection rules different from those in your location.

14. Changes to this privacy policy

  • We may update this policy as the service changes. If changes are material, we will take reasonable steps to notify users through the app, by email, or by another appropriate channel.

15. Contact us

  • Questions or privacy requests can be sent to support@propertyintelligence.app.
PIProperty Intelligence

Property Intelligence is a product of SkyOps Tech.

Product

FeaturesHow It WorksPricingLog In

Support

FAQContactDelete Account

Legal

TermsPrivacy
© 2026 Property Intelligence.Private real-estate message intelligence and CRM.