What you send is not stored.
Request content is processed in memory and discarded once the response is returned. We keep only the metadata needed to bill and to trace a response to the version that produced it. All processing takes place in the United States.
One path, in and out.
Request id, timestamps, token and search counts, price, the assessment version used, and the request trace.
When you ask for the public record, web searches are made about the other party you named, and about you only if you name yourself.
Keys, roles, sign-in, and the audit log.
Shown in full once; stored hashed; listed by prefix, creator, and last use; revoked instantly.
Owner, Admin, Developer, Billing, Viewer. Developers see only their assigned projects. Billing never sees keys.
Email is verified before anything else. Passwords are stored as salted hashes. Sessions are held server-side and can be revoked.
Organization creation, key creation and revocation, payment-method changes, and sign-ins, each with actor, IP, and timestamp.
Cards are entered on a hosted payment page and stored by the payment processor. We hold a payment-method reference, not a card number.
Email verification before payment, a rate limit for the first day, a usage ceiling before the first charge, and a small first charge that validates the card.
Data stays in one region.
Every assessment names the version that produced it. Versions are immutable, so a reading can be attributed later without the content, which was never kept.
Synthetic, non-sensitive test assessments run against production on a schedule, with uptime checks and alerting. Customer content is never sampled.
Ask for the security overview.
If you are running a vendor review, give your reviewer the Viewer role and they can read the audit log and settings without changing anything. Report a vulnerability to hello@malintentdetector.com.