Privacy Policy
Last updated: 2026-10-31
Applies to: the Blyck desktop app and the Blyck mobile app (iPhone and Android) (blyck.dev) · Contact: support@blyck.dev
1. Summary — Principles
Blyck is a local-first desktop app. Your code, terminal contents, database data, and passwords are never sent to Blyck servers. We do no behavioral analytics. The table below lists every case in which the apps talk to the outside world.
2. What we collect and why
| Item | Data | When | Retention |
|---|---|---|---|
| ① Update check | App version requested from update.blyck.dev (a standard HTTP request — your IP address may appear in server logs) | Automatic (at startup + every 4 hours) | Access logs (IP address, request time, file requested, app/browser info) are used only for aggregate statistics such as download and update counts, and are automatically deleted after 90 days |
| ② License validation | License key + a device identifier (derived from hostname, username, OS) sent to Lemon Squeezy | When you enter a key + periodic revalidation | Per Lemon Squeezy's policy |
| ③ Send diagnostics | Recent error log (secrets auto-masked) + app version and OS type | Only when you press the "Send diagnostics" button (opt-in) | Auto-deleted after 90 days |
| ④ AI features | The AI CLI you installed and signed into yourself (Claude → Anthropic, Codex → OpenAI) sends the prompts you type and any code or files you include to that provider under your own account, subject to that provider's data policy. Never routed through Blyck servers | When you use AI chat | Per that AI provider's policy |
| ⑤ Website visits (blyck.dev) | Page request logs (IP address, time, page, browser info), used only for aggregate statistics such as visit counts. Cookies are not logged. Not app traffic | When you visit the site | Automatically deleted after 90 days |
| ⑥ Phone notifications (optional) | Only if you turn on [Get notifications] in the mobile app: your phone's notification address (Firebase messaging token), device type, the list of PCs allowed to notify you, and the notification types you chose are registered with the Blyck notification server (push.blyck.dev). When a notification is sent, its type, the PC name, and the chat title (up to 20 characters; can be turned off) pass through the Blyck notification server and Google's and Apple's notification services to your phone. If "Show progress on lock screen" is on in the mobile app, two progress numbers (e.g. 3/7) and running/ended for AI work also travel the same way (step names are never sent) | When you turn notifications on + when a notification occurs | Notification text and progress numbers are not stored. Registration data is deleted immediately when you turn notifications off, or automatically if the app has not refreshed it for 30 days |
3. How diagnostics are handled (details of ③)
- What: the recent portion of the app's error log. Passwords, tokens, API keys, connection strings, and usernames in home paths are automatically masked (
***) — once at write time and once again right before upload. - How: a consent dialog shows you the exact content that will be sent; nothing is transmitted unless you press [Send]. There is no automatic upload.
- Where: a private AWS S3 bucket operated by us (Seoul region). A ticket number is issued on receipt.
- Who: accessible to the operator (developer) only. Never shared or sold.
- How long: auto-deleted after 90 days by a storage lifecycle policy.
- Deletion: email support@blyck.dev with your ticket number and we will delete it immediately, even within the retention period.
4. The mobile app and notifications (details of ⑥)
- Between your phone and PC: viewing chats, sending messages, approvals, and photos travel directly between your phone and your PC over your own Tailscale network and never pass through Blyck servers (every request and response is signed). The phone stores only paired-PC details, keys, and settings in its secure storage (iPhone Keychain / Android Keystore); it does not store conversations, photos, or anything it receives through the new features below.
- New features exchanged directly between phone and PC: the following also travel directly between your phone and PC over the same Tailscale connection and never pass through Blyck, Google, or Apple servers. ① The command, file names, folder name, and risk level shown when you expand an approval notification (the phone fetches them directly from the PC and adds them to the notification on the phone itself), and the [Allow] / [Deny] you tap in the notification. ② When you start a new chat from the phone: the PC's recent folder paths (up to 8) and any new folder name or path you type on the phone. ③ Your "My to-dos" list (text, folder name, done or not). ④ Pictures of PC panes — only while "Allow viewing the PC screen" is on for that phone under Settings › Remote access in the desktop app (on by default; can be turned off). View only — the phone cannot control anything.
- What a notification contains: the notification type (Needs approval, Reply finished, Error, Long task done), the PC name, the chat title (shortened to 20 characters), and an internal number the phone uses to open that chat (plus the approval card number for approval notifications). Conversation content, commands, files, and code are never put in notifications.
- Turning off chat titles: if you turn off "Show chat title" under Settings › Notifications in the mobile app's settings, the Blyck notification server discards the title even if the PC sends it, and it is not passed to Google or Apple.
- Lock-screen progress: if notifications are on and "Show progress on lock screen" (on by default) is on under Settings › Notifications in the mobile app, then while the AI works through a plan, two progress numbers (e.g. 3/7), running/ended, the PC name, the chat title (same 20-character rule; discarded by the server if "Show chat title" is off), and the chat's internal number travel the same route as notifications. Step names are never sent.
- iPhone progress address: the iPhone hands the delivery address (push token) of its lock-screen progress display (Live Activity) directly to the PC over Tailscale. The PC keeps it only in memory (up to 3 per phone; dropped when the progress ends or the PC restarts) and sends it along with each progress update. The Blyck notification server neither stores nor logs this address; it only passes it via Google (FCM) to Apple (APNs) to deliver the progress display.
- Route: PC → Blyck notification server (AWS Seoul region) → Google Firebase Cloud Messaging → (on iPhone) Apple Push Notification service → your phone. Google and Apple process the above content while delivering the notification, under their own policies.
- What the notification server keeps: the notification address, device type, the list of allowed PCs (PC device IDs), chosen notification types, the title setting, the list of features the mobile app supports (e.g. "actions", "progress" — used only to decide how to send notifications), and an encrypted notification key. Notification text and progress numbers are passed on immediately and not stored. Everything is deleted immediately when you turn notifications off, or automatically if the app has not refreshed it for 30 days (for example, after you delete the app).
- Server logs: access logs (IP address, time, request type, result) are used only to prevent abuse and investigate errors, and are deleted automatically after 14 days. Operational logs (request type and result only) are deleted after 30 days. Request bodies (such as chat titles) are never logged. To prevent registration abuse we count registrations per IP address; these counters are deleted within 2 hours.
- Firebase: the mobile app uses Firebase only to receive notifications (no analytics, advertising, or crash reporting). No notification address is created until you turn notifications on. Technical data needed to deliver notifications (installation identifier, app and SDK versions, delivery status, etc.) may be processed by Google under its policies.
- Turning off: you can turn notifications off entirely, or per PC, at any time in the mobile app's settings. The desktop app contacts the notification server only when it is paired with a phone that has notifications turned on.
5. What we do NOT collect
- Code or documents you edit, terminal I/O, database query results, or SSH/SFTP/DB/VNC/WinRM connection details
- In-app usage analytics (clicks, screens, feature statistics) or advertising identifiers
- Saved connection passwords — encrypted with OS facilities (Windows DPAPI / macOS Keychain / Linux keyring) and stored only on your PC; they never leave it.
6. Third-party processors
| Processor | Role | Data shared |
|---|---|---|
| Amazon Web Services (AWS) | Update delivery (CloudFront), diagnostics storage (S3), access log storage (S3), notification relay (Seoul region) | Items ①, ③, ⑤ and ⑥ |
| Lemon Squeezy (a Stripe company) | Payments and licensing (Merchant of Record) | Item ②, plus payment details at purchase (card data never reaches us) |
| Google (Firebase Cloud Messaging) | Phone notification delivery (iPhone and Android) | Item ⑥ — notification address; notification type, PC name, and chat title (if enabled); progress numbers (if the progress display is on) and the iPhone progress address |
| Apple (Apple Push Notification service) | iPhone notification delivery | Item ⑥ — the same content for notifications and progress displays sent to an iPhone |
7. Your rights
You may request access to or deletion of your diagnostic uploads (ticket number required). Phone notification registration data is deleted as soon as you turn notifications off in the mobile app. License and billing data can be managed directly in the Lemon Squeezy customer portal. Contact: support@blyck.dev
8. Changes
Changes to this policy will be announced on this page and in app release notes.