Data Sparrow
Privacy without vague promises
Browser-capable work stays on your device by default. Remote processing is a visible, per-run choice with short-lived storage and confirmed deletion.
Local processing
Data Sparrow does not send filenames, headers, cell values, result statistics, or recipe contents during a local run. Preferences and recipes may be saved locally; source rows are not persisted by default.
Consented API processing
Native formats and heavy jobs may use data-api.bluesparrow.dev only after you review
the destination, limits, retention deadline, and deletion behavior. Consent applies to one run and
is never silently reused.
Ephemeral retention
API inputs, working files, results, and job metadata are deleted after download or explicit deletion, and also on cancellation, failure cleanup, or short TTL expiry. Data Sparrow has no user accounts or permanent dataset library.
Logging
Operational logs may contain tool IDs, phases, duration and size buckets, or stable error codes. They must not contain filenames, column names, values, SQL, recipes, secrets, run artifacts, or request bodies.
Local data controls
Clearing local data removes saved preferences, recipes, recent tools, and any explicitly opted-in drafts. It cannot remove files you already downloaded.