Customer data stays under customer control
Built for sensitive building information
FireHub works with building documentation, fire safety records, professional assessments and operational information.
AI-native means FireHub is built to understand what the documents say, not just store them. That is why FireHub sees what is missing, suggests the next step and asks the person who can answer. People confirm.
That is why data control is part of the architecture from the start.
Customer data remains under customer control, sensitive document processing takes place within defined infrastructure, and customer information is not used to train public AI models.
Production data stored and processed within the EEA
Customer information is not used to train public AI models
FireHub suggests.People confirm.
Data stays within defined boundaries
FireHub production data is stored and processed within the EEA.
Customer documents are not sent to public consumer AI services for analysis.
Where infrastructure or technology providers are used, they operate within defined contractual and security requirements. Customer data is not made available for unrelated AI model training.
AI does not replace professional responsibility
FireHub uses AI to read, structure, connect and explain information.
FireHub is developing its own domain-specific AI for fire prevention and understanding roles.
It does not replace engineers, inspectors, installers or other competent professionals.
When a professional has made an assessment, FireHub keeps the source, the evidence and the responsibility behind it.
FireHub makes it easier to meet and document the duties under Forskrift om brannforebygging (Fire Prevention Regulations), Brann- og eksplosjonsvernloven (Fire and Explosion Protection Act) and Internkontrollforskriften (Internal Control Regulations). Responsibility still lies with the owner and the user.
A clear basis, not a stamp of approval
FireHub does not label an entire building ‘compliant’ or ‘non-compliant’. Instead, FireHub makes the basis visible.
- Verified
- Presumed
- In conflict
- Missing
- Requires assessment
Important conclusions can be traced back to the documents, evidence and professional sources they are based on.
- Fire strategyPDF · 12 Mar 2024
- Building drawingsDWG · 3 Feb 2024
- Regulatory requirementTEK17 § 11-9
- Professional assessmentFire engineer · 18 Mar 2024
Access is checked on every request
- Permission-based accessAccess is checked on every request. Two users with the same role can have different access.
- Account lockoutAccounts are temporarily locked after repeated failed login attempts.
- Limits against abuseLogin, password changes and uploads each have their own limits.
- Controlled error responsesError responses reveal no internal details.
Frequently asked questions
Here you will find answers to common questions about how FireHub works, how your data is handled, and what you can expect.
For you who are responsible for the building
Can FireHub decide whether our building meets the requirements?
No.
FireHub can analyse the documented basis, find information that is missing or in conflict, and show where action or professional assessment is required.
Professional responsibility remains with the qualified person concerned.
Can FireHub replace a fire safety engineer or inspector?
No.
FireHub makes professional work easier to understand, connect and follow up. It does not replace professional responsibility.
Can FireHub make mistakes?
Yes.
AI can make incorrect interpretations. FireHub therefore combines AI with evidence, traceability, structured logic and human confirmation.
Can FireHub explain why it reached a conclusion?
Yes.
Important conclusions are designed to remain connected to the documents, evidence and professional assessments they are based on.
Uncertainty and conflicting information remain visible.
Who owns the information uploaded to FireHub?
The customer retains ownership of and control over their data.
Using FireHub does not transfer ownership of the customer's documents to FireHub.
Who can access our data?
Only authorised users, services and personnel with the required permissions.
Access is controlled according to organisation, building, role and responsibility.
What happens if we stop using FireHub?
Customers can obtain their data according to their agreement and applicable requirements.
Remaining data is handled according to FireHub's documented retention and deletion procedures.
For IT and privacy
Does FireHub send my documents to ChatGPT or Claude?
No.
Customer documents in FireHub's production environment are not sent to the public consumer services of ChatGPT or Claude for processing.
Does OpenAI or Anthropic train on FireHub customer data?
No.
FireHub does not provide customer documentation to external providers of general-purpose AI models for training their models.
Does FireHub use third-party AI technology?
FireHub may use approved third-party technology where there is a clear technical purpose and appropriate contractual and security controls.
External providers do not gain ownership of FireHub customer data or permission to use it for unrelated model training.
Where is my data stored?
FireHub production data for customers is stored and processed within the EEA.
Relevant infrastructure providers and subprocessors can be documented as part of a customer's security review.
Can customer data leave the EEA?
The standard architecture of FireHub's production environment is designed to keep the processing and storage of customer documents within the EEA.
Any exception requires appropriate legal and contractual safeguards.
Does FireHub use customer data to train its own AI?
Customer data is not automatically used as free training data.
Any use of customer data in FireHub's own domain intelligence must take place within defined contractual, privacy and access boundaries.
Is our data encrypted?
Yes.
FireHub protects data during transmission and while stored using appropriate encryption and access controls.
Can FireHub provide documentation for our IT or privacy review?
Yes.
FireHub can provide relevant information about processing locations, subprocessors, retention, access controls, security measures and the architecture used to process customer data.