Port Ludlow Emergency Committee
Privacy
What this site keeps, what it never publishes, and the choices you have. Written to be read, not skimmed past.
Port Ludlow Emergency Committee
What this site keeps, what it never publishes, and the choices you have. Written to be read, not skimmed past.
This page covers the PLEC portal — the pages under portludlow.org/PLEC. The rest of portludlow.org belongs to the Port Ludlow Village Council and is run separately.
The street you type is sent to our server, matched there, and answered. The portal does not keep a record of what you searched or who searched it.
To stop someone from copying the whole village one street at a time, the server briefly counts recent lookups from each internet address — that count lives in memory for about a minute and is then gone.
What you get back is the Block Captain's name (and email address, where they've provided one) for the matching area only. The preparedness videos are just as anonymous: no sign-in, and nothing recorded about who watches them.
Like nearly every website, the services that deliver this one keep short-lived technical logs of requests for security and troubleshooting — see "The services this site runs on" below.
If you send the volunteer form, we keep what you typed — your name, email, optional phone number, your address, and anything you added — in the committee's roster, marked as an interested prospect. The address is matched against the response area map so the Chair knows which street you are on; it is never shown on the public lookup.
Two emails are sent: an acknowledgment to you, and a notice to the Chair and the Block Captain Coordinator so someone actually follows up. That's the whole journey. If you change your mind, one email to the Chair removes you.
No passwords. We email a six-digit code to the address on the roster; it expires after 15 minutes.
One cookie. Signing in sets a single sign-in cookie so you stay signed in — scoped to this portal's own pages, lasting up to 180 days. It identifies your session and does nothing else. There are no tracking cookies. The fact that you signed in, and when, is written to the committee's activity log, because a working sign-in is the only proof that the address we hold for you still reaches you. What you then read is not recorded; only what you complete.
Asking for a sign-in code is recorded too — the address typed into the box, and whether we hold a record with it. We added this because a volunteer telling us "I asked for a code and nothing arrived" was otherwise impossible to tell apart from a mail failure, when nearly always the address typed is simply not the one on file. The reply on screen is deliberately identical whether or not we know the address, so that box can never be used to find out who is on the roster; only the committee’s administrators can see what was typed.
Training records. Your training page records which modules you've completed and which videos you've watched while signed in — that is its purpose. In-person items like a tabletop exercise or radio practice are recorded for you by a coordinator. Online modules count as current for a year, so a completion also carries the date it comes up for renewal.
Knowledge-check attempts. Every attempt at a knowledge check is kept — the date, the score, and which questions were missed — including attempts that didn't pass. We keep them so we can tell a badly worded question from a genuinely hard one: if most people miss the same question, that is nearly always our fault, and we would rather fix the question. There is no limit on retakes and no consequence for a low score. It is not an exam, nobody is ranked, and a coordinator seeing that you took a module three times is seeing someone who kept at it.
For each volunteer, the roster holds: name, email, phone, address, role and response area, training records, event participation, and any notes. It exists to run the Block Captain program — knowing which streets are covered and who is trained.
Addresses and phone numbers are committee-only, and deliberately so. The public lookup answers one street with a Block Captain's name and, where they have given one, an email address. It has never carried a phone number or an address and it never will — that would turn an answer about your own street into a record of where a named neighbour lives. Both come out only in the roster export, which needs an administrator's sign-in. We hold addresses because the response areas are drawn from them: redrawing the map one day means knowing which homes are where, not just which area each volunteer was filed under.
Only the committee's administrators — the Chair and coordinators — can see it, through a sign-in-protected admin portal. Changes to it are logged, so there is a record of who changed what.
What the public can see is deliberately small: the captain for a street someone looks up, the list of areas with no captain yet (which names nobody), and the committee members on the home page.
Five companies, all based in the United States, each doing one job:
Each keeps the short-lived technical logs normal to running such a service. None of them is given the roster to use for anything of their own.
You can correct your own name, email, phone number and address yourself: sign in and they are under Your details. The Chair and the Block Captain Coordinator are told what changed, so that a new address can be matched to the right Response Area. Changing your email sends a code to the new address, and nothing changes until it comes back; once it does, a short note goes to your old address too, so you would know if it had not been you. Email the Chair at PLEC.Chair@gmail.com to ask what else we hold about you. A volunteer can also step down without asking anyone: the "Stepping down?" section on the home page takes your email, confirms it with a code we send you, and removes you from the roster (the reason box there is optional). A removed volunteer no longer appears in any lookup; the training record stays on file as the evidence their street was covered while they served.
Last updated September 20, 2026. If how this site handles information changes, this page changes with it.