How Zeek uses your data.

From creators

Messaging samples

When you connect your DMs or paste samples, Zeek reads those messages to learn how you write — rhythm, phrasing, emoji use, response patterns.

Raw samples are processed transiently (typically under 60 seconds) and are not stored beyond profile extraction. What persists is the derived structured profile, not the messages themselves.

Personality assessment responses

Your answers map communication style, emotional expressiveness, humour level, conflict approach — stored as structured trait data.

Knowledge Base (KB)

Content you explicitly upload or link: URLs, PDFs, YouTube videos, written text. Becomes reference material Zi can draw on.

Vault data

The deepest layer — memories, beliefs, life chapters, journal entries, relationships and influences you choose to share. Each entry carries a privacy flag you control: shareable or memory-only.

Profile & account

Name, email, profile photo, bio, social handles, timezone, pricing settings, and payout info (via Stripe Connect).

From users

Chat messages

Every message a user sends to a creator's Zi is stored in that user's conversation history. Users own their own threads. Creators see aggregate signals only, never raw content.

Booking & payment activity

Call requests, business inquiries, credit purchases and transaction history. Card processing is handled by Stripe — we never store card numbers.

This is where Zeek goes beyond raw storage — deriving structured signals from the data above.

Communication style model

From samples + assessment, we build a 7-layer profile: lexical fingerprint, emoji signature, burst patterns, emotional response style, conflict repair, episode distribution (warmth vs. humour vs. depth vs. catching up). This drives how Zi writes.

Personality profile

Directness, expressiveness, formality, humour, empathy, decision style — each on a 1–5 scale, cross-validated against your assessment.

Audience signals

Aggregate patterns across user conversations — never individual identities:

• Topics users ask about most → reveals KB gaps
• Sentiment — positive, neutral, frustrated trends
• Advocacy — repeat engagement, calls booked, products bought
• Trust — conversation depth, session length, return rate
• Collab demand — frequency of business inquiry submissions
• Friction — where users disengage or go off-topic

Conversation summaries

Stored per conversation thread so your Zi maintains continuity across sessions — summarised every 15 messages, keyed to that thread. Never aggregated across users, never used to build cross-user profiles.

Granular control beats blanket consent. What you can do with each data type:

Does Zeek train on your data?

No. Zeek does not use your Vault entries, KB items, samples or user conversations to train any AI model. Your data configures your Zi — it's never used to improve Zeek or anyone else's AI.

Which providers?

Zeek uses Azure OpenAI (Microsoft's enterprise deployment of OpenAI models). This means:

• Requests are processed by Azure-hosted models, not OpenAI's consumer infrastructure
• Azure's enterprise terms contractually prohibit using prompts and completions to train any models — Microsoft's included
• Data is processed within Azure's compliant cloud (SOC 2, ISO 27001)

What gets sent

On each user message: Zi's system prompt, the recent conversation history (≤20 messages), and the user's current message. Selective KB injection — only relevant items, not your entire KB.

Reference: Azure OpenAI data, privacy & security.

Vault entry

Immediate. Excluded from future responses. Regenerate your Zi to flush any derived influence.

KB item

Immediate. Excluded from the next message; the system prompt rebuilds fresh each conversation.

Zi

Removes the system prompt, training examples and derived profile. User threads are anonymised but not deleted by default — users own their threads.

Account

Permanent — within 48 hours. Removes all Vault, KB, personality profile, Zi, training data, wallet balance and transaction history (final payout processed first if balance exists). No partial recovery after 48 hours.

Encryption

All data is encrypted in transit (TLS 1.3) and at rest (AES-256). Vault, KB, conversation histories, payment records — all of it.

Account isolation

Every creator's Zi, Vault and KB live inside their own account boundary. User conversations are scoped to the user–Zi pair.

Row-level security

Every database table enforces row-level access policies. User A cannot query user B's records — even with a valid session token.

Payment security

Cards and payouts are handled entirely by Stripe. Zeek stores only a Stripe customer ID and connected-account ID — no card numbers, no bank details.

Questions about your data? Email hello@zeek.club.