Privacy Policy

Peergrowth Pulse is an invite-only Meta ads analytics and lead-pipeline product for agencies and growth teams. We process account and workspace data for users of the Service, and we process Meta Instant Form lead data on behalf of the workspace that connects each ad account.

We do not sell personal information. We do not use third-party advertising or product-analytics pixels (such as Google Analytics or PostHog) in the Service today.

The Service is operated by Peergrowth (also referred to as “Peergrowth Agency,” “we,” “us,” or “our”). Our public site is peergrowth.agency.

For privacy questions or data requests, contact us using the details in Contact below.

• Account & workspace data (your login identity, invites, membership, settings): Peergrowth typically acts as a controller.
• End-customer lead data synced from Meta Instant Forms (names, emails, phones, and other form answers): your organization typically acts as the controller; Peergrowth processes that data as a processor to provide the Service.
• You are responsible for having a lawful basis to collect and share lead data with Meta and with us, and for informing your end customers as required by applicable law.

Account & authentication. Sign-in is provided by Clerk. Depending on how you register, this may include email address, password (handled by Clerk), name, and OAuth profile details from Google or Facebook/Meta. We store your Clerk user ID in our database to link you to workspaces and permissions. Profile credentials and OAuth tokens are held by Clerk.

Invites & team data. When someone is invited, we store invitee name and email, invite codes, roles, granted ad accounts, and related metadata.

Workspace & product settings. Organization name and slug, membership roles, selected Meta ad accounts, currency and performance targets (for example CPL or ROAS), and outcome mode (leads vs sales).

Meta advertising data. When you connect Meta, we access ad accounts, campaigns, ad sets, ads, creatives, Pages, and performance insights needed to power dashboards and reports. Much of this is fetched live from Meta’s APIs rather than permanently mirrored.

Lead pipeline data. Instant Form submissions synced from Meta, including field answers (which may include name, email, phone, and other PII), campaign/ad attribution, sync state, workflow status, and notes your team adds.

Shared reports. Report titles, client/agency labels, public share tokens, and snapshot content (metrics and narrative text). Report snapshots are designed around performance metrics, not raw lead contact dumps.

Usage, diagnostics & support. Application logs (for example errors, sync status, AI operation latency and token usage with user/ad-account identifiers), and error monitoring via Sentry, including Session Replay on a sample of sessions (and on errors).

What we do not collect via the product today. We do not process payment card data in the Service. There is no LinkedIn API integration. Copilot chat transcripts are not stored in our application database (messages are sent to the AI provider for each request).

• Authenticate users and enforce invite-only access
• Provide dashboards, lead sync/workflow, UTM tools, and shareable reports
• Power the AI copilot and AI-assisted report narratives
• Run background/scheduled Meta lead sync jobs
• Maintain security, debug issues, and improve reliability
• Communicate about access, invites, and product-related matters

Connecting Meta is optional but required for core product features. Authorization uses Facebook/Meta OAuth via Clerk. Depending on configuration, scopes may include reading and managing ads, business assets, Pages engagement/ads management, and lead retrieval.

Lead PII from Instant Forms is stored in our database so your team can filter, update status, add notes, and export CSV. Exports include the lead fields present in your workspace.

Meta’s own privacy practices apply to data held by Meta. Review Meta’s policies and your Business Manager settings for how leads are collected on their platform.

Copilot and certain report narratives use Google’s Gemini models (currently configured around gemini-2.5-flash). We send prompts, tool results, and related context to Google to generate responses.

Tooling is designed to work from live metrics and PII-safe lead summaries, not raw contact dumps in chat, and the system is instructed not to output personal contact details. Your free-text messages are still transmitted to the model as written, so do not paste sensitive personal data into Copilot unless necessary.

We share information with service providers that help us operate the Service, under appropriate agreements where required:

• Clerk: authentication, sessions, and OAuth (including Meta access tokens used to call Meta APIs)
• Meta / Facebook: advertising and lead APIs you authorize
• Google (Gemini): AI generation for Copilot and narratives
• Trigger.dev: background and scheduled lead sync jobs (payloads include identifiers such as user and ad account IDs)
• Sentry: error monitoring, performance traces, and Session Replay
• Database & hosting providers: PostgreSQL storage (for example Supabase-hosted Postgres) and application hosting (for example Vercel) as used to run the Service

We may also disclose information if required by law, to protect rights and safety, or in connection with a corporate transaction (such as a merger or sale), subject to applicable protections.

Public report links are accessible to anyone who has the URL until revoked. Treat share links as confidential.

We use cookies and similar technologies that are needed to run the Service (not for third-party ad targeting):

• Clerk session cookies: keep you signed in
• invite_verification: short-lived signed invite session (invite ID and email)
• active_organization, dashboard_ad_account, dashboard_date_range, dashboard_outcome_goals: remember workspace and dashboard preferences
• sidebar_state: UI preference

Browser local storage may remember last auth method and theme preference. Sentry Replay may record a sample of sessions for debugging.

We retain information for as long as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce agreements. Lead records, notes, invites, and report snapshots generally remain until your workspace removes them or we delete them after an account closure request.

Within the product you can revoke invites, remove team members from a workspace, and revoke or delete shared reports. There is no fully automated self-serve account wipe today. To request deletion of your account and associated workspace data, contact us (see Contact). We will respond within a reasonable period and may need to verify your identity.

Unauthorized sign-ups that fail invite checks may be deleted automatically as part of access control.

We use industry-standard measures appropriate to the nature of the data, including encrypted transport (HTTPS), authentication via Clerk, and tenant isolation controls in our database. No method of transmission or storage is 100% secure; please use strong credentials and protect report share links.

We and our subprocessors may process data in countries other than where you are located (including the United States and other jurisdictions where Clerk, Meta, Google, Sentry, Trigger.dev, or hosting providers operate). Where required, we rely on appropriate transfer mechanisms provided by those vendors or by applicable law.

The Service is built for business users and is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided us personal information, contact us and we will take appropriate steps.

Depending on where you live, you may have rights to access, correct, delete, or export personal information, to object to or restrict certain processing, or to withdraw consent where processing is consent-based. Agency customers who control lead data should route end-customer requests to the relevant workspace admin; we will assist processors’ requests as required.

To exercise rights related to your Peergrowth Pulse account, contact us using the details below. You may also manage certain preferences in product settings and by disconnecting Meta or leaving a workspace where those controls exist.

We may update this policy as the Service changes. We will revise the “Last updated” date above and, when changes are material, provide additional notice as appropriate (for example via the product or email associated with your account).

Questions about this policy or privacy requests for Peergrowth Pulse:

• Website: peergrowth.agency
• Book a call: Discovery call (Cal.com)

Please include enough detail for us to identify your account or workspace and the nature of your request.