Partner diligence
ESOMAR-aligned supplier answers
1. Company & sample model
Who is the contracting entity?
Yingsheng Technology Co., Limited（螢盛科技有限公司）, Hong Kong company no. 79656375, incorporated 21 January 2026. Registered office: Room 1508, 15/F, Phase 2, Yalan Centre Office Building, 625 Nathan Road, Mong Kok, Hong Kong. English brand Inso; Chinese brand 螢盛. Commercial contact: leosterling@insosample.com.
What do you supply?
Online sample supply and related fieldwork support for research marketplaces and buyers: community recruitment (Inso Insights), disclosed channel routes, survey routing/reconciliation, and proprietary survey programming/scripting. We do not claim marketplace or peer panels as Yingsheng-owned assets.
What is the current community status?
Public recruitment at join.insosample.com is interest registration today (email, country/region, age 18+, consents). Full member accounts, profiling, and survey invites open in stages. Rewards rules are published as planned and apply when payouts are enabled.
Indicative capacity?
Planning band across owned community routes and disclosed channels: about 2.0–2.6 million monthly inviteable supply (indicative, not a guaranteed complete volume). Exact mix confirmed in writing per allocation.
2. Privacy & security
How do you protect personal data?
TLS on public sites (HTTPS). Access to partnership and operations mailboxes is limited to authorized staff. Respondent interest data is used to contact about access and, later, to operate matching—not sold as an advertising list. Details: corporate and community privacy notices; security questionnaire and subprocessors list under NDA.
Certifications?
ISO/IEC 27001 and ISO 9001: in preparation / not certified yet—no public badge. GDPR is treated as process posture, not a certification mark. We do not claim SOC 2 or TRUSTe unless a current attestation is on file.
Where is data processed?
Contracting entity in Hong Kong. Public websites hosted on our Hong Kong VPS. Business email via Zoho Mail. Interest forms via FormSubmit to our partnerships mailbox. Full residency table is in the subprocessors draft under NDA and updated as systems go live.
Children?
Community is adults 18+. We do not knowingly register minors.
3. Quality & identity
How do you prevent fraud / low quality?
Layered approach: pre-entry (profile basics, geography consistency, duplicate/device rules), in-survey signals (speed, logic, open-text relevance), and post-field reconciliation with partner statuses. No single signal is an automatic silent mass reject without context. We also follow the partner’s fraud and traffic rules when supplying into their platform.
How do you know who respondents are?
Today: self-declared interest registration fields. As member accounts open: profile attributes used for matching; stronger verification may be required for payouts or high-risk studies and will be described before that feature launches. We do not market “certified AI ID” claims on the public site.
Panel engagement / fatigue?
Invitation spacing and fatigue awareness are part of planned community operations. There is no guaranteed daily survey volume.
4. Technology & programming
Can you integrate with marketplace redirects?
Yes. Unique session/respondent IDs on entry, secure entry links, return redirects for complete / terminate / overquota / quality outcomes, and operational reconciliation. Field maps and credentials are shared under NDA after kickoff.
Do you have survey programming?
Yes. Yingsheng operates a proprietary survey programming / scripting platform for multi-device web surveys (logic, quotas, multimedia as scoped per project), in addition to sample supply. Partner-hosted surveys remain under the partner’s environment when we only supply traffic.
Devices?
Desktop and mobile respondent journeys are supported for routing and for surveys we program.
5. Project handling
Feasibility & pilots?
Commercial reply target 1–2 business days (UTC+8). Feasibility outline typically within 3 business days after a complete brief. We recommend a controlled pilot with test redirects before production traffic.
Sourcing disclosure?
See the public Sourcing page. Blends of community and channel routes are disclosed; we never present another platform’s panel as ours.
Where are documents?
Public: diligence facts, vendor pack index, Panel Book PDF, white paper, this page, NDA and Supplier MSA templates. Under NDA: filled security answers, DPA path, subprocessors, redirect field map, ISO timeline.