Seven forms, and the questions each one adds
Thirteen pages stand on this site and seven of them carry a form. The other six — the auto, fire, FAIR Plan, flood and liability guides, and this page — carry none at all. Four lines repeat on every form that does exist: a full name, an email address, a telephone number you may leave blank unless you want to be answered by telephone, and a choice between an answer by email and an answer by telephone. What each form adds on top of those four is set out below, page by page, in the labels the page itself prints.
- Home page
- A topic, chosen from the seven coverage subjects this site publishes plus Privacy, and a written question.
- Aerospace tenancy
- What else stands on the property besides the house, and a written note.
- High desert water
- A ZIP code, whether separate flood cover is in force today, and a written note.
- Plant 42 heritage
- When the rebuilding cost was last looked at, and a written note.
- Homeowners
- A ZIP code, whether the house has been altered since the policy was written, and a written note.
- Earthquake
- What became of the last written earthquake offer, and a written note.
- Quote request
- A ZIP code, a topic from the same list the home page offers, what has brought the question up now, and a written request.
That is the whole of it. No form here asks for a Social Security number, a driver-license number, a card, bank or account detail, medical information, a password, or an alarm or entry code, and none of those belongs in a written note either. No page asks for a street address; where a form asks for a ZIP code, that is the nearest thing to a location anything on this site collects.
From the send button to one agency mailbox
A form that passes every check below leaves this site once, as a single email message to one fixed agency mailbox. Where that mailbox is, is held by the sending service and not by the page, so nothing a visitor edits can point a message somewhere else. The message carries your answers under the same labels the page printed, two reference numbers — one minted by this site when it accepted the form, one minted by the sending service when it built the message — the time the sending service received it, the name of this website, and the address of the page you wrote from. The email address you typed is set as the reply address, so an answer comes back to you, and no copy is filed in a sent folder.
You are told a note was sent only once the sending service has accepted it for delivery. If it refuses, that confirmation never appears and nothing is quietly tried again behind the scenes. This website stores none of it: form answers go to no database here, to no storage inside your browser, and to no ordinary application log. Once the message is in the agency mailbox it keeps whatever retention the agency applies to the rest of its mail, and this site lays no schedule of its own on top of that.
The checks that run before a form will send
Every form is issued a stamp when you press send, minted for that page and that visit, and the page has to find a number which, combined with the stamp, produces a digest beginning with a fixed run of zeros. That work is checked again here when the form arrives, and a stamp stays usable for five minutes and no longer. Three timing rules sit on top of it: a form sent within a few seconds of the page opening is refused, a stamp younger than those same few seconds is refused, and a page left standing open for more than two hours is refused as stale. A field placed off-screen, which nobody filling the page in ever sees or touches, has to arrive empty. Every answer is measured against the same limits the page declares on the control you typed it into. Two counting limits apply as well: one on how many requests reach a single form from one network source, and one on how often the same email address is used. Each of the two is counted against a one-way digest of the value rather than a kept copy of it. Your network address runs those checks and ties a stamp to the connection it was issued to; it is not carried into the message that is sent.
What a refusal tells you, and what it does not
A refusal never names the check that stopped it. It is not one flat line for everything either: three different sentences can come back. When an answer falls outside the limits its own field declares, the reply asks you to look over the marked entries and send again. When one of the two counting limits has been reached, the reply asks you to give it a moment before sending again. Everything else — a page gone stale, a stamp past its five minutes, work that does not hold, a message the sending service would not take — comes back as the same general instruction to reload the page, look over what you entered, and send it again. Your browser adds two marks of its own before anything is sent at all: one beside a field it can already see is wrong, and one asking for a telephone number when you have chosen an answer by telephone and left that line blank.
Recorded calls
A telephone call may be recorded for training or quality assurance. If you would rather it were not, ask at the start of the call not to be recorded. Recordings and client information are not shared with third parties or affiliates without legal authority. Within the agency, client information serves agency business.
Announcements and text messages
Agency announcements can be stopped at any time, and the section below headed “Asking a privacy question” says where to ask. Should the agency ever invite you to receive text messages, that text-message invitation will name the brand, set out the expected message frequency, say that message and data rates may apply, and include HELP and STOP instructions. Nobody has to accept texts in order to buy insurance.
Visitors under thirteen
Nothing here is aimed at children, and no personal information is knowingly collected from anyone under thirteen. Where a child under thirteen wants to read these pages, a parent or guardian should give permission before using them.
Counting visits, without a cookie
Visits are counted over a path on this site’s own domain, and no cookie is set to do it. A browser sending a Do Not Track or a Global Privacy Control signal is left out at both ends of that: the page queues no measurement and fetches no counting script, and a counting request that arrives despite the signal is answered empty and thrown away before its contents are read and before this site has looked at its own settings.
For every other visit a reading is rebuilt here from a fixed list rather than trimmed down from what arrived, so a value that is not on the list has no route onward at all. On the list are the page address with its query and fragment stripped off, the page title, the referring address stripped the same way, the screen size, a short run of yes-or-no flags for what the browser can display, and the counters, timestamps and clock reading that a page view carries. Two further things travel beside a reading, and each only when your browser actually sends it: the browser and device description, and a stated language preference. Neither is invented here when the browser says nothing. Your network address travels with the reading too, and its last two bytes are dropped before anything is stored; the full address is never kept, and that shortened form is the only basis for a location estimate, which is coarse enough to point at a general area and no closer than that. Nothing you typed into a form is part of a reading. Your browsing is not joined up across other websites, and return visits are not tied to one another by a lasting visitor identifier. Raw visit records are deleted ninety days after they are written, while the totals counted from them may outlive that.
The outside services in the path, by what they do
Outside help is named here by function and never by product. One provider sits in front of everything: it carries each request that reaches this site and runs both the form checks and the counting path described above, so a form answer crosses it on the way out. A sending service takes the finished email message and puts it in the agency mailbox. The counted visits themselves are held by measurement software the agency runs and reads for itself. That is the entire list. The counting path never carries a form answer, and nothing this website collects goes to an advertising network, to a data broker, or to any service that builds profiles.
Reading without sending anything
Every page here can be read end to end without a form ever being sent. A Do Not Track or Global Privacy Control setting in your browser switches visit counting off for this site on its own, with nobody to ask and nothing to sign up for.
Asking a privacy question
Questions, corrections and requests to stop announcements all travel the same way: through this site’s own quote request form, with Privacy chosen as the topic. There is no separate privacy form to hunt for, and a note sent that way lands in the same agency mailbox everything else does.
When this statement changes
Practices change and so do the legal duties behind them, so the agency may revise this statement, and visitors should review it periodically. The effective date near the top of this page is the one to check against.