Privacy Policy
AidNow is designed to help in a crisis without collecting personal data. This page describes what the platform does today — honestly — and what may change in the future.
Summary
- No user accounts
- No analytics or tracking of individual users
- No third-party advertising scripts or social widgets
- No sale or sharing of personal data with third parties
- Some preferences are stored on your device (checklists, banner dismissals) — they never leave your browser
What we do today
No accounts or profiles
AidNow does not require you to sign up, log in, or provide your name, email, phone number, or location to use emergency guidance.
No analytics or tracking
We do not run analytics services, advertising trackers, or behavioural profiling. Some project documentation mentions privacy-friendly analytics tools such as Plausible, but no analytics are implemented in the current codebase.
Search queries
When you search for emergency guidance, your query is sent as a GET request to /api/search?q=.... Search is processed to return matching results. We do not log or store search queries, and we do not build search history profiles.
Search requests are rate-limited by IP address to prevent abuse. This is a temporary, in-memory limit — not a persistent record of who searched for what.
Cookies
AidNow uses a small number of cookies. None are used for advertising or cross-site tracking.
- cep_draft_preview — Used only when draft preview is enabled. HttpOnly, 7-day expiry. Lets authorised reviewers see content awaiting professional review.
- cep-admin-token — Admin session cookie for editorial staff only. HttpOnly, scoped to
/admin. Regular visitors never receive this cookie. - cep-admin-csrf — CSRF protection for admin actions only. HttpOnly, scoped to
/admin.
Browser storage on your device
Some features save progress locally so you can pick up where you left off. This data stays in your browser and is not sent to our servers.
- Prepare checklists — Checked items on prepare guides (localStorage)
- Inspection checklists — Safety inspection progress on asset pages (localStorage)
- Draft preview banner — Whether you dismissed the draft banner for this browser session (sessionStorage)
- Admin review decisions — Editorial review notes stored locally during admin review workflows (localStorage, admin users only)
Offline caching
AidNow uses a service worker to cache emergency pages on your device so they remain available without an internet connection. Cached content is stored locally for offline access only — not for tracking, reporting, or identifying you. Learn more about offline access →
Emergency guidance views
Reading emergency guidance is not logged or tied to an identity. We do not record which scenarios you view, when you view them, or how long you spend on a page.
No third-party scripts
The public site does not load third-party tracking scripts, social media widgets, chat widgets, or advertising networks.
What we may do in the future
As AidNow grows, some features may require additional data handling — for example, user accounts for saved preparedness plans, optional analytics to understand which guidance is most needed, or community features. If we add any of these, we will update this policy before they launch and will not retroactively apply new collection to existing users without notice.
Any future analytics would be privacy-preserving by design — aggregated, not individual-level profiling.
Your choices
Because most data is stored locally in your browser, you can clear it at any time through your browser settings (clear site data, cookies, or local storage). Clearing data will reset checklist progress and dismiss preferences.
You can disable or unregister the service worker through your browser to stop offline caching.
Contact
Questions about this privacy policy?
Contact information will be published here when available.