🔒 Infrastructure
- Where is customer data hosted?
- DigitalOcean datacentres (AMS3 — Amsterdam). Your data stays within our managed infrastructure and never leaves approved regions.
- Is data encrypted at rest?
- Yes. PostgreSQL databases use encrypted storage. Sensitive fields (e.g. API keys, credentials) are encrypted with AES-256 using a separate encryption key independent from the application secret key.
- Is data encrypted in transit?
- All traffic between users and our platform uses TLS 1.3 via Let's Encrypt certificates. Internal service-to-service communication uses HTTPS where possible; internal links within the Docker network are isolated by design.
- Who can access production databases?
- Only senior engineers with a business need. All access is logged, audited, and authenticated via SSH keys + bastion host. No direct database access from the public internet.
📦 Backups & Disaster Recovery
- How often are backups taken?
- Daily encrypted backups at 04:00 UTC. PostgreSQL logical dumps are compressed, encrypted with GPG, and uploaded to Backblaze B2 (us-west region).
- Are backups isolated from production?
- Yes. Backups are stored in a separate Backblaze B2 bucket with distinct credentials. A production compromise cannot reach backup storage.
- How long are backups retained?
- 14 days for standard plans. Enterprise customers can request extended retention.
- How often are restoration tests performed?
- Quarterly. A full restore is performed against a staging environment and validated for data integrity.
- What are the recovery objectives?
- Recovery Time Objective (RTO): < 4 hours. Recovery Point Objective (RPO): 24 hours (daily backups). Enterprise plans can negotiate tighter objectives.
🔑 Authentication & Access Control
- What authentication methods are available?
- SSO via Google / GitHub, email + password, and magic links. All authentication is handled by Authentik, our identity provider.
- Is Multi-Factor Authentication (MFA) available?
- Yes. MFA via TOTP (Google Authenticator, Authy, etc.) can be enabled from your dashboard security settings.
- How are user sessions managed?
- Sessions are JWT-based with configurable expiry. Users can view and revoke active sessions from their security settings.
📊 Monitoring & Incident Response
- How is the platform monitored?
- Prometheus collects metrics from all services. Grafana provides dashboards. Loki aggregates logs. UptimeKuma monitors external endpoints. All infrastructure is monitored 24/7.
- What happens when something breaks?
- Alerts flow through Alertmanager → Telegram (instant) + email. Critical incidents page the on-call engineer automatically. Our incident response runbook covers containment, diagnosis, resolution, and post-mortem.
- How are security incidents handled?
- We follow a documented incident response process: detect → contain → eradicate → recover → post-mortem. Customers are notified within 24 hours of confirmed security incidents affecting their data.
🇰🇪 Compliance & Data Protection
- How does JengaStack handle Kenyan data protection obligations?
- We are working toward full compliance with the Kenya Data Protection Act (2019). We maintain data processing records and only engage subprocessors who meet equivalent standards.
- What subprocessors do you use?
- DigitalOcean (cloud infrastructure), Backblaze B2 (backup storage), Brevo (transactional email), Zoho Mail (support email), Sentry (error monitoring). Each has been assessed for data protection standards.
- Do you offer Data Processing Agreements (DPAs)?
- Yes. Enterprise customers can request a signed DPA. Contact [email protected] to initiate.
Have more questions?
We're happy to walk through our security practices in detail.
Chat with our team