This page explains what information this website collects, why, who handles it and the choices you have. The site belongs to Aaron Benson, a REALTOR® with Realty ONE Group. “We” and “Aaron” below mean Aaron Benson.
The short version
- The site collects personal information only when you send the consultation form, the form on a home’s page or your saved homes, or the sign-in at an open house, and it uses that only to answer your request, or when you sign up for email alerts, to watch a home, for mortgage rate emails or for the short email guide for buyers, which it uses only to send those emails.
- Aaron also keeps your request, and a confirmed email alert sign-up, in his own customer-management system (his CRM) so he can follow up. An alert sign-up there is a record of the alerts only, never agreement to marketing.
- Homes you save with the heart, any private notes you write about them, and the homes you recently looked at are kept in your own browser only. They’re not sent anywhere unless you send the list to Aaron (and your notes only if you tick “Include my private notes”).
- Your browser also notes the website or app you arrived from and the page you landed on, so that when you send a form Aaron knows how you found him. It stays in your browser until then.
- The site uses two analytics tools, Google Analytics and Microsoft Clarity, to see how it’s used. They’re never sent your name, phone number, email address or message. The one exception is a scrambled copy of the email or phone you send with a request, which can go to Google to measure Aaron’s ads (below). They set cookies in your browser.
- Analytics don’t load if your browser sends Global Privacy Control, if you turn them off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland.
- There’s no Google Ads tag. Google Analytics is linked to Aaron’s Google Ads account, to measure his ads only: Google Ads can show what his ads cost next to the visits they brought, and count a request sent through the site as a result of an ad. It’s never used for remarketing, audiences or personalized ads: ad personalization and Google signals are off. If you contact Aaron after clicking one of his Google ads, that ad’s click ID may also be reported back to Google Ads, with the step it led to, so he can tell which ads work. Your name and message never go with either, and your contact details go only as the scrambled copy described next. None of this happens if your browser sends Global Privacy Control, you’ve turned analytics off, or you’re browsing from the European Economic Area, the United Kingdom or Switzerland (see “Ads and measurement”).
- Aaron also advertises on Facebook and Instagram. To measure those ads, the site can load Meta’s pixel, a small script from Meta, but only when analytics load for you, and never on the listing pages of the home search. It’s never sent your name, phone number, email address or message, and it sets cookies in your browser (see “Meta’s pixel” under “Ads and measurement”).
- When you send a request, the site may also send Google and Meta a scrambled copy (a SHA-256 hash) of the email address or phone number you gave, so they can tell whether one of Aaron’s ads led to it. Your name and message never go, and this never happens if your browser sends Global Privacy Control, you’ve turned analytics off, or you’re browsing from the European Economic Area, the United Kingdom or Switzerland (see “Matching a request to an ad” under “Ads and measurement”).
- Aaron’s ads can also appear in AI chat assistants. They link to the site with campaign tags only: the site sends nothing to the assistant’s company and loads none of its code (see “Ads and measurement”).
- Aaron doesn’t sell or rent your information. He doesn’t share it for targeted advertising, except with Meta, through its pixel where it loads and the record of a request described in “Matching a request to an ad”: Meta may use your visit, or that a request came from his ad, to choose who is shown his ads, and for its own purposes, which can include ads, under Meta’s Privacy Policy (see “Meta’s pixel”). Global Privacy Control or turning analytics off stops that. Linking Google Analytics to Google Ads, reporting a Google ad’s click ID and the scrambled email or phone sent with a request (see “Matching a request to an ad”) measure his ads; none is used to target ads to you.
The consultation form
When you send the form, it collects:
- what you’re thinking about (buying, selling, selling and buying, relocating or a second home), if you pick one; if you don’t, the form sends “not sure yet”
- your name
- your phone number or email address
- your message, if you write one
- on a form that asks for them, or when you pick “Selling and buying”, the general area or address of a home you’re thinking of selling, and your timing, if you give them
- on the buyer pages that ask, or when you pick “Selling and buying”, and only if you say: a price range you’re considering, when you hope to buy, and whether you plan to pay cash or use a loan. They’re optional, they go to Aaron with your request, and so to his CRM, and nowhere else (never to analytics or an ad service), and every request gets the same reply
- when you pick buying, selling and buying, relocating or a second home, and only if you open “Tell Aaron more” and fill it in: what matters to you in a home (such as views, golf or a single level) and your description of the home you’d buy. Both are optional. They go to Aaron with your request, and so to his CRM, and nowhere else (never to analytics or an ad service), and every request gets the same reply
- on a question about a home, the listing link or address you send, as you typed it (the site doesn’t open the link), or on the page that compares two homes, both links or addresses and whether you’re already working with an agent; and on those pages, the topics you tick, if any (such as the asking price, the layout or the HOA). The topics are optional, they go to Aaron with your request, and so to his CRM, and nowhere else (never to analytics or an ad service), and ticking them or not doesn’t change whether Aaron replies. Your answer about working with an agent goes the same way: to Aaron and his CRM, never to analytics or an ad service.
- on a page about one of Aaron’s offers, such as narrowing a home search or planning a home-search visit, that page’s own questions: where you’re looking and your price range; what your search keeps missing (picks such as guest space or a garage, your own words, and one more requirement or dealbreaker); for a visit, your rough dates (or that they aren’t set), the areas you’re weighing and one or two priorities; and, if you answer them, your timing and whether you’re already working with an agent. They go to Aaron with your request, and so to his CRM, with the offer’s name, and nowhere else. Analytics and ad services hear only which offer’s form was sent, never your answers. Answering the optional questions or not doesn’t change whether Aaron replies.
- on an open house’s page, whether you ticked “I’d like a private showing”
- on a showing request for one of Aaron’s listings, how you’d like to see it (in person or by video) and roughly when, if you say
- how you found the site: the website or app you arrived from, the page you landed on and when (see “How you found the site” below)
- how you heard about Aaron (Google, Facebook or Instagram, ChatGPT, a friend or referral, a sign, or other), if you pick one. The form asks only when the site has no campaign tags or ad click ID for your visit, and it’s optional
- how long the form took to fill in, and a hidden field that people leave empty, both used only to filter out spam
- a one-time pass from Cloudflare Turnstile, the form’s spam check (below)
The form is sent to a small program on the site’s host (Cloudflare) that checks it and passes it to Resend, an email delivery service, which emails it to Aaron. Aaron uses it to reply to you about your request. If you give a phone number, he may call or text you about it. Where analytics load for you, a scrambled copy of your email address or phone number may also go to Google and Meta to measure his ads (see “Matching a request to an ad” under “Ads and measurement”).
Aaron’s CRM. Once the email has gone, the same program sends a copy of your request to Aaron’s own customer-management system (EspoCRM, run for him on a private server and reachable only through Cloudflare’s secure tunnel and access check), where he keeps track of following up. The copy holds what you sent, listed above, without the Turnstile pass or the hidden spam field, and, only when analytics are on in your browser, Google Analytics’ random browser and visit IDs (see “Analytics” below). If the CRM can’t be reached, your request still reaches Aaron by email, and the copy is tried again for up to 7 days. Nothing in the CRM is used for marketing emails. To see which of his ads and pages lead to real requests, Aaron also keeps, on the same private server, a short record of each request: its record number, when it came, the kind of request and, if it came from one of his offers, which offer, how you found the site (the campaign tags; whether a Google click ID came with it, never the ID itself; and your answer to “How did you hear about Aaron?” if the form asked it), the first page you landed on (if that was one of Aaron’s own listing pages, its address names the home), if you’d confirmed an email alert sign-up before the request, when you did and where on the site it started (such as a search page or a guide, never the search itself), how Aaron marked it (such as a qualified conversation or not a fit), when he first replied, and how far it went (such as a meeting or a sale). When a sale closes, the record also keeps its price and Aaron’s commission and his brokerage’s fee, for his own business reporting. Those figures are never sold or shared outside his own business, and they’re the only prices the record holds. It never holds your name, contact details, message or a click ID. If you ask Aaron to delete your request, that record goes too.
Cloudflare Turnstile checks that the form is sent by a person, not a bot. When the form comes into view or you start typing, your browser loads Turnstile from Cloudflare (challenges.cloudflare.com). It usually works without you doing anything; now and then it asks you to tick a box. To decide, Cloudflare processes signals from your browser, such as your IP address, browser details and the site you’re on. Cloudflare says it uses them only to tell people from bots and to improve that check, not to identify, profile or target anyone. When you send the form, the program asks Cloudflare whether the pass is valid; Cloudflare doesn’t receive your name, contact details or message. Turnstile runs in its own frame from Cloudflare, and anything it keeps in your browser there is Cloudflare’s, for this check only. See the Turnstile privacy addendum. The form needs JavaScript for this check; without it, call or text Aaron instead.
The program’s logs record only a summary: which option you picked, whether you gave a phone number or an email, and whether you wrote a message (and, where the form asks, whether you gave an area or address and a timing; on an offer’s page, which offer and how many of its questions you answered). They never record your name, contact details, message, area, address, timing or answers.
Aaron keeps your request only as long as he needs it to work with you and to meet his brokerage’s record-keeping requirements.
Saved homes
The heart on a home for sale saves it to a list kept in your browser’s local storage, on this device and browser only. There’s no account. The list holds each home’s MLS number and nothing else: no address, price, photo, or anything about you. It isn’t a cookie, and it isn’t sent to the site, to Aaron or to either analytics tool. When you open Saved homes, your browser asks the site for each saved home’s listing, as it would load any page.
The list stays until you clear it: remove homes on the Saved homes page, tap a heart again, or clear your browser’s site data for aaronbenson.com.
Private notes. On the Saved homes page you can write a short note on each saved home (up to 280 characters). Notes are kept in your browser’s local storage beside the list, on this device and browser only, and never sent to the site, to Aaron or to either analytics tool. The one exception is your choice: when you send your list or a tour request to Aaron, a box, “Include my private notes”, is unticked unless you tick it. Ticked, each home’s note goes with that request (see the form, below); your emailed copy doesn’t repeat them. Notes are cleared with the list, or when you clear your browser’s site data.
Compare and Plan a tour. Comparing your saved homes and planning a tour happen in your browser. The tour’s order, days and times aren’t kept or sent anywhere until you send the request.
Sharing your list. “Share my list” makes a link to the Saved homes page that carries each home’s MLS number and nothing else: never your notes, the order you chose, or anything about you. Whoever you give it to sees those homes as their listings are now, and can save them to their own browser’s list. The link isn’t stored by the site; anyone who has it can open it. Analytics never see the MLS numbers in it.
Plan a sale
The sale proceeds worksheet on Plan a sale works in your browser. The figures you type aren’t saved, aren’t put in the page’s address and aren’t sent to the site, to Aaron or to either analytics tool; analytics only learn that the worksheet was used. The one exception is your choice: in the form at the end of the page, “Include my worksheet figures” and “Include the checklist items I’ve ticked” are unticked unless you tick them, and each shows exactly what it sends. Ticked, those figures or items go with your request to Aaron, like the rest of the form (see “The consultation form”, above); they aren’t logged. Microsoft Clarity doesn’t run on that page. The preparation checklist’s ticks are kept in your browser’s local storage, on this device and browser only: which items are ticked, nothing else. They aren’t sent anywhere unless you include them in the form. “Clear the ticks” removes them, and so does clearing your browser’s site data for aaronbenson.com.
Recently viewed and since your last visit
To show “Recently viewed” homes and how many homes are new since your last visit, your browser’s local storage keeps the MLS numbers of the last 12 home pages you opened, with the time you opened each, and the time you last looked at the homes page and each area page. Nothing else: no address, price, photo, or anything about you. It isn’t a cookie, and it isn’t sent to the site, to Aaron or to either analytics tool. “Clear” under Recently viewed removes the homes; clearing your browser’s site data for aaronbenson.com removes all of it.
The form on a home’s page and on Saved homes
“Email Aaron about this home” on a home’s page and “Send my list to Aaron” on Saved homes use one form. When you send it, it collects:
- your name and email address, and your phone number if you give one
- your message, if you write one
- whether you’d like to see the homes in person, and the days and times you’d prefer, if you say
- the homes: each one’s MLS number, and its address and price as the page showed them; for a tour request (“Ask Aaron to set up this tour”), in the order you put them
- your private notes on those homes, only if you ticked “Include my private notes”
- how you found the site (see “How you found the site” below), how long the form took to fill in, and a hidden field people leave empty, used only to filter out spam
- how you heard about Aaron, if you pick an answer: the same optional question as on the consultation form, asked only when the site has no campaign tags or ad click ID for your visit
- a one-time pass from Cloudflare Turnstile, the same spam check as the consultation form’s (above)
It’s handled like the consultation form: a small program on Cloudflare checks it and passes it to Resend, which emails it to Aaron. Resend also emails you a copy at the address you gave, with a link to each home’s page on this site and nothing you typed. It shows Aaron’s logo, loaded from this site as in the alert emails (see “Email alerts”). Aaron uses your request only to reply to you about it, and he may call or text you if you give a phone number. The program’s logs record only counts and yes-or-no flags (how many homes, how many had a note, whether you asked to see them, whether you gave a phone number or wrote a message), never your name, contact details, message or which homes.
A copy goes to Aaron’s CRM too (see “The consultation form” above), with each home’s MLS number only: never its address and price as the page showed them, and never your private notes.
Signing in at an open house
At one of Aaron’s open houses, the sign-in card’s code opens a short form on this site. It collects:
- your name
- your phone number or email address
- whether you’re working with a real estate agent (yes or no)
- a note, if you write one
- which home’s open house it is, and the day you signed in
- how you found the site (usually the sign-in card; see “How you found the site” below), how long the form took to fill in, and a hidden field people leave empty, used only to filter out spam
- a one-time pass from Cloudflare Turnstile, the same spam check as the other forms’ (above)
It’s handled like the consultation form: a small program on Cloudflare checks it and passes it to Resend, which emails it to Aaron. No copy is emailed to you. Aaron uses it only to follow up with you about the home. The program’s logs record only yes-or-no flags (whether you gave a phone number or an email, whether you’re working with an agent, whether you wrote a note), never your name, contact details or note.
A copy goes to Aaron’s CRM too (see “The consultation form” above).
Email alerts
“Email me new matches”, on the home search page and on each area page, sends you new homes for sale that match your search, by email. Anyone can sign up; nothing is sent until you confirm. When you sign up, the site keeps:
- your email address
- your search: the place (an area, city or ZIP code, or an area you marked on the map yourself) and the filters you chose, exactly as they are in the search page’s address (from an area page, just the area)
- for an area you marked (“Watch an area”: drawn, along a street or around a pin), its outline and the name you gave it, if any. If you used “Use my location” to place the pin, your location is rounded to about 100 metres first, in your browser, and it’s kept only as the middle of that outline
- how often you want alerts (once a day, a few times a day as listings update, once a week or once a month)
- whether you ticked “I’d like Aaron to contact me about these homes”, and your phone number if you gave one
- when you signed up and when you confirmed, and which version of the sign-up wording you saw
- a one-time pass from Cloudflare Turnstile, the same spam check as the forms’ (above), which is checked and not kept
Your location on the area maps. On the “Watch an area” page and in the home search’s “Draw an area”, the site asks your browser for your location only when you tap “Use my location” on the map, and your browser asks your permission first. The site’s code rounds it to about 100 metres, in your browser, before using it. The map moves there, and if you’re dropping a pin, the pin goes there too. If you sign up for that area, the location is kept only as described above; otherwise it isn’t kept or sent anywhere. Every other page of the site tells your browser not to allow location at all.
It doesn’t keep your IP address. Confirming the email the site sends you is the record that you asked for the alerts. Once you confirm a search, the site sends you one welcome email, saying what to expect and how to change or stop the alerts; it’s never sent again for that search. Aaron sees your email address, your search and the name you gave your area, and gets an email when you confirm. If you didn’t tick the box, Aaron won’t call, text or email you himself, beyond the alerts, unless you ask him to, for example by replying to an alert, and he won’t add you to any other mailing list.
When you confirm, Aaron’s CRM (see “The consultation form” above) records the sign-up: your email address, your phone number if you gave one, the search in words and its areas (for an area you marked, its name and roughly where its middle is, to about 100 metres, never its outline; for a watched home, its MLS number), how often, whether you ticked the box, how you found the site, the page you signed up on (left out when that was a search page or a home’s page, other than one of Aaron’s own listings), and that you agreed to listing alerts. When the alerts end (you unsubscribe or delete them, your email bounces or is reported as spam, or you don’t keep them), it records that too. Agreeing to alerts is never treated as agreeing to marketing: the CRM never puts you on a mailing list, and the alerts themselves, their emails and their unsubscribe links work as described here.
Everything is stored on the site’s host, Cloudflare, in a small database only the site’s program can read. The emails are sent through Resend (or Cloudflare’s own email service), from updates.aaronbenson.com. They have no tracking: no tracking pixels, and links aren’t rewritten. Every email the site sends you, these and the others below, shows Aaron’s logo at the top, loaded from aaronbenson.com. It’s the same file for everyone, and nothing in its address identifies you or the email; the site doesn’t use it to tell whether or when anyone opened an email. When your mail app loads it, the site’s host, Cloudflare, receives the request as it would any visit to the site (your IP address, your mail app’s details and the time), unless your mail app loads images through its own servers, as many do. The site’s own program doesn’t run for it and keeps no record of it. An alert can show a photo of each home. The photo isn’t attached to the email or sent by the site: your mail app loads it straight from the MLS’s photo service (FBS’s Spark platform), as the site’s own listing pages do. Many mail apps (Gmail, Apple Mail, Outlook and Yahoo among them) load images through their own servers, so the photo service doesn’t see you. If yours loads them directly, the photo service receives your IP address, your mail app’s details and the time the photo loaded, as with any image from another site. You can turn off loading images in your mail app; the email shows every detail in text either way. To know which homes it has already sent you, the site keeps a scrambled code for each one (a keyed hash of its MLS number), not the listing. The program’s logs record only counts and outcomes, never your address, your search or your phone number.
How long it’s kept:
- a sign-up you don’t confirm is deleted after 7 days
- on a busy day, an email to you that has to wait for the next day’s sending room (your confirmation, say) is kept, as written, until it’s sent, its link expires, or your sign-up is deleted
- your alerts last until you unsubscribe, until your email bounces or is reported as spam, or until you don’t answer the “Keep these alerts?” email sent every 6 months within 14 days
- if your email bounces for good or you report an alert as spam, your address and searches are deleted and only a scrambled code of the address is kept, so it’s never emailed again
- when you unsubscribe from everything, your address and searches are deleted at once; the site keeps only a scrambled code of the address and the date, so it never emails it again unless you sign up and confirm again
- Resend keeps its own delivery logs for a time it sets
Every alert email has a one-click Unsubscribe link and a Manage your alerts link, where you can change how often, pause or delete a search, or delete everything about you. If you’ve lost the email, the manage page can send you a fresh link.
Watching a home
“Watch this home”, on a home’s page and beside a home in your saved homes, sends you one email when that home’s list price or status changes, or when it’s no longer on the site. It works like the email alerts above, with the same confirmation email, limits, storage, links and deletion, and it keeps:
- your email address
- the home’s MLS number
- whether you ticked “I’d like Aaron to contact me about this home”, and your phone number if you gave one
- when you signed up and when you confirmed, and which version of the sign-up wording you saw
- to notice a change, the home’s status and a scrambled code of its list price (a keyed hash), nothing else about it, and only while you’re watching it
The email can show the home’s photo, loaded from the MLS’s photo service as in the alerts above (never when a home is no longer on the site). An address can watch up to 10 homes. Aaron sees your email address and the home, and gets an email when you confirm. When a home leaves the site, you get one last email saying it’s no longer available, and the site stops watching it for you. Unsubscribe, the manage page and “delete everything about you” cover watched homes too.
Mortgage rate emails
You can ask for an email when the average rate for a 30-year fixed mortgage falls. You ask with its own box on the email alert and “Watch this home” sign-ups (“Also email me when mortgage rates drop”), unticked until you tick it; with “Email me when rates drop” under the payment calculator on a home’s page; or with the “Turn on rate emails” link in an alert email, which opens a page where you choose whether to turn them on. These are marketing emails from Aaron, separate from your home alerts: signing up for alerts never signs you up for them, and they’re never sent unless you ask.
The figure is the CFPB’s weekly average prime offer rate for a 30-year fixed loan, from the table the Bureau publishes, which the site reads about once a week. An email goes only when that average has fallen at least 0.25 percentage points below the figure in the last rate email we sent you (or the figure when you signed up), and never more than one every 14 days. It has no listings and no payment figures; it links to the site.
When you ask, the site keeps:
- your email address
- where you asked (under the calculator, with an alert or watch sign-up, from an alert email, or on the manage page), when you asked and when you confirmed, and which version of the sign-up wording you saw
- the average and its week when you signed up, and the figure, week and date of the last rate email sent to you, so it knows when the next one is due
- from the sign-up under the calculator only, how you found the site, kept until you confirm, for Aaron’s notice
- a one-time pass from Cloudflare Turnstile, which is checked and not kept
It doesn’t keep your IP address. Nothing is sent until you confirm: the sign-up under the calculator sends you a confirmation email; a box ticked on an alert or watch sign-up is confirmed by that sign-up’s own confirmation email, which says so; and the link in an alert email only reaches an address that has already confirmed its alerts, and turns rate emails on only when you press the page’s button. Aaron sees your email address, and gets an email when you confirm the sign-up under the calculator (for a box ticked on an alert sign-up, his alert notice says you asked for rate emails too). He won’t call, text or email you himself, beyond these emails, unless you ask him to, and he won’t add you to any other mailing list. Rate email sign-ups aren’t sent to Aaron’s CRM.
They’re stored and sent like the email alerts above (on Cloudflare, through Resend from updates.aaronbenson.com, with no tracking pixels and no rewritten links), and the program’s logs record only counts and outcomes. A sign-up you don’t confirm is deleted after 7 days, or when the alert it was ticked with is deleted or never confirmed. Otherwise rate emails last until you stop them. Every rate email has a one-click Stop rate emails link, which ends rate emails only and leaves your home alerts alone. “Unsubscribe from all alerts” and “Delete everything about me” end rate emails too, and so does an email that bounces for good or is reported as spam. If you have alerts, their manage page shows whether rate emails are on and turns them on or off.
Email guide for buyers
You can ask for a short email guide for buyers researching Scottsdale and Paradise Valley: four emails from Aaron over about two weeks (the areas side by side, prices and what moves them, how buying here works, and how to use the site’s tools), and then it stops. You ask with “Get the short email guide for buyers” on the area comparison pages and some of the buyer guides, or with the “Yes, send me the guide” button offered after you confirm an email alert. These are marketing emails from Aaron, separate from your home alerts: signing up for alerts never signs you up for the guide, and it’s never sent unless you ask. The emails link to the site’s own guides and pages; they have no listings.
When you ask, the site keeps:
- your email address
- where you asked, as the kind of page (the comparison page, a written comparison, a buyer guide, or after confirming an alert), never the page itself, when you asked and when you confirmed, and which version of the sign-up wording you saw
- how many of the guide’s emails have gone to you and when the last one went, so it knows when the next one is due
- from a sign-up on a page only, how you found the site, kept until you confirm, for Aaron’s notice
- a one-time pass from Cloudflare Turnstile, which is checked and not kept
It doesn’t keep your IP address. Nothing is sent until you confirm: a sign-up on a page sends you a confirmation email, and the button after an alert’s confirmation shows only once that alert’s own confirmation link has proved the address. Aaron sees your email address, and gets an email when you confirm a sign-up on a page. He won’t call, text or email you himself, beyond these emails, unless you ask him to, and he won’t add you to any other mailing list. Guide sign-ups aren’t sent to Aaron’s CRM.
They’re stored and sent like the email alerts above (on Cloudflare, through Resend from updates.aaronbenson.com, with no tracking pixels and no rewritten links). Their links to the site carry campaign tags that say a visit came from the guide and from which of its emails, never anything about you. The program’s logs record only counts and outcomes. A sign-up you don’t confirm is deleted after 7 days. Everything the site keeps about your guide is deleted once its last email has gone, or sooner when you stop it. Every guide email has a one-click Stop the email guide link, which ends the guide only and leaves your home alerts alone. “Unsubscribe from all alerts” and “Delete everything about me” end it too, and so does an email that bounces for good or is reported as spam.
How you found the site
So Aaron knows how you found him, the site notes in your browser the website or app you arrived from and the page you landed on. On the first page you open, it keeps:
- the name of the website or app that linked here (for example chatgpt.com or google.com), never the address of the page you were on or what you searched for
- the page you landed on, without anything after a “?” in its address
- campaign tags in the link, if it has them (
utm_source,utm_medium,utm_campaign,utm_termandutm_content, which names the ad or link within a campaign, such as “gbp” on the link in Aaron’s Google Business Profile, orutm_medium=paidon his paid ads, which marks the source “(ad)”). On his Google ads,utm_termis the keyword Aaron chose that the ad was shown for, such as “paradise valley listing agent”: his words, not what you typed. A tag that looks like an email address or phone number is dropped - whether the link came from an ad (that it had an ad click ID such as
gclid,msclkidorfbclid) - if the link came from a Google ad, Google’s click ID itself (
gclid, orgbraidorwbraid) and the day of the click, for 90 days at most, so that if you send a form, Aaron can report to Google Ads that his ad led to it (see “Ads and measurement” below). It’s dropped from your browser 90 days after the click, and it goes out only inside a form you send - the date
If you come back later from a different website or app, or through a link with different campaign tags, it notes that visit the same way as your latest. Moving around the site changes nothing, and nothing else is tracked by it.
If the site has no campaign tags or ad click ID for your visit, the consultation form and the form on a home’s page or Saved homes may ask how you heard about Aaron: it’s optional, and your answer goes with your request to Aaron’s email and his CRM, never to analytics or an ad service.
The note is kept in your browser’s local storage under one small entry, not in a cookie. It isn’t sent to the site, to Aaron or to the analytics tools as you browse. It’s sent only with a form you send (the consultation form, the form on a home’s page or Saved homes, the sign-in at an open house, or an email alert, “Watch this home”, rate email or email guide sign-up), and Aaron’s copy of your request says, for example, “How they found the site: ChatGPT · first visit Nov 3”, followed by the first page you landed on, such as the Arcadia page, and, if you used the site’s note offering to contact him during that visit, the kind of page it was on (such as “on-site nudge:guide”), if you followed “Talk to Aaron” under the payment calculator, that you did (“on-site calculator:listing”), if your visit began from a link in one of the site’s mortgage rate emails, that it did (“on-site rate-drop:email”), and, for an email alert sign-up, where it started (such as “on-site alerts:search_card”), all kept apart from the campaign tags. It’s never in the copy emailed to you, and the site’s logs record only the kind of source (such as “ChatGPT” or “another website”) and whether a Google click ID came with it, never the website’s name, the page, the tags or the ID. For an alert, watch or email guide sign-up it’s kept with your request only until you confirm, for Aaron’s sign-up notice, then deleted.
It’s deleted when you clear your browser’s site data for aaronbenson.com, and it starts over after a year. If your browser sends Global Privacy Control, if you’ve turned analytics off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland, it’s kept in session storage for this visit only (deleted when you close the tab), any older note is deleted, and no ad click ID is kept at all, not even for this visit: neither whether the link had one nor Google’s ID. Until the site has checked where you’re browsing from (the same check the analytics use, which never keeps your location), the note is kept for this visit only too, with any click ID; once the check says you’re in one of those places, the click ID is dropped, and one sent with a form from there before that is removed by the site’s program (see “Ads and measurement”).
The site also keeps a few small notes in your browser. Session storage holds whether analytics may load where you’re browsing from (yes or no, never your location), so the site asks only once per visit, and whether Google reviews were unavailable, so it doesn’t ask Google again during that visit (never any review). If you turn analytics off, local storage holds that choice until you turn them back on or clear your browsing data. Local storage also keeps the numbers you enter in the payment calculator on a home’s page (your down payment, interest rate, loan term and insurance; never a home’s price, tax or HOA dues) so you don’t have to type them again on the next home, sent nowhere and removed by its “Clear my numbers”. It also remembers that you’ve seen the tip about saving homes, the tip on the saved-homes bar and the note after your first save (yes or no), so each shows only once. On Aaron’s ad landing pages, local storage also keeps which of two versions of the email alert form you were shown (short or long, picked at random), so you see the same one each time. If you tap a landing page’s button to the home search before analytics have loaded, session storage holds that tap (which landing page and which area, nothing about you) for up to 30 minutes, and the next page sends it once, only if analytics turn on there. On some pages (the home search, a home’s page, a guide, an area page and the selling pages) a small note may offer to call, text or message Aaron, at most once a visit. Session storage holds, for this visit only, whether it has shown, whether you’ve already called, texted or sent a form (so it doesn’t show after that), a random group (about one visit in five never sees it, so Aaron can tell whether it helps), and whether you used it. “Don’t show these” keeps that choice in local storage. The note is based only on the page, what you do on it, and how you arrived today (for example from Aaron’s Google profile or one of his ads, which changes its wording), never on anything about you as a person, and it shows whether or not analytics are on. None is a cookie. The note’s group and the kind of page where you used it go only with the analytics events described below (when analytics are on) and with a form you send; the rest is sent nowhere.
Hosting and security
The site is hosted by Cloudflare. Like any web host, Cloudflare processes technical information about each visit, such as your IP address, browser and the page requested, to deliver the site and protect it from abuse. Cloudflare also tells the site which country a visit comes from, only to decide whether analytics (and Meta’s pixel) may load, and whether a request’s scrambled email or phone may go to Google and Meta (see “Matching a request to an ad”; for Meta, Cloudflare’s US state too); the site doesn’t keep either. Cloudflare may set a strictly necessary security cookie to tell people from automated traffic. See Cloudflare’s privacy policy.
If a page breaks one of the site’s security rules (for example, a browser extension tries to run a script the site doesn’t allow), your browser may send the site’s program a short automatic report about it. The program keeps only a daily count of which rule it was, the kind of thing blocked or the name of the website it came from, and the page’s address without anything after a “?” or “#” (for a home’s page or an alert’s page, only which kind of page it was). It never keeps your IP address, your browser’s details or anything you typed, and the counts are deleted after 14 days. They’re used only to find and fix something the site broke.
Fonts and the map
The site’s fonts, map tiles and map labels are served from this site, so viewing them doesn’t send your information to Google or any other third party. The map is drawn from OpenStreetMap data (© OpenStreetMap contributors) through Protomaps, stored on this site.
Google reviews
The “What clients say” sections on the About page and the homepage can show Aaron’s reviews from his Google Business Profile, fetched from Google Maps when you scroll near them. The site asks Google through its own server, so Google doesn’t learn who you are from that request, and the site keeps none of it: it isn’t stored or cached. Each reviewer’s profile photo is loaded straight from Google, so Google receives your IP address and browser details when those photos load, as with any image from Google. That content is Google’s, covered by the Google Maps/Google Earth Additional Terms of Service and Google’s privacy policy. The links to his profiles on other sites (Zillow, Realtor.com and others) are ordinary links: nothing is sent to those sites unless you follow one.
Listing and market data
Aaron’s listings and the area market figures come from RentCast, a real estate data provider. The site fetches that data on a schedule and stores it with the site. Nothing about you is sent to RentCast when you visit.
When the site shows homes for sale from the Arizona Regional Multiple Listing Service (ARMLS), the listing data comes through FBS’s Spark platform when the site is built, and nothing about you is sent with it. If you type a keyword on the home search page (like “casita”), it’s sent to the site’s program on Cloudflare to find the homes whose descriptions contain it, and the program answers with which homes match. It isn’t kept, isn’t written to the program’s logs and isn’t sent to the analytics tools; it stays in the search page’s address in your browser, like the other filters. Each listing’s photos load straight from Spark’s photo servers, so they receive your IP address and browser details when the photos load, as with any image from another site. Pages showing those listings don’t run Microsoft Clarity, and a listing’s own page and the pages of listings by ZIP code run no analytics at all.
Analytics
The site uses two analytics tools to understand how visitors use it, such as which pages are read and which ways of reaching Aaron are used, so he can improve it, and, for Google Analytics, to measure his Google ads (see “Ads and measurement”). They load only after the page has finished loading, and only on aaronbenson.com itself.
Google Analytics (Google LLC) records the pages you view, the site you came from, your browser, device and screen size, and an approximate location (city or region) that Google works out from your IP address. Google Analytics doesn’t log or store your IP address. From the part of a page’s address after a “?”, the site lets both tools see only campaign utm_ tags, the click IDs Google Ads adds to ad links (gclid, gbraid and wbraid, which identify an ad click, not a person), and the site’s own settings, such as the two areas being compared. Anything else is removed from the address before either tool loads. The site also turns off Google signals and ad personalization.
Microsoft Clarity (Microsoft Corporation) records how pages are used, such as clicks, taps, scrolling, mouse movement and the size of your screen, and can replay a visit as a session recording or summarize it as a heatmap. Clarity is set to strict masking: all page text and everything typed into a form is masked in your browser before anything is sent, so recordings show blank shapes in place of words, and the form and its confirmation are always masked. Clarity may also be connected to the site’s Google Analytics account, to combine the two reports.
Both tools also record a few actions: sending the consultation form, tapping to call or text, asking about one of Aaron’s listings (only that it happened), the tips about saving homes and the saved-homes bar (which one showed, and how it closed), the note offering to contact Aaron (the kind of page, whether it showed or would have, which button was used, how it closed, and the visit’s random group), starting and sending an email alert sign-up (only where it started, such as the home search or a home’s page, and on Aaron’s ad landing pages which of two versions of the form showed, short or long; never the search itself), tapping the button to the home search on one of Aaron’s ad landing pages (only which landing page and which area), tapping the link from one of those pages to the page for asking Aaron about a home before an offer (only which landing page), using the payment calculator on one of Aaron’s own listing pages (only that it was used, never a figure), sending the sign-up for mortgage rate emails (only that it happened), sending the sign-up for the email guide for buyers (only that it happened, and whether it was on the comparison page, a written comparison or a buyer guide), and using the area list and the compare tool. Each records only where it happened on the site, the option picked on the form (buying, selling, relocating, a second home or not sure yet), or an area’s short name. For sending a form or an email alert sign-up and tapping to call or text, Google Analytics also records a fixed number for that kind of action (a weight Aaron uses to compare his ads, such as a request about buying or selling counting more than an alert sign-up), never a price or anything about a home. They never record which home listed by another brokerage you text, call or message Aaron about, or its MLS number, address or price. No personal information is ever sent to either tool: never your name, phone number, email address or message. The one exception is the scrambled copy of the email address or phone number you send with a request, which Google Analytics can receive for measuring Aaron’s ads (see “Matching a request to an ad”); Clarity never does. Neither tool learns which homes listed by other brokerages you look at, save or ask about: saving a home sends nothing, and the listing pages of the home search and their form run no analytics at all. Aaron’s own listing pages are an exception, and so are the pages for his open houses and their sign-in: like any other page of the site, the analytics see the page’s address, which includes the home’s street address, so they can tell that a request, a call or text tap, or the payment calculator came from that listing’s page; never anything you typed. Both tools run on his own listing pages and on an open house’s sign-in; an open-house page runs Google Analytics only, and none at all when it shows only the home’s listing from the MLS. The Saved homes page runs Google Analytics only, never Clarity, and records only how many homes are involved when you open Compare or Plan a tour, send your list or a tour request, copy a share link, or open or save a shared list; never which homes, their MLS numbers, addresses or your notes.
Google Analytics’ browser ID and Aaron’s CRM. When analytics are on in your browser, the forms also send Google Analytics’ random browser ID and visit ID (the ones in its _ga cookies) with your request, to Aaron’s CRM only, never in his email. When a request later becomes a meeting, a contract or a sale, the CRM can tell Google Analytics that this happened for that browser ID, with only the kind of request, the stage and the campaign tags: never your name, contact details, message, address, a home or a price. When analytics don’t load (below), no ID is sent.
Google and Microsoft process this information under their own terms and privacy statements: see Google’s privacy policy, how Google uses information from sites that use its services, the Microsoft Privacy Statement and Clarity’s terms.
When analytics don’t load. Neither tool loads, and neither sets a cookie, if:
- your browser sends a Global Privacy Control signal, which the site treats as a request to opt out
- you turn analytics off on Your privacy choices
- you’re browsing from the European Economic Area, the United Kingdom or Switzerland, where the site doesn’t use analytics at all
- the site’s check of where you’re browsing from fails, for that visit
- JavaScript is off in your browser
Where analytics don’t load, Meta’s pixel doesn’t either (see “Meta’s pixel” below). Google Analytics is linked to Aaron’s Google Ads account, to measure his ads only (see “Ads and measurement” below); where analytics don’t load, that doesn’t happen either. Microsoft Clarity isn’t connected to any ad platform, and nothing from it is sent to one. Aaron may look at its totals by where visits came from, his ads included, to improve the pages they land on. Reporting a Google ad’s click ID (below) doesn’t use either analytics tool.
Ads and measurement
Aaron may advertise his listings and services in Google search results, on Meta (Facebook and Instagram) and in AI chat assistants. Ads in a chat assistant link to the site with campaign tags only; the site sends nothing to the assistant’s company and loads none of its code. The site has no Google Ads tag and no other ad network’s code; the only advertising code it can load is Meta’s pixel (below). Google Analytics is the only Google code on the site. Aaron doesn’t use remarketing, audience or customer lists, and never builds an audience of visitors to this site. Meta may still use what its pixel receives, to choose who is shown his ads and for its own purposes, which can include ads, under its own privacy policy (see “Meta’s pixel”). Google’s and Meta’s rules for housing ads also limit how those ads can be targeted.
Google Analytics linked to Google Ads. Aaron’s Google Analytics account is linked to his Google Ads account, so Google Ads can show what his ads and campaigns cost next to the visits they brought to the site, and count actions Google Analytics records, such as sending a form or a request later becoming a meeting (see “Analytics” above), as results (“conversions”) of his ads. When analytics load for you (in the United States, or anywhere else outside the European Economic Area, the United Kingdom and Switzerland, with no Global Privacy Control and no opt-out), the site tells Google that its analytics may be used for this ad measurement (Google’s “ad storage” and “ad user data” consent settings). It’s measurement only: ad personalization is off for every visitor and Google signals is off, so nothing from your visit is used for remarketing, to build audiences or to personalize the ads you see. The site never sends your name or message to Google Analytics or Google Ads, and never your email address or phone number except as the scrambled copy described in “Matching a request to an ad” below. If your browser sends Global Privacy Control, if you’ve turned analytics off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland, analytics don’t load, so none of this happens.
Meta’s pixel. Aaron also advertises on Facebook and Instagram. To measure those ads, the site can load Meta’s pixel, a small script from Meta Platforms, when analytics load for you, so Meta can count visits and requests that came from his ads. It tells Meta that a page on this site was viewed and, if you send a form, tap to call or text, or sign up for email alerts, that this happened: only the kind of action, with a random number that identifies the event, not you. The pixel never sends your name, phone number, email address or message, or anything you typed, and the site turns off the pixel’s automatic reading of buttons and page details and Meta’s “advanced matching” (which would send contact details). The record of a request the site’s program sends Meta is separate (see “Matching a request to an ad”). Like the analytics, it sees the page’s address (cleaned the same way; see “Analytics”) and title, so it never learns which home listed by another brokerage you look at. Aaron’s own listing pages are an exception, and so are the pages for his open houses and their sign-in: their address includes the home’s street address, so Meta can tell that a page view, a request or a call or text tap came from that listing’s page. Meta receives what any website you visit receives (your IP address and browser details) and may connect the visit to a Facebook or Instagram account in that browser. Meta’s pixel sets _fbp and, after a click on one of Aaron’s Facebook or Instagram ads, uses _fbc, which the site sets for it (see “Cookies”). Aaron uses it to measure his ads and to let Meta show them to people likely to visit the page; he doesn’t build audiences from it or retarget visitors. The site also turns on Meta’s Limited Data Use, so in the US states where Meta offers it, Meta limits how it uses the data. It doesn’t load if your browser sends Global Privacy Control, if you’ve turned analytics off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland, and it never loads on the listing pages of the home search (homes listed by other brokerages), or on the home search, Saved homes and email alert set-up pages, whose addresses can hold your search or your saved homes, and never on the page about selling during a divorce. Meta also uses what it receives for its own purposes under Meta’s Privacy Policy, which can include ads; Limited Data Use narrows this where it applies.
Links from ads. A link from one of Aaron’s ads carries campaign tags (for a Meta ad, utm_source=meta&utm_medium=paid), and Google adds its click ID (gclid, gbraid or wbraid); Microsoft and Meta add their own (msclkid, fbclid). The site notes them as described in “How you found the site” above: the tags, whether a click ID was there, and the value of Google’s ID only. Aaron’s copy of your request then says, for example, “Google search (ad)”. Nothing is sent to Microsoft. Meta’s click ID (fbclid) is removed from the page’s address before any tool loads, as every other unlisted part of it is; only where Meta’s pixel may load does the site first keep it in the pixel’s _fbc cookie, so Meta can tell the visit came from its ad (see “Meta’s pixel”). Your browser sends that cookie with a form, as it does with every request to this site. The site’s program passes it only to Meta, with the record of your request (see “Matching a request to an ad”), and never puts it in Aaron’s email or his CRM.
Reporting a Google ad click back to Google Ads. When a request you sent came with a Google click ID, Aaron may upload to his Google Ads account that click ID, the step it led to (a request, a sign-in, a showing or an offer), when, and a value he gives that kind of step (a weight for comparing his ads, never a price). Google matches the ID to its own record of the ad click, so his reports show which ads led to real requests. Nothing else goes with it: never your name, phone number, email address, message, notes, or anything about a home, such as its address, price, MLS number or the page you landed on. A click is reported only within 90 days of it. Google says it processes these uploads as Aaron’s service provider, with restricted data processing on.
A Google click ID is never reported if your browser sends Global Privacy Control, if you’ve turned analytics off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland. The site’s program removes any ad click ID that comes with a form sent with Global Privacy Control or from those places, before Aaron’s email or his CRM gets it, so he never has one to report. Your browser doesn’t keep one either: with Global Privacy Control or analytics turned off, not at all; from those places, not once the site has checked where you’re browsing from (until then, it may sit in that tab for a moment, and it’s still never sent to Aaron). If you’ve already sent a request and don’t want its click reported, tell Aaron and he won’t report it.
Matching a request to an ad. When you send the consultation form, and analytics load for you, the site may also send Google and Meta a scrambled copy of the email address or phone number you gave. Analytics load for you in the United States, or anywhere else outside the European Economic Area, the United Kingdom and Switzerland, when there’s no Global Privacy Control and no opt-out. The copy lets Google and Meta tell whether one of Aaron’s ads led to your request. It’s a SHA-256 hash: a fixed string of 64 letters and numbers worked out from your address or number after a few standard clean-ups (spaces trimmed, letters made lowercase, a phone number written with its country code). It isn’t your address or number itself, but anyone who already has your address or number can work out the same hash, which is how Google and Meta match it to an account of theirs.
- To Google (Google’s “enhanced conversions”, through Google Analytics’ “user-provided data”): your browser makes the hash and sends it with Google Analytics’ record of the request, which Google Ads counts as a result of his ads. Your email address or phone number itself never leaves your browser for Google. Google processes it as Aaron’s processor under the Google Ads Data Processing Terms and says it uses it only to provide Aaron its services, such as this measurement. It’s kept with his Google Analytics data, up to 14 months.
- To Meta (Meta’s “Conversions API”): the site’s program makes the hash from the request it received and sends it to Meta in a short record of the request. That record says only that a request was sent (Meta’s “Lead”) and when, and gives the random event number the pixel uses for it, so Meta counts the request once. It also gives the part of the site the request came from, only as broad as a section, such as the homes pages or the selling pages (never a home’s own page, an area or anything after a “?”), and passes the
_fbccookie if the site set one after a click on his Facebook or Instagram ad. It never sends your name, your message, your IP address, your browser’s details, a home or anything else you typed. Under Meta’s Business Tools Terms, Aaron instructs Meta to use the hash only to match it to a Facebook or Instagram account, and Meta deletes it after matching. What Meta learns from the match, that a request came from one of Aaron’s ads, it uses as it uses what its pixel receives (see “Meta’s pixel”). This record is never sent for a request from a US state where Meta offers Limited Data Use (California, Colorado, Connecticut, Delaware, Florida, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island and Texas), because without your IP address Meta couldn’t apply it, nor when the site can’t tell which state or country a request comes from. Cloudflare’s location check decides this, and the state isn’t sent to Meta or kept. - When it doesn’t happen: never if your browser sends Global Privacy Control, if you’ve turned analytics off on Your privacy choices, or if you’re browsing from the European Economic Area, the United Kingdom or Switzerland. Your browser checks this, and the site’s program checks Global Privacy Control and where the request comes from again before anything is sent. It also never happens for a request sent from the page about selling during a divorce, for the sign-in at an open house, for an email alert, “Watch this home”, rate email or email guide sign-up, or for the form on a home’s page or Saved homes. Aaron doesn’t use it to build audiences or customer lists, or to retarget anyone.
Calls from ads. A Google ad can show a call button or number. That number is a Google forwarding number that rings Aaron’s phone, so Google Ads can report calls from ads. For each one, Google records the start time and duration, the caller’s country and area code, whether it was answered or missed, which campaign and keyword led to it and, for most calls longer than 15 seconds, the caller’s phone number (Google’s list). Calls aren’t recorded. Calling or texting Aaron at the number shown on this site doesn’t go through Google.
Cookies
The site’s own code doesn’t set cookies, except _fbc for Meta’s pixel (below). Cloudflare Turnstile, on pages with the form, runs in Cloudflare’s own frame and may keep what it needs for the spam check there (see “The consultation form” above). When analytics load, the two tools, and Meta’s pixel where it loads, set these in your browser:
- Google Analytics:
_ga(tells one browser from another; lasts up to two years) and_ga_followed by an ID (keeps track of the current visit; lasts up to two years). Because its analytics may be used to measure Aaron’s ads (see “Ads and measurement”), Google’s tag may also set_gcl_auand, after a click on one of his Google ads,_gcl_aw(they note that a visit came from an ad, for that measurement; they last up to 90 days). - Microsoft Clarity:
_clck(tells one browser from another; lasts up to a year) and_clsk(joins the pages of one visit into a recording; lasts a day). Microsoft may also set its own cookies on its clarity.ms domain, such asCLIDandMUID. - Meta’s pixel (see “Meta’s pixel”):
_fbp(tells one browser from another; lasts 90 days) and, after a click on one of Aaron’s Facebook or Instagram ads,_fbc(holds that ad click’s ID, so Meta can tell the visit came from its ad; lasts 90 days). The site’s code writes_fbcitself, from the link’sfbclid, just before it removes that from the page’s address, and only where the pixel may load. When you send a request, the site’s program may pass_fbcto Meta with it (see “Matching a request to an ad”).
Turning analytics off on Your privacy choices removes the _ga, _ga_, _gcl_, _clck, _clsk, _fbp and _fbc cookies from this site and stops both tools, and Meta’s pixel, on that page. Your browser’s settings can block or delete cookies at any time.
Your choices
- You can browse the whole site without giving any personal information.
- You can turn analytics off, or back on, for your browser on Your privacy choices. Your browser’s Global Privacy Control setting turns them off too. Either one also stops Google Analytics from measuring Aaron’s ads in this browser, keeps a Google ad click from this browser from being reported to Google Ads, keeps Meta’s pixel from loading, and keeps a scrambled copy of your email or phone from going to Google or Meta with a request. Google also offers a browser add-on that blocks Google Analytics.
- You can clear your saved homes at any time, on the Saved homes page or by clearing your browser’s data for this site.
- You can unsubscribe from email alerts or a watched home in one click from any of their emails, and change or delete them, or delete everything about you, on the manage page linked from every one.
- You can stop mortgage rate emails in one click from any of them; that leaves your home alerts alone.
- You can stop the email guide for buyers in one click from any of its emails; that leaves your home alerts alone, and the guide stops by itself after its last email.
- To see, correct or delete what you sent through a form, including the copy in Aaron’s CRM, or to ask Aaron to stop contacting you, call, text or email him using the details below.
- Your browser can clear session storage at any time; closing the tab does too. Clearing your browser’s site data for aaronbenson.com also deletes the note of how you found the site.
Children
The site isn’t meant for anyone under 18, and Aaron doesn’t knowingly collect information from children.
Changes
If this policy changes, the date at the top of the page changes too.
Contact
- Call
- 602-785-5095
- Text
- 602-785-5095
- Office
- Realty ONE Group, 7975 N Hayden Rd, Suite A101, Scottsdale, AZ 85258