{"id":988609,"date":"2026-10-03T20:00:00","date_gmt":"2026-10-03T20:00:00","guid":{"rendered":"https:\/\/croncodestudio.com\/en\/?post_type=croncode_post&p=988609"},"modified":"2026-09-08T22:58:43","modified_gmt":"2026-09-08T22:58:43","slug":"choosing-analytics-without-surveillance","status":"publish","type":"croncode_post","link":"https:\/\/croncodestudio.com\/en\/journal\/choosing-analytics-without-surveillance\/","title":{"rendered":"Choosing Analytics Without Surveillance"},"content":{"rendered":"
\n

Analytics is a count of things you chose to remember. Surveillance is a map of a person you did not need. Consumer apps cross that line when every tap, location ping, and clipboard curiosity becomes a \u201clearning opportunity.\u201d At Croncode<\/a> we pick tools to answer product questions, not to rebuild a dossier. The ethics of personalization are in a sibling essay: personalization without creepiness<\/a>. This page is the instrumentation choice.<\/p>\n

\n

Choose analytics that name the job, keep the SDK list short, and refuse events that reconstruct a person\u2019s week. A dashboard is not a license to watch.<\/p>\n<\/blockquote>\n

What questions deserve an event?<\/h2>\n

Did the first job complete. Did the second job complete in week two. Did the paid path fail. Did deletion finish. Did a crash hit the first job. That is enough for a small app to steer. Vanity opens and heatmaps of settings are optional and often noisy. Retention framing: week two<\/a>. Crash framing: crash-free questions<\/a>.<\/p>\n

Jobs we instrument as jobs, not as stalking: YourStyle<\/a> saved a garment, Numira<\/a> structured a choice, Spylie<\/a> finished a case beat, Luviport<\/a> confirmed a window. Catalog: what Croncode builds<\/a>.<\/p>\n

Which SDK habits turn into surveillance?<\/h2>\n
    \n
  1. Five marketing pixels on a consumer utility.<\/li>\n
  2. Events that include raw email, exact GPS, or photo contents.<\/li>\n
  3. Session replay that captures a decision journal or a message.<\/li>\n
  4. A vendor you cannot name on the privacy label.<\/li>\n<\/ol>\n

    Deletion must include the analytics identity: deletion requests<\/a>. Store ownership for the label: App Store account<\/a>. We will not ship mystery SDKs: will not build<\/a>.<\/p>\n

    When is Apple\u2019s own stack enough?<\/h2>\n\n\n\n\n\n\n\n\n
    Need<\/th>\nStart with<\/th>\nAdd a vendor when<\/th>\n<\/tr>\n<\/thead>\n
    Crashes<\/td>\nOrganizer \/ MetricKit<\/td>\nRoles need a shared queue<\/td>\n<\/tr>\n
    Store funnels<\/td>\nApp Analytics<\/td>\nYou need a custom job event<\/td>\n<\/tr>\n
    Experiments<\/td>\nNone<\/td>\nYou can name a hypothesis<\/td>\n<\/tr>\n
    Ads<\/td>\nNone until you buy ads<\/td>\nYou accept the label change<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    A landing page can stay dumb and still send store traffic: store landing pages<\/a>. Do not put a full ad stack on the site and then claim the app is private.<\/p>\n

    How do we write the event list in a brief?<\/h2>\n

    Ten named events, each with a reason. No \u201ctrack everything and we will see.\u201d Quote packet: what to send<\/a>. AI features should not log prompts that contain secrets: AI brief<\/a>. Security: security questions<\/a>.<\/p>\n

    Founder: Goktug Unver<\/a>. Co-founder: Yusufhan Sokur<\/a>. Team: Ozgur Ismet Ozkan<\/a>. Shipping: Istanbul shipping<\/a>.<\/p>\n

    What mistakes look like being data-driven?<\/h2>\n