nomad-days

Privacy & security model

Nomad Days has no server, no accounts, no analytics and no crash reporting. Everything stays on the device unless the user exports a backup.

Data at rest

What Where Protection
Profile, passports, trips, custom rules nomad-days.db (SQLite) Encrypted with SQLCipher (AES-256) using a random 256-bit key
Database key iOS Keychain (WHEN_UNLOCKED_THIS_DEVICE_ONLY) / Android Keystore Never synced, never exported, never leaves the device

Reminders

Reminders are local notifications, scheduled on the device by a small module in modules/local-reminders:

There is no push service, no Firebase and no network use. The app deliberately doesn’t use expo-notifications, because on Android it bundles firebase-messaging, which F-Droid rejects. The Native build CI workflow fails if any com.google.firebase, com.google.android.gms or Play Services dependency appears in the Android build.

Reminder text can show a region name and dates on the lock screen. They are only scheduled while reminders are switched on in Settings.

Encrypted backups (.nomadbackup)

A JSON envelope looks like this:

{
  "format": "nomad-days-backup",
  "version": 1,
  "kdf": { "name": "scrypt", "N": 65536, "r": 8, "p": 1, "salt": "<16 bytes hex>" },
  "cipher": "xchacha20poly1305",
  "nonce": "<24 bytes hex>",
  "ciphertext": "<hex>"
}

Secret scanning

Two layers stop credentials reaching the repo:

Rules live in .gitleaks.toml. That file uses gitleaks’ default rules plus one that catches hard-coded passwords and passphrases. Run npm run secrets:scan to scan the history yourself.

For a false positive, add // gitleaks:allow to the end of the line. Never commit a real secret, even temporarily: it stays in git history.

Reporting a vulnerability

Please open a private security advisory on GitHub rather than a public issue.

Dependency audit exceptions

CI fails on any high or critical advisory in production dependencies (scripts/ci/audit.mjs). When an advisory has no fix yet and doesn’t affect the shipped app, it can be accepted in .audit-allowlist.json with a reason and an expires date (about two months out). CI fails again once it expires, so each exception gets re-checked: fix it if a patch exists, extend it with a new reason, or remove it. CI also warns when an exception is no longer needed.