Programme · Consent

Consent

Who shares data, where the consent conversation is working, and a full record of who looked at what. Every enrolled member counts in the aggregates; consent decides only whether they can be seen individually.

Consent rate
66%
+3 pts vs 90d ago
Total sharing
264
of 400
+12 vs 90d ago
Revoked in period
4
−3 vs prior window
last 90 days
Enrolment to consent
30
days · median
+9 d vs prior window

Consent funnel

Enrolment to data consent. Device stages are modelled until the logistics feed is connected.

Enrolled → consent granted
66% of enrolled members share data
Modelled
Enrolled400 · 100%
Device pairedMODELLED364 · 91%
First syncMODELLED352 · 88%
30-day activeMODELLED320 · 80%
Consent granted264 · 66%
Largest drop: 30-day active → Consent granted (black bar).
Largest dropModelled
30-day active → Consent granted loses 56 members (18%)

In this book the consent ask itself is the largest leak, not activation. Test the prompt copy and timing before investing in device onboarding. Most books show the opposite, so confirm once real device data replaces the modelled stages.

Consent rate by group

Where the consent conversation is and is not working. Groups under 10 members are suppressed.

Segment
Priority · 26359%
Priority Private · 10580%
Private Banking · 3278%
Market
Hong Kong · 13366%
India · 8571%
Singapore · 18264%
Age band
Under 35 · 6763%
35–44 · 11159%
45–54 · 13269%
55+ · 9072%
Branch region
HK-Island · 6964%
HK-Kowloon · 6469%
IN-Bengaluru · 3471%
IN-Delhi · 1958%
IN-Mumbai · 3278%
SG-Central · 6266%
SG-East · 6868%
SG-West · 5256%
Relationship manager
Cheryl Ong · 6266%
Grace Wong · 6964%
Imran Hassan · 6469%
Kavita Bhatia · 3471%
Nithya Reddy · 3278%
Rajiv Chandran · 1958%
Serene Yeo · 5256%
Terence Goh · 6868%
Branch spread
22 points between the highest and lowest branch

IN-Mumbai is at 78%, SG-West at 56%. The difference is in how the conversation is had, not the product, so the higher branch's RM script is the first thing to share.

Revocation tracker

Revocations by month with programme events overlaid. A cluster after an event is the earliest sign something felt wrong to members.

Revocations by month
11 revocations to date
RevocationsProgramme event
Programme events
Peak: 6 in June 2026

Summer Reset started within two weeks before or during the peak month. Review what members were told at launch.

  • 06 JanChallenge · New Year Restart
  • 15 MarChallenge · Spring Steps
  • 01 JunChallenge · Summer Reset
  • 07 AugRM nudge · Recovery debt cluster · Wellbeing check-in
  • 21 AugRM nudge · Improvement leaders · Celebrate & upgrade
  • 01 SeptChallenge · September Sleep Reset
  • 04 SeptRM nudge · Disengaging · Re-engagement call
  • 14 SeptChallenge · Move More Mondays
  • 18 SeptRM nudge · Gate at risk · Wear reminder

Consent register

400 enrolled members. Non-consented members keep their row; health data is never shown for them.

MemberSegmentMarketStateGrantedScopeLast accessed by
M100000
Data sharing not enabled
PriorityHong KongNot shared—Tier & engagement only—
M100007
Data sharing not enabled
PrioritySingaporeNot shared—Tier & engagement only—
Priority PrivateHong KongSharing21 AprFull programmeClaims
M100021
Data sharing not enabled
PrioritySingaporeRevoked
07 Jun
24 JunTier & engagement only—
M100028
Data sharing not enabled
PriorityIndiaNot shared—Tier & engagement onlyUnderwriter
PriorityHong KongSharing25 JanFull programme—
M100042
Data sharing not enabled
PrioritySingaporeNot shared—Tier & engagement only—
M100049
Data sharing not enabled
Priority PrivateHong KongNot shared—Tier & engagement only—
M100056
Data sharing not enabled
PriorityIndiaNot shared—Tier & engagement only—
Private BankingIndiaSharing05 DecFull programmeDistribution
PrioritySingaporeSharing21 MayFull programmeClaims
M100077
Data sharing not enabled
PriorityIndiaNot shared—Tier & engagement only—
M100084
Data sharing not enabled
PriorityIndiaNot shared—Tier & engagement onlyDistribution
Priority PrivateHong KongSharing27 JanFull programme—
PrioritySingaporeSharing25 OctFull programme—
M100105
Data sharing not enabled
PrioritySingaporeNot shared—Tier & engagement only—
PrioritySingaporeSharing31 MarFull programme—
Private BankingHong KongSharing05 FebFull programme—
M100126
Data sharing not enabled
PriorityHong KongNot shared—Tier & engagement only—
Priority PrivateIndiaSharing19 AprFull programme—
PrioritySingaporeSharing16 DecFull programme—
Private BankingIndiaSharing10 DecFull programme—
Priority PrivateIndiaSharing12 SeptFull programme—
PriorityHong KongSharing20 SeptFull programme—
PriorityIndiaSharing11 JunFull programme—
Showing 25 of 400

Audit log

Every access to consented member-level data. Immutable, retained seven years, and visible to the member in the Luna app. This is the artefact handed to a regulator.

7 of 7 entries
WhenUserRoleMemberFields
2026-09-23 09:14Mei TanClaimsM100070Vitals, derived measures, alert history
2026-09-23 08:52Mei TanClaimsM100014Alert detail, RHR trend
2026-09-22 17:40Daniel KohUnderwriterM100070Tier, path, tier inputs
2026-09-22 15:03Cheryl OngDistributionM100063Client card
2026-09-22 11:26Mei TanClaimsM100217Blood panels
2026-09-21 16:18Grace WongDistributionM100084Client card
2026-09-21 10:02Daniel KohUnderwriterM100028Tier, path, tier inputs

The two consents

Joining the programme and sharing health data are two separate consents. Programme consent lets the insurer see a member’s tier, discount band and whether they are engaged — nothing more. Data consent lets each role see the member-level health data it is permitted to see. A discount tier is itself a disclosure, because a lower premium tells the insurer something health-derived; that is why programme consent must say so in plain words. The screen can show a single on/off control, but the contract and the consent copy keep the two apart, so no member can say “I joined for the discount and never agreed to share my health data.” Legal signs off both texts before launch.