Information Security Policy
Effective from: 13. 4. 2026 | Last reviewed: 13. 4. 2026 · v1.0
I. Scope and Purpose
This Information Security Policy defines the controls, processes, and procedures for protecting user data and ensuring secure operation of the DanceStats.cz platform and its lesson booking module. The platform also operates a booking module for dance clubs - each club acts as an independent data controller for their members' personal data. The platform operator ensures the technical security of the infrastructure (see contact details below).
Security Contact
Name: MgPhD.r. AnJan Novákdr8kej ŠiPetr Kovářmk3vo
Role: Owner & Operator / Information Security Officer
Email: see contact page
II. Governance and Risk Management
The organization maintains documented information security policies and procedures that are regularly reviewed and updated:
- Security policy is reviewed at least annually or upon significant infrastructure changes.
- Internal security code review is performed before every deployment (see SECURITY_ARCHITECTURE.md).
- Security controls are continuously updated based on emerging threats and vulnerabilities.
- Responsible vulnerability disclosure is supported via /.well-known/security.txt (SLA: acknowledgment within 48 hours).
III. Identity and Access Management
Access to production systems and sensitive data is restricted by the following controls:
| Control | Description | Status |
|---|---|---|
| OAuth 2.0 Authentication | Users authenticate via Google - no passwords are stored on the server. | Enforced |
| Role-Based Access Control (RBAC) | Four role levels (admin, club, dancer, trainer) with decorator-enforced permission checks on every page. | Enforced |
| Multi-Factor Authentication (MFA) | Enforced via Google OAuth provider - users with MFA enabled on their Google account are automatically protected. All users are encouraged to enable 2FA on their Google account. | Enforced |
| Session Security | HttpOnly, Secure, SameSite=Lax cookies; 30-day session lifetime; CSRF tokens with 2-hour validity. | Enforced |
| Club Data Isolation | Triple-layer tenant isolation in the booking module - middleware, decorator, and query filter. Each club sees only its own data. | Enforced |
IV. Data Encryption
Encryption in Transit
- All communication uses TLS 1.2 or higher (enforced at the Railway platform and Cloudflare level).
- HTTP Strict Transport Security (HSTS) with max-age of 2 years, includeSubDomains, and preload.
- Cloudflare WAF/CDN provides an additional layer of protection and TLS termination.
Encryption at Rest
- PostgreSQL database is hosted on Railway with infrastructure-level disk encryption.
- Banking credentials are encrypted using Fernet (AES-128-CBC symmetric encryption) before storage in the database.
- Sensitive third-party data is encrypted at rest using the same encryption mechanism.
V. Application Security
| Control | Description | Status |
|---|---|---|
| Content Security Policy (CSP) | Nonce-based CSP policy prevents execution of unauthorized scripts. Violations are logged via /api/csp-report. | Enforced |
| CSRF Protection | Flask-WTF CSRF tokens with 2-hour validity on all forms and AJAX requests. | Enforced |
| XSS Prevention | Jinja2 autoescape on all templates, CSP nonce, JSON data via tojson filter. | Enforced |
| SQL Injection Prevention | Parameterized queries (psycopg %s), allowlist for column/table names. | Enforced |
| Rate Limiting | Four-tier system: strict (5/min for login), moderate (30/min), standard (60/min), default (200/min). | Active |
| Security Headers | 9 security headers: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, COOP, CORP, and more. | Enforced |
| Input Validation | Comprehensive validation module (600+ lines) - names, emails, phones, amounts, safe text with 25+ dangerous pattern detection. | Enforced |
VI. Vulnerability Management
The following practices are in place for detecting and patching vulnerabilities:
- Regular dependency review and updates to latest security versions.
- Automated dependency scanning for known vulnerabilities before deployment.
- Security test suite including SSTI (52 tests), XSS, CSRF, SQL injection, and input validation tests.
- Critical security patches are applied within 72 hours of disclosure.
VII. Monitoring and Logging
- Structured JSON security event logging (no PII in logs).
- Brute-force detection (alert on 10+ failed attempts per minute from a single IP).
- CSP violation logging with /api/csp-report endpoint.
- IDOR attempt detection (alert on 5+ authorization failures per minute per user).
VIII. Incident Response
In the event of a security incident or reported vulnerability, the following procedures apply:
- Acknowledgment of report within 48 hours.
- Status update every 7 days.
- Notification to affected users in compliance with GDPR (without undue delay, no later than 72 hours after discovery of a personal data breach).
Responsible vulnerability disclosure policy: /.well-known/security.txt
IX. Data Handling and Privacy
- Credit card numbers are never stored - booking module payments are processed via bank transfer.
- All banking data (API tokens and transaction PII) is encrypted with Fernet before storage.
- Data minimization - we only process name, email, phone, and information necessary for the service.
- Audit log records all changes with IP address and timestamp (append-only, immutable).
- Accounting records retained for 5 years (Accounting Act, §31), tax documents for 10 years (Tax Code). Other data deleted upon account closure.
- Right to erasure: users can delete their account in settings; data is anonymized or removed in compliance with GDPR.
X. Third-Party Processors
We use the following verified service providers who meet security and data protection standards:
| Service | Provider | Data Access |
|---|---|---|
| Hosting & Infrastructure | Railway Corp. | Physical data storage, encrypted disks |
| Authentication | Google Ireland Limited | Name, email, profile image (OAuth 2.0) |
| Authentication (Apple) | Apple Inc. | Name, email (Sign in with Apple) |
| CDN & Protection | Cloudflare, Inc. | Content delivery (CDN), DDoS protection, WAF, visitor country detection |
| Payment Gateway | GOPAY s.r.o. | Transaction data (card numbers are not shared with us) |
| Bank Account Verification | Fio banka, a.s. | Automatic download of incoming payments from bank account (via Fio API) |
| Member Management (optional) | EOS ClubZone | Member list synchronization with the club's EOS ClubZone system (activated by club admin) |
| Error tracking | Functional Software, Inc. (Sentry) | Technical server error records without personal data (sending of IP addresses and user identifiers is disabled), approximately 5% of requests sampled anonymously for performance diagnostics |
This policy is effective from the date shown in the header and is reviewed at least annually. The last review was performed on the date shown in the header.
These documents are governed by the law of the Czech Republic. Where published in multiple language versions, the Czech version is legally binding and prevails in the event of any discrepancy.
This is version 1.0. Any future material changes will be published as a new, numbered version with a summary of the differences.