Privacy Policy.

What we collect

Information you submit. Name, email, phone (if provided), business name, service interest, and messages you send. When you sign up for a ZRG tool (AI Lead Finder, SEO Audit, CRM), we also store your password hash, account preferences, and purchase history.

Automatic / technical data. We collect IP address, user-agent string, request timestamps, and referrer URL on every request to our backend. This is retained for up to 30 days in server logs for security + abuse detection. Successful logins, password changes, invite acceptances, and other auth events are retained in an audit log for up to one year.

Cookies. Essential cookies for sign-in (session + refresh tokens, 2FA trusted-device flag, Square OAuth state). Optional analytics cookies (Google Analytics 4) only if you consent via the cookie banner.

Voice notes. If you use the voice-transcription feature in the CRM, we send audio files to OpenAI Whisper for transcription. Audio is not retained by OpenAI per their API terms, and we store only the resulting transcript.

How we use it

We use your info solely to respond to your inquiry, schedule a call, and follow up if you become a client. We do not sell, rent, or share your data with third parties for their marketing purposes. Form submissions flow into the ZRG CRM (owned and operated by Zay Revenue Group) and to our team email.

Subprocessors

Zay Revenue Group uses the following subprocessors. Each is bound by a data processing agreement and is listed with the data category we send and the purpose.

• Anthropic (Claude) — prompts for AI features (lead enrichment, email drafting, status checks, SEO audit narrative). Per Anthropic API terms, prompts are not used for training. US region.
• Google (Gemini) — fallback AI engine when Claude is unavailable. Same data category as Claude. Global region.
• OpenAI (Whisper) — voice-note audio for transcription only. Audio not retained by OpenAI. US region.
• Resend — transactional + marketing email delivery. Recipient email + message body + send timestamp. US/EU regions.
• Amazon Web Services (S3) — file uploads, contracts, deliverable attachments. US-East-1.
• Fly.io — application hosting (API + worker). IP address and request metadata in edge logs. US region.
• PostgreSQL (managed) — primary database. All app data. US region.
• Redis (BullMQ queues) — background job payloads (email sends, audit runs, social publish retries). US region.
• Sentry — error tracking with user context (user ID, email) for debugging production crashes. US region.
• Square — payments + invoices. Recipient email, amount, card last-4 (never the full PAN). US region.
• Twilio — SMS send if enabled (currently not wired in production). Recipient phone + message body. US region.
• Google Places API — business lookup for the AI Lead Finder. Search query only. Global region.
• RocketReach — contact enrichment when user clicks "Enhance". Name + company as query. US region.
• Google PageSpeed Insights — performance scoring for the SEO Audit. Website URL only. Global region.
• Puppeteer rendering (Fly.io-hosted) — renders user-submitted URLs for the SEO Audit screenshot. URL only, rendered server-side. US region.
• Calendly — meeting scheduling. Name + email + chosen slot. US region.
• Meta Platforms — all data under a separate "Data from Meta platforms" section below, governed by Meta Platform Terms.

If you require a Data Processing Addendum (DPA) as an EU / UK customer, request one at hello@zayrev.com.

What each AI vendor sees

We limit the data each AI vendor receives to the minimum the feature needs. No ZRG AI call sends full CRM database exports or customer PII beyond what the specific feature requires.

• Claude (Anthropic) — sees: the text prompt for the feature plus any user-supplied context (e.g. the single lead row being enriched, the single message being drafted, the URL being status-checked). Does not see: password hashes, Square secrets, Meta tokens, full contact lists, invoice amounts.
• Gemini (Google) — same data scope as Claude. Invoked as a fallback when Claude is unavailable.
• Whisper (OpenAI) — sees only the raw audio of the specific voice note the user recorded. No CRM context attached.

AI-generated content that we send via email or DM is labeled "Drafted with Claude" (or equivalent) so the recipient knows AI touched the message. You can always review + edit AI drafts before sending.

Data from Meta platforms (Facebook, Instagram, Threads, WhatsApp, Messenger)

When you connect a Meta-owned account to ZRG, we receive and store the minimum data required for the feature you enabled. We only use Meta Platform data for the purpose you consented to, and we never sell, rent, or transfer it to third parties outside the Meta-authorized integrations described below.

By Meta use case:

• Facebook Pages management (pages_show_list, pages_manage_posts, pages_read_engagement): we store your Page ID, Page name, the Page access token, token expiry, and metadata of posts you publish through ZRG. We use this only to publish to Pages you admin and to report engagement metrics back to you in the CRM.
• Instagram content publishing (instagram_basic, instagram_content_publish): Instagram business account ID, username, profile photo URL, and metadata of posts you publish through ZRG. We do not mine the public content of any other Instagram user.
• Instagram messaging (instagram_manage_messages): inbound DMs from users who message your connected IG business account. We store only the messages exchanged through your account, never messages to or from other accounts.
• Page engagement + moderation (pages_manage_engagement, pages_read_user_content): comments posted on your Page by third parties, so you can moderate them (hide, delete, reply) from the CRM. We store only comments on content you admin.
• Page metadata (pages_manage_metadata): Page about/phone/hours fields you edit through the CRM. Write-only — we store a copy of what you submitted.
• Lead Ads retrieval (leads_retrieval, pages_manage_ads): personal info fields submitted by users who completed a Meta Lead Ad form (name, email, phone, custom question answers). We also store the ad ID, ad-set ID, campaign ID, form ID, and the form's privacy-policy URL, plus the consent statement the lead saw at submission — so we can honor opt-outs and attribution accurately. Every Lead Ad lead is tagged with source='meta-lead' in our database.
• Marketing API — ad performance (ads_read): ad account IDs, campaign/adset/ad structures, delivery metrics (impressions, clicks, spend, CPC). No personal user data.
• Marketing API — ad management (ads_management): creating and editing campaigns/adsets/ads/creatives. Budgets, targeting, creative metadata you submit. No personal user data.
• Instagram comments (instagram_manage_comments): comments on your IG posts, so you can moderate them from the CRM. We store only comments on content you admin.
• Instagram insights (instagram_manage_insights): aggregated metrics (reach, impressions, profile views) for the IG business account you connected. No individual-user data.
• Messenger messaging (pages_messaging, pages_messaging_subscriptions): inbound Messenger conversations and messages for your connected Page, plus webhook subscription metadata. We store only conversations with users who messaged your Page.
• Threads (threads_basic, threads_content_publish, threads_manage_replies, threads_read_replies): Threads profile info for the account you connected; metadata of threads you publish through ZRG; replies on your threads so you can moderate them. We do not read threads you did not author.
• WhatsApp Business (whatsapp_business_management, whatsapp_business_messaging): your WABA ID, registered sender phone number(s), approved message templates, and conversations with users who messaged your business number. No conversations with other businesses or users.
• oEmbed (oembed_read, instagram_oembed): a proxy call we make server-side when you paste a Facebook / Instagram / Threads URL into a CRM note or email. We cache the rendered embed HTML for 24 hours. No user PII touched.

Retention: we keep Meta-sourced data as long as the integration is active. On disconnect or data-deletion request, we hard-delete all Meta-sourced records within 30 days.

How to revoke: disconnect the integration from ZRG Settings, remove ZRG from your Meta settings (facebook.com/settings?tab=business_tools), or follow the step-by-step flow at zayrev.com/data-deletion.

This section and our Meta integration are governed by the Meta Platform Terms and Developer Policies, in addition to our own terms.

Your rights

You can request a copy of your data, correction of inaccurate data, or deletion of your data at any time by emailing hello@zayrev.com. We respond within 30 days.

Cookies

We use essential cookies for site function and optional analytics cookies only if you consent. You can decline or withdraw consent at any time via the cookie banner.

Contact

Questions? Email hello@zayrev.com or call (321) 666-1102.