Last updated: February 2026
Privacy and Trust CenterLocal data controlsMost byteflow.tools workflows process input and output in your browser. We do not collect, store, analyze, or upload browser-local tool payloads. Tools marked External request may contact the listed network target only when you explicitly run that action.
We use localStorage only for safe UI preferences such as theme, language, sidebar state, favorite tool IDs, recent tool IDs, timestamps, and local tool settings. Sensitive payloads, tokens, logs, file contents, full URLs, and tool outputs are not meant to be stored there.
Analytics are limited to an allowlisted, cookie-free taxonomy for aggregate product signals. Allowed events include tool loaded, tool action, copy, download, search performed, related-tool click, and PWA installed. Search events record only query-length buckets and result counts; tool inputs, outputs, JWTs, secrets, logs, file names, file contents, image contents, hash values, full URLs, user IDs, and session IDs are never analytics fields.
Some tools may request external APIs or user-provided URLs to provide functionality. Those tools are labeled External request and describe the network purpose before you run them.
For privacy-related questions, open an issue on our GitHub repository or contact us via the Contact page.
This list is generated from tool manifests. These tools may contact the listed domains only for the disclosed purpose and only after the external-request action is chosen.
Instagram Photo Downloader
External requestRequests the Instagram URL you provide only after you confirm rights and click Download.
Network access starts only after you choose the external-request action.
Vimeo Thumbnail Grabber
External requestLoads derived public Vimeo thumbnail image URLs only after you choose to load the preview.
Network access starts only after you choose the external-request action.
YouTube Thumbnail Grabber
External requestLoads derived public YouTube thumbnail image URLs only after you choose to load the preview.
Network access starts only after you choose the external-request action.
Byteflow processing stays in your browser. Some preferences and non-sensitive tool settings may be saved locally; sensitive payloads are configured not to persist by default.
Tool input, output, files, logs, tokens, and full URLs are not stored. Inspect and clear safe local state here.
Favorite tool IDs saved in this browser.
Recent tool IDs and timestamps saved locally.
Theme, language, PWA prompts, sidebar state, and safe tool options.
Recipe storage is unavailable.
PWA shell, assets, icons, and tool chunks. Tool payloads are excluded.
Some browsers manage app storage and site data in settings. See Install App and Trust Center verification.
Analytics are disabled by default in this runtime. If a future deployment enables a cookie-free aggregate provider, this local preference prevents analytics events from being sent from this browser.
Current status: Disabled by default
Allowed event taxonomy
Allowed events: tool_loaded, tool_action, copy_output, download_output, search_performed, related_tool_click, pipeline_template_opened, and pwa_installed.
Allowed fields are coarse values only: tool ID, related tool ID, action type, language, size bucket, query-length bucket, result count, source page, and platform.
Never analytics fields
Tool inputs, outputs, payloads, tokens, JWTs, secrets, file names, file contents, image contents, log bodies, hash values, search text, full URLs, user IDs, and session IDs are forbidden.
