How We Track Without Tracking

There's a paradox at the heart of every privacy-first product: you need data to build a great product, but collecting data can violate the very principles you stand for.

At StitchLink, we solved this with a framework we call "measure the flow, not the person." Here's how it works — and why it matters for your privacy.

The Problem With Traditional Analytics

Most SaaS products use analytics platforms that:

• Track individual users across pages and sessions
• Store personally identifiable information (PII) in event properties
• Send data to third-party servers that may sell or aggregate it
• Use advertising pixels that follow users across the web

Even "privacy-focused" analytics tools often still tie every action to a specific user identity. The data itself becomes a liability.

Our Approach: Structured, Consent-Gated, Minimal

We built our analytics around three principles:

1. Consent First, Always

Our analytics (powered by PostHog) are consent-gated. If you decline analytics cookies, we collect nothing. Zero. Not even page views.

This isn't a checkbox. It's enforced at the code level — the tracking library doesn't even initialize without consent.

2. Measure Actions, Not People

We use a strict snake_case event taxonomy that measures what happened, not who did it:

meeting_created          ← A meeting was created
invite_sent              ← An invite was sent
subscription_created     ← Someone subscribed
consensus_slot_confirmed ← A group found a time

Notice what's missing? No names. No email addresses. No meeting titles. No attendee lists.

We never embed PII in event properties. Our internal convention explicitly bans it:

❌ user_email: "jane@example.com" ✅ plan_tier: "pro"

3. Aggregate Over Individual

We care about funnels, not fingerprints:

• Revenue Funnel: How many signups convert to paid?
• Booking Lifecycle: How many created meetings actually get confirmed?
• Viral Loop: Do guests who receive invites come back as hosts?

These funnels tell us if our product is working. They don't tell us what Jane's Tuesday meeting was about — and they never will.

The Zero-Retention Advantage

Our analytics system inherits the same zero-retention architecture that powers our scheduling engine:

Even our session replays (used only for debugging) are configured with maskAllInputs: true — every form field, text input, and password field is automatically redacted before the replay is captured.

Why This Matters for Your Business

If you're scheduling meetings with clients, partners, or candidates, your scheduling tool has access to incredibly sensitive information:

• Who you're meeting with reveals your business relationships
• When you're meeting reveals your availability patterns
• How often reveals the intensity of those relationships

Traditional analytics turn all of this into a data asset for the analytics provider. At StitchLink, it stays where it belongs: nowhere.

The Technical Standards

For the curious, here's how our event system is structured:

• Format: {object}_{action} in snake_case (e.g., meeting_created)
• Properties: Only non-PII metadata (plan_tier, participant_count, page)
• Server-side: Stripe webhook events are captured server-side — never exposed to the browser
• Person properties: Set via $set_once for immutable traits, $set for current state
• Anti-patterns: Title Case events, generic names like click_button, and any PII in properties are explicitly banned

The Bottom Line

You shouldn't have to choose between a product that works well and a product that respects your privacy. At StitchLink, we built our analytics to prove that you can measure what matters without knowing who you're measuring.

That's not just a policy. It's architecture.

Want to see zero-retention scheduling in action? Try StitchLink for free or learn more about our security.