API access, catalogue onboarding, incidents, security reviews and commercial questions — routed to the right team rather than a general inbox.
Response targets below are our general aims. If you hold a signed agreement with specific SLAs, those take precedence.
Production API failures, authentication outages, or recommendations not returning for your users. Include your partner ID, affected endpoints and a timestamp range.
Endpoint behaviour, payload questions, sandbox keys, rate limits, versioning and migration help. Send request/response samples with identifiers removed.
Agreements, pricing, catalogue onboarding, invoices, and adding new brands or categories to your integration.
Suspected vulnerabilities, responsible disclosure, or anything that looks like a data exposure. Please report privately before disclosing publicly.
Data processing agreements, sub-processor lists, security questionnaires, and controller/processor questions for your procurement team.
Contract terms, trademark and brand usage, and anything requiring our legal team.
The path from first conversation to live traffic. Most partners move through it in a few weeks, depending on catalogue size.
We work out which categories you're covering, what data you already hold, and where the engine sits in your product.
You get credentials against synthetic data — no real user records — so you can build and test the integration end to end.
Your products are mapped to the attributes the engine ranks against. This is usually the longest stage and the one worth getting right.
Production keys, agreed rate limits and monitoring. We stay close through the first weeks of real traffic.
The split-data design isn't only a consumer promise — it's the reason integrating us doesn't expand your own compliance surface.
Raw biometric streams are processed into scores on the user's side. Partners receive ranked recommendations, never underlying health data.
Because no special-category data reaches you through the integration, you're not taking on health-data obligations you didn't have before. Confirm the specifics with your own counsel.
Position in a user's shortlist is determined by fit against their data. We don't sell placement — which is what makes the recommendation worth showing.
Sandbox credentials are issued once we've scoped the integration together — they run against synthetic data, so nothing real is exposed while you build.
Production keys are issued after the agreement is signed and your catalogue mapping is complete. Email partners@humotron.com to start.
Ranked recommendations and the reasoning attached to them. Not raw biometric streams, and not the underlying health scores.
This is deliberate: it's the same architecture that protects the consumer, and it keeps special-category data out of your systems.
No. Ranking is determined by fit against the user's data, and placement is not for sale at any price.
What you can improve is the quality of your catalogue data — accurate, complete attributes give the engine more to match against, which is the legitimate route to appearing more often.
Your products are mapped to the attributes the engine ranks against — ingredients, specifications, formats and the claims that can be substantiated.
It's usually the longest part of onboarding, and the part most worth doing properly: incomplete attributes mean the engine has less to match on.
Yes. Email privacy@humotron.com and we'll send the current data processing agreement and sub-processor list for your procurement or legal review.
We also complete security questionnaires — send yours across and we'll turn it around.
Email security@humotron.com with enough detail to reproduce it. We aim to acknowledge within two working days.
Please give us reasonable time to investigate and fix before disclosing publicly. We won't pursue action against good-faith research that respects user privacy and doesn't degrade the service.
Humotron® is a UK registered trade mark. Usage is governed by your agreement with us — check it before publishing anything that implies a partnership, and email legal@humotron.com if you're unsure.
If it's a consumer using the Humotron app directly, point them to humotron.com/support — we'd rather deal with them directly than relay through you.
If it's an issue with recommendations surfacing inside your product, that's an integration matter: developers@humotron.com.
This page is for partners and integrations. If you're using the consumer app — connecting a wearable, reading your results, or managing your own data — that's handled separately.