Skip to content

We're open source. If actrone-memory has been useful to you, a star on GitHub means a lot to us.

Legal

Security policy

Last updated: October 16, 2026

1. What this policy covers

This Security Policy describes how Apocalypse Technologies (“we”, “us”), which owns and operates Actrone, secures what we offer today: the actrone.com website and the open-source actrone-memory libraries. The hosted platform has not launched, and we will publish its security policy before it does.

2. The open-source libraries

Every change to the libraries passes CI before it merges: linting, strict type checks, unit and integration tests, static security analysis, and CodeQL. Dependencies are pinned in lockfiles and audited on every run, and a known vulnerability fails the build (any severity for Python, high or critical for TypeScript). Releases are published from CI through trusted publishing, with no long-lived registry tokens, and the npm package carries a Sigstore-signed provenance attestation. The libraries send nothing to us.

3. The website

actrone.com is served only over HTTPS, with strict transport security, a strict Content-Security-Policy, and headers that prevent framing and content-type sniffing. Form input is validated against a schema with length limits and rate-limited per IP address, and submissions are stored with a server-side token that never reaches your browser.

4. Responsible disclosure

We take security reports seriously and commit to the following, the same timeline as each library's SECURITY.md: acknowledge your report within 72 hours; investigate, develop a fix, and review it within 14 days; release the fix and publish a public advisory by day 15; credit you in the release notes if you wish. Please do not disclose the vulnerability publicly before the fix is released. We will not take legal action against researchers who follow this policy.

5. Reporting a vulnerability

To report a security vulnerability, email security@actrone.com with: a description of the vulnerability; which part is affected; steps to reproduce; your assessment of the impact; any proof-of-concept code (please do not use it to access real user data). We do not currently operate a bug bounty programme, but we acknowledge every valid report and follow the timeline above.

6. Incident response

If a security incident affects personal data we hold, such as waitlist or contact data, we will notify the people affected within 72 hours of confirming it and tell them what was affected and what we are doing about it. If a vulnerability affects the libraries, we will publish a fixed release and a public advisory. We will publish an incident report, without sensitive details, within 30 days of resolution.