Flagship studio
Privacy-First Mobile Telemetry
An 11-week critique studio for iOS and Android teams who still need activation and retention curves after a PDPA review. You leave with a thinner dictionary, a consent map that matches code, and a written list of questions you will no longer answer with product analytics.
Learning outcomes
- Inventory every production event and property, including the ones nobody owns.
- Write a purpose and retention clock for each survivor; publish a do-not-collect list.
- Align consent copy with SDK flags and warehouse gates so reject actually stops jobs.
- Ship on-device or near-device aggregates for session health and activation.
- Choose sampling or hashing for cohorts without running both by default.
- Draft a deletion and export runbook a release engineer can execute.
Who it is for
Product engineers, analytics engineers, and PMs who can change an SDK or a warehouse job. You should bring a live app or a faithful sandbox. Pure strategy roles without a technical partner struggle in weeks five to eight.
Informational price: THB 18,500 as Guided Bench, or THB 42,000 as Mentored Residency. Open Studio recordings cover a subset for THB 4,800. See enrolment options. No checkout on this site.
Modules
-
Inventory without theatre
Dump the live SDK, name owners, and mark properties that exist only because a vendor template suggested them.
-
Purpose limitation on paper
One sentence per event. If the sentence needs a lawyer to finish it, the event is not ready.
-
Consent that matches the code path
Banner copy, SDK flags, and server gates in one map. Reject must stop downstream jobs, not only UI.
-
Property budgets
How many fields an activation event is allowed to carry, and what to do when growth asks for “just one more”.
-
On-device aggregation
Roll session length, screen class, and crash-adjacent counts before they leave the phone.
-
Sampling versus hashing
Pick one strategy for cohorts. Running both doubles payload and rarely improves a roadmap question.
-
Warehouse gates
Jobs that refuse unidentified or rejected traffic even if a client bug ships a packet.
-
Deletion and export runbooks
Runnable steps, including retries that must not re-ingest old rows.
-
PDPA working session
Retention windows and vendor roles using Thailand’s statute as the concrete constraint.
-
Critique of the full dictionary
Faculty and peers mark the artefact. Unanswered product questions are listed in public, not hidden.
-
Release plan
A sequenced SDK diff your release engineer can actually calendar. This is where slow trains show up.
Instructor
Arisa Chaiyawan
Former product analytics lead at a Bangkok fintech, now teaching Privacy-First App Analytics full-time from Ratburana. Arisa still reviews SDK diffs for alumni residencies and sits the legal-adjacent office hour each teaching week.
She does not claim that every metric can be kept. Her written feedback is often shorter than learners expect — usually a list of properties to delete and one measurement to redesign.
FAQ
Do I need a lawyer on the team?
No, but you need someone who can carry questions back to counsel. We teach you to write purpose statements; we do not issue legal opinions. The PDPA week uses Thailand’s statute as a working example even if your app is elsewhere.
Can I take this without shipping mobile code?
Only if you pair with an engineer who can. Weeks five to eight assume you can change an SDK build. Pure dashboard users should start with Open Studio or the PDPA seminar.
What is a real limitation of this studio?
The on-device aggregation module assumes you can ship a custom SDK build within about two weeks. Organisations with slower release trains fall behind here, and office hours cannot invent a faster train. Enrol a release engineer or budget extra calendar time. We say this in week one because pretending otherwise wastes the middle of the syllabus.
Is there a certificate?
You receive a letter describing the artefacts you submitted. We do not sell a framed credential. Hiring managers who know the studio ask to see the dictionary, not a badge.
Reviews from this syllabus
“The property budget in week four stopped a three-month argument with growth. We now have a written cap, not a hallway veto.”
Warehouse gates were the unglamorous win. Our client SDK still occasionally leaked a packet after reject; the job now drops it. I wanted more time on iOS App Tracking Transparency copy — we only spent half a session — so we finished that internally.