Privacy Policy
Last updated: June 19, 2026
In short
The LivingContext browser extension records a workflow only while you are actively recording, and stores what it captures locally in your browser by default. Passwords and payment fields are masked automatically, screen recording is limited to a single browser tab, and nothing is sent to our servers unless you explicitly connect the extension to a LivingContext account and publish a guide. We never sell your data or use it for advertising.
This Privacy Policy explains how LivingContext (“LivingContext”, “we”, “us”) handles information in connection with the LivingContext browser extension (“Capture Workflows into Docs”, the “Extension”) and the optional LivingContext web service it can connect to (together, the “Service”). By using the Service you agree to this policy.
What the Extension does
The Extension turns a workflow you perform in your browser into a step-by-step guide. While you are recording, it captures each action you take — clicks and the text you type — as a step with an annotated screenshot and a short description. You can then edit, replay, or export the guide. Optionally, you can connect the Extension to a LivingContext account to publish guides as living documentation.
Information we process
The Extension processes the following, only while you are actively recording a workflow:
- Screenshots of the active browser tab at each step, and an optional screen recording of the single browser tab you choose to share.
- Action and element metadata for the elements you interact with — for example an element’s label, ARIA attributes, CSS selector, and on-screen position.
- Page context such as the page title and URL, and the labels of nearby interactive elements, used to describe each step.
- Text you type into form fields, captured as the description of a typing step (aggregated per field — never as a raw key-by-key log).
Information you choose to provide:
- An AI provider API key (OpenAI or Anthropic), if you enable optional AI-generated step descriptions. This key is stored locally in your browser and is used only to call that provider directly from your browser.
- Account / connection details (such as an organization-scoped API key and your account identity) if you connect the Extension to a LivingContext account.
What we do not collect: we do not record passwords or credential/payment fields (these are masked at the moment of capture); we do not keep a raw keystroke log; we do not capture your browsing history; we do not read or capture pages or tabs you are not actively recording; and the Extension contains no analytics, tracking, or advertising technology.
Privacy protections built into capture
- Recording is explicit. Capture runs only after you press “Record” and stops when you stop it.
- Credentials are always masked. Password fields and credential/payment autofill fields are masked unconditionally and are never stored or replayed.
- Personal-data redaction is on by default and can be configured in settings; matching values are blurred in screenshots and masked in step text.
- No raw keylogging. Typing is aggregated into one step per field, and stray keystrokes are filtered through an allowlist (only deliberate shortcuts such as ⌘S and Enter/Escape become steps).
- Screen recording is tab-constrained. The optional video can only capture a single browser tab; sharing a full screen, window, or another application is rejected.
How information is stored
Local-first. By default, everything the Extension captures — guides, steps, screenshots, and recordings — is stored locally in your browser (IndexedDB) and never leaves your device.
When you connect to LivingContext. If you sign in and publish a guide to a LivingContext account, the content of that guide is sent to and stored on the LivingContext web service, scoped to your organization, so your team can access it. Our web service is hosted on Cloudflare and Neon (PostgreSQL).
How we use information
We use the information solely to provide the Service: to create, edit, replay, export, and (if you connect an account) publish and maintain your step-by-step guides and documentation. We do not sell your information, and we do not use it for advertising or for training third-party models.
Third parties and sub-processors
- AI providers (OpenAI, Anthropic). Only if you enable AI descriptions. The relevant step context is sent directly from your browser to the provider using your own API key, and is subject to that provider’s privacy policy.
- Hosting providers (Cloudflare, Neon). Only when you connect to the LivingContext web service; they process data on our behalf to host the Service.
We may disclose information if required by law or to protect the rights and safety of users.
Browser permissions and why we need them
- Host access / activeTab / scripting / tabs / webNavigation: to observe the actions you take and capture steps on the page you are recording.
- Storage / unlimited storage: to save your guides, screenshots, and settings locally in your browser.
- tabCapture / desktopCapture / offscreen: to record the single browser tab you choose and to generate screenshots and clips.
- sidePanel / alarms: to provide the recording and library UI and to keep the extension responsive.
Data retention and deletion
You control your data. You can delete any guide at any time, and uninstalling the Extension removes all locally stored data. If you have published guides to a LivingContext account, you can delete them from your account or ask us to delete them by contacting us at the address below.
Your rights
Depending on your location, you may have rights to access, correct, export, or delete your personal information. Because data is local-first, much of this is in your direct control; for data held in a connected LivingContext account, contact us and we will respond consistent with applicable law.
Children
The Service is not directed to children and is not intended for use by anyone under 16.
Chrome Web Store Limited Use disclosure
LivingContext’s use and transfer of information received from the Extension, and from any Google APIs, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We only use the data to provide and improve the user-facing features described in this policy, and we do not sell it or use it for advertising or unrelated purposes.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected by an updated “Last updated” date at the top of this page.
Contact us
If you have questions about this policy or your data, contact us at naresh@mindblaze.ai.