Public availability is not permission
Every source is reviewed before we collect from it, every fact keeps the thread back to where it came from, and every person can see and control what we hold.
How a fact is known
Pull any fact and it leads to the record it came from, the date it was collected and the uses its source allows. This one is live.
- VerifiedChecked against an official record or confirmed by the company itself.
- ReportedStated in a source we trust, such as a filing the company made, but not checked further.
- EstimatedWorked out by a model, such as revenue from headcount. Always labelled, never shown as fact.
- Out of dateNot confirmed within its refresh window. Shown with its date so you can judge it.
Approved sources only
Each use, from display to export and the API, is approved separately for each source. If an approval lapses or is withdrawn, that source's data comes off the platform automatically.
Keeping it correct
- One company, one record
- Records from different sources are matched by government identifiers first, then website, then name, and every merge can be traced.
- Refreshed on a schedule
- Each source has a refresh window. Facts that miss it are marked out of date instead of quietly ageing.
- Corrections reach the source
- Anyone can report a problem on any fact. Our data team checks it against the source and records the outcome.
- Companies can claim their profile
- A verified company can correct its own details, which then show as confirmed by the company.
The people in our data
Anyone can find their record, correct it or have it removed in the Privacy Center.
- Notice before contacts launch
- Contacts are released market by market, only with licensed sources and a notice to the people listed.
- An opt-out that sticks
- When someone asks to be removed, we keep only what stops their data coming back from any source.
- Removals reach customers
- Customers who exported a removed record get a removal notice through the app, the API and webhooks.
- No personal intent tracking
- Website visitors and intent are measured per company. No person is identified.
Security
What we're building in from the start. We don't hold security certifications yet; we'll list them here when we do.
- Encrypted in transit and at rest
- Every connection to the product uses TLS, and stored data is encrypted.
- Least access
- Staff reach customer data only when a task needs it. Every change to sources, approvals and removals is written to an audit log.
- Your workspace, your controls
- Single sign-on, required two-factor sign-in, allowed email domains, and roles that limit who can reveal and export.
- Keys shown once
- API keys are shown once at creation; we keep only a prefix to identify them.
Found a security problem? Email hello@datainside.ai with “Security” in the subject.
See the thread for yourself
Open any company and follow a fact back to its record. It's free.