Privacy Policy
A practical explanation of what SSOVEE OS handles when you use its account, productivity, communication, and sharing features.
Last updated: October 23, 2026
Account
Sign-in and profile information
Browser
Authentication and some app data stay in local storage
Connections
Chat, calls, and transfers use real-time signaling
Information you provide
When you register or use account features, you may provide account and profile information such as your name, email address, and sign-in details. You may also create or upload content, including notes, files, profile details, and app or plugin submissions.
Information handled by the service
SSOVEE OS sends account requests and feature data to its backend services so the requested apps can work. Depending on the feature, this can include profile and settings information, files and file metadata, and requests needed to access your account. The exact data stored depends on the app and action you use.
The website stores authentication tokens and account information in your browser's local storage. Some features also keep data in the browser. Anyone with access to your browser profile may be able to access that locally stored information; sign out on shared devices and protect your device.
Notes, files, and app data
Different apps handle data differently. For example, notes are stored in browser storage, while the home file manager uses account-backed services. Data stored only in your browser may be lost if you clear site data or change devices. Account-backed data may remain available across sessions, subject to the service and your account.
Chat, calls, and peer-to-peer sharing
EchoChat encrypts chat text in your browser with AES-GCM before sending it through the real-time service. The room code is used to derive the encryption key, so share it only with intended participants. The service still handles room and connection signaling, message ciphertext, and related metadata.
Video calls and file transfers use browser peer-to-peer connections where available. The signaling service exchanges connection setup information; files are sent over a WebRTC data channel rather than uploaded as file content through the app's file-sharing flow. Video-call setup may use Google's public STUN servers, which can receive network connection information. Peer-to-peer connections can expose network information to the other participant.
Device permissions and notifications
Camera and microphone access is requested by your browser only when you use video calling. You can deny or revoke these permissions in your browser settings.
If you enable browser notifications, the app and the relevant browser or push service may process the subscription and notification content needed to deliver them. You can change notification permissions in your browser.
Cookies, storage, and service workers
The app uses browser storage for authentication, settings, and feature-specific data. It may also register a service worker to support the web app. You can clear stored site data or manage permissions in your browser, though doing so may sign you out or remove locally stored content.
With your choice, the site uses Google Tag Manager to load Google Analytics 4 and Microsoft Clarity for traffic measurement and interaction analysis. Analytics tags do not load until you accept analytics cookies. Rejecting keeps those tags disabled. Analytics events exclude form field contents. Consent is stored in this browser's local storage. Use the cookie settings control below to change your choice.
Why information is used
- To authenticate you and provide the apps and features you request.
- To save and retrieve account-backed content and settings.
- To establish chat, call, and file-transfer sessions that you initiate.
- To maintain, secure, troubleshoot, and improve the service.
- To respond to support requests and meet applicable legal obligations.
Service providers and third parties
The service relies on backend, hosting, networking, and browser-platform services to operate. Those providers may process the information needed to deliver their part of the service under their own terms. Features you choose to use, including browser push, public STUN servers, and third-party plugins, may involve additional providers. Review their privacy information before using them.
Retention and your choices
Retention depends on where and how data is stored. Browser-stored data remains until you remove it or clear site data; account-backed data is subject to the backend's retention and account-management processes. This application does not promise a fixed deletion period. You can review or remove browser data in your browser and use the account controls available in the app. Contact support for account or privacy requests.
Security
We use measures in the application such as encrypted transport through the configured service endpoints and client-side encryption for EchoChat messages. No online service or encryption method can guarantee absolute security. Protect your account credentials and room codes, use trusted devices, and avoid sharing sensitive information with people you do not trust.
Children and policy updates
SSOVEE OS is a general-purpose productivity platform and is not specifically designed for children. If you believe a child has provided personal information inappropriately, contact us.
We may revise this notice as the service changes. The date below indicates when this version was prepared. Material changes will be reflected on this page.
Contact
For privacy questions or requests, email support@ssovee.com.
This notice describes the application behavior currently implemented. Data handling may vary by feature, account configuration, and service provider.