Privacy Protocol · v1.1.1

Your DataStays With You

Chronos is a voice-powered AI assistant for Windows that launches your applications on command — no cloud, no tracking, no compromise. This document defines exactly how your privacy is protected.

Windows 10 / 11 100% Local Processing Zero Data Exfiltration Offline Capable
D3F4U17 CHRONOS 15R431 ONLINE

What Is Chronos

Chronos is a locally-executed voice assistant built for Windows 10 and 11. It listens to your spoken commands, interprets them using the Vosk speech recognition engine, and launches or controls your applications — all without sending a single byte to external servers.

Voice Recognition

Powered by Vosk, an offline-first speech recognition engine. Vosk models are downloaded once and run entirely on your CPU. No microphone data ever leaves your device.

FULLY LOCAL

TTS Voice Engine

Chronos responds using KOKORO TTS — a neural voice that closely mirrors the iconic Jarvis tone. The voice synthesis runs within the Edge runtime already on your Windows system.

EDGE RUNTIME

Application Control

Chronos executes local system commands to open, switch, and manage applications installed on your PC. All command resolution happens on-device via an editable local app registry.

ON-DEVICE ONLY

Adaptive Offline Mode

At first launch, Chronos may fetch the Edge-tts voices (one-time download). After this setup, the system transitions to fully offline operation — no recurring network traffic.

SETUP ONLY

No Cloud Dependencies

After the initial model download, Chronos has zero cloud dependencies. There are no API calls, no telemetry pings, no usage analytics, and no crash reporting sent to any server.

ZERO CLOUD

User Owned Data

Your command history, app list, and preferences are stored exclusively in local configuration files on your machine. You can view, edit, or delete them at any time.

YOUR MACHINE

How Privacy Works

Understanding the data lifecycle within Chronos — from the moment you speak to the moment your app launches.

STEP 01

Microphone Capture

Your system microphone captures audio. This audio stream is piped directly into Chronos's local processing pipeline in memory. The raw audio is never written to disk, uploaded to any server, or retained after the recognition process completes.

RAM only · never persisted
STEP 02

Vosk Speech Recognition

The audio is transcribed using the Vosk engine running entirely on your CPU. Vosk is an open-source, offline-capable speech recognition toolkit developed by Alpha Cephei. The language model (typically 40–500 MB depending on selected model) lives in your local AppData folder and performs inference without internet access.

Offline · open source · CPU-bound
STEP 03

Command Parsing & Intent Matching

The transcribed text string is matched against your local command registry — a configuration file listing your apps, aliases, and custom shortcuts. This matching is purely string-based pattern logic, executed on-device with no external model calls.

Local config · editable by user
STEP 04

System Process Execution

Chronos calls the Windows API to launch or interact with the target application. It uses standard subprocess invocation — the same mechanism as double-clicking an icon. No elevated privileges are required or requested beyond what the application itself needs.

Windows API · no elevation required
STEP 05

Edge TTS Voice Response

Chronos confirms the action using Microsoft Edge's built-in TTS engine. This voice synthesis is processed using the neural TTS runtime bundled with Microsoft Edge — the same voice engine that powers Edge's read-aloud feature. For offline use, Chronos falls back to Windows SAPI voices available on your system.

Edge runtime · local SAPI fallback
CHRONOS · DATA FLOW AUDIT
# Data flow verification — Chronos v2.4.1
audio_input = microphone.stream() # stays in RAM
transcript = vosk.transcribe(audio_input) # local model
command = registry.match(transcript) # local config
result = os.execute(command) # system call
response = edge_tts.speak(result) # local runtime
 
# Network requests during this session:
external_calls = 0 # ✓ verified

What Data We Handle

A complete, transparent breakdown of every category of information Chronos interacts with and where that data goes.

Data Type Purpose Storage Location Retention External Access
Microphone audio stream Speech recognition input RAM (transient) Discarded after recognition NEVER
Transcribed command text Intent matching RAM (transient) Discarded after execution NEVER
App registry / command config Command resolution %AppData%\Chronos\config.json Until user deletes LOCAL ONLY
User preferences & settings Customization %AppData%\Chronos\settings.json Until user deletes LOCAL ONLY
Vosk language model Offline speech recognition %AppData%\Chronos\models\ Persistent (user-removable) DOWNLOADED ONCE
Command execution logs Debugging (opt-in only) %AppData%\Chronos\logs\ 30-day rolling (if enabled) LOCAL ONLY
Crash reports Not collected N/A N/A NEVER
Usage telemetry Not collected N/A N/A NEVER
Personal identifiers Not collected N/A N/A NEVER
One-Time Network Activity
The only time Chronos initiates a network request is during first-run setup, when it downloads the Microsoft Edge-TTS voices for response. This is a one-time download. The downloaded URL, model version, and timestamp are logged locally. After installation, Chronos operates in complete network isolation. You can verify this using Windows Firewall, Wireshark, or any network monitoring tool.

Security Guarantees

Privacy is only as strong as the security underneath it. These are the technical safeguards built into every release of Chronos.

  • All audio processing occurs entirely in-process within the Chronos runtime, never written to disk and not accessible to other applications or users on the machine.
  • The Vosk inference engine runs as a sandboxed library call with no filesystem write access outside the designated AppData directory.
  • Chronos does not register as a Windows startup service by default. You control when it runs.
  • No Windows registry entries are created outside the standard user-scoped HKCU hive for application registration.
  • The Edge TTS integration uses the documented Windows Speech Synthesis API and does not establish independent network connections.
  • Command execution uses CreateProcess with the user's own token — no privilege escalation, no UAC bypass, no administrator requirements.
  • All configuration files are stored in plaintext JSON in your personal AppData folder — fully readable, auditable, and editable by you at any time.
  • No DRM, no license servers, no activation pings. Chronos runs entirely from local files.
  • The local command log (if enabled) is stored with user-level file permissions and is never transmitted anywhere.
  • Chronos does not inject into other processes, hook keyboard events globally, or monitor system-wide activity beyond its own microphone capture when activated.
SECURITY PROFILE
network_access: false
admin_required: false
registry_writes: HKCU only
global_keyboard_hook: false
process_injection: false
telemetry: none
crash_reporting: none
audio_written_to_disk: false
data_encryption: N/A (no stored secrets)
auto_update: manual only
 
# Verified by: local file audit
# Network monitor: 0 external IPs
# Status: CLEAN

Open Source Components

Chronos is built on trusted, auditable open-source technology. No black-box SDKs. No proprietary analytics libraries.

Vosk Speech Recognition

Developed by Alpha Cephei. Vosk is open-source (Apache 2.0) and runs 100% on-device. The model is downloaded once from the official Vosk model repository and stored locally. No Vosk servers are contacted during recognition.

APACHE 2.0 LICENSE

Microsoft Edge TTS

Chronos uses the edge-tts Python library which interfaces with the Microsoft Edge Read Aloud feature. This library sends the response text to Microsoft's TTS service during synthesis. For fully offline operation, Chronos falls back to Windows SAPI voices installed on your system.

NETWORK DURING SYNTHESIS
About Edge TTS Network Usage
When Edge TTS is active, the text of Chronos's verbal response (e.g., "Opening Chrome") is sent to Microsoft's Edge Read Aloud service for synthesis. This text contains no personal data, no command history, and no audio. If you prefer zero network activity at all times, enable Windows SAPI mode in Chronos settings — this routes all voice synthesis through offline Windows voices at the cost of voice quality.

Your Rights & Controls

Because all your data stays on your machine, you already have the highest level of control possible. These are the specific actions you can take.

Access Your Data

Navigate to %AppData%\Chronos\ in File Explorer at any time to view all configuration files, logs, and model data stored by Chronos. No special tools required — it's all plaintext JSON and binary model files.

Edit Your Config

Your app registry, voice preferences, wake-word settings, and all other configuration values live in human-readable JSON files. Open them in any text editor (Notepad, VS Code) and modify them freely. Chronos reloads on next launch.

Delete All Data

Uninstalling Chronos or manually deleting the %AppData%\Chronos\ folder removes everything completely. There is no server-side data to delete because none was ever sent.

Disable Logging

Command logging is disabled by default. If you enabled it for debugging, set "logging": false in settings.json or toggle it from the Chronos system tray menu. Existing logs can be deleted from the logs subfolder.

Offline Mode

After the initial Vosk model download, enable full offline mode in settings. In this mode, Chronos uses Windows SAPI for voice output instead of Edge TTS, eliminating all network activity. The assistant functions identically — only voice quality differs.

Audit Network Activity

We encourage you to verify Chronos's network behavior using Windows Firewall logs, Wireshark, or GlassWire. With offline mode enabled, you should see zero external connections from the Chronos process. The Vosk model download is the only expected outbound request.

Additional Provisions

Children's Privacy

Chronos does not collect any personal information from anyone, including children under the age of 13. Because Chronos operates entirely locally and collects no user data whatsoever, COPPA compliance is inherently satisfied. No registration, no account, no data — for users of any age.

Policy Changes

If this privacy policy changes, the updated version will be posted with a new effective date. Since Chronos does not collect contact information, we cannot notify you directly — we recommend bookmarking this page if you wish to stay informed. Breaking changes in data handling will always accompany a major version update with release notes.

Jurisdiction

Because Chronos does not transmit or store data on external servers, no cross-border data transfers occur. This policy is published in English and is intended to meet the spirit of major privacy frameworks including GDPR and the Worldwide Consumer Privacy rules, even though traditional compliance obligations do not apply to a fully local application.

Open Source Verification

We believe trust must be earned through transparency. The Chronos source code is available for review on GitHub. You are encouraged to audit the codebase, inspect network calls, or run it through any static analysis tool. If you identify a discrepancy between the code and this policy, please open an issue immediately.

Privacy Contact

Questions About This Policy?

If you have any questions about how Chronos handles your data, want to report a privacy concern, or would like clarification on any point in this document, reach out directly. We respond to all privacy-related queries within 72 hours.

Telegram

Contact Us
0
SERVERS STORING YOUR DATA
0
EXTERNAL API CALLS IN OPERATION
100%
OF YOUR DATA STAYS ON YOUR DEVICE