Security and data handling
Read live. Not kept. Always logged.
mcpbizapps reads business app data live and does not store it. People sign in without passwords, credentials are encrypted in AWS Secrets Manager, every change is previewed and approved where your rules require it, and every request is logged under a named person for one year by default.
What mcpbizapps stores, and for how long
| Business data | Read live from your business app when the assistant asks, returned, and not stored. |
|---|---|
| Conversations | Your prompts and the assistant’s replies never pass through mcpbizapps storage. |
| Prepared changes | Kept encrypted until confirmed or decided: at most 10 minutes for a confirmation, 24 hours for an approval. Deleted when created, declined or expired. |
| Credentials | The integration user’s password is encrypted in AWS Secrets Manager and never shown again. |
| Sign-in | No passwords. People sign in with their work email and a 6-digit code that works for 10 minutes. |
| Audit log | Who, which tool, which connection, the result and the time. Personal fields and free text are removed from request details. Kept one year by default. |
| Region | Stored in AWS in the United States (N. Virginia). |
| Offboarding | Deactivating a person cuts off every AI client on their next request. Removing a connection deletes its credentials. |
Controls
Identity and sign-in
- Only people an admin invites can sign in.
- Sign-in by work email and a 6-digit code that works for 10 minutes; no passwords to steal or reuse.
- AI clients connect through standard secure sign-in. Each connection works only for mcpbizapps and one app.
- Deactivating a person cuts off every AI client on its next request.
Least privilege
- Roles decide which tools each person may use; the assistant only sees those tools.
- One dedicated integration user per app connection, with only the access the tools need.
- Admins can switch each kind of change off while keeping look-ups.
Governed changes
- Every change is prepared as a preview and needs the person to confirm it.
- Approval rules by amount and currency, counted with the same person’s recent orders for that customer.
- Separation of duties: nobody can approve their own request.
- Confirmations are single use, expire after 10 minutes and are bound to the person, organization, connection and the exact change.
- Created records carry a note in the app naming the person who asked.
Audit and evidence
- Every request, approval decision, sign-in and admin change is logged with person, tool, result and time.
- Request details keep only allowed fields; free text and personal fields are removed. Results are not stored.
- Filter, open any event, and export to CSV for your auditors. Kept one year by default.
Data protection
- Business data is read live, returned to the assistant and not stored.
- Prepared changes waiting for confirmation or approval are encrypted and deleted when they end.
- Integration credentials are encrypted in AWS Secrets Manager and never shown again.
- All traffic uses HTTPS. By default, logs carry no business data, and they never carry credentials.
Where it runs
- Hosted on AWS in the United States (N. Virginia).
- Dedicated instances per customer are planned; ask us if you need one.
What we do not claim
Your security team will check, so here is the plain list. mcpbizapps does not yet offer certifications such as SOC 2 or ISO 27001, data residency outside the United States, customer-managed encryption keys, or private network links. Tell us which of these you need; they shape our roadmap.
For your security review
We share the data handling details, architecture, threat model and audit log samples during a pilot.
Questions people ask
Does mcpbizapps store our business data?
No. Customers, orders, receivables and other figures are read live when the assistant asks, returned and not stored. A prepared change waiting for confirmation or approval is the one exception: it is kept encrypted for at most 10 minutes for a confirmation or 24 hours for an approval, then deleted.
Does mcpbizapps see our conversations with the AI assistant?
No. It only receives the tool requests the assistant sends, such as "find customers named Becker", and returns the results. Prompts and replies stay in your AI assistant.
Where is data stored?
In AWS in the United States (N. Virginia). What is stored is limited to people (work email, name, roles), settings, encrypted credentials, the audit log, prepared changes for up to 24 hours, and technical logs for about 30 days.
Can we prove who did what?
Yes. The audit log ties every request and decision to a named person and the AI client used, and exports to CSV. Records created in ByDesign carry a note naming the person.
Do you have SOC 2 or ISO 27001?
Not yet. We share our security documentation, data handling details and architecture with your security team during evaluation.
How do we report a security issue?
Use the contact form and choose "Security" in the message, We acknowledge every report and keep you updated until it is resolved.
Last updated
See it with your own questions
In 30 minutes we show an AI assistant looking up and preparing work in a business app, with the approval and the audit trail. Bring the questions your team asks every week.