Your data
Every value says where it came from.
One identity is built from many systems, so it never pretends a value is its own. You can see which system said what, who changed it, and who is allowed to look.
Whose value is it?
Every name, number, address and contact on an identity carries the system it came from, and every system's own ids for the company are listed beside it. Nothing is overwritten: when two systems disagree, both values are kept, and the one from the system you trust more is shown first.
Records are never corrected or translated. БРЕЗМИРА ООД stays exactly as the invoicing system wrote it; the identity's name sits beside it.
- Name
- Brezmira OOD
- ERP · high
- БРЕЗМИРА ООД
- Invoicing · high
- Brezmira
- Marketplace · normal
- VAT
- BG204817361
- ERP · Marketplace
- Your ids
- C-10422 · 88417 · seller/2291
- one per system
People
A person's details are not for everyone.
People's names, e-mails, phones and job titles, and any field a system's mapping marks as personal, are masked for viewers. A curator sees them because settling who is who needs them.
Webhooks leave personal fields out unless a subscription is set up to receive them, on purpose, one subscription at a time.
As a viewer sees it
works at Brezmira · from CRM
Who can do what
Four roles, and an audit log of all of them.
People sign in with e-mail and two-factor and are invited into an organisation. Each change is logged with who made it, and every change to a company is also an event the systems hear.
- OwnerEverything, including the organisation itself and who is in it.
- AdminConnects systems, makes API keys and webhooks.
- CuratorSettles held records, merges and undoes merges, accepts suggestions.
- ViewerReads companies and people, with personal fields masked.
Kept apart
Your companies are only ever yours.
- Separated in the database itself. Every query runs inside your organisation, enforced by the database's own row-level security, not just by the application.
- Your organisation comes from your key. Never from what a request says about itself.
- Keys are never stored. API keys and sessions are kept only as hashes; a key is shown once, when it is made.
- Secrets encrypted. Webhook signing secrets are encrypted at rest (AES-256-GCM). Tokens and passwords are never written to logs.
- Webhooks go outside only. https only; private, internal and cloud-metadata addresses are refused when you subscribe and again at every delivery.
- In the EU. The API, the dashboard and the database run in Frankfurt.
Send us two customer lists.
An export from two of your systems is enough. We show you how many are the same company, which ones it is sure of, and which it would hold for you. No project, no new system.