The Goldfish Protocol: Why Our AI Forgets Your Screen Recording Instantly

The traditional approach to employee monitoring is a security nightmare waiting to happen.

If you are a CTO, founder or manager you know the anxiety. You need visibility into your team's workflow, but the current market offers you "spyware" that records 8 hours of video or constant screenshots per employee, per day.

That isn't just creepy; it's a massive liability for data breaches.

If you have 50 employees, you are generating thousands of hours of sensitive footage every month. That database contains inadvertent captures of personal banking logins, private medical emails, and confidential client DMs. If that database leaks, you haven't just lost productivity data. You've exposed your entire company's digital history.

We decided to build something different. We call it The Goldfish Protocol.

Our system has the memory of a goldfish when it comes to video, but the memory of an elephant when it comes to insights. Here is the architectural breakdown of how we built a privacy-first time tracker using Google Gemini and InfluxDB.

The Problem: The "Big Brother" Data Honeypot

Most activity trackers operate like a dumb security camera. They record everything, dump it into an S3 bucket, and hope for the best.

From a data engineering perspective, this is inefficient. From a security perspective, it's reckless.

You are storing terabytes of unstructured video data (blobs) that require massive bandwidth to upload and massive storage costs to retain. Worse, 99% of that video is noise. You don't need a 4K video of your senior developer staring at a stack trace for 45 minutes. You just need to know that they were debugging.

We realized that video is the transport layer, not the destination.

The Solution: Intelligent Ephemerality

The core philosophy of the Goldfish Protocol is simple: The video file exists only as long as it takes to understand it.

We leverage the multimodal capabilities of LLMs (specifically Google Gemini) to act as a real-time interpreter. The AI watches the screen so you don't have to. It converts pixels into text, and then crucially it permanently deletes the video file.

The Architecture: How It Works

We built a pipeline that prioritizes metadata over media. Here is the lifecycle of a 60-second work block in ScreenJournal:

1. The Input & The Prompt Firewall

The desktop client records a short segment of screen activity. Before this data is stored anywhere, it is sent to our AI processor.

This is where Privacy by Design kicks in. We don't just ask the AI to "describe the screen." We use aggressive prompt engineering to sanitize the data of PII (Personal Identifying Information) before it becomes a database entry.

Our system prompt looks something like this:

"Analyze this screen activity. Identify the primary task, application, and context. CRITICAL PRIVACY RULE: If you detect any PII, credit card numbers, or password fields, IGNORE them completely. Do not transcribe them. Do not describe them. Return only a clean, high-level summary of the work context in JSON format."

2. The Processing Logic

The AI parses the visual data. It recognizes that "VS Code" is open and that the user is editing a React component. It ignores the Spotify notification in the corner. It ignores the WhatsApp web tab in the background.

It returns a clean JSON object, with only the important data:

{
  "timestamp": "2026-01-07T14:30:00Z",
  "app_name": "VS Code",
  "window_title": "auth-provider.tsx",
  "category": "Development",
  "context_summary": "Refactoring authentication logic in the frontend codebase.",
  "privacy_flag": false
}

3. The "Kill Switch"

Once that JSON object is received and validated, the video buffer is wiped from memory. It is not uploaded to a cloud bucket. It is not moved to a temp folder. It is overwritten.

The Storage: Why We Use InfluxDB

We chose InfluxDB because it is purpose-built for time-series data.

Employee productivity is not a static record; it's a stream of events. By storing text metadata instead of video blobs, we reduce our storage footprint by orders of magnitude.

This allows us to query your team's timeline with zero latency. You can ask, "How much time did we spend on the login page refactor last week?" and get an instant answer based on aggregated tags. You don't have to scrub through hours of footage to find the answer.

The Result: Insights Without Invasion

The Goldfish Protocol solves the "Creep Factor" of employee monitoring.

When a manager looks at the ScreenJournal dashboard, they see a detailed, searchable timeline: "10:00 AM - 11:30 AM: Writing API Documentation."

They cannot click "Play." They cannot zoom in to see who emailed you. They cannot criticize your choice of desktop wallpaper.

We have removed the ability for micromanagement and surveillance, leaving only the pure data required for business intelligence.

Stop Hoarding Video, Start Gathering Insights

We believe that the future of work is based on trust, not surveillance. But trust requires verification. We built an architecture that verifies work without violating privacy.

If you are ready to replace your "Big Brother" security cameras with a "Big Data" sports analyst, it's time to switch.

---

Ready to experience privacy-first employee monitoring? Book a call to see how ScreenJournal transforms workforce intelligence for your team.

Join the ScreenJournal beta today →