Certified, in Frankfurt, and written down.
For software that holds receivables data, information security and data protection are not an annex to the contract — they are the condition for it. What we can demonstrate is here, with the standard, the state and the place, rather than badges without content.
Certifications
- ISO/IEC 27001:2022 Information security management system
- ISO/IEC 27017:2015 Additional controls as a cloud provider
- ISO/IEC 27018:2019 Protection of personal data in the cloud
- SOC 2 Type 1 & Type 2 Security, availability, confidentiality, privacy
Processing
- Frankfurt am Main AWS Germany, European data centres only
- TLS/SSL Encrypted on access, in the application and in transit
- Separated tenants Customer data is processed separately from other customers'
Access
- Two-factor authentication Available for every account
- Roles & data scopes Closed when in doubt, for people and agents alike
- Ledger Who changed what, and when, stays readable
Your data stays in Germany.
All customer data, and the data of their customers, is stored and processed in Frankfurt am Main at Amazon Web Services Germany. Every connection to and from Bilendo is encrypted — opening the application, the application itself and the transport routes, including to the service providers you have connected.
-
ISO/IEC 27001:2022
Information security
-
ISO/IEC 27017:2015
Cloud security
-
ISO/IEC 27018:2019
Cloud data protection
-
SOC 2 Type 1 & Type 2
AICPA Trust Services
The data centre in use is certified to ISO/IEC 27001:2022, 27017:2015, 27018:2019, 27701:2019, 22301:2019, 20000-1:2018, 9001:2015, CSA STAR CCM v4.0, PCI DSS Level 1, TISAX and SOC 1–3.
Data-processing agreement
We provide the data-processing agreement with all its annexes — it stands at the beginning of a connection, not after it.
Technical and organisational measures
Access controls, encryption, network security, privacy by design and identity management are annexed to the agreement.
Sub-processors
An Art. 28 GDPR processing agreement is in place with every partner and service provider.
Records of processing
The records of processing activities are available for the obligation under Art. 30(4) GDPR.
Not certified once, but tested continuously.
A certificate says a management system exists. What it is worth is decided by the testing in between — which is why the cadence is here, not just the standard.
-
ISMS
A binding framework and policies for business processes, complemented by standardised, automated monitoring of the system and the infrastructure.
continuous
-
Vulnerability scanning
The infrastructure is scanned with several scanners; findings are closed or patched according to the agreed service levels.
daily
-
Penetration test
An external provider tests the systems comprehensively — commissioned by us, not on request.
at least annually
-
Training
Staff are trained in information security and data protection; emergency and business-continuity plans are in place.
ongoing
External data protection officer
Bilendo has appointed an external data protection officer. Data subjects can exercise their rights to access, deletion, rectification, portability and objection; we make sure they can.
What an agent reads, and what happens to what it read.
Once a language model is involved, the question gets more specific: what leaves the system, how long does it stay anywhere, and what is done with it? Four statements that are built this way in the product — and one that is not built yet and is therefore marked as planned.
No training on your data
Your data does not feed model training. The agent does not learn from your record — it reads it per request and starts from scratch on the next one.
Only what the person may see
Every query checks the acting person's roles and data scopes and returns nothing when in doubt. So an agent sees no record that would be hidden in the familiar interface.
No figure from the model
Every total, every count and every classification comes from the database. The model selects and phrases; the arithmetic happens without it.
No intermediate cache
Nothing is cached in the subagent stack. What an analysis read is not left in a cache someone else could be served from.
Pseudonymisation towards the language model
Replacing customer names and personal fields with placeholders before a request reaches the model is planned and not implemented today: the agent names cases with the customer's name, because a proposal without that attribution would be unusable for the people acting on it. We write this down rather than leaving it open — until then, what is processed is governed by the data-processing agreement.
Those permitted see. Those not permitted see nothing.
Permissions are not a filter over the interface but the condition of every query — and the same condition holds for an agent. An account without a company assignment gets an empty result, not the company's.
How release and the ledger workWhat we explicitly do not promise.
This page summarises how Bilendo handles information security and data protection. It is not legal advice, and the points below are here so that nobody reads them in.
- No legal advice and no guide to your own organisation's GDPR compliance.
- No claim that your processes are compliant — our management system is certified, not yours.
- No model training on your data — and therefore no improvement that would come from it.
- No pseudonymisation towards the language model while it is not built.
- No undo. What was released and executed is not pulled back.
- No uptime figure on this page. What is committed is in the contract, not on a marketing page.
What compliance and IT check first.
In European data centres only; customer data and the data of your customers is held in Frankfurt am Main at Amazon Web Services Germany. Transfers are TLS-encrypted throughout, including to the service providers you have connected.
Bilendo is certified to ISO/IEC 27001:2022, ISO/IEC 27017:2015 and ISO/IEC 27018:2019, and demonstrates the Trust Service Criteria for security, availability, confidentiality and privacy through SOC 2 Type 1 and Type 2. The data centre in use brings its own attestations, among them ISO/IEC 27701:2019, 22301:2019, PCI DSS Level 1 and TISAX.
Yes — and we say so rather than working around the question. An agent names cases with the customer number and the customer name, because a proposal without that attribution would be unusable for the people acting on it. What does not happen: your data is not used for model training, nothing is cached in the subagent stack, and no figure comes from the model. Pseudonymising the names is planned and not implemented today.
Yes, with all annexes including the technical and organisational measures. An Art. 28 GDPR agreement is in place with every sub-processor, and the records of processing activities are available under Art. 30(4) GDPR.
The infrastructure is scanned daily with several vulnerability scanners, and findings are closed or patched according to the agreed service levels. At least once a year we additionally commission an external provider for a comprehensive penetration test. Internal and external audits review the effectiveness of the measures regularly.
An external data protection officer is appointed. Access, rectification, deletion, portability and objection can be exercised; we make sure those rights can be exercised towards us as the processor.