Trust
Built for the EU regulatory environment from day one
Compliance is not something you add to a data product afterwards. The way data enters MasterDB, the way it is stored, and the way it is retrieved were all designed around consent, authorisation and an auditable record.
Authorised means you authorised it.
Control
Your data, on terms you set and can change
You decide what is published
Nothing is retrievable until you publish it, and withdrawing it removes it. There is no default state in which your data is exposed without your action.
You decide who may use it
Every AI company connected to MasterDB is listed in your account and any of them can be blocked, at any time, without affecting anything else you publish.
You set the terms
Your instructions on source authority, representation and excluded subjects are published in the same channel as your data, so they travel with it.
Nothing is altered
MasterDB stores what you submit exactly as you submitted it. No reformatting, no reinterpretation, and an unambiguous record of what was published and when.
The regulatory position
Taking data without consent is running out of road
The current way AI gets product data, by scraping and approximating without authorisation, is difficult to reconcile with where European regulation is heading. MasterDB replaces it with a channel where authorisation is explicit, documented and recorded on every retrieval.
An authorised channel
Authorised data is data your business published itself. Its use is authorised because you authorised it, not because permission was assumed after it was taken.
A record on every retrieval
Each retrieval carries where the data came from, that its use was authorised, and when it happened. Provenance is recorded rather than reconstructed.
Nothing is taken
Nothing enters MasterDB except by a business publishing it. There is no crawler, no inference and no third party supplying data about you.
Designed to keep pace
Requirements under the EU AI Act and the EU Data Governance Act are still developing. The architecture is built to move with them, with legal and regulatory advice as it does.
Security
Access to the Business Portal is protected by a second factor at sign in. Each business controls who in its organisation has access and what that access covers, and any access granted outside the organisation can be given an expiry date.
The Product Catalogue API uses separate credentials for the sandbox and for live data. The live credential is inactive until the business is verified, because publishing with it makes data retrievable by AI companies. The sandbox is isolated and safe to build against before verification.
Personal data
What a business publishes to MasterDB is business data, not personal data about consumers. MasterDB does not receive, and has no use for, the content of anyone's conversation with an AI system. Analytics reported back to a business cover subject area, geography and outcome, never what a person asked or said.
Personal data handled through this website is limited to what you submit on the early access form. That is covered in the Privacy Policy.
This website
This site sets no cookies, runs no analytics and loads no third-party scripts. Fonts are served from the site itself. There is nothing here that tracks you, which is why there is no cookie banner to dismiss.
Ensure AI users receive accurate authorised information about your business, your brand and your products & services.
MasterDB opens to a closed group of businesses first. Publishing is completely free. Apply now and we will be in touch with your access.