Operator details, retention periods, logging, backups, service providers, and applicable privacy rights require verification. This is not a finalized privacy policy.
What the current interface sends for conversion
For server tools, a conversion request includes the selected file, its filename, and the chosen settings. The request passes through the API gateway to the Python conversion service. The browser receives output data for preview and download. Local SVG customization does not send the selected SVG to that conversion endpoint.
Browser-side processing is not a no-network promise
The interface uses system fonts instead of requesting an external font stylesheet. Loading website pages and scripts and contacting the conversion API still involve network requests. Local SVG customization describes the selected-file processing path, not the behavior of every website resource.
Retention, logs, and infrastructure remain to be verified
This draft makes no zero-retention or immediate-deletion promise. Temporary-file handling, proxy and application logs, backups, hosting providers, access controls, and deployment-specific retention must be verified before a final privacy policy is published. Avoid uploading sensitive documents while those practices are unresolved.
Privacy requests and future integrations
The operator must supply a monitored contact channel and the applicable privacy-rights procedure. Analytics, advertising, international processing, and consent disclosures must match the integrations and regions actually used at launch. They are not finalized by this draft.