Encrypted transport
Traffic to and from Converterer is protected with TLS.
Security
Protecting customer data is a core part of operating the service. This page summarises the practical safeguards we rely on today and how to contact us about security issues.
Last updated: 16 April 2026
Controls
Traffic to and from Converterer is protected with TLS.
Files and website capture jobs are processed only to complete the work you requested.
Operational data is removed after processing on a rolling basis, with limited backup retention for recovery and compliance needs.
Access to systems and customer data is limited to people and service providers who need it to operate, support, or improve Converterer.
Payment card details are handled by our payment processor over encrypted connections. Converterer does not intentionally store raw card numbers in its own application systems.
Account security depends on strong unique passwords and careful handling of API keys. Store credentials securely and rotate them if compromise is suspected.
We maintain the application and supporting libraries on an ongoing basis and apply security-related updates as a priority.
If you believe you have found a security issue, email contact@converterer.com with enough detail for us to investigate. Please do not publicly disclose vulnerabilities before we have had a reasonable chance to respond.
Retention
Converterer processes files, URLs, rendered pages, and account metadata to deliver conversions and website captures. Those inputs are not used for advertising, resale, or model training.
Operational copies are typically short-lived, but some logs and backups may remain temporarily for disaster recovery, fraud prevention, and legal compliance.
If you need more detail about how personal information is handled, see our Privacy Policy.
Contact
For vulnerability reports, security questionnaires, customer security reviews, or general support, contact contact@converterer.com.
For legal and policy context, see Terms of Use.
We may update this page as our controls, vendors, and practices evolve.