A desktop AI app runs as a program on the endpoint, so it can reach local files, the clipboard and other apps, and it must be updated and managed like software. A web app runs in a browser sandbox, with less local reach and central updates. Your review should shift from tenant controls to endpoint controls.
What a desktop app adds
A browser tab can only touch what the browser allows. A desktop program can often do more, depending on the permissions the operating system grants it. The app may:
- Read files in folders the user can read
- Watch the clipboard or capture the screen, with permission
- Launch other programs or scripts
- Run background processes that outlive the window
- Store tokens and cached content on disk
None of those is automatically a problem. Many are the reason a team picks a desktop app. They do change who must approve the tool, since endpoint and platform teams now share the review with the application security team.
Side by side
| Topic | Web app | Desktop app |
|---|---|---|
| Local file access | Via file picker only | Possibly broad, per OS permission |
| Updates | Server side, immediate | Client side, depends on updater and policy |
| Version spread | One version | Many versions in the fleet |
| Offline use | Rare | Possible, with cached data |
| Credential storage | Browser session | Possibly local store or keychain |
| Central control | Tenant admin console | Console plus device management |
| Inventory | Tenant user list | Device level discovery |
| Uninstall and cleanup | Close account | Remove app, caches, tokens |
Questions that change
- What permissions does the app request from the operating system, and can they be limited?
- Where does it store tokens, caches and logs on disk, and are they encrypted?
- How does it update, and can IT hold or pace updates?
- Can an administrator enforce settings through device management?
- Is the installer signed, and can you verify the signature or a checksum?
- What does the app do when the account is deprovisioned?
The last one often exposes gaps. If a user is removed from the identity provider, does a cached session on the desktop keep working?
What stays the same
Data handling questions do not change with the packaging. Where prompts go, how long they are kept, whether they train models, and which sub-processors are involved are the same questions for both. So are identity questions: single sign-on, role based access, and audit logs.
OWASP's excessive agency guidance points at three root causes that apply to any form: excessive functionality, permissions and autonomy. A desktop app tends to hand an agent more functionality by default because the machine has more to offer. That makes the permission list the most important artifact in your review.
When each form fits
Choose a web app when staff mostly need chat and documents, you want fast central change, and you prefer a smaller endpoint footprint. Choose a desktop app when the work needs local files and tools, and you can manage the endpoint rig. Many organizations allow both, with the desktop version limited to named groups.
If you are rolling out a desktop security tool of your own, the same review applies, and the posts on which Safeguard surface to use show how one vendor lays out its choices.
A worked example: two teams, two choices
A company has two groups that want an assistant. The support team handles tickets and writes replies. The platform team works in large local codebases and wants the assistant to run tests and edit files.
For support, a web app is a good fit. They need chat, documents and a few connectors. The reviewer checks single sign on, roles, retention and logs in the tenant console. No software lands on laptops, and updates are the vendor's job.
For the platform team, a desktop app gives the local access they want. Here the reviewer adds endpoint questions: which folders, which commands, how it updates, how settings are enforced, what is stored on disk. The group is small and trained, and the pilot is limited to them, with managed settings.
The two reviews overlap in data handling and identity, and differ in the endpoint parts. That overlap is why you do not need two entirely separate processes.
Step by step: extend your existing review
- Start with your standard vendor review: data handling, identity, logging, contracts.
- Add a desktop appendix with the six questions in the earlier section.
- Ask your endpoint team to review the installer, signing and update behavior.
- Test the permission questions on a spare machine.
- Choose a pilot group and enforce settings through device management.
- Add the app to your software inventory with an owner and an approved version range.
- Record exceptions, such as a developer group with broader folder access.
Who needs to be in the room
| Question area | Likely owner |
|---|---|
| Data handling, contracts | Security and legal |
| Identity, access, logs | Identity team |
| Installer, updates, settings | Endpoint or IT |
| Local permissions and commands | Security engineering |
| Day to day use rules | The team sponsor |
A common failure is leaving the endpoint team out until after purchase, then discovering that settings cannot be enforced the way the vendor described.
Offline and cached data
A desktop app may keep conversations, files or tokens on the device. Ask where, whether they are encrypted, and what happens when a device is lost. If your device policy requires disk encryption and remote wipe, check that cached content falls under it. For web apps, ask the equivalent question about browser storage on shared computers.
Decision summary
Pick web for broad, low risk use with fast central change. Pick desktop for groups that need local reach, with managed settings and a limited pilot. Revisit every six months, since both forms change quickly.
Try it yourself
Click through it at your own pace, or open it full screen. Watch what the assistant is allowed to reach once a tool connection is configured.
Quick check
Is a desktop app less secure than a web app?
Not by definition. It shifts the controls to the endpoint, where you need device management, update control and a reviewed permission set.
Do data handling questions differ for desktop apps?
No. Retention, training use and sub-processors are the same. What changes are local storage and update behavior.
Can we allow both web and desktop versions?
Yes. Many organizations allow the web app broadly and the desktop app for named groups with managed settings.
Sources
Last reviewed: 19 October 2026.
