GEM AI Security & Privacy
Your content. Your decisions.
GEM AI Workstation helps you turn videos on your Windows PC into clips you can review, approve, and export. Its local-first workflow keeps you involved in the decisions that matter.
Local-first
A local-first workflow
GEM works with local video files and stores its media records locally. Approved clips are exported to your local GEM output folder. Connected features can have separate network and data requirements; review the relevant settings and consent before using them. Local-first does not mean that every optional feature is offline.
This website is separate from the app. It uses IONOS SiteAnalytics cookies to count visits, only if you accept them in the cookie banner. GEM AI Workstation does not use these website cookies.
Your review
Review before publishing
Clip candidates are suggestions for you to review. You decide which clips to approve, reject, or adjust. The core workflow prepares exports for posting; it does not automatically post them to social platforms.
Authorization
Permissions belong to the security system
For operations integrated with GEM Security Core, policy checks use the requesting identity, the requested operation, and its permitted scope. Missing or invalid authorization information must not become permission. The dashboard displays security information and directs you to the appropriate controls; displaying a button does not grant authority to execute an action.
Assistant settings
Personalization does not grant access
An assistant's name, avatar, or tone is a presentation preference. It must not change the internal role or locked safety permissions used to govern protected actions.
Private records
Records you can review
GEM's in-app security views show available status information, pending approvals, and recorded Security Core outcomes. These are private operational records, not information published on this website. Audit records help explain supported operations; they are not a guarantee that logs cannot be altered.
Imported media
Layered checks for imported media
GEM treats imported videos as untrusted files. Intake checks combine supported file types and file signatures with path checks, file-change checks, and limits on file size, duration, and stream count. Files that fail applicable intake checks are recorded as blocked. These checks reduce risk; a matching extension or signature does not prove a file is harmless.
Where supported, GEM uses a local Microsoft Defender custom scan for direct imports and selected managed-library videos. GEM does not automatically upload private media to online scanning services. Scan results distinguish clean, detected, failed, unavailable, pending, unsupported, and not run. A detected threat blocks the affected media workflow and creates a quarantine record without GEM automatically deleting the original file.
Scanning does not cover every file before processing. External watched-folder videos and photos can remain pending and still be processed. Failed, unavailable, or unsupported scanning can also allow processing; these outcomes are never presented as clean. Keep Windows security enabled and use trusted sources for media.
Agent tasks
Limited access for supported agent tasks
Supported agent media views use short-lived, single-use grants tied to the task, internal role, resource, and arguments. The views return the fields needed for that task and omit private filesystem paths. Imported text is treated as untrusted data rather than approval authority. These application checks do not isolate malicious code already running inside the same desktop process.
Media processing
Media tools with practical restrictions
GEM resolves supported media tools from configured trusted locations and passes commands as argument lists without shell interpretation. The shared runner applies protocol restrictions, timeouts, a reduced environment, and Windows process controls where available.
These controls are not an operating-system sandbox. Media processing still runs with the logged-in Windows user's authority. Some processing paths have incomplete folder restrictions, and a decoder vulnerability could reach files or network resources available to that user.
Releases & backups
Release integrity and recovery
Release checks help identify private runtime files that should not be distributed. Signed and verified releases establish publisher identity and integrity of the signed executable; signing does not certify that software is free of malware. GEM does not provide an automatic updater through these security components.
Versioned backup and restore helpers cover the local database, including stored approvals, and supported settings. Restore checks recorded file hashes. Keep valuable media and exports backed up separately. Backups writable by the same Windows account remain vulnerable if that account is compromised; maintain a disconnected or independently protected copy.
Honest boundaries
Practical protection with honest boundaries
Security Core integration is developing incrementally. Protections for integrated operations should not be read as a claim that every operation is covered. In-app checks are not a substitute for Windows security, trusted software, backups, or protection against malicious code running on your computer. This page does not claim independent security certification or complete protection from every threat.
In the app
Where to manage security
Use GEM's Settings and Approval Queue to review the controls and decisions available in your installed version. This page explains the approach; it does not expose your files, account credentials, approval requests, or audit history.