How Fixora processes data
A transparent explanation of Fixora local file and text processing.
Inside your browser
React tool interfaces read the values you enter or files you select. Text and structured data use bundled JavaScript processors. Image tools use browser decoding, Canvas, Blob, and download APIs. Meeting times use the browser’s Intl time-zone database; the calendar file is created locally. Some text/data tools use a local Web Worker.
What is not sent
Fixora does not send file contents, filenames, typed input, extracted content, results, or generated downloads to analytics, ads, a backend, or an AI service. There is no Fixora account or database.
Memory and cleanup
Input lives in the page memory while the tab is open. Generated object URLs are released when replaced or reset. A loaded local processor may remain in the tab until the page closes. Reloading the page clears tool state. Your browser may retain ordinary cache and download history under its own settings.
Practical limits
Local processing consumes your device memory and CPU. Safety caps reduce accidental overload but cannot predict every device limit. Close other heavy tabs and work with smaller batches if the browser becomes slow.
Keep your source files private.
If you report a problem, share the tool name and a nonsensitive example—not confidential files or secrets.
Help & contact