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.
Pick how you’re integrated. Every question has its own link, so you can send a colleague straight to the answer rather than to the page.
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.
It adds one prompt to your product and cart pages: an invitation for a shopper to connect the tracker they already wear. If they do, they get a short, ranked shortlist drawn from your catalogue, with a plain reason beside each product.
From your side it behaves like a very well-informed upsell. The difference is where the ranking comes from — recovery, sleep and activity signal rather than what other people happened to buy.
Eleven providers, covering the fitness and recovery trackers most people already own. The current list sits on the app's setup screen, and connecting is two steps — the shopper signs in with their provider, never with us, and never with you.
A shopper without a supported tracker closes the prompt and your store behaves exactly as it does today. Nothing is withheld from them and nothing is pushed at them.
No. The app asks for no customer permissions at all — it cannot read names, email addresses, baskets or orders, even if someone asked it to. It reads your products, writes recommendation detail back onto them, and serves the prompt on your own domain.
Your shoppers consent to us directly for their tracker data and we remain the controller of it. That is the reason installing this doesn't hand you a health-data liability to manage. The mechanics — every permission, the one cookie, the retention clock — are in the platform annex to our Data & Privacy policy.
Five steps inside the app, in order, with no theme code and no developer: install, sync your catalogue, choose which products are eligible, set how the prompt looks, go live.
The sync is the step worth your attention. The engine matches on ingredients, format and dose, so thin product copy gives it less to work with — the app tells you which products are thin rather than leaving you to find out from a weak shortlist.
The prompt is an app block you place where you want it, and the recommendations are served from your own domain. Nothing is written into your theme's layout, and removing the block removes the prompt.
You can add it to an unpublished theme and walk the whole flow before a shopper sees any of it. Once live, one switch in the app stops the prompt appearing without uninstalling anything. And if you do uninstall, the recommendation detail we wrote stays on your products — that work is yours and travels with your catalogue.
Yes, and it's a step in setup rather than a setting buried three screens down. You choose which products are eligible, and anything you exclude never appears in a shortlist.
Most stores start narrow — one category they know well — then widen once they've watched it run for a week. Prescription lines, clearance and gifting are the usual exclusions.
No. Position is decided by fit against the shopper's own signal, and placement is not for sale at any price.
That restraint is the whole reason the shortlist is worth showing. A shopper who senses they're being steered stops believing the recommendation, and the one after them does too. What you can change is what the engine has to work with: complete, accurate attributes on the products you want seen. It's the legitimate route and the better investment.
The app's home screen is the report. It's grouped by what you're trying to do — shoppers shown the prompt, shoppers who connected, shortlists returned, products added to a basket — and each number carries the one action that moves it.
One piece of honesty. Because the app holds no order permissions, it reports what it can actually see rather than claiming credit for revenue it can't verify. If you want attribution against orders, your own analytics is the right place for it.
We do, directly. A shopper who can't connect their tracker, wants to disconnect, or asks what we hold about them deals with us rather than with your support inbox — the prompt carries that route itself.
Anything about the app on your store — placement, eligibility, a prompt that isn't appearing — comes to developers@humotron.com.
Through the platform's own billing, so the charge lands on your store invoice instead of becoming another supplier for your finance team to set up. The current plan and any trial are shown on the app listing before you install.
Multi-store setups, and anything that doesn't fit the published plan: partners@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.