Privacy policy

Plain English, because the people affected by it are homebuyers and small sales teams, not lawyers. If anything here is unclear, write to us and we will explain it.

Draft prepared for review — last updated 21 September 2026.

This document has been written by OpenDesigns and has not yet been reviewed by a lawyer. It describes how we intend to handle data and is published so that it can be checked. It is not legal advice. Questions, corrections and objections go to hello@opendesigns.in.

Who we are

OpenCRM is a customer-relationship system for Indian real-estate developers, built and operated by OpenDesigns. Each customer — we call them a workspace or a tenant — gets their own subdomain and their data is kept separate from every other workspace at the database level.

You can reach us at hello@opendesigns.in about anything on this page.

Whose data is whose

Most of the personal information inside OpenCRM is not ours and is not about our own customers. It is about their customers — the people who enquire about a flat. Two different relationships sit on this page, and they have different answers:

The developer using OpenCRM decides what is collected from their enquirers, why, and for how long. They are responsible for having a lawful basis and for telling their enquirers. We hold and process it on their instructions.
OpenDesigns decides how the accounts of the developer’s own staff work — sign-in, roles, support. That part is ours.

In practice this means: if you enquired about a property and want your details removed, the developer you contacted is the fastest route. Write to us too and we will pass it on and help them act on it.

What we collect

Three distinct piles.

1. CRM data, held for a workspace

Leads — name, mobile number, email, the project or location they asked about, budget, property type, notes your team writes, and the history of calls, visits and follow-ups against them.
Business records — projects, towers, units, site visits, bookings, payment schedules and receipts, channel partners and targets.
Chat transcripts from the website widget, including whatever the visitor typed.

2. Lead data arriving from connected sources

Website forms and the WordPress plugin — whatever fields the developer mapped onto lead fields.
Meta Lead Ads — the answers a person gave on a Facebook or Instagram lead form, and the identifiers of the ad, ad set and campaign it came from.
WhatsApp — the sender’s WhatsApp number, their first message, and, where Meta provides it, the click-to-WhatsApp ad they tapped.
Google Ads lead forms and portal feeds, where configured.

3. Account and technical data

Staff accounts — name, work email, mobile, role, and whether the account is active.
A sign-in cookie. We set one cookie to keep you signed in. There is no advertising cookie, no third-party analytics tag, and no cross-site tracking on this site or in the app.
Server logs — IP address, request path and timestamp, kept for security and debugging.

We do not ask for and do not want government identity numbers, card numbers or bank account numbers. Do not paste them into a notes field.

What we use it for

Running the service the workspace pays for — nothing on this list is a surprise use.
Delivering a lead to the right agent, and notifying them.
Preventing duplicate leads from the same mobile number.
Producing the workspace’s own reports about its own data.
Keeping the service secure: rate limiting, abuse prevention, audit of who changed what.
Support, when someone in the workspace asks us for help.
Billing the workspace.

We do not sell personal information, we do not share it between workspaces, we do not use one customer’s leads to benefit another, and we do not use lead data to train machine-learning models of our own. Where an AI feature is switched on for a workspace, the specific text needed for that feature is sent to the AI provider to produce the answer and is not used by us for anything else.

Meta and WhatsApp data

When a workspace connects a Facebook Page or a WhatsApp Business number, we request only the access needed to receive their own leads, and we take only:

the answers on their own lead forms, and the questions those forms ask;
the name and id of the Page the forms belong to;
the identifiers and names of the ad, ad set and campaign a lead came from, so the developer can see which ad works;
for WhatsApp, the sender’s number and first message, and the click-to-WhatsApp referral details when Meta sends them.

We do not read a Page’s inbox, its followers, its posts, or anybody’s Facebook profile. We do not use Meta data for advertising, and we never pass it to another workspace or to a third party.

When a workspace disconnects a Page or a number, the stored access token is deleted immediately, no further data is requested from Meta, and the form definitions and connection records are removed. Leads already captured stay in the workspace — they are the developer’s own business record — and are deleted on request as described below.

How long we keep it

Workspace data is kept for as long as the workspace is active, because it is the developer’s live business record.
On cancellation we hand over a full export and delete the workspace’s data on written confirmation from them.
Individual records are deleted whenever the workspace deletes them, or when we are asked to delete them under the next section.
Server logs and backups roll over on a short cycle. A record deleted from the live system can persist in a backup until that backup expires.

We do not yet publish a fixed number of days for each of these. That is on the list to pin down, and this page will say the number once it is set rather than imply a policy we are not running.

How it is protected

Every workspace’s data is separated at the database level and checked on every request.
Access tokens and API keys for connected services are encrypted at rest and are never shown back to anyone, including us.
Traffic is served over HTTPS.
Staff access is limited by role, and a workspace can mask customer phone numbers from its own sales role.
Inbound webhooks from Meta are signature-verified, so a third party cannot inject fake leads.

No system is perfectly secure. If we become aware of a breach affecting a workspace’s data, we will tell that workspace what happened, what was affected, and what we are doing about it.

Your choices

If you are an enquirer whose details are in a developer’s workspace, you can ask to see what is held about you, to have it corrected, or to have it deleted. Ask the developer you contacted, or write to us and we will route it.

If you are a workspace, you own your data. Export leads, units, bookings and collections to CSV at any time, and ask us for a full export whenever you want one.

Asking us to delete data

Write to hello@opendesigns.in with “Data deletion request” in the subject line, and tell us:

the phone number or email address the record is under;
the developer or project you enquired about, if you know it;
whether you want everything deleted, or only a particular connected source.

We will acknowledge within 3 business days and complete or refuse the request within 30 days, telling you which and why. If the data belongs to a developer’s workspace we will act on their instruction and tell you who they are so you can go to them directly.

To remove the Meta connection itself, a workspace admin can press Disconnect on the Meta or WhatsApp card in Settings → Integrations at any time, without contacting us. That deletes the stored token immediately.

Children

OpenCRM is a business tool. It is not directed at children and we do not knowingly collect information about anyone under 18. If you believe a child’s details have ended up in a workspace, tell us and we will get them removed.

Changes to this policy

When this page changes we update the date at the top and the bottom. If a change materially affects how a workspace’s data is handled, we will tell that workspace directly rather than relying on them noticing a date.

Contact

OpenDesigns — hello@opendesigns.in. We reply within one business day. For anything on this page, that address reaches a person, not a ticket queue.

Last updated: 21 September 2026 · Draft prepared for review. Not legal advice. Send corrections to hello@opendesigns.in.