Trust center
Security & privacy at Anony Botter
Everything your IT, security or procurement team needs to review us: how data is protected, who processes it, our GDPR and CCPA commitments, and a completed CSA security questionnaire.
Security highlights
CSA STAR Level 1
Our full CAIQ v4.1 self-assessment (283 questions on the Cloud Controls Matrix) is submitted to the Cloud Security Alliance STAR Registry.
Read our answersGDPR & CCPA
We act as your processor under a Data Processing Agreement with EU Standard Contractual Clauses and the UK Addendum. Nothing sent through the app is sold or shared.
Read the DPASign in with Slack
No new accounts or passwords. People use the app through Slack, so your workspace's SSO and two-factor rules apply.
Minimal Slack scopes
The app can't read your channels or DMs. It only sees what people type into its own forms and commands.
See every permissionEncrypted everywhere
TLS on every endpoint and database connection. AES-256 encryption at rest for the database and its backups.
Locked-down access
One operator, with two-factor login on every admin account. The server accepts SSH keys only, and the app runs as an unprivileged user behind a default-deny firewall.
Audited infrastructure
Hosted on DigitalOcean and MongoDB Atlas, whose datacenters hold SOC 2 Type II and ISO 27001 reports. Encrypted backups run every night.
View subprocessorsPCI DSS via Paddle
Paddle is our merchant of record and processes all payments in a PCI DSS Level 1 environment. We never see or store card details.
Dependency scanning
Automated weekly update checks and a monthly vulnerability scan that blocks releases with high or critical issues. Critical fixes ship within 7 days.
AI is opt-in
No message text goes to an AI provider unless a workspace admin turns an AI feature on. Your data is never used to train models.
Written security policy
A published information security policy covering access, change management, encryption, incident response and suppliers, reviewed every year.
Read the policyVulnerability disclosure
Found something? Email us with "Security" in the subject. We reply within 3 business days and won't pursue good-faith research.
Report an issueWho runs Anony Botter?
Anony Botter is built and operated by an independent developer. That means exactly one person can access production systems and customer data, and there are no employees or contractors with access. The practices below are set out in our Information Security Policy. We don't hold a SOC 2 or ISO 27001 certificate; instead we publish the self-assessment below, built on the Cloud Security Alliance's Cloud Controls Matrix, so your team can review us quickly.
How is data protected?
- Slack requests are verified. Every request from Slack is checked against Slack's signing secret before the app acts on it.
- Encrypted in transit and at rest. HTTPS/TLS on every endpoint and database connection; AES-256 storage encryption in MongoDB Atlas.
- Minimal Slack permissions. The app can't read your channels' message history. It only sees what people send to it.
- Locked-down access. The server accepts SSH keys only; the admin dashboard uses bcrypt-hashed credentials, short-lived HttpOnly sessions and login rate limiting. Secrets live in server environment variables, never in code.
- AI is opt-in. No message text leaves for an AI provider unless a workspace admin turns an AI feature on.
What can the app access in Slack?
These are the only bot permissions Anony Botter asks for when you install it. It has no permission to read channel history.
| Scope | Why we need it |
|---|---|
channels:read | List public channels so you can pick where to post |
groups:read | List private channels the app was added to |
chat:write | Post anonymous messages, polls and replies as the app |
chat:write.public | Post to public channels without being invited first |
commands | Run the /anony slash command |
users:read | Look up member names and admin roles for replies and settings |
im:history | Part of the app's read-only Messages tab. The app subscribes to no message events, so it never receives DM text |
Subprocessors
These providers process customer data for us. We'll update this list before we add a new one; customers who signed our DPA can ask to be notified by email.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Slack Technologies | Platform the app runs in | All app content, posted as app messages | Per your Slack data residency |
| MongoDB Atlas | Database | Installation records, messages, polls, settings, subscriptions | United States |
| DigitalOcean | App hosting | All app data in transit and in memory | United States |
| Vercel | Website hosting and the Paddle billing webhook | Website requests; subscription events written to the database | United States |
| Paddle | Payments (merchant of record) | Billing name, email, payment details | United Kingdom / United States |
| Sentry | Error monitoring | Error reports, which can include IP addresses | European Union (Germany) |
| OpenAI | AI features, only if an admin turns them on | Message text, banned-topics policy text | United States |
GDPR and CCPA
There is no official GDPR or CCPA certificate, so no vendor can honestly show one. What we do:
- Act as your processor for workspace content, under a Data Processing Agreement that includes the EU Standard Contractual Clauses and the UK Addendum for transfers.
- Publish an accurate privacy policy listing everything we store, who can see anonymous senders, and how to delete data.
- Honor access, correction, deletion and export requests, and never sell or share anything sent through the app (CCPA "sale" or "sharing").
- Notify affected customers of a personal data breach without undue delay and within 72 hours of becoming aware of it.
Report a vulnerability
Email hi@hamzawaleed.com with "Security" in the subject. We acknowledge reports within 3 business days and won't pursue good-faith research that avoids privacy violations and service disruption.
Security questionnaire
Pre-answered, grouped by the 17 domains of the CSA Cloud Controls Matrix v4, which the CAIQ and SIG Lite both map to. Updated 2026-11-22. Need your own form filled in? Email it to us and we'll return it.
A&AAudit and assurance
- Do you hold third-party security certifications (SOC 2, ISO 27001)?
- No. Anony Botter is run by an independent developer and has no third-party audit. We publish a self-assessment against the CSA Cloud Controls Matrix (this page) and answer customer questionnaires on request.
- Do your infrastructure providers hold certifications?
- Yes. MongoDB Atlas, DigitalOcean, Slack, Paddle and Sentry each publish SOC 2 Type II and/or ISO 27001 reports through their own trust centers.
AISApplication and interface security
- How are requests from Slack authenticated?
- Every request from Slack is verified with Slack's request signing secret (HMAC-SHA256 with a timestamp check) by the Bolt framework before any handler runs.
- How is the internal admin dashboard protected?
- Username plus a bcrypt-hashed password, compared in constant time; a signed JWT session in an HttpOnly, Secure, SameSite=Strict cookie scoped to /admin that expires after 8 hours; and a lockout after 5 failed logins in 15 minutes per IP.
- Is code tested before release?
- Yes. Unit and integration test suites run in a pre-commit hook and must pass before code reaches the production branch.
BCRBusiness continuity and operational resilience
- How is the service kept running?
- The app runs under the pm2 process manager, which restarts it automatically if it crashes. Data lives in MongoDB Atlas, a managed, replicated database, separate from the app server.
- Do you have a business continuity plan or uptime SLA?
- We maintain a business continuity and disaster recovery plan with recovery objectives per service, exercised annually (first exercise November 2026). There is no contractual uptime SLA. Messages already posted stay in Slack even if the app is unavailable.
CCCChange control and configuration management
- How are changes deployed?
- All code is version-controlled in Git. Production deploys only from the main branch after tests pass, with a separate staging environment for testing changes.
CEKCryptography, encryption and key management
- Is data encrypted in transit?
- Yes. Slack, the website and the app's public endpoint are served over HTTPS/TLS, and the app connects to MongoDB Atlas over TLS.
- Is data encrypted at rest?
- Yes. MongoDB Atlas encrypts all cluster storage and backups at rest by default (AES-256). We don't add field-level encryption on top.
- How are secrets managed?
- API keys, Slack secrets and database credentials are kept in environment variables on the server, not in source code.
DCSDatacenter security
- Where is data hosted?
- In the datacenters of MongoDB Atlas (database) and DigitalOcean (app server). We don't operate our own datacenter; physical security is covered by those providers' audits.
DSPData security and privacy
- What customer data do you store?
- Workspace installation records and Slack tokens, anonymous message and poll content, workspace settings and subscription records. We don't read channel history. The full list is in our privacy policy.
- Can workspace admins see who sent an anonymous message?
- Not by default. Only if an Enterprise workspace turns on audit mode, which senders are told about in the compose window. See the privacy policy for every case.
- Do you sign a Data Processing Agreement?
- Yes. Our DPA is published at /dpa and includes the EU Standard Contractual Clauses and UK Addendum by reference.
- How is data deleted?
- Workspace data is deleted on request by a workspace owner or admin, confirmed by email. Payment records may be kept where the law requires it.
- Do you sell or share data for advertising?
- No. Nothing sent through the app is sold or shared.
- Is customer data used to train AI models?
- No. AI features are off by default. When an admin turns one on, message text goes to OpenAI through its API, which doesn't train on API data by default.
GRCGovernance, risk and compliance
- Who is responsible for security?
- The developer who runs Anony Botter is responsible for security, privacy and incident response, and is the contact for security questions.
- Do you have written security policies?
- Yes. Our Information Security Policy is published at /security-policy and reviewed at least annually. Internal documents cover business continuity, risk, a DPIA, a threat model, key management, vulnerability management and incident response.
HRSHuman resources
- How many people can access customer data?
- One: the developer who runs the service. There are no employees or contractors with access.
IAMIdentity and access management
- How is production access controlled?
- The app server accepts SSH key authentication only; password login is disabled. Every administrative account (hosting, database, source code, Slack, billing, monitoring) requires multifactor authentication. Database credentials are held only by the developer.
- Do end users have accounts or passwords with you?
- No. People use the app through Slack; identity comes from Slack, so your workspace's SSO and 2FA rules apply.
IPYInteroperability and portability
- Can we export our data?
- Yes, on request. Email us from a workspace owner or admin account and we'll send your workspace's data as JSON.
IVSInfrastructure and virtualization security
- How is the network exposed?
- The app listens on localhost only. Public traffic reaches it through nginx over HTTPS, which terminates TLS. The server runs a default-deny firewall, accepts SSH keys only, and runs the app as an unprivileged user.
LOGLogging and monitoring
- Do you log and monitor errors?
- Yes. Application errors are reported to Sentry (EU region) and process logs are kept on the server.
SEFSecurity incident management
- Will you notify us of a breach?
- Yes. We'll notify affected workspaces without undue delay, and within 72 hours of becoming aware of a breach affecting personal data, as set out in our DPA.
- How do we report a vulnerability?
- Email the security contact on this page. We acknowledge reports within 3 business days.
STASupply chain management, transparency and accountability
- Which subprocessors do you use?
- Listed on this page, with what each one processes. We update the list before adding a new subprocessor.
TVMThreat and vulnerability management
- How do you manage vulnerabilities in dependencies?
- Dependencies are pinned with lockfiles. Dependabot and Renovate propose updates, and a scan runs monthly and on every change, failing on high or critical advisories. Fixes follow CVSS-based deadlines: critical within 7 days, high within 30.
- Do you run penetration tests?
- No third-party penetration test has been performed.
UEMUniversal endpoint management
- Do you manage endpoints that access customer data?
- Customer data is accessed only from the developer's own computer. There is no fleet of managed devices.