Why browser storage is used
SearchLink uses essential access cookies to recognize approved browsers and local browser storage to remember operational preferences. SearchLinkHQ has not enabled analytics cookies, advertising pixels, remarketing or session-recording tools. This notice is informational, not an “accept all” request for optional tracking. Location permission is separate and is not granted by reading this policy.
Current application storage
Storage implemented in the current version
Storage Purpose Current lifetime
__Host-sar-[incident ID] Responder registration and approved access in that browser. Contains a random session token, not a case report. Seven days from registration. Visits do not currently extend this expiry. Server permissions can end usable access sooner.
__Host-observer-[incident ID] Observer registration and view-only access using a random session token. Seven days from registration. Current observer access ends when the search closes, or approval is declined or revoked, even if the cookie remains stored.
sar-notices:… local storage Remembers which incident notifications have been marked read. No automatic expiry currently. Remains until browser storage is cleared or removed by the browser.
The application’s access cookies use Secure, HttpOnly and SameSite=Lax protections. A cookie remaining on a device does not mean its associated permission is still valid. Closing a browser window does not necessarily remove persistent cookies.
Staff sign-in and service providers
Dispatcher and administrator sign-in is currently provided through ChatGPT and the hosting platform. Their authentication and security storage is controlled by those services; SearchLinkHQ does not currently enforce a separate 30-day inactivity window. This table lists application-managed storage, not a claim to inventory every provider cookie. Provider cookies and lifetimes can differ. Consult the sign-in provider’s privacy policy for its practices.
Map, hosting and external communications services may receive your IP address and other request information when used. A public flyer visit does not itself register you as a responder or observer or request GPS. Cookies previously set on the same site may still be sent by your browser.
Planned access and cleanup rules
The following rules are agreed product requirements, not current functionality. They will be reflected as active rules after implementation:
- Responders: seven days from the last visit while the search is active, renewed on return. After closure, limited checkout access lasts no later than seven days after closure, with no extension for later visits.
- Dispatchers and administrators: 30 days of inactivity.
- Observers: access while the search is active and a fixed three-day read-only window after closure. Continued closed-search access is a roadmap feature.
- Logout, checkout where applicable, or revoked access ends the associated search access sooner. Search preferences clear on exit or closure, or after seven days without a visit. Limited completion access is separate from operational preferences.
Your controls
You can delete or block cookies and local storage using your browser’s site-data settings. Blocking essential cookies prevents registration sessions and approved access from working reliably. Clearing them may require new registration and dispatch approval. Signing out or losing authorization is not the same as physically deleting every cookie from the device.
Deleting browser data does not delete stored registration information, reports, photographs, GPS history or incident records. Contact the organization using the privacy contact above about those records. Any future optional tracking will require updated disclosures and appropriate controls before activation.
Contact and updates
Cookie questions go to the same organization privacy contact as other privacy requests. See the Privacy Policy for collection, sharing, retention and rights. Changes to this policy will be published with an updated effective date.