Scout security and data handling

This page is for IT and security teams reviewing Scout. It covers what workbook content Scout can use, what leaves the machine, how long data is retained, and how access is controlled.

Read it alongside Security and Architecture, which covers the Daloopa Excel Add-In. Those controls apply to Scout because Scout runs inside the same add-in. This page covers what’s specific to Scout as an AI feature.

What Scout is

Scout is a feature of the Daloopa Excel Add-In, not a separate install. There’s nothing extra to deploy, no additional binary, and no macro. Scout runs in the same web add-in, origin, Office.js sandbox, and manifest controls as the rest of the Daloopa Excel Add-In.

Scout adds a chat panel and a backend service that calls a large-language-model provider on your behalf.

What workbook content Scout can use

Scout follows the same sandbox limits as the Daloopa Excel Add-In. The add-in accesses workbook content through the Office JavaScript API. It can’t access the COM or operating-system layer, read from local disk, write files to the workstation, or create or run macros.

When Scout needs workbook context to complete a request, it uses the referenced range rather than the entire workbook.

Scout-specific safeguards include:

While a run is in progress, the active sheet is locked and a banner appears so Scout’s writes and the user’s edits don’t collide.
Revert undoes Scout’s most recent action.
Worksheet protection guards are in place.

Data sent for processing

To answer a request, Scout sends the prompt and the workbook context needed for that request to Daloopa’s backend. Daloopa’s backend calls the model provider on your behalf.

Scout currently runs on Claude from Anthropic. Daloopa evaluates models on an ongoing basis and may add or change providers.

Neither Daloopa nor Scout’s third-party model provider uses customer workbook content to train models.

Scout runs in Daloopa’s multi-tenant AWS environment, with logical isolation between customers, TLS 1.2 in transit, and AES-256 at rest.

Data storage and retention

Data	How Scout handles it
Chat history	Stored in the user’s browser profile, on their machine. It isn’t synced across machines and is cleared if browser data is cleared.
Global instructions	Stored by Daloopa against the individual user account.
Prompts, responses, and referenced workbook context	Retained for 14 days for service operation, support, and troubleshooting.
Usage records	Daloopa records each billable request for metering, including timestamp, token counts, and credit cost.
Model output	Written into the workbook, which stays under your control.

Scout uses the same retention policy across customers. It doesn’t currently offer a separate customer-controlled retention setting or a zero-retention/no-logging option.

Access control

Scout is off unless your Daloopa plan includes it. Users without Scout entitlement see the Scout screen with the prompt box disabled.
Entitlement is set per user and per organization by Daloopa administration, on request from your account team. Adding or removing a user doesn’t require redeploying the add-in.
Authentication follows the add-in. Scout uses the same credentials and session behavior as the Daloopa Excel Add-In, including SSO where configured. See the FAQ.
Usage is capped by a monthly credit allowance, per user or pooled across the firm.

What Scout doesn’t do

Scout doesn’t browse the web, use non-Daloopa data sources, connect to customer-supplied external systems, or run on a schedule. A person starts each run and approves the plan before Scout writes to the workbook.

Scout also doesn’t send email, create files outside the workbook, or act outside Excel.

For more information

For security questionnaires, subprocessor questions, or customer-specific review requirements, contact your Daloopa Customer Success Manager or Account Executive and share the control framework or questionnaire you’re working from.