Keep, review and export local recognition history
OKYAWATCHDocumentation

Privacy & reliability

Keep, review and export local recognition history

Understand what a record contains and why browser storage is not a synchronized backup.

Updated 3 min read

Share only screens you are allowed to inspect. Local recognition does not make external notifications or cloud translation local.

What this guide covers

Recognition history is a working record in the current browser, not a hosted account archive. Entries can contain recognized text, a timestamp, source and task names, parsed values, translations and action results. A source image is processed in memory rather than attached as a full screenshot to each entry. Review the text before treating an exported row as an accurate observation.

Set it up

Open history, choose the relevant entries and copy a result or export the records as CSV. Give sources and tasks meaningful names before a long session so rows remain understandable afterward. Keep the original context for important readings separately; a timestamp and a short task label may not explain which dashboard or account was visible.

Check the result

The current history store retains up to 500 records. New work can displace older entries, and browser storage has its own capacity and eviction rules. Export important results before clearing history, resetting settings, switching profiles or removing site data. Signing into an account does not turn these local entries into a cloud synchronization promise.

Before you rely on it

CSV export includes time, source, task, type, recognized text, condition, execution results, translation and numeric value. Spreadsheet applications can interpret text in surprising ways, so inspect identifiers, leading zeros and dates after opening a file. The export escapes cells and guards common formula prefixes, but it does not validate the meaning of every recognized value.

Troubleshooting

If saving fails, browser storage may be unavailable or full. First export whatever important records remain accessible, then remove unneeded entries and retry a small test. Private-browsing sessions, browser cleanup tools and another profile can have different persistence behavior. Do not repeatedly reload while assuming that an unsaved result has already been backed up.

Product reference

An external notification and a history entry represent different outputs. A saved result may show that a channel failed; an empty history does not prove that no external service received earlier text. Review your selected actions and service settings before sharing an export, since recognized material can contain personal information even when no screenshot is included.

By default, screenshots are processed in this browser's memory and are not uploaded as recognition records. Tasks and records stay local. External notifications or authorized cloud translation send recognized text to services you configure. Image matching stores only a reduced reference pattern.

Further reading

Sources