Trust center
We sell security tools, so our own house rules are public. This page says where your data lives, who touches it, how it is protected, and how to reach us when something looks wrong. The privacy policy covers what we collect and why; this page covers the machinery. Last updated: November 9, 2026.
Our platforms run on a virtual server operated by Contabo in France, in the European Union. Account and result data is stored in managed PostgreSQL databases run by Neon, on Amazon Web Services in the US East (Ohio) region. Cloudflare sits in front of every site for DNS, content delivery and firewall protection, so web traffic passes through Cloudflare's network on its way to us.
When you create an account we store your email address and a hashed password — never the password itself in readable form. When you use a tool, we store the input you submit and the result it produces, so your history is there when you come back. We keep request logs with IP address, browser type and time of request, and we use them to stop abuse and fix faults. When you buy a plan, we keep a record of the purchase. We never receive or store your full card number.
We keep account data while your account is open. Scan and report history stays until you delete it or close the account. If a retention period ever changes, this page changes with it — we would rather publish the real rule than a rounder number.
Email [email protected] from the address on your account and ask for deletion or an export. Deletion removes the account and its stored results. Exports are prepared by a person, not a machine queue, and sent to your account email. Business customers can also end processing under their agreement this way; see the business terms summary below.
In transit: every site is served over HTTPS with HSTS, so browsers refuse to fall back to an unencrypted connection. At rest: stored data sits in Neon's managed databases, which encrypt data at rest. Passwords are hashed with salted PBKDF2-SHA-256 and are never stored or logged in plain text. License keys are signed with HMAC and stored in our database only as SHA-256 hashes; API keys are likewise stored hashed and shown in full once, at creation. Service secrets live in server-side environment configuration — they are never shipped in page code or client downloads.
Ingenious AI is a small, single-operator studio, and that is a security property we state plainly: production systems are administered by one named operator, reached by SSH key, and there is no shared staff access to spread credentials across. Administrative functions inside the platforms are authenticated and gated on the server, not just hidden in the interface. Each processor below receives only the data its job needs.
These are the companies that run parts of the service. The list is the whole list; if it changes, this page is updated.
Stated without qualifications: content you submit to our tools — domains, code, files, text — is processed to produce your result and stored for your history. It is not used to train models, ours or anyone else's, and personal data is not sold. Ever.
Orders today are confirmed by a person, over WhatsApp or email, and a license key is issued for each billing cycle. Nothing auto-renews: each cycle is a fresh manual payment, so there are no surprise charges. That is the rule in our refund policy, and it is how the business actually runs.
When your team submits data to a platform, we act as your processor for that data: we process it only to run the tools you use, through the processors listed on this page, and for no other purpose. We will help with your customers' deletion and export requests through the contact below, and we delete your stored data when you close the account or end the agreement. A data processing agreement is available on request for business accounts — ask at [email protected].
The fleet is watched around the clock by an automated defense system that probes every platform's live posture and restores known-good protections when they drift. If an incident ever exposes customer data, we will email the affected customers without undue delay, saying what happened, what data was involved, and what we changed. Security contact for everything on this page: [email protected].
Found a vulnerability in one of our sites or platforms? Tell us at [email protected] with what you found and how to reproduce it, and give us reasonable time to fix it before publishing details. We read every report and we fix real problems. We do not currently run a paid bug-bounty program.