Privacy
mcpbizapps service privacy policy
mcpbizapps connects your AI assistant to your business apps. It reads business data live and does not keep it, and it never stores your prompts or the assistant's replies. It stores only what it needs to run: people's work email, name and roles, your settings, encrypted app credentials and an audit log, all hosted on AWS in the United States.
Effective
Who this policy is for
This policy covers the mcpbizapps service: the connector that Claude, ChatGPT, Microsoft Copilot and other AI assistants use to work with your business apps, the sign-in, and the admin console. The service is run by AIONDATA. This website has its own website privacy notice. The terms and data processing details that apply to your organization are part of your agreement with AIONDATA.
What we collect and store
- Account details. The work email, name and roles of each person your admin invites.
- Sign-in data. One-time sign-in codes, stored only in scrambled form, and the sign-in sessions of your AI clients.
- Settings. Your app connections (without their passwords), roles, rules and approval rules.
- Integration credentials. The user name and password of the integration user for each app connection, encrypted in a managed secrets vault.
- Audit log. For every request: the person, the tool, the app connection, the request details, the result status, any approval reference, the response time and a trace reference. Request details keep only allowed fields; free text and personal fields are removed. Results are not stored, only counts, status and the IDs of the records involved.
- Prepared changes. When the assistant prepares a change that needs your confirmation or an approval, we keep the fields needed to show the preview and make the change, encrypted, until it ends. These can include personal data, for example the old and new email and phone numbers when a customer contact change is prepared.
- Technical logs. Events that help us run and secure the service. By default they carry no business data, and they never carry credentials. If your organization turns on detailed logs, the details are redacted.
What we do not store
- Your business data. Customers, orders, receivables, project figures and other records are read live from your app when the assistant asks, returned to the assistant and not kept. The only exception is a prepared change, described above, which is deleted when it ends.
- Your conversations. We never store your prompts or the assistant's replies. The service receives only the tool requests the assistant sends, such as a customer name to look up.
How we use it
We use the data above only to provide the service to your organization:
- to sign people in and check their roles before each request;
- to run requests against the business apps your organization connected;
- to show previews, apply your approval rules and send sign-in and approval emails;
- to keep the audit log your organization uses to see who did what;
- to operate, secure and troubleshoot the service.
Where it is stored and how it is protected
All stored data is hosted on AWS in the United States. We do not offer data residency in other regions today. All traffic uses HTTPS, including requests from the service to your business apps. Integration credentials are encrypted in a managed secrets vault and never shown again. Prepared changes are encrypted before they are stored.
Who receives data
- Amazon Web Services (AWS) hosts the service, stores the data described above and delivers our emails.
- The AI assistant you choose, such as Claude, ChatGPT or Microsoft Copilot, receives the answers to the requests it sends. What it does with them is governed by your organization's own terms with that provider.
- Your business apps receive the requests made on your behalf, under your organization's agreement with each app's vendor.
How long we keep it
| Business data from your apps | Not stored. Held in memory only while a request runs. |
|---|---|
| Prompts and assistant replies | Never stored. |
| Account details (work email, name, roles) | Until an admin removes the person, then deleted under your organization’s policy. The audit log keeps a reference to the person. |
| Sign-in codes and sessions | From a few minutes for a sign-in code up to the length of a sign-in session. |
| Settings | For as long as your organization uses the service. |
| Integration credentials | Until the app connection is removed. |
| Audit log | One year by default. Your organization can set a different period. |
| Prepared changes | At most 10 minutes while waiting for confirmation, or 24 hours while waiting for approval. Deleted when the change is made, declined or expires. The approval decision stays in the audit log without the change details. |
| Technical logs | About 30 days. |
Deletion
- Removing a person. An admin can deactivate a person at once; every AI client they use is cut off on its next request. Their account details are then deleted under your organization's policy. The audit log keeps a reference to the person.
- Removing an app connection. Its credentials are deleted. The audit log is kept.
- Leaving the service. When your organization leaves, we delete the organization, its people, settings, requests, audit log and sessions, and then its connection credentials.
If you use mcpbizapps through your employer, ask your organization's admin first. You can also contact us at the address below.
Changes to this policy
When this policy changes, we update this page and its effective date.
Contact
Questions about this policy or about data we hold: email info@aiondata.io.