Legal
Privacy Policy
Last updated: 22 September 2026
This policy describes how RELMS (“we”, “us”) processes personal information when real-estate companies use our CRM, including when we receive data from Meta platforms (Facebook, Instagram Lead Ads, and WhatsApp Cloud API) through our Meta app and webhooks.
1. Who this policy covers
RELMS is a B2B product. We process two kinds of information:
- Customer accounts: staff of real-estate companies who sign in to RELMS (admins, managers, salespeople).
- Leads and prospects: people who submit a Meta Lead Ad form, message a connected WhatsApp Business number, or are entered into the CRM by a company using RELMS.
Each company (tenant) is the controller of its own lead and customer data. RELMS processes that data on the company’s behalf to operate the CRM.
2. Information we collect
From Meta Lead Ads and Pages
When a company connects a Facebook Page and a lead submits an Instant Form, Meta may send us, via webhook and Graph API, fields the company requested on that form. This typically includes:
- Name, phone number, and email
- Form answers such as budget, location, property type, bedrooms, and buying timeline
- Campaign, ad, form, and lead identifiers needed to ingest the enquiry once
From WhatsApp
When a company connects WhatsApp Cloud API, we receive and send messages needed to follow up on enquiries. That can include phone number, message content, delivery status, and related WhatsApp identifiers (for example phone number ID).
From RELMS users
Account name, email, optional phone, role, and authentication session data. We do not ask users to type Facebook passwords into RELMS; Page and WhatsApp access is granted through Meta’s OAuth or tokens the company stores in Settings.
Automatically
Security and operational logs (for example request time, error codes, and webhook routing). We do not use advertising cookies on this privacy page.
3. How we use the information
We use personal data only to:
- Create and update leads in the company’s CRM after a Meta or WhatsApp event
- Send and receive WhatsApp messages the company authorizes (including automated follow-ups)
- Qualify and score enquiries, including with AI analysis of conversation content
- Assign leads, notify sales teams, and track site visits through booking
- Honor opt-out requests (for example a lead sending STOP) and keep the product secure
We do not sell lead data. We do not use Meta or WhatsApp data to build advertising audiences for our own marketing, and we do not share it with other tenants.
4. Meta Platform data
Data received from Meta is used solely to provide the RELMS features the connecting company enabled: lead capture, messaging, and CRM workflow. We follow Meta Platform Terms, including limits on using Platform data outside those product functions. Access tokens and page identifiers are stored so we can fetch lead details and send WhatsApp messages on that company’s behalf. We do not transfer that data to unrelated third parties except processors needed to run the service (hosting, database, and AI providers used for qualification).
5. Sharing
We share data only:
- With the real-estate company that owns the lead or user account
- With infrastructure and AI vendors that process data under contract to operate RELMS
- When required by law, or to protect the security of the service
6. Retention
Lead, conversation, and account records are kept for as long as the company uses RELMS or as required for legitimate business, legal, or security purposes. When a company account is deleted, associated tenant data is removed from our primary database (including cascaded lead and message records). Backups expire on a rolling schedule.
7. Access, correction, and deletion
Prospects should contact the real-estate company they enquired with, or email us and we will route the request to the relevant company. Company admins can update or delete records in RELMS. To request deletion of data obtained through our Meta app, email privacy@relms.dev with enough detail to identify the lead or Facebook user. We will delete or instruct deletion of associated CRM records we control, unless we must retain them for legal reasons.
8. Security
Access to the CRM requires authentication. Webhooks are verified with Meta’s hub challenge and tokens. Session cookies are used only to keep staff signed in. We apply standard transport and application controls (HTTPS in production, access control by tenant).
9. Children
RELMS is not directed at children. We do not knowingly collect personal information from children through Meta Lead Ads or WhatsApp.
10. Contact
Privacy questions, Meta data-use questions, and deletion requests: privacy@relms.dev.
11. Changes
We may update this policy when the product or legal requirements change. The “Last updated” date at the top will change. Continued use of RELMS after an update means the revised policy applies.