Staying honest about privacy

I recently started testing a very small Google Ads campaign for PanicMode. That also meant adding a minimal Google attribution script to the website, which honestly felt a bit ironic for a privacy-focused project.

I still wanted to handle it in the most transparent way possible. The website now asks for consent before loading anything advertising-related, and PanicMode itself still runs fully locally without recording or uploading anything.

Trying to find the balance between growing a small indie project and staying aligned with the original privacy-first mindset behind it.

23 views

Add a comment

Replies

Best
Diego Rincon
I’m in the same boat developing a privacy focused app. It’s not easy to find the balance between analytics and privacy. What exactly would you be worry about google tracking? In my case the main focus is to protect photos and videos. So cloud storage and encryption is what I’m most concerned about. For analytics I split it between PII and others. Others are tracked in different platforms, including google analytics. PII on the other hand is only tracked and stored in European servers that comply with GDPR

@diego_2r87 I’m intentionally avoiding collecting anything that could identify users. The only things I track are a few anonymous interactions that help me understand whether the website is actually useful.

For example I noticed a lot of visitors but very few downloads, so I added a live interactive demo directly in the browser so people can try the concept before installing anything. Right now I only track events like demo activations or download button clicks, without attaching personal information to them.

Unfortunately Google's script collects it's own information via cookies, and to comply with GDPR I have to make it transparent and ask for consent before loading it.

It does feel a bit ironic for a privacy-focused app, but I’d rather be upfront about it and keep data collection to the absolute minimum.