Security

Our security and privacy practices

This page describes the controls Hiboty has in place today. Hiboty does not hold an independent security certification such as ISO 27001 or SOC 2.

Data encryption

  • Channel access keys (Telegram token, WhatsApp access token, AI provider API keys) are encrypted in the application with AES-256-GCM; the encryption key is kept in the server environment, not in the source code.
  • All traffic is protected with TLS. Session cookies are issued as HttpOnly, Secure and SameSite=Lax.
  • Passwords are hashed with bcrypt (12 rounds); API keys are hashed with SHA-256 and never stored in plain text.

Access and isolation

  • Each organization is a separate tenant; every query is filtered by organization ID and permissions are verified on the server (seeing a screen does not imply permission).
  • Roles: Owner, Admin, Member. Critical actions such as approving campaigns and creating keys require Admin or higher.
  • Sign-in attempts are rate-limited per IP; failed sign-ins are written to the audit log.

Auditing and traceability

  • Sign-in/out, bot creation, channel connection, campaign approval and API key creation/revocation are written to the audit log; records are kept for 2 years (failed sign-ins for 90 days).
  • AI calls, outgoing messages and campaign sends are recorded as usage events; quotas and billing are based on these records.
  • Secret values are masked in logs.

KVKK and GDPR

  • Personal data comes from users who interact with your bot or Mini App and from lists you import (CSV); it belongs only to your organization.
  • Data subject requests (access, deletion, portability) are handled via destek@hiboty.com; the dashboard provides tools to delete and export contacts; the steps are on the Data Deletion page.
  • Only the conversation context needed to generate a reply is sent to the AI provider; there is no automatic cross-organization training.

Operations

  • The database is backed up daily and before every release; backups are kept for 14 days in an access-restricted directory.
  • Dependencies are managed with exact versions and a lockfile; the deployment process runs type checks and automated tests before release.
  • Report vulnerabilities to guvenlik@hiboty.com. We thank researchers who practice responsible disclosure.