Published desktop release

Nitoru 0.2.0

Release dateSeptember 6, 2026

Nitoru 0.2 brings encrypted Google sync to your approved devices, Windows Hello protection for sensitive sections, and a Journal streak that keeps your momentum visible.

Your world, in sync

Connect Google when you choose, then keep Journal, Wallet, Calendar, Goals, and Discipline in sync across your approved Windows devices. Your records stay encrypted in Google Drive.

Privacy that feels natural

Choose the sensitive sections you want to protect, then unlock them together with Windows Hello using your Windows PIN, face, or fingerprint.

Keep your momentum visible

See your current consecutive-day Journal streak on the Dashboard, with a clear nudge when today still needs an entry.

Complete changelog

Everything included in 0.2.0

Encrypted synchronization

Connect a Google account only when you want synchronization; Nitoru continues to work without it.
Synchronize Journal, Wallet, Calendar, Goals, and Discipline across approved Windows devices.
Synchronize automatically while Nitoru is running and retry offline changes when the connection returns.
Keep cloud records encrypted in Google Drive instead of uploading Nitoru’s local database.
Review a new installation’s name, platform, request time, and comparison code on a trusted device before approving it; declining securely blocks it until a fresh request is made.
Use streamlined same-account setup and one-time trusted-device approval instead of the old manual approval-code enrollment menu.
Enroll devices with a signed QR flow or copy-and-paste fallback, inspect their fingerprints, and rename or remove them from the trusted-device list.
Disconnect only the current installation without revoking Google access for your other devices, or choose a separate confirmed account-wide revocation; cancelled or failed sign-in leaves other devices connected.
Recover access with your saved recovery kit and authenticated Google Drive history—not with Google sign-in alone.
When provider sync is inactive, rotate the Vault root after removing a device; remaining devices pause for reapproval and the old recovery kit must be replaced.
Keep conflicting changes visible for review and reject or quarantine corrupt, unsigned, wrong-role, and revoked-device operations.
Create explicit recovery copies for eligible changes from a removed device instead of silently accepting them.

Windows privacy

On supported Windows 11 devices, optional Windows Hello protection replaces the old local Journal passcode.
Use the Windows Hello method Windows offers—PIN, face, or fingerprint where configured and supported.
Choose whether Journal, Wallet, and Discipline require verification.
Lock protected sections manually from the sidebar whenever you step away.
Automatically lock after 1–60 minutes of inactivity—five minutes by default—and immediately when Nitoru is minimized or hidden, Windows is locked, or the computer is suspended.

Journal and Dashboard

Build a consecutive-day Journal streak as you keep showing up.
See your streak and whether today still needs an entry directly on the Dashboard.
Hide the Dashboard quote when you prefer a quieter workspace, without deleting saved quotes or changing another device’s preference.

Update and onboarding experience

Meet Nitoru 0.2.0 through a cinematic introduction after updating.
Take an optional guided feature tour, postpone it, or skip it entirely.
Review the expanded privacy notice once before opening an upgraded workspace with encrypted synchronization.
Check Microsoft Store without interrupting startup, then wait 12 hours after a successful check before checking again across launch, focus, resume, and long-running sessions.
Show the update prompt only when Microsoft Store confirms an update and Nitoru’s fixed HTTPS stable manifest validates a newer public release; retry missing or stale notes after three hours.
Dismiss the reminder for later or open Microsoft Store directly from the update prompt.
Keep a confirmed update reminder across an app restart by revalidating the stable manifest without repeating the rate-limited Store request.

Interface and reliability

Use a simpler Sync & Devices settings area with one clear status, the last sync time, and expandable diagnostics.
See clearer synchronization states for syncing, up to date, offline, approval, quarantine, and conflict copies.
Get more specific Google authentication guidance, including permission-aware retry steps.
Reduce repeated synchronization work with a bounded session-only encrypted Drive cache and incremental change reads.
See selected Journal and Goals actions update optimistically while their changes are saved.
Use a safe Back button in Settings and find developer and ownership credit in About & diagnostics.
Rely on fixes across synchronization, Google sign-in, update checks, and first-open Discipline setup.