At 10am, security and privacy are fundamental to our design. Learn how we protect your data and maintain your privacy while delivering personalized cognitive entrainment.
Privacy-First Design
10am is built with privacy at its core. Sensing data — camera, microphone, eye metrics, keyboard and mouse timing, window titles, and active application names — stays on your device. 10am does not operate a server that receives, stores, or processes your sensing data.
No Screen Reading: We never access, read, or capture your screen content
On-Device Camera Processing: Camera data for Adaptive Mode is processed locally by an on-device model (MediaPipe) and immediately discarded — no images are stored or transmitted anywhere
On-Device Microphone Processing: If you enable Music Coherence, microphone audio is analyzed locally to extract only musical key and tempo. Audio samples, recordings, and voice content are never stored or transmitted
No Keystroke Content: OS Context Sensing captures only typing timing patterns — never the content of what you type
Window Titles Stay On-Device: When OS Context Sensing is on, the foreground app's window title is read locally to help classify the type of work you're doing. It is never transmitted to our servers, to OpenAI, or to any other third party
Explicit Consent: Camera, microphone, and behavioral sensing each require your explicit opt-in before activation, and each can be disabled independently at any time
Local Encryption: All sensitive logs are encrypted at rest using a key derived from your machine
Local-Only Context API: 10am's optional Context API runs as a localhost-only HTTP server inside the app. Tools running on your own computer that you authorize with a key you generate can read an abstracted view of your current state. The Context API does not transmit anything off your device
Desktop App Permissions
As an Electron desktop application, 10am's permission requirements depend on which features you enable:
Always required
Window Overlay: Creates a transparent, always-on-top window for visual effects only — cannot interact with or capture other windows
Audio Output: Permission to play entrainment tones through your default audio device
Network Access: Required for authentication, subscription verification, AI-assisted configuration, syncing settings, calls to OpenAI when you use Hesper, and a one-time IP geolocation check when enabling biometric features (to comply with local biometric privacy laws)
Local File Storage: Reads and writes its own settings, logs, and encrypted data stores on your device. Cannot access your personal files or documents
Optional — Adaptive Mode (requires consent)
Camera Access: Used for real-time eye tracking to detect your attention state. Frames are processed on-device by MediaPipe and immediately discarded — no images are stored or transmitted. Requires your explicit consent before activation
Optional — OS Context Sensing (requires consent)
Keyboard Timing: Captures inter-key timing intervals to infer cognitive state. Only timing metadata is captured — never the content of your keystrokes
Mouse Dynamics: Tracks cursor velocity, movement efficiency, and click patterns for cognitive state inference
Active Application Name and Window Title: Reads the foreground application name and its window title for local task-type classification (e.g., "development", "communication"). Both stay on your device — they are never transmitted to our servers, to OpenAI, or to any other third party. 10am never reads URL contents, file contents, or any other document data
Optional — Music Coherence (requires consent)
Microphone Access: Used to detect the musical key and tempo of audio in your environment so 10am can align stimulation parameters to the music. Audio is processed locally and discarded in real time — no audio samples, recordings, or voice content are stored or transmitted. On macOS, you can optionally route system audio instead of the microphone. Requires your explicit consent before activation, and can be disabled at any time
Never used
No Clipboard Access: Cannot read or monitor your clipboard
No Background Microphone: The microphone is only used while Music Coherence is actively running, and only to compute key and tempo. It is not used for voice recognition, dictation, calls, or any other purpose, and is not listened to in the background
No Screen Capture: Cannot take screenshots or record your screen
No Personal File Access: Cannot read your documents, downloads, or any files outside its own data directory
What Data We Store
Cloud (Firebase)
We use Firebase to store minimal user data necessary for the service:
Account Data:
Email address (for authentication)
Encrypted password hash (never plain text)
Account creation date
Subscription status (active/trial/expired)
Usage Data:
Total AVE minutes used (for usage limits)
Session timestamps (start/end times only)
Streak tracking for gamification
Settings Data:
Your AVE effect preferences (frequency, intensity)
UI preferences (theme, layout)
No personal content or activity data
Local Device (encrypted)
The following data is stored locally on your device. 10am does not operate a server that receives or stores your sensing data, so none of the items below are transmitted to Halotropic, Inc. or any third party.
Stimulus-response logs (which setting adjustments were applied)
Outcome measurements (effectiveness of adjustments)
Encrypted with AES using a machine-derived key
Automatically deleted after 6 months
OS Context Logs (if enabled):
Cognitive state scores derived from behavioral patterns
Adaptation event logs (what was adjusted and why)
Same encryption and auto-deletion policies as Adaptive Mode
Local Dashboard History (if enabled):
Tier-3 semantic snapshots only — categorical labels such as "deep_focus", "high stress", "development" — used to render your personal session dashboard
Contains no raw biometric metrics, no raw keyboard/mouse timing values, no window titles, and no specific application names
Deletable at any time from Context API settings
Hesper Chat History:
Your conversation with Hesper is stored locally in the app's renderer storage
You can clear it at any time from the Hesper panel
Chat history is not synced to our servers
Local Context API Keys:
API keys you generate to authorize local tools to read 10am state
Stored encrypted on your device using your operating system's secure-storage facility (macOS Keychain / Windows Credential Manager via Electron's safeStorage)
Revocable at any time from Context API settings
Learned Profile:
Personalization tuning numbers (which adjustments work best for you)
Contains no biometric data or behavioral data — only optimization results
Deletable at any time from the app settings
What we DON'T store (anywhere)
Camera images, video frames, or facial geometry
Microphone audio, recordings, voice content, or any sound captured for Music Coherence
Keystroke content (what you type)
Screen content or screenshots
Window titles, URLs, or file names on our servers — window titles are read locally only and are never transmitted to Halotropic, Inc., to OpenAI, or to any other third party
Clipboard content
Browsing history or network traffic
Personal documents or files
Precise location, GPS coordinates, or IP addresses (a one-time IP geolocation check is performed when enabling biometric features for legal compliance — only the detected US state is stored locally, not your IP or coordinates)
Hesper chat history on our servers (chats live only on your device; individual messages are sent to OpenAI per turn for processing, governed by OpenAI's API terms)
AI Privacy & Data Handling
10am uses OpenAI's API in two distinct, opt-in ways. Both make calls directly from your app to OpenAI's servers — 10am does not proxy or relay them through a server we operate. Per OpenAI's API terms, requests are not used to train OpenAI's models.
AI-assisted session configuration
Goal in, parameters out: When you ask 10am to generate a session configuration from a goal (e.g., "focus", "wind down"), only your selected goal and preferences are sent. No biometric data, OS activity data, microphone data, or personal account information is sent for this purpose
No cloud storage on our side: 10am does not store these requests on a server we operate
Hesper (in-app companion)
Hesper is 10am's optional conversational companion. When you send Hesper a message, the message is sent to OpenAI together with a snapshot of your current state so Hesper can respond in context. Powered by OpenAI's GPT family of models (currently gpt-5.4-mini).
What is sent per message: your recent chat with Hesper (up to the last 50 messages), a system prompt describing Hesper's role, and a runtime context block containing a snapshot of your current cognitive state (focus, fatigue, stress, engagement, attention state, energy, interruptibility) and a categorical work-context label (e.g., "development"). If you have enabled Context History, a summary of the past 60 minutes of cognitive state is also included
What is NOT sent: camera frames, microphone audio, raw eye-tracking metrics, raw keyboard or mouse timing, window titles, specific application names, your email or credentials, and your payment information
Local chat history: Your conversation with Hesper is stored locally in the app, not on our servers. You can clear it at any time
Settings proposals require your click: Hesper can suggest specific 10am settings adjustments and present them as proposal cards inside the chat. You apply or undo each proposal with a single click. Hesper is restricted to a fixed allowlist of settings keys and cannot read or write any other part of your account, your device, or your data. Proposed changes are not applied automatically
Opt-out by not using it: Not opening or sending messages in the Hesper panel means no Hesper data is transmitted
Local Context API
10am includes an optional local-only Context API so tools running on your own computer — for example, a desktop AI assistant, a personal automation, or a script you've written — can read an abstracted view of your current 10am state. It is off by default and is enabled from Settings → Context API.
Localhost only: The Context API runs as an HTTP server on 127.0.0.1 inside the 10am app. It is bound to localhost and is not reachable from the network
Key-based authorization: You generate API keys from inside the app and provide a key to each tool you want to authorize. Without a valid key, requests to the local Context API are rejected. Keys are stored encrypted on your device using your OS's secure-storage facility
Abstracted data only: Authorized local tools see semantic labels (e.g., "deep_focus", "high stress", "development app category") and your current AVS configuration. Camera frames, microphone audio, raw biometric metrics, raw keyboard/mouse timing, window titles, and specific application names are not exposed even with a valid key
No off-device transmission: The Context API does not call out to our servers, to OpenAI, or to any other third party. What an authorized local tool then does with the data it reads is governed by that tool's own privacy practices, not 10am's
Revocation in one click: Disabling the Enable Context API toggle immediately stops the local server. Individual keys can be revoked at any time, immediately preventing the corresponding tool from reading further state
Security Infrastructure
Data Encryption
All data transmitted using HTTPS/TLS 1.3 encryption
Firebase data encrypted at rest using AES-256
Local biometric and behavioral logs encrypted at rest using AES with a machine-derived key (via device hardware ID + SHA-256)
API keys stored encrypted in production builds
Secure WebSocket connections for real-time features
Authentication & Access Control
Firebase Authentication with industry-standard security
Secure session management with automatic token refresh
Password requirements: minimum 8 characters
Secure password reset via email verification
Server-side validation of all user operations
Infrastructure Security
Firebase hosted on Google Cloud Platform infrastructure
Auto-scaling with DDoS protection
Rate limiting on all API endpoints
Security rules enforce user data isolation
Regular automated security scanning
Payment Security
Your payment security is handled by Stripe, a PCI-DSS Level 1 certified payment processor:
PCI Compliance: Highest level of payment security certification
No Card Storage: We never store credit card details on our servers
Tokenization: Card details are tokenized for secure processing
Fraud Detection: Advanced machine learning to prevent fraudulent transactions
Data Protection Practices
Minimal Data Collection: We only collect data necessary for the service
Consent-Gated Features: Camera access and behavioral sensing require explicit opt-in before any data is collected
Automatic Retention Limits: Biometric and behavioral logs are automatically deleted after 6 months
User-Controlled Deletion: You can delete all locally stored biometric and behavioral data at any time from the app settings
Access Controls: Strict internal access controls to cloud-stored user data
Regular Audits: Security practices reviewed and updated regularly
Incident Response: Established procedures for security incidents
Security Best Practices for Users
Help us keep your account secure by following these practices:
Strong Passwords: Use unique, complex passwords for your account
Keep Software Updated: Always use the latest version of 10am
Secure Network: Use 10am on trusted networks
Review Permissions: Periodically review which optional features (Adaptive Mode, OS Context) you have enabled and disable any you no longer use
Report Issues: Contact us immediately if you suspect unauthorized access
Compliance & Standards
We adhere to industry standards and regulations:
Local-first architecture: 10am does not operate a server that receives, stores, or processes your sensing data. Camera, microphone, biometric, and behavioral data stay on your device by design
GDPR compliant for European users
CCPA/CPRA compliant for California residents
BIPA-aware design for biometric data handling (on-device processing, encrypted storage, explicit consent, user-controlled deletion, geofencing of biometric features in Illinois)
HTTPS everywhere policy
Regular third-party security assessments
Reporting Security Issues
If you discover a security vulnerability, please report it responsibly:
Email: security@go10am.com
Please include as much detail as possible to help us understand and address the issue quickly. We appreciate your help in keeping 10am secure for everyone.
Security Updates
We continuously improve our security measures. This page will be updated to reflect any significant changes to our security practices. For the latest updates, check back regularly or subscribe to our security announcements.