Recovery or sharing?
JSON preserves the application data model; CSV and PNG are review or sharing outputs, not importable backups.
Elysia Tools
Navigation
Workflow Playbook
Preserve a local habit journal, test JSON restoration without overwriting your working records, and prepare reviewed CSV or PNG copies without private notes.
New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.
First tool: Private Habit Heatmap Tracker
Hubs
| Tool | What it does | Category |
|---|---|---|
| Private Habit Heatmap Tracker | Your habits stay in this browser. No account, no AI, no automatic upload. | Utilities |
| JSON Formatter | Format and validate JSON data | Format Conversion |
| Text Diff | Compare two text inputs and show differences | Text Processing |
| CSV Validator | Validate CSV structure, detect malformed rows, unbalanced quotes and column mismatches | Data Processing |
| File Hash Verifier | Calculate MD5/SHA1/SHA256 hash values for files and verify against expected hashes |
Hubs
| Utilities |
For an individual keeping daily habits, the deliverable is a recoverable notebook plus a separately approved sharing copy, not a medical assessment or cloud synchronization service. Record browser, local date, habit start dates and the year and habit selected in the heatmap. Export JSON before clearing site data, changing devices or testing imports. Local storage can be lost and is not encrypted; extensions, same-origin scripts or other people using the browser may access it. Keep the backup in an appropriately protected location outside browser storage.
The tracker opens an independent page without site analytics, ads or login scripts and does not send records through the tool API. This guarantee does not extend to generic helpers: use synthetic or explicitly redacted copies there, not confidential originals. JSON formatting checks parsing, not valid references, dates or recoverability. The current importer limits files to 2 MB, 30 habits and 20,000 entries and rejects unknown fields, duplicate habit/date pairs, future dates and orphan entries. Do not silently delete failing records; investigate the original and document a deliberate repair.
Prepare an isolated browser profile with no valuable records, and save its baseline if it is not empty. Import the original locally only after reading the replacement confirmation; this is not a merge. Export restored JSON and compare locally, using sanitized copies with text diff if needed. Whitespace and ordering differences can be harmless, while changed dates or completion flags are not. Check habit IDs, start dates, entries and meaningful notes. Empty unfinished entries can be normalized away. Record the local date: timezone changes can affect which dates are considered future. Test representative checked, unchecked and noted days, then reopen to verify persistence.
CSV contains recorded entries, not a complete calendar or full restore model. A missing row is not proof that a day was missed. Today is not in the completion-rate denominator until checked in; statistics begin at the habit start date. Inspect names and notes, then remove sensitive columns or values from a sharing copy without modifying the backup. CSV validation checks structure only. Spreadsheet-safe apostrophe prefixes and quoted fields may affect display; do not strip protections blindly. Inspect the exact PNG for selected year, habit filter, labels and revealing patterns. An image is neither editable evidence nor a backup.
Record source and restored counts, explained differences, local date, tester and the exact backup location. Hash a final approved copy, or use a trusted local hashing utility for confidential originals; never upload a secret file just to obtain a checksum. Hash equality identifies bytes, not encryption, authenticity or recovery success. Keep backup and sharing files separate. Use the general archive restore workflow for ZIP recovery, and tabular cleanup for substantial CSV transformations; neither replaces this application's restore test.
Workflow playbook
Record dates and selection, export JSON and avoid clearing browser storage.
Check syntax on a synthetic or redacted copy; keep the actual recoverable source unchanged.
Import into an isolated profile, export again and compare copies; reconcile meaning rather than whitespace alone.
Validate a safe CSV copy and manually inspect rows and the PNG before distribution.
Hash only an approved copy through helpers and record the exact backup revision; a hash does not encrypt data.
JSON preserves the application data model; CSV and PNG are review or sharing outputs, not importable backups.
A JSON parser cannot establish valid habit references or dates. Only a successful application import and reconciliation test restoration.
Keep notes in protected backups; remove identifiers and sensitive context from separately reviewed sharing files.