Security and data
Review Grunt ONE asset storage, external AI processing, saved content, and sharing with your IT team
For an IT review, identify both where your Grunt services run and which AI assistant you use. Grunt ONE connects an assistant to Grunt's chart and table tools; the assistant or model provider supplies the AI. Grunt AI is a separate chat experience inside the Grunt PowerPoint add-in.
#Where content is processed and stored
| Workflow | Data path |
|---|---|
| Grunt-hosted MCP and Web Editor | Requests sent to Grunt and saved asset data, models, and versions are processed and stored in Grunt's Azure-hosted environment. Saved assets are persistent content, rather than data held only in your browser. |
| Customer-hosted MCP and Web Editor | Content storage, history, rendering, and exports run in your installation. The installation contacts Grunt for activation, entitlement renewal, and aggregate usage reporting. |
| Your external AI assistant | Prompts, files, and any Grunt tool results provided to the assistant follow that provider's data path and your agreement with it. Hosting Grunt on your infrastructure does not move an externally hosted AI provider into your network. |
| Grunt AI in PowerPoint | Content submitted to Grunt AI is processed through Grunt's AI service and its applicable model provider. See the PowerPoint IT FAQ. |
| Local Grunt objects in PowerPoint | Local edits are saved in the presentation. They are not automatically published back to the web asset. Using AI or another connected feature introduces that feature's separate data path. |
The hosting guide describes deployment responsibilities and aggregate usage reporting. Use On-premise setup for the evaluation package, sign-in, network requirements, and backup instructions.
#Saved content and retention
Saving a chart or table retains its data, model, formatting, and saved versions so you can reopen, edit, and export it. A generated image or completed AI request does not delete that saved asset or its history.
Saved customer content follows the applicable agreement and data-management policy. Transient AI inputs, saved assets, account records, and backups have different retention purposes. Use the current privacy and data policies and confirm the applicable retention and deletion requirements with Grunt for your evaluation. Your external assistant's retention and training settings are governed separately by your agreement with that provider.
#Asset access and sharing
Assets created with user sign-in belong to that user. Assets created with organization credentials belong to the organization and are available to its other MCP clients. See MCP authentication when choosing the ownership model.
Share links grant access to their holder:
- A view link exposes the rendered visual and underlying data.
- An edit link also exposes the complete Grunt model and grants editing permission.
Treat these links as access credentials and share them only with the intended recipients. Revoking a link prevents further access through that link; it cannot recall files or data already downloaded. See Share an asset for the link behavior, and Plans and AI access for the separate product access requirements.
#Prepare an IT review
Agree the following with your IT team and Grunt:
- The hosted or customer-hosted environment and the content you intend to use.
- The approved assistant, model provider, and client configuration.
- User sign-in or organization credentials, asset ownership, and who may create share links.
- The applicable retention, deletion, backup, and contractual requirements.
- The capabilities enabled for your evaluation, using the rollout status.
The MCP connection guide and tool reference provide the technical setup and operations. For company security policies and subprocessors, use the Trust Center. Contact Customer Success to coordinate any remaining product or contractual questions.