One ledger, eight identities
Every sensitive field encrypted with AES-256-GCM, with its own random IV.
Vaše heslá, vaša kontrola.
Zabezpečte svoje heslá, prístupové kľúče, 2FA a platobné karty šifrovaním AES-256-GCM. Lokálne úložisko, voliteľná synchronizácia iCloud.
Built on modern iOS primitives
Jeden záznamník, len tvoj. Žiadna tretia kópia, nikde.
Nie je to „aplikácia na heslá“ — je to šifrovaný záznamník, ktorý zjednocuje každú digitálnu identitu na jednom mieste. Všetkých osem typov položiek prechádza tým istým pipeline šifrovania na úrovni polí.
No second app needed
Scan to save. AutoFill fills the 6-digit code along with the password.
A strong one, in a second
Random string or EFF wordlist phrase. Live entropy meter.
FIDO2 / WebAuthn
Generated and stored locally. Private key never leaves the device in plaintext.
HIBP · k-anonymity
Only the first 5 chars of the SHA-1 hash leave the device. Your password never does.
Safari · apps · keyboard — one step
System-level AutoFill extension. Face ID confirms; codes get filled in too.
End-to-end · optional
Routed via Apple's private CloudKit. Sensitive fields are encrypted on-device before upload — only ciphertext reaches the server. Toggle off anytime to go fully local.
Yours to keep, anytime
1Password · Bitwarden · LastPass · KeePass · Dashlane · Apple Keychain. Three export formats: JSON / CSV (plaintext) + encrypted .bytegx.
Edited wrong? Deleted by accident? Recoverable.
Every password change saves the previous value — up to 5 history versions kept, one-tap rollback. Deleted items go to a recycle bin and clear after the retention window.
Clipboard counts down. App locks itself.
Pasteboard auto-clears after a configurable delay; foreground / background auto-lock timers can be set separately.
Tap from the lock screen, password's there
Two widgets: quick vault access + on-the-fly password generator.
Tri veci, na ktorých som odmietol zľaviť
Vstavaný TOTP, bezpečnostný audit na zariadení a Passkeys — tri miesta, kde ByteGuard najjasnejšie predčí bežných správcov hesiel.
Codes, without juggling two apps.
Scan to save — every 2FA in one place. The detail page shows the live code with a countdown ring; long-press to copy. With AutoFill, the code goes in along with username and password.
- RFC 6238 TOTP, 6/8 digits · SHA-1 / 256 / 512 HMAC
- iCloud cross-device sync (E2E encrypted, Premium)
- Three export formats: JSON / CSV (plaintext) + encrypted .bytegx
You can only fix what you can see.
Backed by Have I Been Pwned with the k-anonymity protocol — only the first 5 chars of the SHA-1 hash ever leave the device. Every weakness comes with a concrete next step.
- Detects leaked / weak / reused / outdated
- HIBP k-anonymity (SHA-1 prefix-5); plaintext never sent
- One tap jumps to the entry to replace
Private keys never leave the device.
WebAuthn / FIDO2 standard. ES256 (ECDSA P-256, COSE alg -7). Private keys are AES-256-GCM encrypted with the Item Key — plaintext never written to disk. AutoFillExtension handles registration and assertion via the Apple system bridge.
- ES256 (ECDSA P-256, COSE -7)
- AutoFill Extension handles registration + assertion
- iCloud E2E encrypted sync (Premium)
Takto to naozaj vyzerá
Desať obrazoviek v poradí scenárov — celá aplikácia krok za krokom. Bez marketingových fráz.
Every digital identity, in one place.
Top 10 / All / Favorites / Logins multi-view; live filtered search. All eight DataType cases run the full field-level encryption pipeline — not a 'password app', but a digital-identity ledger.
- 8 types: login / card / API key / identity / note / license / passkey / OAuth token
- Each entry gets its own AES-256-GCM key; plaintext never leaves the device
- Local-first; optional iCloud end-to-end encrypted sync
Codes, without juggling two apps.
Scan to save — every 2FA in one place. The detail page shows the live code with a countdown ring; long-press to copy. With AutoFill, the code goes in along with username and password.
- RFC 6238 TOTP, 6/8 digits · SHA-1 / 256 / 512 HMAC
- iCloud cross-device sync (E2E encrypted, Premium)
- Three export formats: JSON / CSV (plaintext) + encrypted .bytegx
One entry — every field at once.
Login detail: username, password, history, linked TOTP, website, custom fields. Each sensitive field independently decrypted with its own IV, shown only on demand. Copy auto-clears the clipboard.
- Each sensitive field independently AES-256-GCM encrypted with its own IV
- TOTP / Passkey two-way linking shown together
- Copy auto-clears clipboard (5 presets)
Made a typo? Deleted by mistake? Recoverable.
Every change saves the previous value (spec:R3 — up to 5 versions kept); tap the timeline to restore. Deleted items are retained for 90 days before permanent removal.
- Up to 5 history versions kept
- Four source markers: manual / AutoFill / imported / sync
- Deleted items retained 90 days
You can only fix what you can see.
Backed by Have I Been Pwned with the k-anonymity protocol — only the first 5 chars of the SHA-1 hash ever leave the device. Every weakness comes with a concrete next step.
- Detects leaked / weak / reused / outdated
- HIBP k-anonymity (SHA-1 prefix-5); plaintext never sent
- One tap jumps to the entry to replace
A strong one — in one second.
Random (4-64 chars / exclude look-alikes / digits-only for PIN) or EFF passphrase, with live entropy meter. Replaces the old value and records the change in history.
- Two modes: random (incl. PIN) + EFF passphrase
- Apple system CSPRNG (Swift Int.random + SecRandomCopyBytes)
- Live entropy meter and strength indicator
Tap in Safari, and the password fills itself.
AutoFill Extension uses Apple's official ASCredentialProviderViewController; after Face ID / Touch ID, the username, password and TOTP all go in together. Info.plist also declares SupportsSavePasswordCredentials, so new passwords save back to ByteGuard from any flow.
- ASCredentialProviderViewController, system-level credential provider
- Safari + third-party apps, all flows covered
- Unlock via Face ID / Touch ID; TOTP delivered in the same step
Private keys never leave the device.
WebAuthn / FIDO2 standard. ES256 (ECDSA P-256, COSE alg -7). Private keys are AES-256-GCM encrypted with the Item Key — plaintext never written to disk. AutoFillExtension handles registration and assertion via the Apple system bridge.
- ES256 (ECDSA P-256, COSE -7)
- AutoFill Extension handles registration + assertion
- iCloud E2E encrypted sync (Premium)
PAN encrypted, CVV never stored.
Card number (PAN) gets its own AES-256-GCM key with a unique IV. Cardholder name, expiry, brand (Visa / Mastercard / etc.) stay searchable as metadata. CVV/CVC are never persisted on this device.
- PAN encrypted; BIN (first 4-6) / last 4 shown in plaintext
- CVV/CVC never persisted on device
- Cardholder / expiry / brand / billing-address metadata
Dark / Light / System.
AppearanceMode three modes: system / light / dark — switch any time, no restart. Premium tier unlocks multi-color themes; Home Screen widgets stay in sync.
- AppearanceMode three modes: system / light / dark
- Multi-color themes (Premium)
- Home Screen widgets follow theme
Zero-knowledge, v doslovnom zmysle.
Tvoje hlavné heslo nikdy neopustí tvoje zariadenie. Tvoj Secret Key sa generuje lokálne a ukladá do Apple Keychain — synchronizovaný medzi tvojimi Apple zariadeniami cez end-to-end šifrovaný Keychain od Applu (môžeš ho tiež ponechať na jednom zariadení). Na dešifrovanie dát sú potrebné oba kľúče a ani ja, ani Apple nedokážeme prečítať žiaden z nich. Nie je to sľub — je to architektúra.
Argon2id key derivation
password + Secret Key + 32B salt → Master Key. Parameters: 64 MB memory · 3 iterations. Resistant to GPU/ASIC brute force.
HKDF-SHA256 key hierarchy
Master Key → KEK → random DEK. Each vault gets its own DEK — no horizontal decryption path.
Field-level AES-256-GCM
Every sensitive field encrypted independently · new random IV on every write. Same plaintext → different ciphertext · authenticated tag prevents tampering.
128-bit Secret Key
A random key (a 12-word BIP39 mnemonic in form), independent of the master password. Even if the master password leaks, your vault still cannot be opened without it.
Toto nie je „nechcem“ — je to architektonicky „nemôžem“.
- See, access, or decrypt your stored data
- Reset your master password
- Recover a vault without your Secret Key
- Hand over decrypted data to anyone — by architecture, no party can decrypt without your master password
- Plant a backdoor in the encryption flow
- Collect analytics or crash reports
What I built. What I chose not to.
No competitor table. No checkmarks. Just an indie developer listing — plainly — what I wrote, and what I deliberately didn't. Read it, then decide whether to trust me with your ledger.
— WHAT I BUILT —
Field-level AES-256-GCM
Every sensitive field encrypted independently, with its own random IV.
Argon2id key derivation
64 MB memory × 3 iterations — resistant to GPU/ASIC brute force.
128-bit Secret Key
A random key independent of the master password — your second line of defense.
Full offline mode
iCloud sync can be turned off in one tap; the app falls back to pure local storage.
HIBP k-anonymity lookup
Only the first 5 chars of the SHA-1 hash are sent — your password never leaves the device.
Native system integration
AutoFill, Passkey, and TOTP all use Apple's official APIs. No reinvented wheels.
Zero third-party SDKs
No analytics. No tracking. No ads. No crash reporters.
— WHAT I CHOSE NOT TO —
No web app or browser extension
XSS, extension supply-chain attacks, CDN takeovers — that surface is excluded by architecture, not policy.
No Android or Windows builds
Each platform means re-implementing the crypto primitives correctly. Get one line wrong and the whole chain breaks.
No team or enterprise sharing
Sharing is trust delegation — I'm still working out how to do it right. Until I am, I won't ship it.
No self-hosting option
Under zero-knowledge, self-hosting just shifts the operational burden to you with no real security gain.
No third-party audit yet
Honestly: I haven't paid for one yet. The /security page documents every crypto decision against the source so anyone can verify independently. Independent audit + open-sourcing the crypto core are both on the 2026 roadmap — follow the GitHub repo to be notified when they land.
No "recover master password" path
If I could recover it, it wouldn't be zero-knowledge. The most reliable backup is still old-school: write your master password and Secret Key on paper and store them apart.
No aggressive release cadence
Crypto-related changes will move very conservatively. Stability over novelty.
Jednoduché. Férové. Tvoja voľba.
Žiadne skryté poplatky. Predplať si mesačne, ročne, alebo zaplať raz na celý život. Všetku fakturáciu rieši Apple.
O tejto aplikácii a o človeku, ktorý ju postavil.
Kto si? Prečo by som ti mal/a zveriť svoje heslá?
Som nezávislý vývojár. ByteGuard píšem sám — žiadny tím, žiadne financovanie, zatiaľ žiadny nezávislý bezpečnostný audit. (V sekcii vyššie to uvádzam úprimne.) Jediné, čo môžem sľúbiť, je samotná architektúra: tvoje hlavné heslo a Secret Key nikdy neopustia tvoje zariadenie a na mojom serveri nie je nič, čo by mohlo dešifrovať tvoje dáta. Ak ti táto premisa nestačí, táto aplikácia pre teba nie je — a to je úplne v poriadku.
Čo ak zabudnem hlavné heslo?
Nedokážem ho obnoviť. To je cena za zero-knowledge: nemôžem resetovať to, čo som nikdy nepoznal. Na denné odomykanie používaj Face ID / Touch ID a hlavné heslo aj Secret Key si napíš na papier uložený v sejfe alebo bankovej schránke. Znie to ako 90. roky — a stále je to najspoľahlivejšia záloha, akú máme.
Čo ak stratím Secret Key?
Záleží, či si pre Secret Key zapol/zapla synchronizáciu cez iCloud Keychain. Ak je iCloud Keychain sync zapnutý (predvolené odporúčané nastavenie): tvoj Secret Key je end-to-end šifrovaný Applom a synchronizovaný naprieč tvojimi Apple zariadeniami. Na novom zariadení stačí prihlásiť sa Apple ID a Secret Key sa obnoví automaticky — stačí si pamätať hlavné heslo. Ak je iCloud Keychain sync vypnutý (maximálna bezpečnosť, oba kľúče si držíš sám/sama): Secret Key nikdy neopustí zariadenie, kde bol vygenerovaný. Jediná záloha je 12-slovná recovery fráza (štandard BIP39) zobrazená pri prvom vytvorení trezora. Napíš si ju na papier a ulož oddelene od hlavného hesla. Bez tej papierovej zálohy nemožno Secret Key na novom zariadení obnoviť. V oboch prípadoch: hlavné heslo je stále potrebné na dešifrovanie čohokoľvek — samotný Secret Key nestačí. A ja som nikdy nevidel ani jeden bit z ani jedného z nich: na mojom serveri nie je nič, čo by mohlo dešifrovať tvoje dáta, a Apple tiež nedokáže prečítať tvoj Secret Key (je E2E šifrovaný v ich vrstve Keychain).
Je synchronizácia cez iCloud naozaj bezpečná? Apple naozaj nič nevidí?
Všetky citlivé polia sú šifrované pomocou AES-256-GCM ešte predtým, než opustia zariadenie. iCloud dostáva iba ciphertext; ani ja nemám kľúč (kľúč nikdy neopustí tvoje zariadenie). Ak nechceš cloud používať vôbec, môžeš sync v nastaveniach vypnúť — aplikácia prejde do plne lokálneho režimu, čo je úplne legitímny spôsob použitia.
Prečo nie Android / Windows / Web?
Dva dôvody. Jeden človek uživí len určité množstvo kódu a multiplatformnosť znamená správne reimplementovať kryptografické primitívy na každej platforme — stačí jeden riadok zle a celá reťaz padne. Druhý: útočná plocha webovej aplikácie (XSS, supply-chain rozšírení, CDN takeover) je oveľa väčšia ako natívna iOS aplikácia. Radšej urobím jednu platformu poriadne, než aby som dodal niečo, čo vyzerá komplexne, ale je nerovnomerne bezpečné.
Je migrácia z 1Password / Bitwarden ťažká?
Priamy import z exportných súborov 1Password / Bitwarden / LastPass / KeePass / Dashlane / Apple Keychain je podporovaný. Celý import prebieha lokálne — nič sa neodosiela. Ak ti exportný formát starého správcu robí problémy, napíš mi mail a podporu doplním.
Bude sa cena zvyšovať? Zmení sa doživotný tarif na predplatné?
9,99 $ doživotne je trvalých a zahŕňa všetky budúce aktualizácie. Ak niekedy pribudne tarif „prémiové predplatné“ (napr. hlbšia bezpečnostná analytika), bude iba predplatný — existujúce doživotné funkcie zaň nikdy nebudú skryté. To je záväzok, ktorý som ochotný dať na túto stránku.