Quoroom.org

Quoroom.org

Privacy policy

This describes what actually happens on this site, not what a template says usually happens. One third-party script loads on every page except the request and claim forms, and is named below. If you send a request for quotes we keep what you typed on our own server and, with your tick, send it to any inspectors of elections listed on Quoroom.org at the time.

Effective 2026-11-19 Cookies measurement only Analytics Google Tag Manager Data sold none Passed on only to the inspectors you ask us to send a request to

The short version

One third-party script loads on every page except the two with a form: Google Tag Manager, which we use to count which pages get read. It may set a measurement cookie. There is no advertising, no pixels, no fingerprinting and no session recording, and nothing is sold or shared for advertising. Fonts are served from this site rather than from Google. The personal information we hold is what you put in the request form or the claim form, and our server's access log described below. We do two things with a request: pass it to any inspectors listed on Quoroom.org at the time when you tick the box, each of whom then holds their own copy, and reply to you.

Reading the site

Every page here is a static file. Nothing is personalised, so nothing needs to know who you are.

Our web server writes an ordinary access log: your IP address, the time, the page requested, the response code, the referring page if your browser sent one, and your browser's user-agent string. That log exists to keep the server running and to see abuse — it is not analysed for behaviour and it is not joined to anything else. It is rotated daily and kept 14 days, after which it is deleted.

Measurement

Every page on this site except the two that hold a form loads Google Tag Manager (container GTM-WR8H797R) from googletagmanager.com. It is the one third-party request a page makes, and it happens as the page opens, before you do anything.

It does not load on the request page or the claim page. A tag in the container can read what is typed into a page, so the pages where you type your name and email make no request to a third party at all.

Making that request necessarily tells Google your IP address, the page you asked for, and your browser's user-agent string — that is true of any request to any server, and it happens whether or not a tag then runs.

The container holds measurement tags, and a measurement tag may set a cookie in your browser so that two visits can be told apart. We use this to see which pages are read and which are not. We do not run advertising tags, we do not use it to build a profile of you, and we do not link it to an advertising account.

If you would rather it did not load: any content blocker stops it, and so does your browser's tracking protection. Nothing on this site requires it — every page, the calculator and the enquiry form all work with it blocked.

The deadline calculator

The calculator runs entirely in your browser. The meeting date you type is never sent to us — the arithmetic happens on your machine.

It does put that one date in your browser's sessionStorage, under the key quoroom:meeting, so that if you go on to the enquiry form the date is already filled in. Session storage is cleared by your browser when you close the tab, it is readable only by this site, and it never reaches us.

The request form

If you send a request for quotes, we store exactly the fields you filled in:

Who receives a request for quotes

With the box ticked, we send your request by email to each inspector of elections listed on Quoroom.org at the time (the request page shows how many are listed), one message each, with your address as the reply address, so that any reply comes straight to you. The confirmation we send you names every recipient. Each inspector is a separate business: they hold their copy of your request under their own responsibility, not ours, and we do not see any reply. If you would rather they did not keep it, write to us and we will ask each of them to delete it. Each inspector decides that under its own privacy practices; we cannot delete a copy we do not hold.

We take nothing from inspectors, and they pay us nothing. Our founder takes no new appointments as an inspector of elections in California.

That record is written to a file on our own server, readable only by the account that runs the site. It is not sent to a third-party form service, a CRM, or a mailing list provider, because we do not use any.

What we do not do with it

We do not sell it, rent it, or trade it, and we share it with no one but the inspectors you asked us to send it to. We do not add you to a newsletter. We do not use it to advertise to you anywhere. We do not use it to train anything.

Two things the form does that are worth naming

A hidden field. The form carries a field named company that is hidden from you and visible to automated submitters. If it arrives filled in, the message is discarded. If you are using a screen reader or an unusual browser and it is not hidden from you, leave it empty.

A rate limit. We count recent submissions per IP address to stop a flood. Those counts live in memory only, for an hour, and your IP address is not written into the stored enquiry.

How long we keep a request

Until it has served its purpose. We keep a request for quotes long enough to answer questions about who received it and to pass on a deletion request to the inspectors, 12 months, and then delete it. You can ask us to delete it sooner, at any point, and we will.

Your choices

Write to privacy@quoroom.org and ask for any of the following. We will act on it and tell you we have, normally within a few business days.

  1. A copy of what we hold about you.
  2. A correction if something is wrong.
  3. Deletion of your enquiry.
  4. An explanation of why we still hold something, if we think we should.

We will not ask you to create an account to exercise any of these, and we will not charge for it.

On the California Consumer Privacy Act

We will say this plainly rather than imply more than is true. The CCPA, as amended by the CPRA, applies to businesses above thresholds — annual revenue, or the personal information of 100,000 or more consumers, or deriving half of revenue from selling personal information. This site is nowhere near any of them, so the Act does not currently impose its obligations on us.

We honour access and deletion requests anyway, as set out above, because the right thing to do does not depend on a revenue threshold. If we ever cross one, this page will say so and will set out the statutory rights in the form the Act requires.

Links out of the site

The reference pages link to the Legislative Counsel's own publication at leginfo.legislature.ca.gov and, for verification, to california.public.law. Those are other people's sites with their own practices. Nothing about you is passed to them by us; following a link is an ordinary visit made by your browser.

Children

This site is addressed to association boards, managers and owners. It is not directed at children, and we do not knowingly collect anything from anyone under 16.

Security, stated honestly

The site is served over HTTPS. The enquiry file is stored with permissions that restrict it to the account running the service, and the service itself runs with the operating system's privileges stripped back — no new privileges, a read-only filesystem apart from the one directory it writes to, and a memory cap.

No one can promise a server will never be breached. What we can say is that the amount of personal information here is deliberately small: there are no accounts, no passwords, no payment details and no browsing profiles to lose.

Changes

If this policy changes, the effective date at the top changes with it, and the change is described here rather than applied silently. The current version is dated 19 November 2026. It names the claim form and the server's access log among the personal information we hold, says that our founder takes no new appointments as an inspector of elections in California, no longer covers a paid engagement with us, and no longer mentions the Global Privacy Control signal. The version of 3 November 2026 stopped loading Google Tag Manager on the request page and the claim page. The version of 2 November 2026 added Google Tag Manager and its measurement cookie (under Measurement) and the sending of a request to the listed inspectors when you tick the box (under The request form); the version of 10 October 2026 had neither.

Related