VibeGrowth

Privacy policy

Vibe Growth connects the advertising, analytics and CRM accounts you already own, reports on them, and, when you ask Claude to, lets Claude change them. This policy explains exactly what is collected, why, who else processes it, how long it is kept, and how to have it removed.

Last updated 3 October 2026

Who is responsible

Vibe Growth is operated by Shaswat Singh, a sole proprietor based in Bengaluru, Karnataka, India, trading as Vibe Growth. For anything in this policy, including access and deletion requests, write to [email protected].

What Vibe Growth can do with your accounts

Vibe Growth does two things with the platforms you connect:

  • It reads. It periodically pulls reporting data from the accounts you select into your workspace so you can see performance in the web app. This background sync only reads.
  • It can also modify, when you ask Claude to. Vibe Growth runs a connector that your own Claude account can use. When you instruct Claude, the connector can read and modify data on the platforms you connected: create, edit, pause or delete campaigns, ad groups or ad sets, and ads, and change budgets and bids (Google Ads, LinkedIn Ads, Meta Ads); read reports (Google Analytics 4); read search performance and manage sitemaps (Google Search Console); and read and write contacts, companies and deals (HubSpot).

Changes are made only in response to your own instructions to Claude, in your own Claude account. Vibe Growth does not take actions on your accounts on its own schedule or on its own initiative.

There is no separate confirmation step inside Vibe Growth. You are responsible for the instructions you give, and Claude may ask you to confirm in its own interface. Every request made through the connector, reads included, is recorded in an audit log, described below.

What is collected and stored

  • Sign-in details. The email address, name and profile picture returned by the sign-in provider (for example Google) are held by our authentication provider. The app uses your email address and display name to sign you in and to contact you about the service.
  • Workspace and membership data. Workspace names and URLs, who belongs to each workspace and in which role (owner, admin or member), and any open invitations (invitee email address and role; the invitation link is stored only as a SHA-256 hash).
  • Authorization credentials. Access and refresh tokens for each platform you connect, encrypted at rest with AES-256-GCM. Vibe Growth never receives or stores your password for any connected platform.
  • Connector access records. For each Claude connection or access token: its name, when it was created, last used and revoked, and a SHA-256 hash of the token. The token itself is never stored.
  • Account details. The names, identifiers, currency and time zone of the advertising accounts, properties, sites or CRM portals your authorization can reach.
  • Synced performance data. Daily campaign-level figures (spend, impressions, clicks, conversions, leads and pipeline values, with campaign names and identifiers) in normalized reporting tables, together with the raw API responses they were derived from, for the accounts you enable. For Search Console and Google Analytics 4 these are aggregate query, session and conversion figures. For HubSpot, each synced deal's name, stage, pipeline, amount and dates.
  • Audit log of connector requests. Described in its own section below.
  • Skills content. The instructions and reference files (text only) that you or your teammates author as Skills, and their version history.

What is deliberately not collected

The background sync does not collect the personal profiles of people who saw or clicked your ads. The advertising figures it stores are aggregates reported by each platform, not individual-level records. It does not copy your HubSpot contacts, companies, email addresses, phone numbers or free-text notes.

If you ask Claude to read or edit contacts, companies or other records through the connector, those records pass through Vibe Growth on their way to and from your Claude session, and a copy of the request and the platform's response can appear in the audit log (truncated as described below).

Platforms you can connect, and the permissions requested

Each connection is authorized by you and can be withdrawn at any time. Connecting a platform grants the permissions listed below, which cover both the background sync and the changes Claude can make at your instruction. Only workspace owners and admins can connect platforms or authorize a Claude connection.

  • Meta Ads — ads_read to read campaign structure and performance through the Marketing API, and ads_management to create, edit, pause and delete campaigns, ad sets and ads, and change budgets, when you instruct Claude to.
  • Google Ads — https://www.googleapis.com/auth/adwords, which gives read and write access to your Google Ads accounts. Used for reporting, and to create, edit, pause or delete campaigns, ad groups and ads and change budgets and bids when you instruct Claude to.
  • Google Analytics 4 — analytics.readonly. Read-only session, channel and conversion reporting.
  • Google Search Console — webmasters. Reads query, impression and click data, and can add or remove sitemaps when you instruct Claude to.
  • LinkedIn Ads — r_ads, r_ads_reporting and rw_ads. Reads campaign structure and reporting, and can create, edit, pause or delete campaigns, ad groups and ads when you instruct Claude to.
  • HubSpot — read and write access to deals, contacts and companies (crm.objects.deals, crm.objects.contacts and crm.objects.companies, each .read and .write) and read access to their property schemas.

Google Ads, Google Analytics 4 and Search Console share one Google authorization, so connecting any one of them shows a single Google consent screen requesting the three permissions together. Signing in with Google requests only your identity (openid, email, profile).

How the data is used

Only to provide the service to you: to show performance in your workspace, to calculate funnel and attribution figures, to carry out the reads and changes you instruct Claude to make, to serve the Skills you author, to keep an audit trail, and to keep the service secure.

Your data is never sold, never rented, never shared with advertisers, and never used to build profiles for anyone other than you.

Audit log of connector requests

Every request that Claude makes to a connected platform through the Vibe Growth connector is recorded in an audit log held against your workspace. Each entry holds the time, the platform and account, which connector credential was used, the request (HTTP method, resource, parameters and body) and the platform's response, or the error if it failed. Reads are logged as well as changes.

Entries are truncated: if a request or response is larger than about 20,000 characters when serialized, only its length and the first 2,000 characters are kept. Entries can still contain data from your connected accounts, including records you asked Claude to read.

The log exists so changes can be reviewed after the fact. It does not block or reverse any request. It cannot be read by other workspaces or from the browser; it is held for your workspace's owners, who can ask for a copy by email (there is no in-app log viewer yet). It is kept for the life of the workspace, because no automatic deletion is currently applied, and is deleted when the workspace is deleted. Disconnecting a platform or revoking a connector credential does not delete earlier entries.

Who else processes it

Vibe Growth runs on a small number of infrastructure providers, each acting as a processor under instruction:

  • Supabase — managed PostgreSQL database and authentication. Stores everything described above, isolated per workspace by row-level security.
  • Vercel — application hosting and serving.
  • Cloudflare — DNS and edge delivery for vibegrowth.pro.
  • Anthropic — only the data that your own Claude session requests through the connector (and the Skills you invoke) flows to Anthropic, as part of your own use of Claude and under your agreement with Anthropic. Anthropic is not engaged by Vibe Growth to process your data.

Apart from the platforms you connect, which receive the requests you instruct Claude to make, no other third party receives your connected-platform data. If a processor is added, this list is updated before the change takes effect.

Claude and the connector

Vibe Growth exposes a connector (an MCP server) that you add to your own Claude account, or to another MCP-capable client using an access token you create. When you do that, whatever your client requests through the connector, and the instructions you give it, flow between your client, its AI provider and the platforms you connected, under your agreement with that provider, not ours. Vibe Growth does not choose the model or see your conversation.

You can revoke a Claude connection or token in Settings at any time, which cuts off access immediately. No customer data is used to train any AI model by us. The full detail is in the AI policy.

Where data is held, and for how long

Data is stored in the managed database region configured for the service. It is retained while your workspace exists, so that period-over-period reporting continues to work. The audit log and Skills are retained for the same period.

  • Disconnecting a platform deletes its stored credentials and its account list immediately. The synced performance data and raw responses attached to those accounts are deleted with them. Earlier audit-log entries remain.
  • Deleting a workspace (owners can do this in Settings) deletes its connections, credentials, accounts, synced data, audit log, connector credentials, Skills, memberships and invitations.
  • Closing your account, or a deletion request, removes everything. You can delete your account yourself in Settings, which also revokes access at the connected platforms; email requests still work. See data deletion, which is completed within 30 days, with encrypted backups overwritten on their normal rotation within 35 days.

Deleting data from Vibe Growth does not undo changes already made on a connected platform, and does not delete data the platforms themselves hold.

Security

Platform credentials are encrypted at rest with AES-256-GCM using a key held outside the database, and connector access tokens are stored only as hashes. The tables that hold credentials, raw platform responses and the audit log are not readable from the browser under any role. Every other query is scoped to a single workspace and enforced by database row-level security, so one workspace cannot read another's data. Connector sign-in uses OAuth 2.1 with PKCE. Traffic is served over HTTPS.

Because a connector credential can read and change your connected platforms, treat it like a password and revoke it if it is exposed.

Your rights

You can ask for a copy of the data held about you, ask for it to be corrected, ask for it to be deleted, or withdraw a platform authorization at any time. Write to [email protected]; requests are acknowledged within 7 days.

Where the GDPR applies, the lawful basis for processing is the performance of the contract between us. Where India's Digital Personal Data Protection Act applies, processing is on the basis of the consent you give when you connect an account.

Google user data, and the Limited Use requirements

Vibe Growth's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Data obtained through Google Ads, Google Analytics and Google Search Console is used only to provide and improve the user-facing features you connected those accounts for: reporting in your workspace, and the reads and changes you instruct Claude to make. In particular:

  • We do not transfer it to others except as needed to provide or improve those user-facing features (including returning it to your own Claude session when you ask for it), for security purposes, to comply with applicable law, or as part of a merger, acquisition or sale of assets with notice to you.
  • We do not use it to serve advertising, and we never sell it.
  • No human reads it, except with your consent for specific data (for example when you ask for support), where necessary for security purposes such as investigating abuse or an incident, to comply with applicable law, or when the data is aggregated and anonymized and used for internal operations.
  • We do not use it to develop, improve or train generalized artificial intelligence or machine learning models.

You can revoke this access at any time from the Connections page, or directly at myaccount.google.com/permissions.

Meta platform data

Through Meta Ads, Vibe Growth requests ads_read and ads_management for the ad accounts you choose. Data received from Meta is used only to show performance to you in your workspace and to carry out the reads and changes you instruct Claude to make. It is not sold, not shared with data brokers, and not used for surveillance or to build profiles of people.

To remove Meta-related data, disconnect Meta Ads in the app (this deletes the stored credential and the data synced from those accounts) or follow the data deletion instructions. You can also remove the app in Meta under Settings and Business Integrations.

LinkedIn data

Data received from the LinkedIn Advertising API is used only to provide features to the authenticated member who connected the ad account: reporting in their workspace, and the reads and changes they instruct Claude to make. Vibe Growth complies with the LinkedIn API Terms of Use and does not sell or share LinkedIn data with third parties other than the processors listed above.

No affiliation

Vibe Growth is not affiliated with, endorsed by, or sponsored by Google, Meta, LinkedIn, HubSpot or Anthropic. Their names are used only to describe the platforms and services this product works with.

Changes

Material changes are reflected in the date at the top of this page, and account holders are notified by email before the change takes effect.