Trust Center
Security you can verify
INBULK runs an information security management system built to ISO/IEC 27001:2022. This page explains how we protect your data and how to request our security documentation.
Overview
Companies trust the INBULK platform with commercial terms, logistics details, contracts and identity documents. Protecting that information is part of how we build and run the product, not an add-on.
Our information security management system (ISMS) covers software development and integration, customer maintenance and support. It applies to all three INBULK entities: LLC INBULK.COM (Ukraine), INBULK FZ-LLC (UAE) and Bulk Technologies OÜ (Estonia). Security policies are approved by the CEO, reviewed at least once a year and checked by independent audit.
At a glance
- Hosting
- DigitalOcean
- Encryption in transit
- TLS on all public services
- Encryption at rest
- Provider-level encryption; encrypted off-site backups
- Administrative access
- Multi-factor authentication, private zero-trust network only
- Backups
- Daily, with point-in-time recovery for the production database
- Monitoring
- Centralised logging and security alerting
- Business continuity
- Approved continuity and disaster recovery plans
Compliance
ISO/IEC 27001:2022
Certification audit completed in October 2026. Certificate issuance in progress.
Scope: Software Development and Integration, Customer Maintenance and Support Services.
Data protection
We process personal data in line with the EU General Data Protection Regulation (GDPR), the Law of Ukraine “On Personal Data Protection” and UAE Federal Decree-Law No. 45/2021 (PDPL).
How we protect your data
Infrastructure
Production runs on DigitalOcean; development is kept on separate infrastructure.
No company servers in our offices; all processing is in professional data centres.
Changes to infrastructure go through documented change management with approval, rollback plans and post-change checks.
Data security
Data is encrypted in transit with TLS and at rest by our cloud providers.
Backups sent off-site are encrypted before they leave our systems.
Production data is never used in development; test environments use synthetic or anonymised data.
Access control
Access follows least privilege and is granted per role.
Administrative access requires multi-factor authentication and is reachable only through a private zero-trust network. No administrative services are exposed to the internet.
Developers have no access to production cloud infrastructure.
Privileged access is reviewed every quarter; all other access every six months and whenever someone joins, moves or leaves.
Application security
All source code is held in private repositories with two-factor authentication required for every member.
Changes to production branches need a pull request and peer review before merge.
Security requirements are defined as acceptance criteria when features are planned.
Secrets are kept in approved secret stores and never committed to code.
Network security
Cloud and host firewalls restrict inbound traffic; only public services are reachable from the internet.
Development and production networks are separated.
Endpoint security
Company laptops use full-disk encryption (AES-256), malware protection and central device management.
Screens lock automatically after 5 minutes of inactivity.
Personal devices used for work must meet a security baseline and be approved before use.
Monitoring and threat intelligence
Logs from servers and workstations are collected centrally and kept for 12 months.
Security alerts cover suspicious logins, firewall and account changes, malware detections and backup failures.
We scan for known vulnerabilities and review national CERT advisories every month.
Incident response
A documented incident management procedure covers detection, triage, containment, recovery and lessons learned.
Where personal data is affected, we notify supervisory authorities within 72 hours as required by GDPR, and inform affected customers without undue delay.
Business continuity and disaster recovery
Business continuity and disaster recovery plans with recovery time and recovery point objectives approved by management.
Daily backups, point-in-time recovery for the production database and an encrypted off-site copy.
Restores are tested on a schedule and the results recorded.
Supplier security
Every supplier with access to information is assessed before use and reviewed every year.
For critical cloud providers we verify ISO/IEC 27001 or SOC 2 attestations.
Contracts and data processing agreements set security and confidentiality requirements.
People and training
Employees and contractors sign confidentiality agreements.
Security awareness training is part of onboarding, and every employee is required to acknowledge our security policies.
Access is revoked on the day a person leaves.
Risk management
Information security risks are assessed and treated under a documented methodology aligned with ISO 31000.
Risks are reviewed at least once a year and whenever systems or threats change.
Internal audits and an annual management review track corrective actions to closure.
Responsible use of AI
An approved AI policy defines which AI tools may be used and what data may be shared with them.
AI-assisted code is reviewed by a developer before it is merged.
Documents
ISO/IEC 27001:2022 certificate
Public (after issuance)
- Privacy Policy
Public (link)
- Statement of Applicability
On request, under NDA
- Information Security Policy
On request, under NDA
- Business continuity summary
On request, under NDA
- List of subprocessors
On request
Request security documentation
Fill in the form, or send us your security questionnaire, and we will reply within 2 business days. Restricted documents are shared after a non-disclosure agreement is in place.
Report a security issue
Found a vulnerability or a security concern in INBULK services? Email [email protected]. Please include enough detail for us to reproduce the issue and do not access or change other users’ data. We confirm receipt within 2 business days and keep you informed until the issue is resolved.
Last updated: November 17, 2026.