not read yet
Use
- For
- Market analysts and teams choosing where to grow across European regions, using AI assistants
- Price
- Price not read
- Activity
- Actively maintainedsite updated 2 days ago
- Company
- Hiasynth AB · since 2025terms of service · per their About page
- Runs as
- No-code
- count households in a chosen European region
- rank places by audience size
- compare consumer segments across European borders
- Founded2025per their About page ↗
- HeadquartersStockholm, Swedenper their About page
- Run byHiasynth ABterms of service ↗
- Trains on your dataNoprivacy policy ↗
- Certifications they stateGDPRprivacy policy ↗
- Privacy policy updated2026-09-16privacy policy ↗
“We do not sell customer data, and we do not use customer usage data to train models.”
privacy policy ↗
These are /hiasynth's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverco.hiasynth/humanityverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-13
- Address to connectmcp.hiasynth.co
- MCP docshiasynth.co/docs/connect-anythe vendor's page ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
What is /hiasynth?
Serves a synthetic model of Europe's population, with 700 attributes per simulated person, to AI assistants via MCP for market queries.
Who is /hiasynth for?
Market analysts and teams choosing where to grow across European regions, using AI assistants
Do people use /hiasynth?
Little sign of use.
Is /hiasynth still maintained?
Actively maintained: site updated 2 days ago.
Who owns /hiasynth?
/hiasynth is run by Hiasynth AB, per its terms of service (2026-10-12).
Does /hiasynth train AI on your data?
No, per its privacy policy (2026-10-12): “We do not sell customer data, and we do not use customer usage data to train models.”
Is /hiasynth safe?
We do not audit vendors. What /hiasynth publishes, read 2026-10-12: GDPR stated on its privacy policy; on training with your data, “We do not sell customer data, and we do not use customer usage data to train models.”.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.