> cat /privacy/capybara-notes.txt

CAPYBARA PRIVACY NOTES // v1.0.0

Your problemsstay yours.

problem.me is designed to work without an account or cloud investigation store. Your reasoning can stay in the browser, but “local” does not mean “magic vault.” These notes explain the boundaries.

LOCAL-FIRST_

WORK STAYS IN YOUR BROWSER

Standalone technique drafts use browser local storage. Saved Shared Investigations use IndexedDB on the current browser and device.

PRIVATE SESSION_

NO PROBLEM.ME PERSISTENCE

Private Session keeps current investigation changes in page memory instead of writing them into problem.me browser storage. Refreshing or closing can discard them.

PORTABLE FILE_

.PROBLEMME IS READABLE JSON

Exports are data files, not encrypted containers. Anyone you give the file to can read the investigation content.

NO SECRET VAULT_

DO NOT PASTE CREDENTIALS

Avoid passwords, API keys, access tokens, private keys, recovery codes or other secrets in problem descriptions and evidence notes.

WHAT “LOCAL” MEANS_

When Local Save is active, problem.me writes investigation data into storage controlled by your browser. Shared Investigations use IndexedDB; the older standalone technique workspaces use localStorage for their own drafts.

That storage belongs to the current browser profile on the current device. Clearing site data, privacy cleanup tools, browser resets or changing devices can remove it.

BROWSER STORAGE IS NOT A BACKUP. Export important investigations as .problemme files and keep those copies somewhere you trust.

WHAT PRIVATE SESSION MEANS_

Private Session is a problem.me storage mode. While active, current investigation changes are not persisted into problem.me local investigation storage. An older saved copy can remain untouched while you work privately.

Private Session is not the same as browser Incognito/Private Browsing and it does not make the device anonymous. Your browser, operating system, clipboard manager, screenshots, downloads or other software can still create traces outside problem.me.

WHAT LEAVES THE PAGE_

The current problem.me runtime is static and does not include analytics, telemetry, cloud investigation persistence or third-party tracking scripts. The application code does not send investigation field contents to a remote service.

Normal website delivery still requires your browser to request the HTML, CSS, JavaScript and other site files from the hosting infrastructure. Those ordinary page requests are separate from the content you type into an investigation.

EXPORTS, CLIPBOARD AND PDFS CREATE COPIES_

.PROBLEMMEReadable UTF-8 JSON. Portable, useful, not encrypted.
COPY SUMMARYPuts investigation text on the system clipboard, where other software may have access depending on your device settings.
PRINT / SAVE PDFCreates a document through your browser or operating-system print flow. That copy is outside problem.me storage.
SCREENSHOTSAre device files. Private Session cannot retract them.

BEFORE YOU PASTE THAT_

Problem-solving notes can contain sensitive business, personal or operational details even when they do not contain passwords. Use the minimum detail needed to reason clearly.

  • Do not enter credentials, secrets or recovery codes.
  • Prefer roles or pseudonyms when a person’s real identity is unnecessary.
  • Keep exported files only where you intend them to be stored or shared.
  • Review a summary before copying it into email, chat or another system.
  • If the information requires regulated or organization-specific handling, follow those rules first.

DELETING LOCAL DATA_

My Investigations can delete individual saved investigations or all locally saved investigation records. Standalone technique pages also expose local-data clearing controls for their drafts.

Deletion from problem.me browser storage does not delete copies you already exported, printed, copied, screenshotted or backed up elsewhere.

IF AI OR CLOUD FEATURES ARRIVE LATER_

The privacy boundary should stay explicit. Any future feature that intentionally sends investigation content to a remote service should say so before transmission and should remain distinguishable from the current local-first workflow.

CAPYBARA RULE: Never make the user guess whether their problem is staying on the device.

OPEN PRIVATE INVESTIGATION →MY INVESTIGATIONS →