NUBack home

Security Controls

Effective date: July 22, 2026 | Last updated: July 22, 2026

Security controls and safeguards for NU Nothing Unseen.

Mission

NU exists to make records, source trails, and AI-readable context easier to find. Search and AI assistants can only work with what they can read. NU focuses on public records, court documents, legislation, studies, source-backed articles, captions, text descriptions, and citations so useful information is not invisible just because it is buried, visual, or poorly described.

NU is founder-led by Austin Little, an indie vibe coder and senior code viber, with Claude, Codex, and local Ollama/Gemma agents assisting production, review, search, and iteration. The agents help move fast; Austin owns the direction, judgment, and final calls.

Access Controls

Access to production systems, providers, and connected services should be limited to authorized users and least-privilege credentials.

Security in Transit

Public pages, APIs, account flows, and connected-account callbacks should use HTTPS/TLS.

Secrets and Tokens

API keys, OAuth secrets, database URLs, search keys, webhook secrets, and provider tokens should live in encrypted secrets or provider-managed environment variables, not public repos, static bundles, logs, or pages.

Approval Gates

Workflows that publish pages, commit code, deploy, send campaigns, change DNS, charge money, or alter connected systems should preview changes and require explicit approval unless the owner intentionally enables automation.

Responsible Testing

Only run diagnostic, search, email, DNS, or security tests against systems you own or are authorized to test.

Report Issues

Report suspected security issues through the email link on the NU home page. Do not send secrets in plain email unless a secure exchange method is arranged.