Privacy

Privacy policy

SiteCurb builds websites for real estate agents. This page says what we store about agents, what we store about the people who contact them, and what we never do with either.

Updated October 2026

Who we are

SiteCurb (sitecurb.com) is the website builder behind every site on sitecurb.com and the custom domains attached to it. Questions about this policy or your data go to john@sitecurb.com.

This policy covers two groups of people:

  • Agents, who have a SiteCurb account and a website built with it.
  • Visitors to those websites, including anyone who sends an agent a message through one.

What we store about agents

  • Your account: your email address and password. The password is stored hashed by our sign-in provider, never in plain text.
  • Your website: everything you enter to build it: name, title, brokerage, phone, public email, licence number, bio, headshot, logo, service areas, social links, testimonials, colours, and your listings and their photos. Most of this is published on your website on purpose.
  • Billing: payments are handled by Stripe. We keep your Stripe customer and subscription IDs and your plan status. Your card details go to Stripe and never reach us.
  • Your domain, if you attach one.
  • Technical logs (IP address, browser, time of request), kept by our hosting providers for security and fixing faults.

What we store about visitors

Agent websites have a contact form and a “get new listings first” sign-up. When a visitor uses one, we store the name, email, phone and message they typed, and which listing they were looking at. We deliver it to that agent only: by email, and in the agent’s dashboard.

That inquiry belongs to the agent. The agent decides what to do with it, and we process it on the agent’s behalf. We never sell it, rent it, share it with other agents, add it to any list, or email the visitor ourselves. No other agent can read it: each agent’s inquiries are locked to their account at the database level.

Agent websites carry no analytics, advertising or tracking scripts, and set no cookies for visitors.

How we use it

We use this information to run your website and account, take payment, send the emails the service depends on (confirming your sign-up, password resets, and new-inquiry notifications), keep the service secure, and answer you when you write to us. We don’t sell personal information, and we don’t use it for advertising.

Who processes it for us

ProviderWhat for
SupabaseDatabase, sign-in and photo storage (United States)
VercelHosting for sitecurb.com and every agent website
StripeSubscription payments
ResendSending account emails and new-inquiry notifications

If you connect another tool to SiteCurb (see below), we send your inquiries to that tool because you asked us to. We send them only to the account you connected.

Connected tools

SiteCurb Leads for Google Sheets

The add-on writes your SiteCurb inquiries into the spreadsheet you open it in, and only that spreadsheet. It can’t open your other files, and it never sends the contents of your sheet to SiteCurb.

From your Google account it uses only your email address, taken from Google’s sign-in token. We use that address to match you to your SiteCurb account, so you never type a password into the add-on. We keep the Google address you allowed and the time of your last sync, and nothing else.

SiteCurb’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We don’t use Google user data for advertising, we don’t sell it, and people don’t read it except to fix a problem you’ve asked us to look at.

To stop, remove the add-on from Google Sheets (Extensions → Add-ons → Manage add-ons). Then remove the Google address under Dashboard → Integrations.

SiteCurb for Canva

When you publish a design to SiteCurb from Canva, Canva sends us the exported image. We store it on your website as the listing photo, headshot or logo you chose, and from then on it’s public on your website like any photo you upload yourself. Canva also sends a signed token so we can confirm the request really came from Canva.

We can’t see your other designs or your Canva account. Disconnect under Dashboard → Integrations, or in Canva, and the connection stops working at once. Photos you’ve already published stay on your site until you remove them.

SiteCurb for Outlook

The Outlook add-in reads one thing from your mailbox: the email address of the other person in the email you have open. It sends that address to SiteCurb to look up that person’s inquiries from your website, and shows them beside the email. It doesn’t read, copy or store the email itself, your other mail, your contacts or your calendar, and it doesn’t use Microsoft sign-in.

When you connect it, SiteCurb gives that Outlook a random key, kept in the add-in on that device. We keep only a fingerprint (hash) of the key, the kind of Outlook it is, and when it was last used. When you press “Mark as contacted”, we record the time on that inquiry. Disconnect in the add-in or under Dashboard → Integrations and the key stops working at once.

Pipedrive

When you connect Pipedrive, Pipedrive gives SiteCurb an access token for your account, which we store encrypted. We use it for one thing: each time a new inquiry arrives on your website, we look up the person by the email address (or phone) they gave, add them if they aren’t in your Pipedrive yet, and add a lead with their message, the listing, and your website address as a note.

The permissions we ask for are people and organizations (to find or add that person) and leads. We don’t read your deals, activities, email or anything else, apart from your Pipedrive user and company name, which the Integrations page shows so you can see which account is connected. Disconnect under Dashboard → Integrations and we revoke the access and delete the token at once; uninstalling the app in Pipedrive does the same.

Zoho CRM

When you connect Zoho CRM, Zoho gives SiteCurb an access token for your account, which we store encrypted, together with the Zoho data center your account is in. We use it for one thing: each time a new inquiry arrives on your website, we look for a lead with the email address (or phone) the person gave, add them as a lead if there isn’t one, and add a note with their message, the listing, and your website address.

The permissions we ask for are to find and add leads, to add notes, and to read your organization’s name, which the Integrations page shows so you can see which account is connected. We don’t read your contacts, deals, email or anything else. Disconnect under Dashboard → Integrations and we revoke the access and delete the token at once. Removing SiteCurb from the connected apps in your Zoho account also ends our access.

ActiveCampaign

When you connect ActiveCampaign, we store your account’s API URL and API key, encrypted. We use them for one thing: each time a new inquiry arrives on your website, we add or update that person as a contact in your ActiveCampaign (by their email address), tag them “SiteCurb website inquiry”, and add a note with their message, the listing, and your website address.

We don’t read your contacts, lists, campaigns or anything else. The only other calls are one check, when you connect, that the key works (it returns your user name, which the Integrations page shows), and finding or creating our one tag. Disconnect under Dashboard → Integrations and we delete the key at once. You can also delete the key in ActiveCampaign.

Notion

When you connect Notion, you choose which pages or databases SiteCurb may use, and Notion gives SiteCurb an access token for just those, which we store encrypted together with your workspace’s name and the database your inquiries go to. We use it for one thing: each time a new inquiry arrives on your website, we add a page to that database with the person’s name, email, phone and message, the listing, and your website address. If you didn’t choose a database, we first make one, called “SiteCurb inquiries”, in the page you chose, or in your Private pages if you ask for that on the Integrations page.

The only other things we read are the names of the pages and databases you shared, so you can pick one on the Integrations page, and the columns of the database you pick, so each part of an inquiry goes into the right column. We don’t read or change anything else in your Notion. Disconnect under Dashboard → Integrations and we delete the token at once. Removing SiteCurb under Settings → Connections in Notion also ends our access.

How long we keep it

  • While your account is open: we keep your website and inquiries.
  • If you cancel your subscription: your website comes offline, but its content stays so you can come back.
  • If you ask us to delete your account: we delete your website, listings, photos and inquiries within 30 days. Copies in our providers’ backups expire on their normal schedule.
  • Billing records are kept as long as tax law requires.

Your choices

  • Agents can see and change almost everything in the dashboard. For a copy of your data, or to delete your account, write to john@sitecurb.com.
  • Visitors who contacted an agent can ask that agent directly, or write to us and we’ll pass the request on or act on the agent’s instruction.

Wherever you live, we’ll answer an access, correction or deletion request.

Security

Every page is served over HTTPS. Passwords are hashed by our sign-in provider. Each agent’s inquiries are locked to their account inside the database. Keys for tools you connect are stored encrypted.

Children

SiteCurb is a tool for working real estate professionals and isn’t directed at children.

Changes

If we change what we collect or how we use it, we’ll update this page and its date. If the change is significant, we’ll also email agents before it takes effect.