TL;DR
Vehla is a local-first macOS app. The text you process never touches a Vehla inference server. When you use a BYOK cloud provider (OpenAI, Anthropic, Google, DeepSeek, or OpenRouter), your Mac talks to that provider directly using the API key stored in macOS Keychain. Local models run on-device; Ollama and LM Studio use the server you configure. Vehla also sends optional anonymous device and lifecycle analytics to Supabase. You can disable this collection in Settings.
What we collect
We collect the following license, purchase, and optional analytics information:
- Your email address - to issue and revoke licenses, to send your license key, and to honor refund requests.
- A hashed hardware ID - derived from a system identifier to count your two-Mac license slots. We can't reverse it to identify your Mac.
- License events - activation and deactivation timestamps. Stored in Supabase on encrypted-at-rest Postgres.
- Purchase information - handled by our payment processor (Stripe). We see masked card details and a transaction ID; nothing else.
- Anonymous analytics - anonymous device and usage data that can't be used to identify you. Vehla sends this to Supabase when anonymous analytics are enabled.
What we don't collect
- Your prompts, selections, clipboard contents, or AI outputs.
- What apps you use Vehla in.
- What snippets, personas, or memory notes you've configured.
- Your Apple hardware UUID, serial number, hostname, or other direct hardware identifier as part of anonymous analytics.
- Your prompts or outputs in update or license requests.
Cloud providers
When you pick a cloud provider, your Mac sends prompts directly to that provider's API. We are not in the loop and have no way to see what you sent. Each provider has its own privacy policy and data-retention behavior:
If you turn on Local AI, none of these are contacted.
Local mode
Local mode runs Gemma 4 models through MLX on your Mac. Vehla makes no cloud-provider request for inference when Local AI is enabled.
API keys
API keys are stored in macOS Keychain, encrypted by the system, scoped to the Vehla app. We don't see them. They never touch our infrastructure. If you uninstall Vehla, the keys remain in Keychain until you remove them from Keychain Access.
Update checks
Vehla periodically fetches https://vehla.s3.us-east-2.amazonaws.com/update.json to check for a newer build. The request does not include prompts, outputs, snippets, personas, clipboard contents, or selected text.
Analytics
Anonymous system analytics are enabled by default and help us understand usage and device compatibility. Vehla sends anonymous data to our Supabase database using an anonymous device ID generated randomly for this app installation. The analytics payload does not include your email address, license key, files, clipboard contents, prompts, AI outputs, or the names of apps you use.
You can stop future analytics at any time by turning off Share anonymous system analytics in Vehla Settings. The vehla.app website does not currently include an analytics script.
Cookies on this site
None. Not a single cookie is set when you browse vehla.app. Theme preference (dark/light) is stored in your browser's localStorage, which is local to your browser and never sent to us.
Your rights (GDPR, CCPA, etc.)
You can:
- Access what we have on you (license records and, when enabled, anonymous device and lifecycle analytics).
- Delete all of it. Your license is revoked when you do.
- Object to processing. You can disable anonymous analytics in Settings without affecting core app access.
Email kailaconsulting@outlook.com from the address tied to your license. We respond within 7 days.
Contact
Kaila Consulting Inc. · Ottawa, Canada · kailaconsulting@outlook.com