Information Security Policy
Adopted November 20, 2026 · Next review November 2027 · Approved by the owner of Anony Botter
1. Purpose and scope
This policy sets out how Anony Botter protects the confidentiality, integrity and availability of customer data and of the systems that run the Anony Botter Slack app and website. It covers all production systems, source code, subprocessors and the devices used to administer them. It is organized around the domains of the Cloud Security Alliance Cloud Controls Matrix v4.
2. Governance, roles and review
- Anony Botter is operated by a single owner, who is accountable for security, privacy, risk and compliance, approves this policy and any exception to it, and is the security contact (hi@hamzawaleed.com).
- Applicable requirements are identified and documented: the GDPR and UK GDPR, the CCPA, Slack's App Directory and API terms, and customer commitments in the Terms and DPA.
- This policy, the privacy policy, the security page and the DPA are reviewed at least annually and whenever the system, its subprocessors or the data it stores change significantly.
- Exceptions must be decided by the owner, recorded with a reason and an end date, and revisited at the next review.
- Risks are reviewed as part of the annual review and before significant changes, and recorded with a decision to treat or accept them.
3. Access control
- Only the owner has access to production servers, the database, secrets and subprocessor consoles. Access is granted to no one else without a written decision recorded in this policy.
- Multifactor authentication is required on every administrative account (database, hosting, source code, Slack, billing and error monitoring). Server access uses SSH keys, not passwords. Each system is accessed with a unique, individual identity; shared accounts are not used for people.
- The internal admin dashboard requires a username and a bcrypt-hashed password, uses short-lived signed sessions in HttpOnly, Secure, SameSite=Strict cookies, and rate-limits login attempts.
- The app requests only the Slack permissions it needs and cannot read channel history. Workspace members authenticate through Slack, so each customer's SSO and 2FA rules apply.
- Credentials and keys are revoked and rotated when they may have been exposed, and when a person's access ends.
4. Application security and change management
- All code is kept in Git. Changes are tested by automated unit and integration tests that run before commit, and production deploys only from the main branch.
- Changes are tried in a separate staging environment with its own database when they carry risk. Production data is not copied into non-production environments.
- Every request from Slack is verified with Slack's signing secret before it is processed.
- A faulty release is rolled back by redeploying the previous Git commit.
- Vulnerabilities in the code or its dependencies are fixed in order of severity, with critical issues treated as emergency changes.
5. Cryptography and secrets
- Data in transit is protected with TLS on every public endpoint and on database connections. Data at rest is encrypted with AES-256 by MongoDB Atlas.
- Only standard, well-maintained cryptographic libraries are used (Node.js crypto, bcrypt, the providers' TLS); custom cryptography is not allowed.
- Secrets are stored in environment variables on the server, never in source code, and each secret is used for one purpose.
6. Data handling and privacy
- The data the app stores, why, and where, is inventoried in the privacy policy; the providers that process it, and their locations, are listed on the security page.
- Data is classified as: customer content (messages, polls: confidential), credentials (Slack tokens, secrets: restricted), and business data (billing, analytics: internal). Restricted and confidential data never leaves production systems except through the subprocessors listed.
- Privacy by default: AI features and Enterprise audit mode are off until a workspace admin turns them on.
- Data subject requests (access, correction, deletion, export) are handled by email and answered within one month. Workspace data is deleted within 30 days of a verified request.
- Requests from law enforcement are disclosed to the affected customer unless the law forbids it, and answered only when legally required.
- New subprocessors are added to the public list at least 14 days before use, as the DPA requires.
7. Infrastructure and operations
- The app runs on a DigitalOcean server behind nginx, which exposes only HTTPS publicly. The process manager restarts the app automatically if it stops.
- The database is MongoDB Atlas, a managed, replicated service separate from the app server, with encrypted cloud backups enabled. Each workspace's records are keyed by its Slack workspace ID, and every query is scoped to it.
- Physical and environmental security of datacenters is the responsibility of the hosting providers and covered by their independent audits.
8. Logging and monitoring
- Application errors are reported to Sentry, which alerts the owner by email. Process logs are kept on the server, which only the owner can access.
- Alerts and unusual errors are reviewed promptly and handled under section 9 if they may be security-related.
9. Incident response
- Detect and triage: any suspected incident, from monitoring, a customer, a provider or a researcher, is assessed by severity (data exposure, service outage, other).
- Contain: revoke and rotate affected credentials, stop the affected component, preserve logs.
- Notify: affected customers without undue delay and within 72 hours of becoming aware of a personal data breach, and authorities and other parties where the law requires.
- Recover and learn: fix the cause, restore service, and record the incident, its root cause and the corrective actions in a private incident log, reviewed at each annual review.
Vulnerability reports go to hi@hamzawaleed.com and are acknowledged within 3 business days.
10. Suppliers and shared responsibility
- Subprocessors are chosen only if they publish independent security audits (SOC 2 and/or ISO 27001) and sign data protection terms at least as protective as our DPA. Their status is checked at each annual review.
- Shared responsibility: Anony Botter is responsible for the app, its code, its data and its configuration; hosting providers for physical infrastructure; Slack for the Slack platform; and customers for who can use the app in their workspace, their Slack retention settings, and the features their admins turn on.
11. Business continuity
- The source code is stored in Git with a remote copy, so the app can be redeployed to a new server. Configuration needed to rebuild it is documented in the repository.
- During an outage, customers are updated by email for affected paid workspaces. Messages already posted remain in Slack.
12. Devices
Production systems are administered only from the owner's own computer, kept on a supported operating system with security updates installed, full-disk encryption, the firewall turned on, a password required after screen lock, and Find My enabled for locating or remotely erasing it.