Security
Last updated November 21, 2026
How the service is protected
- No passwords. Members sign in with a one-time code sent to their work email. A code is valid for 10 minutes, allows a limited number of attempts, and is stored only as a hash.
- Sessions. A session is a random token in an HTTP-only cookie. The server stores only its hash, so a copy of the database cannot be used to sign in.
- Rate limits. Sign-in requests, code attempts and reports are limited per email address and per IP address.
- Encryption in transit. Every connection uses HTTPS.
- Content safety. Article HTML is sanitized with an allowlist, and images from other hosts are fetched by the server only from public addresses and re-served with a restrictive policy.
- Least privilege. Members see only their own business's data; moderation is limited to named administrators.
Reporting a vulnerability
Email support@amention.com with the steps to reproduce the issue and its impact. Reports are acknowledged, investigated and kept confidential, and the reporter is told when the issue is fixed. The same contact is published in security.txt.
Good-faith research is welcome within these rules:
- Use only accounts you own, and do not access, change or delete other people's data.
- Do not run denial-of-service tests, send spam, or use social engineering or physical attacks.
- Stop and report as soon as you find an issue.
- Allow reasonable time for a fix before telling anyone else.
amention does not pursue legal action against research that follows these rules.