Security
Know what stays local. Know what leaves.
SmartyAI uses OS-backed protections for selected local data and user-controlled desktop capture. AI requests can send context to a backend and provider. Screen-share exclusion is best effort, never guaranteed.
Test your setupSecurity architecture
Desktop renderer windows use sandboxing and context isolation with Node integration disabled. Sensitive actions pass through a narrow preload bridge and validated main-process requests. Production AI provider credentials live on the backend, not in the desktop renderer.
- 01Desktop app
- 02Secure preload / IPC
- 03Backend API
- 04AI provider
The diagram shows AI requests. Local OCR and transcription run in desktop helpers before extracted text may be sent for an answer.
Data handling
Selected local context and grants use Electron safeStorage, backed by macOS Keychain or Windows DPAPI. This does not mean every file is encrypted or that synced data stays on-device.
| Data | Processing and storage | Retention and deletion |
|---|---|---|
| Resume, job description, preferences | Selected locally saved context uses Electron safeStorage. Resume and job description can also sync to the backend; relevant text can be sent for AI requests. | Local and backend copies are separate. Backend retention and account-wide deletion require confirmation from the service operator. |
| One-shot screenshots and audio | OCR and transcription use local helpers and temporary media files. Extracted or transcribed text can be sent to the backend for an AI answer. | Temporary processing files are removed after normal helper completion; this is not a promise of cleanup after a crash. |
| Recording sessions | Full recording sessions can save media segments, transcripts, and session events in the desktop app's local sessions folder. | Stopping capture marks a session complete; it does not delete the saved session. |
| Account and AI requests | Account data and submitted prompts reach the backend. The backend may pass request content to its configured AI provider. | Backend backups, provider retention, and full account deletion are not specified here without a confirmed policy. |
Clear conversation removes the local conversation copy, not necessarily saved recording sessions or backend profile data. See the privacy notice for service-policy boundaries.
Capture and screen share
Desktop capture requires a user action and applicable consent. Recording sessions have start and stop controls; stopping a saved session is not the same as deleting it. Whether the overlay appears to others depends on your OS, meeting app, and chosen sharing mode. Test the participant view before an important call.
| Capability | macOS | Windows |
|---|---|---|
| Microphone transcription | Supported with permission | Not advertised in the current Windows release |
| System-audio transcription | Supported with required access | Supported when a usable audio track is available |
| Screenshot OCR | Apple Vision path | Not advertised in the current Windows release |
| Capture exclusion | Best effort | Best effort |
| Screen-share verification | Test your sharing mode | Test your sharing mode |
Capability depends on app version, permissions, available helpers, and the selected audio source. See macOS and Windows release details.
Permissions and failure states
- Microphone
- Needed to access your voice for supported transcription. If denied or revoked, microphone capture cannot continue; check OS settings and retry.
- Screen Recording
- Needed for supported screenshot and display capture on macOS. A permission change may require restarting the app before retrying.
- System audio
- Captures a supported system or shared-source audio track when you start it. If the OS, permission, or source supplies no track, transcription cannot start for that source.
If one capture source fails, do not assume every other source has stopped: use the app controls to check each state and stop the session explicitly.
Before your interview
Run a 60-second setup check
- 01Open a private meeting in the Zoom, Meet, or Teams setup you intend to use.
- 02Choose the exact screen or window sharing mode you intend to use.
- 03Open SmartyAI and check its permission and capture indicators.
- 04Join from another device or account and inspect what that participant actually sees.
- 05With participant consent, test microphone and supported system-audio capture separately.
- 06Where supported, trigger screenshot OCR yourself and check the result.
- 07Stop capture and confirm its state is off before leaving the test meeting.
Test your exact setup before an important interview. A successful private test does not guarantee the same result after a software update or sharing-mode change.
What we do not guarantee
No universal screen-share invisibility, identical behavior in all meeting apps, uninterrupted access after permission changes, or automatic deletion of saved recording sessions. Review meeting and workplace rules, obtain participant consent, and avoid sharing data you are not authorized to use.
For release authenticity and published checksums see downloads. For security questions or reports see contact; do not include active credentials or private interview content.