Security and data protection at bloo.Cards
Security, by design. Your data and your network's data are hosted in the European Union, encrypted in transit, and stay under your control. Here is exactly how, without any certification badge we don't actually hold.
Hosted in the EU · GDPR · Flow from bloo.Cards to your CRM
European hosting and GDPR
Data in the EU
bloo.Cards is developed and hosted in the European Union, and your data is stored there. A few technical providers are based outside the Union (sign-in with Google, Apple or LinkedIn, e-mail delivery, AI reading of the cards you scan): these transfers are covered by GDPR safeguards and described in the privacy policy.
Controller and processor
MOLDEREZ-CONSULT SRL (Brussels) is the controller for your account, and the processor for the contact data you collect. Data processing agreement: annex to the Terms of Use; signable version: privacy@bloo.cards.
Your rights
Access, rectification, export and erasure from your account, at any time. Deleting your account erases your data according to our retention policy.
Encryption at every layer
In transit
All traffic runs over HTTPS (TLS). No page, no API call in the clear.
Passwords & tokens
Passwords are hashed with Argon2id, never stored in the clear. Sign-in codes, magic links and reset tokens are hashed with SHA-256, and the session is renewed at each sign-in.
CRM credentials encrypted at rest Available
A connected CRM's credentials are encrypted at rest (XChaCha20-Poly1305) with a key specific to your organisation, and are never shown again. Since 5 October 2026, your address book contacts (names, company, address, notes, email addresses and numbers) are also encrypted at rest, with a key specific to your account, as are exchange notes, reminder notes and the bloo.Cards Pocket history.
An outbound-only architecture
Contacts flow from bloo.Cards to your CRM, with no automatic reverse synchronisation. Depending on the integration you choose, contacts are passed on by export, webhook or connector. The permissions a connector needs, notably to create a contact or look for a duplicate, are specified when it is set up.
Keys under your control
bloo.Cards API key: viewing and webhook subscriptions
The keys you generate (bc_live_…) let you view your bloo.Cards contact data without changing it. They also let you create, view and delete your webhook subscriptions.
Signed webhooks
Every outbound notification is signed (HMAC-SHA256) with a secret shared between bloo.Cards and your system: your system can verify it really comes from bloo.Cards.
Revocable at any time
A key is revoked in one click; the cut-off is immediate. Keys are never shown twice or stored in the clear: only their hashed fingerprint is kept.
Access to your account
Two-factor authentication
Enable two-step verification on your account: at each sign-in, a one-time code is emailed to you.
Sessions & rate limiting
Sessions regenerated at login, limits on the number of attempts, a log of logins and sensitive actions.
Distinct roles
Separate owner, administrator and member rights for team accounts: everyone sees and does exactly what concerns them.
An activity log whose integrity is verifiable: the blooChain
Interactions, card changes, billing, payments, sign-ins: every action is chained and hashed (SHA-256), signed, verified every day and timestamped by an independent authority. How the blooChain works.
What we never do
We do not resell your data or your contacts' data. We do not train an AI model on your contacts. We access your CRM only within the integration you configure. And there is no advertising in bloo.Cards.
Built to recognised best practices
bloo.Cards follows OWASP best practices (access control, injection protection, data integrity) and undergoes regular internal audits. We claim no external certification we don't hold: we prefer to describe our measures precisely rather than display a logo.
Report a vulnerability
Think you have found a security flaw? Write to support@bloo.cards with a description and the steps to reproduce it. We acknowledge receipt within three working days and keep you informed until it is fixed. Please do not access other people's data, do not disrupt the service and do not publish anything before the fix. This information is also in our security.txt file.
Frequently asked questions
Where is my data hosted?
In the European Union. Development and hosting both take place in the EU.
Do you sign a data processing agreement (DPA)?
Yes. The data processing agreement is annexed to the Terms of Use and applies to all accounts; a signable version is available for CORPORATE accounts on request at privacy@bloo.cards.
Can bloo.Cards access my CRM?
Only as far as the integration you choose requires. The flow goes from bloo.Cards to your CRM, with no automatic reverse synchronisation; a connector's permissions (create a contact, look for a duplicate) are specified when it is set up.
How do I revoke an API key?
From the Developers section of your account, in one click. Revocation cuts off access immediately.
Are you ISO 27001 or SOC 2 certified?
We claim no certification we don't hold. We apply TLS, Argon2id, encryption at rest of CRM credentials and address book contacts (one key per account) and OWASP best practices, and we describe our measures openly.
What happens if I delete my account?
Your data is erased according to our retention policy; backups then expire on their own cycle.
Questions about security?
Data processing agreement: annex to the Terms of Use; signable version: privacy@bloo.cards. For the details of our technical measures or hosting: hello@bloo.cards. Contact us.
Create my free cardGo further
Contact us- Privacy policyWhich data is processed, why, and how to exercise your rights.
- Cookie policyThe cookies used, their purpose and how to manage them.
Free for life while your account stays active: a free account inactive for more than 12 months may be closed after prior e-mail notice of at least 30 days. See the terms of use.