Privacy Policy

Version 1.1 · Effective 2026-06-02 · Applies to Klyr v0.3.x for macOS (MAS Free + DMG Pro) and the klyr CLI

Short version: Klyr does not phone home, run analytics, or upload anything about you to our servers. Everything Klyr stores lives on your Mac. The only network calls it ever makes are an opt-in update check and, if you turn it on in Pro, AI requests sent directly from your Mac to the provider you chose using your API key.

Contents

1. What Klyr does and doesn't collect

The Mac App Store edition is fully local. It makes no network calls and does not offer account sign-in, external Pro purchases, or cloud AI. Across all Klyr editions there are no analytics, telemetry uploads, remote crash reports, tracking, or advertising IDs.

The only network calls in the separately distributed Pro edition are:

CallWhenWhere it goes
Sparkle update check When you choose Klyr ▸ Check for Updates dl.klyr.app over HTTPS
AI provider request When you trigger an AI categorization with an API key set The provider you chose (Anthropic / OpenAI / Google), using your key
Pro interest signup If you submit your email in the direct-download Pro app stringswaytech.com/api/klyr/interest (only when you click Send)
Sign in with Apple verification When you click "Sign in with Apple" in the direct-download Pro app Our Cloud Function on Firebase (verifyKlyrAppleSignIn on deployinstantwebapp, US-Central)

These calls are unavailable in the Mac App Store edition, whose updates are handled by Apple. In the direct-download Pro edition, they are off by default and triggered only by explicit user action.

2. What stays on your Mac

These files persist between launches. None of them are ever uploaded.

DataStored atWhy
Watched-folder list~/Library/Application Support/Klyr/watched-folders.jsonSo your sidebar survives a relaunch.
Whitelist patterns~/Library/Application Support/Klyr/whitelist.jsonGlob patterns Klyr will never trash.
Scan history~/Library/Application Support/Klyr/history.jsonPer-scan record (timestamp, root, file count). No filenames.
Error + breadcrumb logs~/Library/Application Support/Klyr/logs/YYYY-MM-DD.logRotated daily, kept 5 days, deletable.
AI provider API keysmacOS Keychain (service app.klyr.Klyr)Encrypted at rest by the OS.
License token (Pro)~/Library/Application Support/Klyr/license.jsonEd25519-signed; verified offline.
Settings + UI preferencesUserDefaults (app.klyr.Klyr suite)Toggles for autoscan, threshold, provider choice.

To wipe everything: Settings ▸ Reset to defaults clears the whitelist, provider choice, and API keys; Clear logs wipes the log directory; the watched-folder list survives reset by design and can be edited per row (right-click ▸ Remove from watched). To remove the lot, drag the directory ~/Library/Application Support/Klyr/ to Trash.

3. What we never see

The Mac App Store edition never collects your Apple ID. The direct-download Pro edition collects Apple identity data only if you sign in with Apple.

If you submit a support bundle (Settings ▸ Bundle for support), Klyr writes klyr-logs-YYYY-MM-DD.txt to ~/Downloads. Nothing is uploaded — the bundle sits there until you choose to share it. Breadcrumbs are opaque tags (scanner=largeFile, phase=enumerate) and never include file paths.

4. AI features (Pro tier, optional)

The Pro build can route file-categorization questions to a Large Language Model. You bring your own API key (Anthropic Claude, OpenAI, or Google Gemini). The request goes directly from your Mac to the provider you selected — Klyr never proxies it through our servers.

What's sent to the provider:

What's never sent: the file body, your username, your machine name, any keychain content, your IP (well, the provider sees it — but Klyr does not forward it).

Your usage with the provider you chose is governed by your separate agreement with them. See:

You can disable AI entirely by setting Settings provider to rule-based; Klyr then uses a 19-rule deterministic classifier with no model and no network calls.

5. Third-party services

ServicePurposeData shared
Apple App Store (MAS Free) Distribution, updates, payment Whatever Apple collects when you install or update the app. See Apple's privacy policy.
Sparkle (Pro DMG only) Update delivery Request to our update server only; no user data sent beyond standard HTTPS metadata.
Your chosen AI provider (Pro) File categorization, optional See section 4 above.
Google Cloud Firestore (Klyr Pro interest signup) Storing your contact details so we can reach out about Pro access, only if you submit the form. We run a Cloud Function on Firebase that writes to Firestore; the data lives in Google Cloud (US-Central region). The email address you typed, optionally your name and phone number if you chose to include them, an optional flag for whether you want beta access, the source page tag, the signed-up-at timestamp, a truncated SHA-256 hash of your IP (not the IP itself — kept only for abuse forensics), and your browser's User-Agent header. Klyr usage data on your Mac is never linked to your interest signup. We control the data ourselves; no third-party email-marketing service holds it.
Google Cloud Firestore (Klyr Pro account identity) Direct-download Pro only: storing your Apple identity (opaque user id), email and name (if Apple shared them), and app/OS version when you sign in with Apple. Data lives in Google Cloud (US-Central region). The Apple user id (Apple's opaque per-app identifier; not your Apple ID itself), email + verified flag + relay flag, optional name, app + macOS version, signed-up-at + last-seen-at timestamps, a truncated SHA-256 of your IP. Klyr usage data on your Mac is still never linked to your identity.

Withdrawal. Email vivek.yadav@stringswaytech.com with the subject "delete my interest" (or "unsubscribe") and we'll delete your klyr_waitlist record the same business day. To delete your Sign in with Apple account record, email the same address with the subject "delete my account" and we'll purge the klyr_users record the same business day.

6. Cookies and tracking on this website

This website (klyr-app.web.app / stringswaytech.com/klyr) sets no cookies, runs no analytics, and embeds no third-party trackers. The only outbound network calls your browser makes when viewing this page are to Google Fonts (for the typography) — that request is governed by Google's privacy policy. We do not log or store any data about your visit.

7. Data retention

8. Your rights

Because we don't store anything about you on our servers, most data-protection rights (GDPR, CCPA, India's DPDP Act, etc.) reduce to "delete the app and its files." Specifically:

9. International data transfers

Klyr's local-only architecture means no personal data leaves your Mac under normal use. The exceptions:

By submitting either, you consent to those transfers.

10. Security practices

11. Children's privacy

Klyr is not directed to children under 13 (or 16 in the EU). We do not knowingly collect data from anyone in that age bracket. Since we don't collect data from anyone over that age either, this is mostly a formality.

12. Changes to this policy

If this policy changes in a material way, the next app update will surface a notice on first launch and a link to a diff against the prior version. Minor edits (typos, clarifications) ship silently. The version + effective date at the top of this page always reflect the current document.

Version history

13. Contact and data controller

Data controller: Stringsway Technologies (the entity publishing Klyr)
Email: vivek.yadav@stringswaytech.com
Website: stringswaytech.com

Email us with privacy questions, takedowns, "I think Klyr did something unexpected", security disclosures, or anything else covered by this policy. Average response time is under 48 hours, weekdays.

14. Governing law

This policy is governed by the laws of India. Disputes — to the extent they survive the privacy-first design above — are resolved in the courts of Pune, Maharashtra, India.

This policy is the current author's draft. A licensed attorney should review it before any commercial launch. If you spot a clause that doesn't match the engineering reality of the app, email us — we treat documentation drift as a bug.