Security, described the way we would want to read it about someone else

Two products, two very different risk shapes. ChatAdmin makes real changes to Microsoft Azure, so its security story is about control: who approved what, under which identity, with which permissions. The Planning Data Auditor for Microsoft Dynamics 365 Supply Chain Management reads commercially sensitive planning data, so its story is about boundaries: the data never leaves your machine, and you can verify that yourself.

One thing to know before anything else on this page: Neopiq holds no security certifications. The section at the bottom says exactly what that means.

Architecture and data flow

Where each product runs, what moves, and what never does.

Planning Data Auditor · free, browser-only

Client-side by construction — and checkable, not just claimed

The Planning Data Auditor is a web page that reads your Dynamics 365 extract files locally, applies its rule library, and renders findings in the same tab. There is no upload, no account, no login, no cookie, no analytics, and no server that receives anything. Nothing is stored between runs — closing the tab is the delete button.

You do not have to take our word for any of that. Two tests anyone can run: open your browser’s network tab before loading your files and watch no request carry your data anywhere, or pull the network cable (or switch to flight mode) after the page has loaded and run the whole check offline. It works, because there is nothing to send.

What crosses the boundary: nothing. Your extracts, your findings, and the fact that you ran the check all stay with you.

ChatAdmin · acts inside an Azure subscription

The compute goes to the resources, not the other way around

ChatAdmin is built to run inside the Azure subscription it administers — that is the deployed model its managed-identity mode exists for. A conversation turns into specific, enumerated operations against Azure Resource Manager; in the browser chat, every operation that would change anything is shown to a person on an Approve / Reject card and does not run without approval. If nobody answers within five minutes, it declines by itself. Read-only listing runs without interruption.

Today ChatAdmin has no sign-up, no login and no multi-tenancy, and it has only ever run against Neopiq’s own subscription. No customer environment and no customer data are behind it. The full list of what it can touch, operation by operation, is on the permissions page — including the parts we are not yet happy with.

What crosses the boundary: instructions in, results and an audit trail out. It pulls nothing out of the subscription it works in.

This website itself

The site you are reading is static pages with no scripts, no login, no contact form, and no account system — there is no customer database behind it to breach. What little there is to say about data on this site is in the privacy notice.

Access and authentication

ChatAdmin has two sign-in modes to Azure, and which one is in force depends on how a deployment is configured. The default is a certificate-based service principal: the agent authenticates with a certificate whose private key is held on the runtime host — in the machine’s certificate store or a key file — so no passwords and no client secrets exist anywhere, but key material does exist on that host and must be protected there. The second mode, built for deployments hosted inside Azure, is managed identity: the platform issues short-lived tokens and no credential exists in the container image, in configuration, or on disk. In both modes tokens are cached only in memory, and the code never logs, prints, or returns them. The agent is also guardrailed against ever creating identity credentials — requests to create app registrations, service principals, client secrets or certificates are refused before any Azure call is attempted, as are requests to output private key, certificate or token material.

Human access is the honest gap to state: the chat front-end has no user login of its own and is designed to sit behind an authenticating front door. Because ChatAdmin currently runs only against Neopiq’s own subscription, the people who can reach it today are the people who operate it. Related, and stated plainly on the permissions page: the audit trail records every action, but does not yet record which human approved it.

The Planning Data Auditor has no access to control. No account, no credentials, no session on our side — there is nothing to authenticate to.

Data handling and residency

Planning Data Auditor: your data stays on the machine you run it on, in the country it is already in. We never receive it, so we cannot store it, share it, lose it, or be compelled to produce it. There is no retention policy because there is no retention.

ChatAdmin: the resources it creates live in whatever Azure region the administrator names in the conversation, and every action is confirmed against a named subscription before it runs. Its audit trail is structured JSON — timestamp, operation, target resource, result — with a redaction pass that strips anything that looks like secret material before a line is written. Passwords, SSH keys and workspace keys supplied in a conversation are masked on the approval card, excluded from the audit log, and never echoed back in results.

This company: Neopiq GmbH is a Swiss company; the e-mail you send us is handled as the privacy notice describes.

Reporting a vulnerability

If you have found a security problem in this website, in the Planning Data Auditor, or in ChatAdmin, we want it reported more than we want it polite. Write to contact@neopiq.ai with a subject line starting SECURITY — there is deliberately no separate security alias to guess at today, and marked mail to that address is read first. For anything actively dangerous, call 0041 78 223 6716 as well.

Useful in a report: what you found, where, how to reproduce it, and what you believe the impact is. We read security mail with the same first-response target as support — one business day, a target rather than a contractual promise — and we will tell you what we did about it. We do not run a bug bounty and will not pretend to; credit, if you want it, we will give plainly.

Certifications and compliance posture

We hold none, and we will not imply otherwise

Neopiq has no SOC 2 report, no ISO 27001 certification, and no security certifications of any kind. You will not find trust badges on this site, and we do not describe ourselves as “compliant” with frameworks we have never been audited against. If your procurement process requires a certification, we will not pass that gate today, and it is better that both of us know it now.

What we do instead, until certifications are worth their cost at our size, is make the claims themselves checkable:

The Planning Data Auditor is built so its central security property — nothing leaves your machine — can be verified by you, in minutes, without trusting us.
ChatAdmin’s scope is enumerated operation by operation on the permissions page, from the code that ships — including the current over-broad role and the unrecorded-approver gap, because a scope document that hides its weak points is marketing.
In the browser interface, every mutating action ChatAdmin takes passes a human approval gate that fails closed: silence is a no. The one exception is stated on the permissions page: the operator’s own terminal interface has an explicit auto-approve flag, which the browser flow does not have.
When something is not built yet, this site says “not yet” instead of writing it in the present tense.

The permissions page is the real test of this one

Anyone can write a reassuring security page. The page that lists every operation an agent can perform against your cloud, and why, is harder to fake.

Read the permissions page Verify the free check yourself