Safety & Trust
Permissions and Access
A detailed breakdown of the permissions Hepi requires to provide advanced AI and system integration features.
Permission Requirements
Hepi requires specific system permissions to interact with your operating system and provide AI-driven assistance. Below is a breakdown of why these are necessary and when they are used.
| Permission | Usage Context | Functional Requirement |
|---|---|---|
| Administrator Access | Safe Exam Browser (SEB) sessions, Patch Enforcement, and Kiosk Bypass. | Required to interact with other protected processes and manage virtual desktops. |
| Microphone Access | AI voice interaction and meeting transcription modes. | Used to capture audio context for real-time analysis and response. |
| Screen Capture | Region capture, text grabbing, and persistent overlays. | Allows Hepi to “see” your screen and process visual data for the AI. |
| Browser Sign-in | Initial setup and account synchronization. | Required for secure OAuth 2.0 authentication and plan verification. |
Understanding Administrator Rights
Many users ask why Hepi needs Administrator privileges. This requirement is strictly for Advanced SEB Integration:
- Process Patching: To prevent SEB from closing Hepi, the app must have permission to adjust SEB’s internal security monitors in memory.
- Desktop Management: Creating and switching to a virtual desktop (where SEB lives) is a restricted Windows operation that requires elevated rights.
- Low-Level Input: Features like Ghost Mode require access to low-level keyboard and mouse hooks to function correctly across different desktop environments.
Info
Hepi only requests Administrator rights when you enable features that physically require them. Standard chat and assistant features work perfectly with normal user permissions.
Resolving Permission Issues
If a feature is disabled or fails to start, follow these verification steps:
- Check Settings: Ensure the feature is enabled in the Hepi settings panel.
- Verify Windows Prompt: If a Windows UAC (User Account Control) prompt appears, you must select “Yes” to grant the necessary elevated rights.
- App Permissions: Check your Windows Privacy settings to ensure Hepi is allowed to access the Microphone and Screen Recording.
- Restart Hepi: Some permission changes require the application to be restarted to take effect.
Privacy Note
Hepi only captures screen or microphone data when you explicitly trigger a capture or start a meeting mode. We do not monitor your activity in the background without your direct interaction.
Related Pages
Last updated: 2026-04-25
Was this page helpful?