Privacy Policy
Last updated: August 2026
realestatecrm.top compares CRM software written for agents, teams, and brokerages, and it publishes those comparisons in twenty-one language editions. This notice explains the small amount of personal data that passes through the site, on what footing we hold it, and what you can require of us. Read it as the companion to our Terms of Service.
The short version
- An email address only reaches us if you type one in.
- Outbound clicks to vendors are logged for commission purposes, with your IP address reduced to a hash first.
- Nothing here is sold, rented, bartered, or handed to an advertising network.
Sign-up boxes on this site
Two of them exist: the prompt that appears as you move to leave a page, and the opt-in at the end of the matching quiz. Both ask for one thing, an email address. Alongside it the form quietly carries three markers, none of which identify you: the label of the block you submitted from, the language edition you were reading, and, for the quiz, the CRM the answers pointed at. The language marker matters in practice, because it decides which of the twenty-one editions we write back in. The submission lands in a log on our server and is copied to the internal queue the editorial team answers from. The commission calculator further up the page is different in kind: it computes in the browser and posts nothing anywhere, so the deal volumes and team sizes you experiment with stay on your own machine.
Vendor links, and how a commission gets tracked
Every recommendation on this site ends in a link to one of the fourteen real estate CRM vendors we cover. Passing through that link writes one line: the moment of the click, which vendor it was, the campaign tags carried by whatever ad or post brought you here, the referring page, and a truncated one-way hash of your address and browser string. The hash is what lets us tell two clicks apart without ever holding the address that produced them. From the moment the vendor's page opens, the vendor is the one processing your data, under their own policy, not ours. The same caveat applies to the social profiles linked in our footer: opening one takes you onto that network, which measures you by its own rules.
Things we deliberately do not gather
No accounts, no passwords, no billing details, no uploaded documents, no listing data, no client records out of your own CRM. We have not installed an advertising pixel, and we operate no profiling of individual readers. Traffic is read in aggregate, as counts, never as a dossier on one person.
Cookies and what your browser keeps
The site issues no cookies of its own. What it does leave behind sits in local storage: your chosen display currency for the pricing tables, plus a marker recording that you have dismissed the notice bar. Both are removable by clearing site data, and everything on the site still functions once they are gone. Cloudflare, which fronts the domain, may set a short-lived cookie while filtering automated traffic. Browser settings can block that, at the cost of some features behaving oddly.
Retention
Addresses are kept while the correspondence is live and until you ask for removal. Click lines survive as long as a partner programme can still dispute a commission, and then they rotate out. Hashed values are irreversible, so age matters less to them.
Safeguards
Delivery is HTTPS end to end. Identifiers are hashed before they are stored. The logs live on infrastructure the editorial team administers, and only the people who answer readers' mail have reason to open them. These are reasonable precautions rather than a guarantee, since no route across the public internet is immune from interception.
Exercising your rights
Send a note to support@realestatecrm.top, or use the addresses on our contact page, from the address you are asking about. You may request a copy of what is held, require its erasure, or refuse the aggregate traffic measurement, in which case the lines matching you are struck from the log. A specific request gets a specific answer.
If this notice changes
Revisions are published on this page and dated at the top. There is no archived edition to hunt for: whatever appears here is the version in force.