Security
Last updated November 19, 2026
You send us identifiers that matter to your business and to the people behind them. This page describes how we approach protecting them. We would rather describe our practices plainly than list badges.
Draft. This page is a working draft that has not yet been reviewed by counsel. It is not final and should not be relied on until this notice is removed.
Encryption
- All traffic to the website, dashboard, API and MCP server uses TLS. Plain HTTP requests are redirected.
- Data is encrypted at rest by our infrastructure providers.
API keys and sign-in
- API keys are shown once at creation and stored as hashes. We cannot show you a key again, only replace it.
- Keys can be named, scoped to a purpose such as one AI client, and revoked instantly from the dashboard.
- MCP clients can authorize with OAuth, so you do not have to paste a long-lived key into a third-party tool.
- Test keys return sample data and never spend credits.
Access
- Access to production systems is limited to the people who need it and is logged.
- Team seats let you give colleagues their own sign-in instead of sharing one.
Data handling
- Lookup inputs are used to perform the lookup and are not sold or used to build marketing lists.
- Results are cached for 7 days to provide free repeats. History and bulk files remain until you delete them.
- You can delete lookup history and bulk results from the dashboard.
What we do not claim
We do not currently claim any third-party certification or attestation. If your procurement process needs a specific report or a completed questionnaire, contact us and we will tell you what we can provide.
We are not a HIPAA business associate. Do not send protected health information.
Reporting a vulnerability
If you believe you have found a security issue, write to 1lookup@volods.com with the details and steps to reproduce. Please give us a reasonable chance to fix it before disclosing it publicly, and do not access data that is not yours.