> For the complete documentation index, see [llms.txt](https://policies.heavymelon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://policies.heavymelon.com/security-overview.md). # Security overview ## We protect your data. All data are written to multiple disks instantly, backed up daily, and stored in multiple locations. Files that our customers upload are stored on servers that use modern techniques to remove bottlenecks and points of failure. ## Your data are sent using HTTPS. Whenever your data are in transit between you and us, everything is encrypted, and sent using HTTPS. Within our firewalled private networks, data may be transferred unencrypted. Our application databases are generally not encrypted at rest — the information you add to the applications is active in our databases and subject to the same protection and monitoring as the rest of our systems. Supportress production application is deployed on Heroku. Heroku regularly performs audits and maintains [PCI, HIPAA, ISO, and SOC compliance](https://www.heroku.com/compliance) to further strengthen their trust with customers. ## We protect your billing information. All credit card transactions are processed using secure encryption—the same level of encryption used by leading banks. Card information is transmitted, stored, and processed securely on a [PCI-Compliant network](https://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard). All billing details, transactions and handling is done via [Chargebee](https://www.chargebee.com/privacy/) and [Stripe](https://stripe.com/en-gr/privacy). ## Have a concern? Need to report an incident? Have you noticed abuse, misuse, an exploit, or experienced an incident with your account? Please [send us the details](mailto:support@heavymelon.com) and we'll handle it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://policies.heavymelon.com/security-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.