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 “learning opportunity.” At Croncode we pick tools to answer product questions, not to rebuild a dossier. The ethics of personalization are in a sibling essay: personalization without creepiness. This page is the instrumentation choice.

Choose analytics that name the job, keep the SDK list short, and refuse events that reconstruct a person’s week. A dashboard is not a license to watch.

What questions deserve an event?

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. Crash framing: crash-free questions.

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

Which SDK habits turn into surveillance?

1. Five marketing pixels on a consumer utility.
2. Events that include raw email, exact GPS, or photo contents.
3. Session replay that captures a decision journal or a message.
4. A vendor you cannot name on the privacy label.

Deletion must include the analytics identity: deletion requests. Store ownership for the label: App Store account. We will not ship mystery SDKs: will not build.

When is Apple’s own stack enough?

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

How do we write the event list in a brief?

Ten named events, each with a reason. No “track everything and we will see.” Quote packet: what to send. AI features should not log prompts that contain secrets: AI brief. Security: security questions.

Founder: Goktug Unver. Co-founder: Yusufhan Sokur. Team: Ozgur Ismet Ozkan. Shipping: Istanbul shipping.

What mistakes look like being data-driven?

• Optimizing a paywall with fear copy because a chart moved: honest paywalls.
• Pushing users who asked for quiet: earn the permission.
• Reading reviews as anecdotes and analytics as gospel: both lie. reviews as a team and users vs data.
• Adding Android pixels before the iOS job is true: Android after iOS.

Choose a studio that will argue this list: choose an iOS studio. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/.

How should a weekly review use the dashboard?

Thirty minutes. Three job events. One decision. If the meeting becomes a tour of funnels, you are entertaining yourselves. Founder-led support still beats a clever cohort when you have thirty users: founder-led support. Lean hours: small team, multiple products.

We do not publish fake conversion ranks for Croncode apps. If a vendor slide starts with “#1 analytics,” treat it as ads. Identity: we are not croncodetech.com. Identity.

Frequently asked questions

Is on-device analytics enough?

It can be, if you can still answer the job questions. Many teams still need a small server count. Small is the point.

Do I need consent banners in the app?

Follow the law of your markets and Apple’s rules for the data you collect. Do not copy a website cookie modal as a substitute for a real choice.

Can I use analytics to personalize?

Only with a line the user can understand. If you cannot put it on a permissions screen, do not do it. See the creep essay linked above.

What if an investor wants more events?

Give them the job completion count. A raw event firehose is not a board story.

Will Croncode install any SDK the client names?

No. We will refuse SDKs we cannot explain on the privacy label. Talk to us via contact.