Why I keep my YouTube data on my own server (and why that matters for a behaviour tracker).

The obvious objection

When I tell people about Gazenest, the question comes up quickly and it is the right question to ask: "So you're building an extension that watches everything I watch on YouTube, and you want me to install it?"

Yes. And I understand why that sounds alarming at first pass. A YouTube behavioral tracker, by definition, has access to sensitive data. It knows what you watch, when you watch it, how long you stay, what you click away from. If you're managing anxiety and you watch certain content in difficult moments, Gazenest knows that. If your watch patterns reveal something about your mental state, your schedule, your relationships, Gazenest has the data that could surface those patterns.

That is exactly why the data stays on your server, not mine.

How it's structured

When you install Gazenest, you're running two things: the browser extension and the backend. The backend is what stores and processes your data. In the standard setup, that backend runs on Gazenest's infrastructure, but the data model is designed around individual user accounts, not aggregation. Your watch history is not pooled with other users' data. It is not analyzed across accounts. It is not used to train models or inform product decisions in ways that touch your personal data.

The self-hosting option goes further. You can run the Gazenest backend on your own server, a VPS, a home server, a NAS. In that configuration, your data never touches infrastructure I control. The extension communicates with your server, your server stores and processes your data, and the only party with access is you.

Why this matters specifically for a behaviour tracker

There's a general principle here that applies to any privacy-sensitive application: data you generate about yourself should be under your control. But behavior tracking has a specific property that makes this more urgent.

Most apps that collect sensitive data collect it as a byproduct of their core function. A maps app collects location data in order to give you directions. The location data is sensitive, but the app's purpose is navigation.

A behavior tracker's purpose is the sensitive data. The behavioral profile, the attention patterns, the Clarity Score, the hourly heatmap, these are not byproducts. They are the product. Which means a behavior tracker that sends your data to a third party is not incidentally handling sensitive information as a side effect of something useful. It is making a business out of your psychological profile.

I didn't want to build that, and I didn't want to use something built that way. The data-stays-yours architecture was not an afterthought. It was the founding constraint.

The honest trade-off

Keeping data on your own server means I can't do certain things that cloud-hosted products can do. I can't build aggregate features that require pooling user data, "people who watch X also tend to watch Y" recommendations, for instance. I can't train machine learning models on your behavior without your explicit participation. I can't offer features that require real-time cross-user comparison.

I think these are acceptable losses. The features that require your data to leave your server are mostly features that benefit the product at your expense. The features I want to build, the ones that help you understand your own behavior, work entirely within your own dataset. They don't need to know anything about anyone else.

What the extension sees

The Gazenest extension runs in your browser and observes your YouTube activity: which videos you watch, when you start and stop, how you navigate between videos, which entry point brought you to each video. This data is sent to the Gazenest backend, either hosted by Gazenest or self-hosted by you, and stored there.

The extension does not send data anywhere else. It does not report to YouTube. It does not communicate with advertising networks. It is not a data broker. It observes your YouTube behavior in order to give you information about your YouTube behavior, and that information goes to the backend you're running.

The codebase is open to inspection. I've been deliberate about keeping the extension's data transmission auditable, the data it sends, where it sends it, and what it does not send are all visible in the source.

The question I'd ask before installing any tracker

Before installing any tool that monitors your behavior, the question worth asking is: whose interests does this data serve? If the answer is "yours, and only yours," that is an architecture you can trust. If the answer is "yours, and also the company's business interests, and also potentially their advertising partners," that is a different arrangement, regardless of how the privacy policy is written.

With Gazenest, the answer is yours. The data is about you, it stays with you, and the insights it generates are for you. A behavioral tracker that measured your intentions while sending your data elsewhere would be a contradiction. The whole point is that this is your information, precise, sensitive, and worth keeping private.

Gazenest is available on all plans. The self-hosting option gives you full control of where your data lives.