K9 SAR Log

Feature

Field SOS

Field SOS in K9 SAR Log emails configured emergency contacts with handler, dog, and location context from the open session.

It does not fan out to every account. Recipients come from SOS_RECIPIENTS or the default contact list (one address when unset). Rate limits are 3 per IP and 3 per email in the guard window.

Who receives an SOS

SOS_RECIPIENTS on the Pages project overrides the default. When it is unset, DEFAULT_SOS_CONTACTS from sos.ts is used. Signing up does not put you on the SOS fan-out list.

That split is deliberate: an account can sign in without receiving every emergency email.

Rate limits that keep the button from becoming spam

requestGuard.ts caps SOS at 3 per IP and 3 per email in the rate-limit window. Sign-in OTP separately allows 5 attempts per challenge before the code is burned.

The SOS control is for a real field emergency contact path, not a chat ping.

SOS and auth caps from requestGuard / k9Auth
CapValue
SOS_IP_LIMIT3
SOS_EMAIL_LIMIT3
OTP_MAX_ATTEMPTS5

What it does not do

SOS is an email to people you configured — not a 911 dispatch product.

Common questions

Who gets a K9 SAR Log SOS email?

Configured SOS_RECIPIENTS, or the default contact list in sos.ts when that secret is unset — not every account on the service.

How many SOS messages can I send?

The API allows 3 per IP and 3 per email in the rate-limit window.

Does SOS text 911?

No. SOS sends email to configured contacts. Call local emergency services separately when you need them.

Does signing up put me on the SOS list?

No. SOS recipients are a separate configured list, not every account that can sign in.