1. Scope
This policy explains how the Reconce Chrome extension processes information while recording, editing and exporting browser workflows. Reconce is an NBOUND.IN software project currently distributed as a beta.
2. Local-first processing
Reconce is designed to process workflow recordings locally on the user's device. The current beta does not automatically upload recorded workflows, screenshots, videos or project files to an Reconce cloud service.
3. Information Reconce processes
When the user explicitly starts or continues a recording, Reconce may process the visible content of the selected browser tab, page titles, user-initiated clicks, scrolling, navigation, keyboard interaction metadata, screenshots, tab video and selected page semantics needed to describe workflow steps.
Reconce can optionally save page addresses according to the privacy setting selected by the user. URL storage can be disabled or limited to origin/path information.
4. Typed values and credentials
Reconce does not intentionally store text-field values, passwords or payment-field values as structured workflow data. However, screenshots and video recordings reproduce what was visibly displayed in the selected browser tab and can therefore incidentally contain personal, confidential, financial, health or communication content visible on screen.
Users should review and redact sensitive information before exporting or sharing recordings or documentation.
5. Chrome permissions
Reconce uses Chrome permissions only to provide its recording and documentation features. activeTab and scripting enable user-initiated workflow capture in the selected tab; tabCapture records that tab when requested; offscreen supports the MediaRecorder lifecycle; and storage keeps settings and workflow state locally.
6. Remote code, analytics and advertising
The current Reconce beta does not download or execute remote code. Executable extension code is packaged with the extension. The current beta does not include advertising or third-party analytics inside the extension.
7. Sharing and sale of data
Reconce does not sell recorded workflow data. The current beta does not automatically transfer recorded workflow content to third parties. Data leaves the extension only when the user intentionally exports or shares a file or recording using their own chosen destination.
8. Retention and deletion
Workflow data is retained locally in the browser profile until the user deletes the relevant guide/project or browser data, or removes the extension/profile in a way that clears local storage. Users should export any project backup they want to retain before removing local data.
9. Security and user responsibility
Reconce minimizes collection and keeps processing local where practical, but no local storage mechanism can guarantee protection against all device-level access. Users are responsible for reviewing recordings before sharing them and for protecting their device and exported files.
10. Changes
This policy may be updated as Reconce evolves. Material changes will be reflected on this page with a revised date.
11. Support
For questions about Reconce privacy or beta behavior, use the Reconce support page.