Security built around clear access and European processing by design.
HumaMap is designed to keep professional people context available to the people who are meant to have access to it, without turning personal profiles into company owned data.
Last updated 30 August 2026European processing by design.
HumaMap is designed to keep core storage, databases, search and AI processing within Europe. The production architecture, backups, logging, monitoring and relevant subprocessors must be verified and kept aligned with the security and privacy claims published by HumaMap.
Access follows the sharing setup.
Personal HumaMaps are not intended to be visible to everyone by default. Access depends on the sharing context available in the product, such as private use, workplace sharing, connections or public visibility.
Ask HumaMap only uses context the person asking the question can access through that setup.
Ask HumaMap provides context, not decisions.
Ask HumaMap is HumaMap's AI assistant. It uses available HumaMaps and reports to help people make sense of professional work context. It does not make hiring, leadership or other people decisions for the user.
HumaMap gives context. People make the decisions.
Professional work context only.
HumaMap is designed for professional work information and is designed not to collect, require, infer or use GDPR Article 9 special category data as part of HumaMap profiles. Users should not add special category data to their profiles.
Keeping the data scope narrow is a product requirement, not an optional setting.
Company access does not transfer profile ownership.
Companies can use the information a person makes available through the workplace setup. The personal HumaMap remains with the individual.
Specific organisational controls, contractual requirements or data processing terms may be defined in the agreement that applies to a company account.
Security questions.
For security or data handling questions, contact hello@humanmap.com.