Privacy policy
Effective 10 August 2026
What EGAMUS processes
EGAMUS processes the account identity needed for secure sign-in, the workspace details you provide, product events sent through your connectors, and content you deliberately submit to the AI CEO, research, voice, and social tools.
Website tracking
The EGAMUS website sensor records anonymous visits, page paths, traffic sources, safe button labels, form-submission events, browser errors, and performance measurements. It does not read form values, passwords, email fields, or page content. Do Not Track and Global Privacy Control are respected.
Mobile application telemetry
The optional EGAMUS mobile sensor records app installations, sessions, screen names, app versions, events selected by the product owner, app errors, and network-performance measurements. A product may supply its own internal user identifier for retention analysis. The sensor does not collect passwords, message contents, microphone audio, photos, contacts, or precise location. Each write-only app key is scoped to one registered package or bundle identifier.
How data is protected
- Every record is scoped to a specific workspace.
- Connector write keys are stored as secure hashes.
- Provider and webhook secrets are encrypted server-side and are not returned after setup.
- AI services receive only the workspace context required for the requested task.
Your choices
You can stop collection by removing the sensor or connector, revoke social authorization at the relevant network, remove teammates, and stop submitting AI or voice requests. Product owners are responsible for giving their visitors any notice or consent required by applicable law.
Service providers and retention
EGAMUS uses trusted infrastructure, identity, payment, AI, voice, and social-platform processors to deliver requested features. Data is retained while the workspace is active and as reasonably necessary for security, billing, dispute handling, and legal obligations.