Back to Home

Verify It Yourself

Don't trust marketing. Verify it yourself.

This guide walks you through verifying our privacy claims using Chrome DevTools. No technical expertise required—just follow the steps below to confirm that your conversations never leave your device.

Step 1: Open Chrome DevTools

First, open Chrome's built-in developer tools to monitor network activity:

  1. Open Chrome DevTools:
    • Windows/Linux: Press F12 or Ctrl+Shift+I
    • Mac: Press Cmd+Option+I
  2. Click the “Network” tab at the top of DevTools
  3. Clear any existing requests by clicking the 🚫 (clear) icon

What you should see:

An empty Network tab with columns like “Name”, “Status”, “Type”, “Size”, etc.

Step 2: Start a Chat

Now, use the application normally while monitoring network activity:

  1. Navigate to the chat page (if not already there)
  2. Type a message in the chat input
  3. Send the message
  4. Wait for the AI response
  5. Send a few more messages to be thorough

Keep the Network tab visible while you chat. Watch what network requests appear.

Step 3: Verify Zero Network Calls

Here's what you should observe in the Network tab during your chat session:

What you WILL see:

  • plausible.io/api/event - Anonymous analytics events (e.g., “chat_started”)
  • These events contain NO conversation content, only event names

What you WON'T see:

  • ❌ Your messages being sent to any server
  • ❌ AI responses being sent anywhere
  • ❌ Any API calls to OpenAI, Anthropic, or other AI services
  • ❌ Any database or storage requests
  • ❌ Any other network activity during chat

Why this matters:

If your messages were being sent to a server, you would see network requests with your message content in the payload. The absence of these requests proves that your conversations are processed entirely on your device.

Step 4: Verify in Payload

To confirm that even our analytics are anonymous, inspect the Plausible event payload:

  1. In the Network tab, click on a plausible.io/api/event request
  2. Click the “Payload” or “Request” tab
  3. Examine the data being sent

What you'll see:

{
  "n": "chat_started",        // Event name only
  "u": "https://thischatneverexisted.com/chat",
  "d": "thischatneverexisted.com",
  "r": null
}

Notice: No message content, no user identifiers, no session IDs. Just anonymous event names.

What This Proves

By completing this verification, you've confirmed:

  • ✅ Local conversations: Your messages never leave your device
  • ✅ Local AI processing: AI responses are generated on your machine
  • ✅ Anonymous analytics: Only event names are tracked, no content
  • ✅ Zero backend: No server receives or stores your data

Audit the Source Code

For the technically inclined, verify our claims by auditing the source code:

# Clone repository
git clone https://github.com/aykutuysal/thischatneverexisted
cd thischatneverexisted

# Search for forbidden storage patterns
grep -r "localStorage" src/     # Result: None
grep -r "sessionStorage" src/   # Result: None
grep -r "indexedDB" src/        # Result: None

# Check for backend API routes
find src/app/api                # Result: Doesn't exist

# Review dependencies for data exfiltration
cat package.json                # No suspicious libraries

The entire codebase is open source and available for audit:

View Source Code on GitHub

Summary

Privacy through architecture means our claims are verifiable, not just promises. You don't have to trust us—you can verify it yourself.

Don't trust. Verify.