Skip to content
Knowledge Base

Security Statement

Effective Date: January 1, 2025 Last Updated: November 16, 2026 Language: This document is published in English, German, Spanish, French and Hungarian. The translations are provided for convenience; where a translation differs from the English version, the English version prevails, except that a consumer may rely on the version in their own language where it is more favourable to them.

At Askalot, security is foundational to everything we do. This statement describes our security practices, infrastructure, and commitments to protecting your data.

We understand that you trust us with sensitive survey data. We take this responsibility seriously by implementing comprehensive security measures across our platform, infrastructure, and organization.

Customers are separated in one of two ways:

  • Shared environment (the default): customers share the tenant’s compute and storage, and each customer’s data is separated logically by organization and project, enforced on every request
  • Dedicated deployment: under a Service Agreement, a customer’s tenant runs on infrastructure of its own

Tenant Separation: Each tenant has its own containers, data volumes and database; tenants cannot communicate with each other

Askalot runs in containers and does not depend on a particular hosting provider. The shared tenants run on infrastructure Askalot operates within the European Union. A dedicated deployment runs where the customer chooses — a cloud provider such as AWS, Azure or Google Cloud, or the customer’s own premises — and its physical security is governed by the customer’s agreement with that provider.

  • Firewalls: Multi-layer firewall protection
  • DDoS Protection: Automatic detection and mitigation
  • Intrusion Detection: Continuous monitoring for suspicious activity
  • Network Segmentation: Isolated network zones for different service tiers

All data is protected with strong encryption:

Data State Encryption Standard
In Transit TLS 1.2+ (HTTPS)
At Rest AES-256
Backups AES-256 with separate key management
  • Role-Based Access Control (RBAC): Users only access what they need
  • Multi-Factor Authentication (MFA): Available for all accounts
  • Single Sign-On (SSO): Centralized authentication via OIDC
  • API Token Management: Secure token generation and revocation
  • Session Management: Automatic timeout and secure session handling
  • Daily encrypted backups
  • Geographic redundancy
  • Regular recovery testing
  • Point-in-time recovery capabilities
  • Security-focused code reviews
  • Automated security scanning in CI/CD
  • Dependency vulnerability monitoring
  • Regular security training for developers
  • OIDC-Compliant: Standards-based authentication
  • Password Security: Bcrypt hashing with high work factor
  • JWT Tokens: Cryptographically signed session tokens
  • Secure Cookies: HttpOnly, Secure, SameSite flags
  • Bearer token authentication
  • Rate limiting to prevent abuse
  • Input validation on all endpoints
  • SQL injection and XSS protection
  • Real-time security monitoring
  • Comprehensive audit logging
  • Alerting for anomalous activity
  • Log retention for forensic analysis

We maintain a formal incident response process:

  1. Detection: Automated monitoring and alerting
  2. Containment: Immediate isolation of affected systems
  3. Investigation: Root cause analysis
  4. Remediation: Fix vulnerabilities and restore service
  5. Communication: Timely notification to affected customers
  6. Review: Post-incident analysis and improvement
  • Regular vulnerability scanning
  • Timely patching of security updates
  • Penetration testing by independent security firms
  • Bug bounty considerations for responsible disclosure

We align our security practices with industry standards and are committed to achieving formal compliance certifications.

We are committed to compliance with ISO/IEC 27001:2022, the international standard for information security management systems (ISMS). Our security program is designed to meet ISO 27001 requirements, including:

  • Risk Management: Systematic identification and treatment of information security risks
  • Security Controls: Implementation of Annex A controls appropriate to our risk profile
  • Continuous Improvement: Regular review and enhancement of security measures
  • Management Commitment: Leadership engagement and resource allocation for security
  • Documentation: Comprehensive policies, procedures, and records
  • Internal Audits: Regular assessment of ISMS effectiveness

We are committed to compliance with ISO/IEC 42001:2023, the international standard for Artificial Intelligence Management Systems (AIMS). As AI capabilities are integrated into our platform, we ensure responsible development and governance through:

  • AI Governance: Clear policies and accountability for AI system decisions
  • Risk Assessment: Evaluation of AI-specific risks including bias, fairness, and reliability
  • Transparency: Documentation of AI system purposes, capabilities, and limitations
  • Ethics: Alignment with ethical principles throughout the AI lifecycle
  • Human Oversight: Appropriate human involvement in AI-assisted processes
  • Regulatory Alignment: Preparation for compliance with the EU AI Act and emerging regulations
  • GDPR: General Data Protection Regulation compliance for EU data protection
  • ISO/IEC 27001: Information security management system framework
  • ISO/IEC 42001: AI management system framework
  • OWASP: Web application security best practices
  • CIS Controls: Critical security controls implementation

We are actively working toward:

  • ISO/IEC 27001 Certification: Formal third-party certification (in progress)
  • ISO/IEC 42001 Certification: AI management system certification (in progress)
  • SOC 2 Type II: Service organization controls audit
  • GDPR Certification: Under approved certification mechanisms

Security is a shared responsibility. We recommend:

  • Use strong, unique passwords
  • Enable multi-factor authentication
  • Review and revoke unused API tokens
  • Monitor account activity regularly
  • Use password protection for sensitive surveys
  • Limit access to survey results
  • Configure appropriate data retention
  • Review participant access permissions
  • Store API tokens securely
  • Rotate tokens periodically
  • Use environment variables, not hardcoded credentials
  • Implement proper error handling

The shared tenants store and process data within the European Union; request metadata passes in transit through Cloudflare’s global edge network (see the Data Processing Agreement, Appendix 3). A dedicated deployment processes data where its Service Agreement states.

A dedicated deployment under a Service Agreement runs where that agreement states, including on infrastructure the customer chooses. Contact us for details.

We continuously improve our security posture:

  • Regular security assessments
  • Ongoing infrastructure hardening
  • Proactive threat monitoring
  • Security feature enhancements

If you discover a security vulnerability:

  1. Do not publicly disclose the issue
  2. Email details to [email protected]
  3. Include steps to reproduce the issue
  4. Allow reasonable time for us to address it

We appreciate responsible disclosure and will acknowledge security researchers who help us improve.

For security-related inquiries: