Skip to content

Cookie notice

Rightmark sets six cookies, all first-party and none for advertising. Our analytics set no cookies at all.

Updated

On this page

Six cookies, all first-party, none for advertising

All six cookies are set by rightmark.ai itself. None is used for advertising, and none is shared with another site.

  • Four keep sign-in and forms working safely.
  • One saves an intake form you have not finished.
  • One records which Rightmark Scout introduced you, so the right Scout is credited.

Our analytics set no cookies. This notice explains each cookie and how to remove it; the privacy notice explains the rest of what we collect.

Optional device notifications

When you enable device notifications, your browser keeps a Rightmark service worker and push subscription so it can receive updates while the page is closed. This does not add an advertising cookie. Turn notifications off in Rightmark, change your browser notification permissions, or clear Rightmark site data to remove the browser subscription. The privacy notice explains what we keep on the server.

How our cookies are built

Every Rightmark cookie belongs to the exact site that set it. None is shared across domains, so bscout.ai and rightmark.ai never read each other’s cookies.

Every cookie is sent only over HTTPS, and only with requests that start on our site or come from an ordinary link to it.

Five of the six cannot be read by scripts on the page. The one that can holds only a flag, so the header can show "Portal" while you are signed in. No cookie holds your name or email address.

Strictly necessary cookies

These cookies make sign-in and forms work safely. The site cannot work without them, so they are always on.

  • __Host-rm_session

    Strictly necessary
    What it does
    Keeps you signed in.
    What it holds
    A random id. Our database stores only a fingerprint of it.
    How long
    14 days at most, or 7 days without use, for owners, Scouts and buyers. 24 hours at most, or 24 hours without use, for staff. Signing out removes it.
    Readable by page scripts
    No
  • __Host-rm_pending

    Strictly necessary
    What it does
    Ties a sign-in link to the browser that asked for it, so a forwarded link does not sign anyone else in.
    What it holds
    A random id.
    How long
    30 minutes. Removed when you sign in.
    Readable by page scripts
    No
  • __Host-rm_csrf

    Strictly necessary
    What it does
    Stops another website from submitting our forms in your name.
    What it holds
    A signed random token.
    How long
    Until you close your browser.
    Readable by page scripts
    No
  • rm_hint

    Strictly necessary
    What it does
    Lets the header show "Portal" while you are signed in, without asking our server.
    What it holds
    Only the value 1. No identity and no secret.
    How long
    Ends with your session.
    Readable by page scripts
    Yes

A functional cookie that saves your form

A draft you never submit loses its personal fields after 30 days, whether or not the cookie is still in your browser.

  • __Host-rm_draft

    Functional
    What it does
    Saves an intake form you have started, so a reload or the back button does not lose your answers.
    What it holds
    A random draft id.
    How long
    30 days. Removed when you submit.
    Readable by page scripts
    No

The attribution cookie credits the Scout who introduced you

When you arrive through a Rightmark Scout link, the attribution cookie records that first introduction for 12 months, so the Scout who introduced you is credited if you later submit.

  • __Host-rm_attr

    Scout attribution
    What it does
    Records the Rightmark Scout whose link first brought you here, so that Scout is credited if you later submit.
    What it holds
    A signed id of the click record on our server. Not your name and not the Scout’s name.
    How long
    12 months, the length of the attribution window. A later Scout link does not replace it.
    Readable by page scripts
    No

How it works:

  • A Scout link on bscout.ai or rightmark.ai records the click on our server first. The click record holds the link used, the landing page, a device class, a coarse referrer class and a network address hash that is cleared after 30 days.
  • The cookie is set only on rightmark.ai, and only when you clicked the link yourself. Forced redirects and automated visits do not set it.
  • The first introduction counts. If you later follow another Scout’s link, we record that visit, but the cookie keeps the first one.
  • It lasts 12 months, the length of the attribution window.
  • It is first-party. We do not use it to follow you on other sites, and we do not share it with anyone.

It does not change what an owner is paid. Scouts are paid from Rightmark’s own income. Today the cookie is set on the first real click on a Scout link.

What our code keeps in your browser’s local and session storage

Besides cookies, our own code keeps thirteen small items in your browser’s local storage or session storage. An item in session storage belongs to one tab and is gone when you close it. An item in local storage stays until it is removed as described below or you clear this site’s data in your browser. None is used for advertising.

  • rm:lead-prompt-seen, in session storage. Holds a flag when you see or use an invitation to get started, so we do not automatically show another one in this tab. Your browser deletes it when you close the tab. Applies to visitors browsing public pages.
  • rm:lead-prompt-dismissed-at, in local storage. Holds the time you dismissed an invitation, so automatic invitations stay hidden for seven days. We ignore the saved time after seven days. It remains on your device until you clear site data or dismiss another invitation. Applies to visitors who dismiss an automatic invitation.
  • rm:lead-completed, in session storage. Holds a flag after a form displays its confirmation, so invitations stay hidden during this tab session. It contains no form answers. Your browser deletes it when you close the tab. Applies to visitors who submit a public form.
  • rm-theme, in local storage. Holds the word light or dark: the theme you picked with the day and night switch. It is saved only when your pick differs from your device’s own setting. Picking your device’s theme again removes it. Applies to every visitor who uses the switch.
  • rm:sign-in-email, in session storage. Holds the email address you typed on the sign-in page, so the page that asks for your code can fill it in. Removed when you finish signing in. Applies to people signing in.
  • rm.repo-check.handoff.v1, in local storage. Holds the Repo Check reports you saved on the Repo Check page and have not yet added in your portal: for each, the contents of its share.json file, its label, the id our server gave it and the time you saved it. A report leaves the list when you add it in your portal. We stop reading a report 24 hours after you saved it, and the next save or add in this browser deletes it. Applies to people who save a report with Repo Check.
  • rm:token-reload, in session storage. Holds the address of one page: a form page that opened without its security token and reloaded itself once to get one. Removed as soon as that page has its token. Applies to people using our forms, signed in or not: for example the contact form, the Scout application, and forms in the portal and the staff console.
  • rm:first-touch, in session storage. The campaign tags of the link that brought you, the domain of the site that sent you and the first page of your visit, so a form you send during the visit can say how you found us, and so our analytics can record the channel and campaign the visit came through. Your browser deletes it when you close the tab.
  • rm:appraise-answers, in session storage. Holds the answers you gave on the appraisal page for the kind of data you chose, so a reload, or a visit to another page and back, does not start the appraisal over. It never holds your name, email address, phone number or Scout code, or your consent to be contacted. Removed when you send your answers for a verified appraisal or make a share card, and your browser deletes it when you close the tab. Applies to people who use the appraisal. Draft for counsel review
  • Staff console items, in local storage and session storage. Pages of the staff console keep four items. Three hold what a page shows again after it reloads, such as a confirmation message, and the reloaded page reads them once and removes them. One holds the view a staff member last chose on a page, and our code never removes it. Applies to Rightmark staff.

You can remove all of them at any time by clearing the site data for rightmark.ai in your browser settings. Your theme then follows your device’s setting again, and a Repo Check report you saved but had not yet added in your portal is no longer in the browser.

This list matches the storage keys in our code, and a test keeps the two the same.

Analytics without cookies

We measure how the site is used with two cookieless analytics services, one from our hosting provider and one from our DNS provider. Neither sets a cookie on your device.

Both also record how fast pages load, with no cookie and no visitor identifier. The first page view of a visit includes the address of the site you came from, as that site reports it, never a Rightmark address with its query.

For public page views and browser events, our hosting provider also receives the source, medium and campaign labels of the link that brought you. We keep using those labels on ordinary public pages during the visit when the current page has no campaign tags. A new tagged link takes precedence. Pages whose addresses we shorten for privacy do not reuse stored campaign labels. We filter these labels and do not send the other details held in session storage.

The events we send carry no personal data. They record things like "appraisal started" with the data family, or "submission completed" with whether a Scout code was used, and the kind of channel the visit came through, such as search, social media or a direct visit. They never include names, email addresses or text you typed. The staff console does not load analytics at all.

Bot protection on forms

To stop spam and automated sign-in attempts, we run a bot check from our hosting provider on sign-in, intake, the Scout application, buyer requests, document requests and the partner widget.

The check loads when you first use one of these forms, not on every page. Our server passes it the request headers, never what you typed in the form.

Partner sites that embed our appraisal

Some partners embed our appraisal estimator on their own sites. The embedded estimator reads no Rightmark session, receives no session cookie and collects no personal data. If you ask for a reviewed estimate, it opens rightmark.ai in a new tab, where this notice applies.

The partner’s own site may use its own cookies. Its own notice covers those.

How to remove or block cookies

You can delete or block cookies in your browser settings. If you block the strictly necessary cookies, you cannot sign in or submit forms.

Signing out removes the session cookie and the hint. Submitting a form removes the draft cookie.

Deleting the attribution cookie stops it crediting a Scout from this browser. It does not delete the click record on our server. That record is not linked to you unless you submit, and its network address hash is cleared after 30 days. You can still type a Scout code on the intake form if you want a Scout credited.

Changes to this notice

When we add, remove or change a cookie, we update this notice and the date at the top. The list on this page matches the cookies in our code, and a test keeps the two the same.

Questions about cookies

Ask us about the data behind any cookie. Write with "Privacy" in the subject line.

Email hello@rightmark.ai