Your data stays under your control.

From creators

Messaging samples

When you paste samples or upload chat exports (including Instagram DM exports), 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. Uploading an export is not the same as connecting Instagram for live replies.

Instagram DMs (optional)

If you connect Instagram, Zeek accesses that inbox so Zi can read incoming DMs, draft and send replies in your voice, and keep relationship and sentiment summaries. This is ongoing access, not a one-shot sample. Details are set out in Instagram DMs.

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).

Google Calendar (optional)

If you choose to connect Google Calendar, Zeek accesses calendar availability and related scheduling metadata solely to block occupied time from fan bookings. Details are set out in Google Calendar data & Google API compliance.

From users

Chat messages

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

Instagram DMs are different: you already own that inbox. When connected, you can review, approve, edit, or pause Zi's replies on those threads. Fans chatting with you on Instagram are using Instagram, not Zeek's in-app chat privacy model.

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 conversations on Zeek and, if connected, Instagram, never used to train models:

• 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, user conversations, Google Calendar data, or Instagram DM content to train any AI model. Your data configures your Zi, powers scheduling, or (for Instagram) operates the connected inbox—it is 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. For connected Instagram threads, the same pattern applies to that thread's recent messages so Zi can reply in context.

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, connected Instagram authorization, wallet balance and transaction history (final payout processed first if balance exists). No partial recovery after 48 hours.

Instagram connection

Disconnect anytime. Zeek stops accessing that inbox. Stored Instagram messages, tokens, and derived summaries tied to the connection are deleted when you disconnect, when you delete your account, or on a verified request, subject to any retention required by law.

Encryption

All data is encrypted in transit (TLS 1.3) and at rest (AES-256). Vault, KB, conversation histories, connected Instagram tokens, 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.

Zeek offers an optional Google Calendar integration for creators who want their platform availability to reflect their real schedule. This section describes how Zeek accesses, uses, shares, protects, and retains Google Calendar data when a creator authorizes the connection through Google OAuth. It applies only to users who elect to connect Google Calendar.

Google Calendar data access

When you connect Google Calendar, Zeek requests OAuth authorization to access Google Calendar data associated with your Google account, solely as needed to determine when you are busy or free for booking purposes. Access is limited to what is required to provide scheduling synchronization. We do not request or use Google Calendar access for any purpose unrelated to availability and appointment booking on Zeek.

Purpose of Google Calendar access

The sole purpose of the Google Calendar integration is to synchronize calendar availability so that occupied time slots are automatically blocked from fans booking appointments through the Zeek platform. This helps prevent double-booking and ensures fans can only request times that appear available on your connected calendar.

How Google Calendar data is used

Google Calendar data obtained through the integration is used only to:

• Determine busy and free intervals relevant to booking;
• Block occupied slots from appointment requests on Zeek; and
• Keep platform availability aligned with your connected calendar for scheduling functionality.

We do not use Google Calendar data for advertising, marketing, profiling, analytics unrelated to scheduling, personalization beyond scheduling, or any other secondary purpose.

Data sharing and third parties

Zeek does not sell, rent, or share Google user data—including Google Calendar data—with advertisers, data brokers, or other third parties. Google Calendar data is not disclosed to third parties except where necessary to operate the scheduling feature itself (for example, secure hosting infrastructure that processes data solely on our behalf under contractual confidentiality and security obligations), or where required by law. Fan users of Zeek do not receive the contents of your Google Calendar; they only see booking availability outcomes derived from busy/free status (for example, that a slot is or is not bookable).

Data security

Google Calendar data and related OAuth credentials are protected using industry-standard security measures, including HTTPS/TLS encryption in transit, encryption at rest, secure authentication, and access controls designed to limit access to authorized systems and personnel. OAuth tokens are stored and handled securely and are used only to maintain the calendar connection you authorize.

Data retention and deletion

Zeek retains Google Calendar data only as long as needed to provide the scheduling synchronization functionality while your account remains connected, or as otherwise required to comply with legal obligations. You may disconnect your Google account from Zeek at any time. Upon disconnection, Zeek will cease accessing your Google Calendar through the revoked authorization. Stored Google Calendar data associated with the integration will be deleted when you disconnect, when you delete your Zeek account, or upon your verified request, subject to any retention required by applicable law or legitimate operational necessity (such as resolving an active dispute). Account deletion is otherwise described in Deletion & reversibility.

Google API Services User Data Policy & Limited Use compliance

Zeek's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, Google Calendar data obtained via Google APIs is used only to provide or improve user-facing scheduling features that are prominent in our application, is not transferred to others except as necessary to provide or improve those features or as required for security, legal compliance, or with your consent, and is not used or transferred for serving advertisements, or for other unauthorized purposes under the Limited Use rules.

AI / machine learning compliance

Google Calendar data is never used to develop, improve, or train generalized artificial intelligence or machine learning models. Google Calendar data is not transferred to third-party AI providers for model training. This restriction applies regardless of whether other Zeek features use AI (such as Zi); Google Calendar data is kept outside those processing paths and is used only for scheduling availability as described above.

Your rights

With respect to Google Calendar integration, you may:

• Disconnect your Google account from Zeek at any time through the application's calendar or account settings (and/or by revoking Zeek's access in your Google Account permissions);
• Request deletion of stored Google Calendar data associated with your Zeek account by disconnecting, deleting your account, or contacting us; and
• Contact us with privacy questions or deletion requests at hello@zeek.club or support@zeek.club.

Zeek offers an optional Instagram connection so your Zi can answer DMs in your voice. This section applies only if you connect Instagram. Uploading a DM export to train Zi is covered under messaging samples above, not here.

What Zeek accesses

When you connect Instagram, Zeek requests authorization to read incoming direct messages on that account and to send replies you have allowed Zi to send. Access is limited to operating that inbox. We do not post to your feed, follow or unfollow accounts, or use Instagram for advertising.

Purpose

The sole purposes of the connection are to:

• Let Zi draft and send replies in your tone on Instagram
• Let you approve, edit, reject, or pause those replies
• Keep a living relationship summary per person Zi is talking to
• Show aggregate audience sentiment and themes in Insights

How the data is used

Message content is processed so Zi can reply in context, the same way in-app Zi uses recent thread history. Derived relationship summaries and sentiment stay in your creator account. Instagram DM content is never used to train generalized AI models, serve ads, or profile people for anyone but you.

Sharing

Zeek does not sell Instagram message data. It is not disclosed except as needed to run the feature (for example, secure hosting that processes data on our behalf), or where required by law. Instagram / Meta remains a third party; their terms apply to the Instagram account itself.

Your control

• Approve, edit, reject, or pause Zi's replies in Review Chats
• Disconnect Instagram anytime in account settings (and by revoking Zeek in Instagram / Meta permissions)
• Request deletion of stored Instagram data by disconnecting, deleting your account, or contacting hello@zeek.club