What we do with your data, in plain language.

Aceleron Intelligence, LLC builds custom AI agents for businesses. This policy covers two things: the agent we build and install into your own Microsoft 365 tenant as a Microsoft Teams app, and this website.

Throughout this page, you means the business that engaged us and deployed the agent. Your team means the named people inside that business who are allowed to message the agent in Microsoft Teams. We and Aceleron mean Aceleron Intelligence, LLC.

If you are an employee using the agent at work, the business that deployed it decides what it is pointed at and who may use it. Start any question about your own data with your employer. We will support them in answering it.

Your business is the data controller. You decide what the agent is pointed at, who may use it, and what happens to the results. Aceleron acts as a processor: we handle data on your instructions, for the purpose of delivering and supporting the system, under the services agreement we signed with you.

We do not sell personal data. We do not use your data for advertising, and we do not share it with advertisers or data brokers.

The agent runs on hardware you own and control, on your own premises. Aceleron does not host it. There is no Aceleron server sitting in the middle holding your business files or your conversations.

Conversation session state, meaning the running context of a conversation with the agent, is stored locally on that same machine. It stays on your hardware, under your control. It is not copied to Aceleron systems.

Three kinds of data pass through the agent when someone uses it:

• Message content. What a member of your team types to the agent in Microsoft Teams, and the reply the agent sends back.
• Sender identity. The Microsoft Teams identity of the person sending the message, which the agent uses to check the access list and to route the reply to the right conversation.
• Your business files. The files inside the single working folder you point the agent at. Those are your own files, on your own machine. The agent reads them to answer questions about your work.

The current version of the agent does not receive or store file attachments sent through Microsoft Teams.

The agent is deliberately fenced in. These limits are enforced by the software, not by policy alone:

• One folder only. A security fence confines the agent to a single working folder of your business files. It cannot read anything outside that folder.
• Sensitive paths blocked outright. Credential stores, environment files, and key material are denied even if they sit inside the working folder.
• Named users only. Access is restricted to an explicit allowlist of named people. Anyone not on that list does not get a response.

To produce an answer, the agent has to send the question to an AI model. That is the one place data leaves your machine, and we want it stated plainly rather than buried.

If we ever add a subprocessor that receives your content, we will update this page and tell you directly.

• Conversation session state lives on your machine and stays under your control. Deleting the local session store removes the stored conversation history. There is no separate copy on our side to delete.
• Your business files are yours and stay where they already are. The agent reads them in place. It does not build a second copy of your archive on Aceleron systems.
• Operational records that we do hold, such as support correspondence, scoping notes, contracts, and invoices, are kept for as long as the engagement runs and afterwards for as long as our legal, tax, and accounting obligations require.

These are the actual controls in place, stated as facts rather than as badges:

• The working-folder fence: reads are confined to one folder you nominate.
• Blocked paths: credential files, environment files, and key material are denied outright.
• An explicit allowlist of named users, so access is granted person by person.
• Session state stored locally on hardware you own, on premises you control.
• No Aceleron-hosted copy of your files or your conversations.

If you are a member of a team using an agent at work, your employer is the controller of that data. Send requests to access, correct, export, or delete your data to your employer first. We will help them respond.

If you contacted Aceleron directly, for example through the audit request form on this website, you can ask us to show you what you sent, correct it, or delete it. Email pete@aceleron.ai and we will handle it.

Depending on where you live, local privacy law may give you further rights over your personal data, including the right to object to how it is used or to complain to a regulator. Send the request to the business that deployed the agent, or to us at the address above, and we will route it to the right place.

The agent and this website are separate. Here is what the website itself does:

Aceleron sells to businesses. Neither the agent nor this website is directed at children, and we do not knowingly collect personal data from anyone under 13. If you believe a child has sent us data, contact us and we will delete it.

When this policy changes we update this page and change the date at the top. If we materially change how a deployed agent handles your data, we will tell the business that deployed it directly rather than relying on you noticing a new date here.

Questions about this policy, about what an agent in your environment is doing with your data, or about a specific request: write to pete@aceleron.ai. A partner reads it.

Aceleron Intelligence, LLC, Miami-Dade / South Florida.