Last updated 2026-09-01
Job Recorder is a Chrome extension whose recorded jobs stay in your browser. This page explains the limited, optional data that may leave it.
The jobs you teach Job Recorder — the recorded steps, and the values you mark as fixed, ask-me, or manual — are stored locally in your browser using Chrome's built-in storage. We don't operate a server that receives or stores your job data.
If you explicitly allow anonymous analytics, Job Recorder creates a random installation identifier and sends limited product events: recording or saving a job, run start/success/failure/cancellation, extension version, generic failure category, coarse step/duration buckets, and opaque random job and run identifiers. This is used only to understand whether the product works and whether people return.
You can decline during onboarding or turn anonymous analytics off in extension settings. When it is off, no new extension telemetry is sent.
Job Recorder requests only the permissions it needs to record and replay actions on the tab you're using, and to store your saved jobs locally. It doesn't request access to tabs or sites you haven't interacted with through the extension.
Replays run inside your normal browser tab, so they reuse whatever login session is already active there. Job Recorder doesn't manage or store separate credentials for the sites you automate.
PostHog processes optional anonymous product events without creating a person profile. Written feedback is stored separately in Supabase and may include an email only if you choose to provide one. We don't sell personal data or use it for advertising.
Feedback messages, optional sentiment, optional reply email, source, extension version, status, and submission time may be stored. Written feedback is not linked to the anonymous installation identifier by default.
Job Recorder is an early product and this policy may change as it evolves. Check this page for the current version.
Questions about this policy: nlukava2002@gmail.com.