Press kit — fact sheet, assets, contact.

All you need to write about ByteGuard, in one place. No PR people, no NDAs. Just the facts.

Fact sheet

The core facts. Quote them. Verify them. Send corrections if anything is wrong.

• What: Privacy-first password manager for iPhone, iPad, and Mac. Encrypted vault for passwords, passkeys, 2FA / TOTP, bank cards, identity documents, software licenses, OAuth tokens, and secure notes — 8 data types covered.
• Who: Built by one developer (solo). Background: payment systems engineering. The transparency center and continuity plan exist specifically because a single-developer closed-source password manager would normally be untrustworthy by default.
• When: Launched on the App Store in 2026. Currently version 2.3.x. Public security whitepaper published 2026-05-03. Crypto module open source targeted for Q3 2026 (if the date slips, the page will be updated with the new date and reason); independent third-party audit targeted for Q4 2026 (if the date slips, the page will be updated with the new date and reason).
• Where: App Store: apps.apple.com/app/id6756919439 · Website: bytelink.online (35 languages) · GitHub: planned Q3 2026.
• Why it exists: Existing password managers fall into two camps. Cross-platform SaaS (1Password, Bitwarden) means many subprocessors and a subscription model. Apple Keychain is free and integrated but only handles passwords — no cards, no notes, no TOTP for everything. ByteGuard fills the middle: Apple-only, lifetime pricing, full digital identity coverage, zero-knowledge architecture.
• How it works: Argon2id key derivation (64 MB × 3 iterations, OWASP recommended) · HKDF-SHA256 key hierarchy (Master → KEK → Vault DEK → Item Key) · AES-256-GCM field-level encryption with per-write IV · BIP39 12-word Secret Key as independent second factor · local-first with optional end-to-end encrypted iCloud Keychain + CloudKit Private DB sync · Passkey (FIDO2 / WebAuthn ES256) · HIBP breach detection with k-anonymity (only SHA-1 prefix-5 leaves the device) · AutoFill extension (login + passkey + TOTP).

What makes ByteGuard different

These are the angles editors usually ask about. Verify each against the linked source page.

• Only 2 subprocessors (Apple + HIBP). Most password managers list 5 to 20. See the Transparency Center for the full list with status pages.
• Open-source crypto core publicly targeted for Q3 2026 (if the date slips, the page will be updated with the new date and reason). The cryptographic primitives (KDF, ciphers, key hierarchy) will be MIT-licensed and independently auditable.
• Independent third-party security audit publicly targeted for Q4 2026 (if the date slips, the page will be updated with the new date and reason). Target firms: Trail of Bits, Cure53, or Doyensec. Audit report and remediation will be published in full.
• $9.99 lifetime option (vs $36/yr for 1Password). No subscription trap. The price reflects honest math from a solo developer, not a race to the bottom.
• HIBP breach detection is free for every user, not gated to a paid tier. Most managers paywall this.
• 35-language UI with prerendered HTML — every page is crawlable and translatable end-to-end.
• Apple ecosystem only, on purpose. iOS / iPadOS / macOS forever — no web app, no browser extension, no Windows / Android builds. Each platform missing is a deliberate architectural decision documented on the honest list section of the home page.

Pricing at a glance

Three tiers. No hidden fees, no expiring keys, no enterprise upsell.

• Free: Full local password management, password generator, biometric unlock, AutoFill, passkey management, 2FA authenticator, HIBP breach detection. All without paying anything.
• Premium: $0.99/month or $5.99/year. Adds iCloud cross-device sync (E2E encrypted), unlimited vaults, TOTP linked to entries, batch import / export, multi-color themes. 30-day free trial on the first subscription. Cancel anytime.
• Lifetime: $9.99 one-time purchase, no subscription, all future updates included. App Store handles billing.

Brand assets

Use these directly in your article — no permission email needed. Attribution appreciated but not required.

• Site OG image (1200×630, EN + ZH): /og-image-en.png · /og-image-zh.png
• Secondary page OG images (6 pages × 2 languages, /og-images/): transparency · continuity · pricing · security · architecture · press
• iOS app screenshots in 6.9" (1320×2868): /marketing/shots/en-light/01.webp through 10.webp (vault, totp, history, security, autofill, passkeys, cards, etc.)
• App icon (1024×1024): /apple-touch-icon.png
• Security Whitepaper (EN + ZH markdown): /docs/whitepaper/
• RSS feed (35 languages): /{lang}/blog/feed.xml

Press contact

One email handles all inquiries. Subject-line prefixes help triage.

• Press inquiries: [email protected] with subject line prefix [PRESS]. Interview requests, fact-checking, embargoed deep dives, podcast invitations — all welcome.
• Security disclosures: [email protected] with subject [SECURITY]. Acknowledged within 24 hours; coordinated disclosure window negotiable per CVE / severity.
• Partnership / general: [email protected] (no prefix). Best-effort response within 5 business days.

Interview availability

What I can talk about, and what I won't.

• Cryptographic decisions — Argon2id parameters, key hierarchy, IV strategy, what 1Password / Bitwarden chose differently and why.
• Solo developer reality — release cadence, audit timing trade-offs, why I'm closed source for now and what triggers open sourcing.
• Apple-only strategy — why no Android / Windows / browser extension, and the security argument behind each missing platform.
• Transparency center model — the editorial decision to publish subprocessors, incident log (currently empty), and dated roadmap commitments.
• Continuity plan — five concrete promises that hold if I'm hit by a bus, including the GitHub dead-man's switch mechanism.
• I won't share user data, vault numbers, individual revenue figures, or internal Apple feedback. Specific financial metrics are not part of the transparency commitment.