Privacy Policy

Last updated: October 11, 2026

Realatic ("Realatic", "we", "our", or "us"), operated by Technix Infotech LLP, provides a real-estate CRM platform consisting of a web application (realatic.com / app.realatic.com), the Realatic Android app and the Realatic iPhone app (together, the "Service"). This Privacy Policy explains what information we collect, how we use and share it, how we protect it, and your rights.

For users in India, Realatic acts as a Data Fiduciary under the Digital Personal Data Protection Act, 2023 (the "DPDP Act"). By using the Service, you agree to this Privacy Policy.

1. Information We Collect

a. Account information. Name, email, phone number, organization name, RERA registration number.

b. CRM / lead data you enter. Contact names, phone numbers, emails, property preferences, notes, tasks, bookings, payments, documents, and communication history about your leads, together with AI summaries and call transcripts created from that data.

c. Mobile app data.

Android app

  • Call log — we access your device's call log to record each call's outcome (answered, missed) and duration on the relevant lead, and to match an incoming caller's number to a lead. (READ_CALL_LOG)
  • Call recordings — Realatic does not record calls. Where your phone's own dialer creates a recording, the app can read that file and upload it to attach it to a lead, only after you grant access and consent.
  • Phone & call state — to place calls and detect when a call starts/ends. (CALL_PHONE, READ_PHONE_STATE)
  • Audio file access — to read the recordings you choose to attach. (READ_MEDIA_AUDIO / a folder you select)

iPhone app

  • Sign-in session — stored securely in the Keychain on your iPhone.
  • Photos and camera — only the pictures you choose or take, to attach to a property listing or a message.
  • Call state — when you tap Call, the app opens the iPhone's own dialer. The app uses Apple's CallKit call observer, which reports only whether a call started or ended and how long it lasted (never the phone number or any audio), so the app can pre-fill the call outcome and duration on the lead.
  • Call recordings — the iPhone app cannot record calls and does not read your call log. If your organization has attached a call recording to a lead, the app can play it back.
  • The iPhone app does not access your contacts, microphone, location, SMS or advertising identifier, and it contains no advertising or tracking SDKs. Its only third-party SDK is Google's Firebase Cloud Messaging, used for push notifications.

d. Integration data. Facebook/Meta, LinkedIn, and WhatsApp access tokens, page/account info, and lead-form data submitted through those channels; LinkedIn campaign and ad-performance data used for reporting.

e. Usage & device data. App interactions, diagnostics/crash data, device identifiers. Our servers also record technical request details (such as IP address, app version and time) for security and reliability.

f. AI inputs and outputs. When you use AI features (see Section 7), the content sent to the AI provider, and the summaries, replies and transcripts that come back.

2. How We Use Your Information

To provide and improve the Service; manage leads, calls, visits, and bookings; log calls (outcome and duration) to the right lead, identify which lead is calling, and attach recordings you choose; provide AI-assisted features such as summaries, call transcription and WhatsApp AI replies; communicate with leads via WhatsApp/email/SMS; capture leads from Facebook Lead Ads and LinkedIn Lead Gen Forms; show ad campaign performance and ROI reporting for connected LinkedIn accounts; send transactional messages; provide support; and prevent fraud/abuse.

We do not sell your data or use it for third-party advertising.

3. Mobile App Permissions

Android. We request only the following permissions:

  • Call log (READ_CALL_LOG) — for logging call outcomes and caller matching.
  • Phone & call state (CALL_PHONE, READ_PHONE_STATE) — for in-app calling.
  • Audio file access (READ_MEDIA_AUDIO) — for attaching recordings you choose to upload.
  • Notifications — for lead alerts and follow-up reminders.

iPhone. The app asks for access only to:

  • Photos and Camera — only when you choose to attach a picture.
  • Notifications — where push notifications are available on iPhone, we ask for your permission first. Delivery uses Apple's Push Notification service through Google Firebase Cloud Messaging.

We do not request microphone/audio recording, contacts, SMS, or location permissions. You can revoke any permission in Android Settings or iPhone Settings at any time. On Android, before first accessing the call log or uploading a recording, the app shows an in-app notice and asks for your consent.

4. Call Recordings

Realatic does not record calls. Some Android phones record calls via their own built-in dialer; with your explicit consent, the Service can read and upload those recordings to attach to a lead record. The Realatic iPhone app cannot record calls; it can only play back recordings that have been attached to a lead.

You are responsible for obtaining any consent required by law from the other party before recording, storing, or uploading a call. You can delete uploaded recordings at any time from within the app.

5. Facebook / Meta Data

We access your Facebook Page name/ID and Lead Ads form data solely to import leads into your Realatic pipeline. We do not sell, share, or use this data for advertising purposes. You can disconnect your Facebook integration at any time in Settings, which immediately revokes our access.

6. LinkedIn Data

With your consent, we connect to your organization's LinkedIn account to:

  • Import leads — capture Lead Gen Form responses (name, phone, email, company, job title, and any custom form questions) submitted through your LinkedIn ad campaigns, directly into your Realatic pipeline.
  • Report on ad performance — read your campaign, campaign group, and ad account data (spend, impressions, clicks) so we can show you cost-per-lead and ROI inside your Realatic dashboard.
  • Send conversion events — with your consent, we send events back to LinkedIn (e.g., "lead qualified," "booking confirmed") via LinkedIn's Conversions API, so LinkedIn can better optimize your ad delivery. We do not send any personal data beyond what's needed for LinkedIn's conversion matching.

We do not sell, share, or use LinkedIn data for any purpose outside your own organization's sales pipeline, and we never combine or cross-reference data from one organization's LinkedIn account with another organization's data. You can disconnect your LinkedIn integration at any time in Settings, which immediately revokes our access and stops further data collection.

7. AI Features

Some parts of the Service use artificial intelligence (AI). Examples are AI summaries of a lead's history and calls; the WhatsApp AI assistant, which can reply to enquiries (only if your organization turns it on); transcription and summaries of call recordings your organization uploads; and the in-product help assistant.

What is sent. When one of these features runs, the content it needs is sent to an AI or speech-to-text provider, which returns the result. Depending on the feature, that can include a lead's name, notes, messages and activity history, the text of a conversation, or the audio of a call recording your organization uploaded. We do not send anything to an AI provider that has not been entered or uploaded into the Service.

Which providers. Your organization's administrator can choose the AI provider, using the organization's own account with that provider. Supported providers include Anthropic, OpenAI, Google (Gemini), Mistral AI, Groq, xAI, DeepSeek and Alibaba (Qwen), and, for call transcription, Deepgram and Sarvam. Where no provider has been set up, certain features run on AI providers that we operate under our own accounts (currently Anthropic, Google or OpenAI). The Settings screen shows, where we know it, where a provider handles data before it is switched on. The in-product help assistant uses providers that we choose.

Your control. Your administrator decides in Settings whether the WhatsApp AI assistant is on and which AI provider your organization uses. You are responsible for making sure your organization has the right to share its leads' personal data with the AI provider it chooses.

Provider terms and location. Each provider handles content under its own terms and privacy policy, and some providers process data outside India (for example in the USA, the EU, Singapore or mainland China). We do not sell your data to AI providers.

Accuracy. AI output can be wrong or incomplete. Please review it before you rely on it or act on it.

8. How We Share Information

We share your information only with service providers acting on our behalf under data-protection obligations:

  • Supabase — hosting and authentication
  • Vercel — web application hosting
  • AWS SES — transactional email delivery
  • Meta — lead capture and messaging you initiate
  • LinkedIn — lead capture, ad campaign reporting, and conversion events you initiate
  • Razorpay — payment processing
  • AI and speech-to-text providers — only for the AI features described in Section 7
  • Google (Firebase Cloud Messaging) and Apple (Push Notification service) — push notifications to the mobile apps
  • Google Analytics and PostHog — website and web-app analytics (see Section 14)

We do not sell your data. We may disclose information if required by applicable law, regulation, or governmental request.

9. Data Security

Your data is protected with:

  • Encryption in transit (TLS 1.2+) and at rest (AES-256)
  • Access tokens encrypted with AES-256-GCM
  • Row-level security for tenant isolation
  • Access logging and regular security reviews
  • Regular automated backups with point-in-time recovery

10. Data Retention

Your data is retained while your account is active. On account or data deletion, we remove your personal data — including leads, communication history, call logs, call outcomes, AI summaries, call transcripts, and uploaded recordings — within 30 days. Backup copies are purged within 90 days. You can export all your data at any time before deletion.

Data obtained via LinkedIn's or Meta's marketing APIs is deleted within the timeframe required by their respective API terms upon disconnecting the integration, and in any case no later than our standard 30-day deletion window.

AI and speech-to-text providers keep content under their own retention rules (see Section 7).

11. International Transfers and Storage

Our primary database is hosted by Supabase in Mumbai, India. Some of the service providers listed in Section 8, including AI providers, email delivery and analytics providers, may process data outside India. We transfer personal data outside India only as permitted by the DPDP Act and applicable rules.

12. Your Rights

Under applicable Indian data protection laws, including the Digital Personal Data Protection Act, 2023 (DPDP Act), you have the right to:

  • Access — request a copy of the personal data we hold about you.
  • Correct / Complete — request correction of inaccurate or incomplete personal data.
  • Erasure — request deletion of your personal data.
  • Export — download your CRM data at any time in standard formats (CSV, Excel).
  • Withdraw consent — disconnect integrations or revoke permissions at any time.
  • Grievance redressal — raise a complaint with our Grievance Officer or the Data Protection Board of India.
  • Nomination — nominate a person to exercise your rights in the event of death or incapacity.

To exercise these rights or raise a grievance, contact our Grievance Officer at support@realatic.com. We respond within 90 days. If unsatisfied, you may complain to the Data Protection Board of India.

13. Data Deletion

To delete your account and data: in the web or Android app go to Settings → Organization → Delete Account; in the iPhone app open Settings → About → Delete my account, which takes you to our deletion page; or email support@realatic.com with subject "Data Deletion Request" and your registered email and organization name.

We will acknowledge within 48 hours, complete deletion within 30 days, and purge backups within 90 days. See also: realatic.com/data-deletion.

14. Cookies and Tracking Technologies

On our websites and web app we use cookies and similar technologies for:

  • Essential cookies — required for authentication and session management.
  • Analytics cookies — help us understand how visitors use the Service (Google Analytics, PostHog).
  • Preference cookies — remember your settings and preferences.

You can control cookie preferences through your browser settings. Disabling certain cookies may affect Service functionality. The iPhone app does not use cookies or tracking SDKs.

15. Children's Privacy

The Service is not directed to individuals under the age of 18. We do not knowingly collect personal data from children. If we become aware of such collection, we will delete that information promptly.

16. Changes to This Policy

We will notify you of significant changes by updating the "Last updated" date above and, for material changes, by email or in-app notice. Continued use of the Service after changes constitutes acceptance.

17. Contact Us

Realatic, operated by Technix Infotech LLP, Noida, UP, India.