Privacy Policy for StepFill
1. Overview & Local-First Architecture
StepFill is built with a local-first, privacy-first architecture. Your recorded step-by-step SOP guides, screenshots, redacted images, and saved form templates remain stored locally inside your browser (IndexedDB and chrome.storage.local) unless you explicitly sign in and trigger Cloud Sync or optional AI features.
2. Information We Process & Collect
- User Activity & Website Content (Only When You Trigger Recording or Form Filling): During user-initiated recording or form-filling sessions, StepFill captures click coordinates, element selectors, field labels, page URLs, and screenshots of the active tab solely to assemble your step-by-step guide or match and fill form inputs inside your browser.
-
Password & Sensitive Field Protection:
Values typed into
<input type="password">fields are masked automatically inside the browser (••••••••) before any storage, preview, or export occurs. Plaintext passwords are never collected, stored, or transmitted. Optional Auto-PII Blur and Canvas Screenshot Redactor tools run locally in the browser to mask emails, phone numbers, card numbers, and currency values in captured images. -
Optional Account & Authentication Information:
If you voluntarily create a StepFill account, sign in to enable Pro Cloud Sync, or verify a subscription/license key, StepFill processes your email address, authentication session tokens, and Pro entitlement state through our Supabase backend (
deiojirnsefjhimfssvr.supabase.co). - Optional User-Triggered AI Assist: Core SOP recording, local step title generation, Markdown/ZIP/HTML/PDF export, PII redaction, and local form field mapping operate 100% locally on your device without sending page data to external servers. Only when you explicitly click AI Polish or AI Map (or configure your own BYOK API endpoint in Extension Options) are minimal sanitized text snippets or form field labels transmitted over HTTPS for that single request. We do not train AI models on your data.
3. Chrome Web Store Limited Use & What We Never Do
- We do not run background browsing-history trackers outside active recording sessions.
- We do not sell, rent, or transfer user data to third parties, data brokers, or advertising networks.
- We do not use or transfer user data for purposes unrelated to StepFill's single purpose (SOP documentation and user-initiated web form filling), nor for determining creditworthiness or lending purposes.
- We do not collect or transmit authentication cookies from unrelated third-party websites.
4. Chrome Extension Permissions Explained
StepFill requests only the minimal Manifest V3 permissions required for its core functionality:
sidePanel: Displays the StepFill workspace alongside the active webpage so you can control recording, redact screenshots, and trigger form fills without switching windows.activeTab: Reads interactive element metadata and populates form fields in the currently focused tab when you initiate recording, scanning, or replaying.tabs: Tracks page navigation transitions during active SOP recording sessions across tabs and opens captured URLs during multi-step workflow replay.scripting: Supports reliable content interaction during user-initiated recording and form autofill when tab context is needed.storage: Stores local preferences (language, theme, screenshot crop mode), optional Supabase session tokens, monthly free fill counters, and cached entitlement status on device.downloads: Saves user-exported guide files (.zip,.html,.pdf) directly to your local machine.- Host permissions (
https://*/*,http://*/*): Enables SOP recording and user-initiated form autofill across the arbitrary web apps, CRM tools, and internal admin dashboards you work in.
5. Data Retention & Deletion Requests
You can delete any locally stored guides or form templates inside StepFill at any time, or uninstall the extension to erase all local IndexedDB and chrome.storage.local data.
If you created an optional StepFill account for Cloud Sync or billing, you may request account and cloud data deletion through our official Chrome Web Store Support page or the developer contact listed on our Chrome Web Store listing.