Tizzy

Privacy Policy

Last updated: September 23, 2026

1. Introduction

Tizzy ("we", "us", or "our") operates the website www.tizzy.tech and the application at app.tizzy.tech (collectively, the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service.

2. Information We Collect

Account information

When you create an account, we collect your name, email address, and authentication credentials provided through your identity provider (e.g., Google Sign-In).

Ad platform data

When you connect your Google Ads, Meta Ads, or LinkedIn Ads accounts, we access campaign, ad group, and ad-level performance data through the respective platform APIs using OAuth tokens you authorize. We do not store your ad platform passwords. Google data is described in detail in Section 3.

Usage data

We automatically collect information about how you interact with the Service, including pages visited, features used, and timestamps. We use the following analytics services for this purpose:

  • Google Analytics: Collects anonymized usage data including page views, session duration, and device information. Google Analytics uses cookies to identify returning visitors.
  • PostHog: Collects product usage data such as feature interactions, click events, and session recordings to help us understand how you use the Service.
  • Cloudflare Web Analytics: Collects privacy-friendly, aggregated performance and usage metrics via a lightweight script. Cloudflare Web Analytics does not use cookies or track individual users across sites.

3. Google User Data

This section describes, specifically, what Google user data Tizzy accesses, how it is used, who it is shared with, how it is protected, and how long it is kept. It applies to both Tizzy products that use Google OAuth: Ads Copilot (connect a Google account to work with Google Ads, Search Console, Analytics, and Tag Manager) and MCP Center (expose those same Google services to your own AI client as hosted Model Context Protocol servers).

3.1 What Google user data we access

We access Google user data only through Google APIs, only with the OAuth scopes you explicitly grant on Google's consent screen, and only for the Google account you choose to connect. The scopes we request, and the raw data each one gives us access to, are:

  • openid — the opaque Google account identifier (sub) issued for your login. We store it so that reconnecting the same Google account updates the existing connection instead of creating a duplicate.
  • userinfo.email — the email address of the connected Google account. We store it so you can tell multiple connections apart in the dashboard.
  • userinfo.profile — your basic profile (name, profile picture) used only to label the connection in the interface.
  • adwords (Google Ads) — accounts and their metadata (customer ID, name, currency, time zone, manager/client links); campaigns, ad groups, ads, keywords, budgets and bidding settings; performance metrics (impressions, clicks, cost, conversions, CTR, CPC, CPM, search terms, device and geography breakdowns); and the names of audience/remarketing lists attached to the account. Where you ask us to, we also make changes on your behalf (for example pausing or resuming a campaign).
  • webmasters (Search Console) — search performance data (queries, pages, clicks, impressions, CTR, position), indexing and sitemap status for the sites you have verified, and the ability to submit or remove sitemaps.
  • analytics.readonly and analytics.edit (Google Analytics 4) — GA4 account, property, and data-stream configuration, and aggregated reports (sessions, users, conversions, traffic sources, audience and event breakdowns). The edit scope is used only when you ask us to create or change configuration such as data streams, conversion events, or audiences.
  • tagmanager.readonly, tagmanager.edit.containers, tagmanager.publish (Tag Manager) — your GTM accounts, containers, workspaces, tags, triggers and variables, and the ability to create or modify them and publish a container version (for example, to install a GA4 or Google Ads conversion tag you asked for).
  • Google Sheets (Tracking Center only) — if you use lead tracking and share a Google Sheet with the Tizzy service account, we read and write the rows of that sheet. We do not use your personal Google login for this and we have no access to any other file in your Drive.

We do not request and cannot access your Gmail, Drive, Contacts, Calendar, Photos, or location data. We do not receive your Google password.

Aggregated and anonymized Google data. Much of what the Google Ads, Analytics, and Search Console APIs return is already aggregated by Google (for example, daily campaign totals or query-level click counts) and contains no identifiers for individual end users. Separately, we derive anonymized operational metrics of our own — counts of API calls, error rates, response times, and how often a connection is used — to run and debug the Service. These operational metrics contain no Google user content and are not linked back to individuals.

3.2 How we use Google user data

Raw Google user data is used only to provide features you have asked for:

  • Displaying your accounts, campaigns, reports, and charts inside the Tizzy dashboard.
  • Answering questions you ask the in-app AI assistant or the autonomous agent about your own advertising and analytics data, and — where you explicitly request or approve it — making the change you asked for through the Google API (pausing a campaign, creating a GA4 conversion event, publishing a GTM container version).
  • Serving your data to the AI client you connect to MCP Center (for example Claude), in response to tool calls that client makes using an API key you generated.
  • Keeping your connection working — refreshing expired access tokens and telling you when a grant has been revoked.
  • Attributing leads and conversions between the sources you connect, where you have enabled Tracking Center.

Aggregated and anonymized data is used only to operate, secure, debug, and improve reliability and performance of the Service.

Purposes we will never use Google user data for. We use Google user data — raw, aggregated, or anonymized — only to provide or improve user-facing features that are prominent in the Tizzy interface and that you have chosen to use. Specifically, and without limitation, we do not:

  • use it for advertising of any kind, including targeted, personalized, retargeted, or interest-based advertising, or to build advertising profiles or segments;
  • use it for lending, credit, credit-worthiness, underwriting, insurance, or eligibility decisions;
  • use it to train, fine-tune, or improve any machine learning or artificial intelligence model, our own or anyone else's;
  • use it for any purpose unrelated to the user-facing features you requested, including internal profiling or market research beyond the operational metrics described in 3.1.

The only exceptions are the narrow ones the Google API Services User Data Policy itself permits: acting on your explicit instruction, complying with applicable law, or conducting internal operations strictly necessary to run and secure the Service — and in the last case, only on data that has been aggregated and anonymized.

Limited Use. Tizzy's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

3.3 What Google user data we share, and with whom

We never sell Google user data, and we never transfer it to a third party for any purpose other than providing or improving the user-facing features you use. This applies equally to raw, aggregated, and anonymized Google user data. Specifically, and without limitation, we do not transfer or sell it to data brokers, information resellers, advertisers, ad networks, analytics or measurement companies, lenders, insurers, or any other party for their own independent purposes. The only exceptions are the narrow ones the Google API Services User Data Policy permits: transfers you explicitly direct, transfers required by applicable law or legal process, and transfers to service providers who process the data solely on our behalf, under our instructions, and under contractual confidentiality and security obligations.

Within those limits, Google user data leaves our systems only in these cases:

  • You and your team. Members of your Tizzy team (which you control) can see the data from connections that belong to that team. If you publish a public report link, anyone holding that link and its access key can see the report it contains.
  • Your own AI client, at your direction. When you connect MCP Center to an AI client such as Claude, that client receives the Google data returned by the tool calls it makes. That data is then handled under the privacy policy of whoever operates that client (for example, Anthropic).
  • Our AI inference provider (processor). The in-app assistant and the autonomous agent call a large language model through OpenRouter, which routes the request to the model provider serving that model. The prompt and tool results — which may contain your Google data — are transmitted to that provider to generate the response. We send these requests with training and data-collection disabled, so your data is not used to train the provider's models; the provider may retain the request briefly under its own operational policy. No Google data is sent to a model provider except as part of fulfilling a request you made.
  • Infrastructure providers (processors). Our servers and database are operated by us on hosting infrastructure, and traffic reaches them through Cloudflare. These providers process data on our behalf under their own terms and do not use it for their own purposes.
  • Legal requirements. We may disclose data where required by law or to protect our rights or the safety of users.

Aggregated and anonymized data (operational metrics as described in 3.1) is used internally and, in aggregate form only, in materials such as uptime or usage summaries. It never identifies you, your customers, or the contents of your Google account, and it is not sold or transferred to any third party.

Our product analytics providers (Google Analytics, PostHog, Cloudflare Web Analytics) receive usage data about the Tizzy interface, as described in Section 2. They do not receive Google user data obtained from Google APIs, and no Google API data is sent to them.

3.4 How Google user data is secured

  • In transit: all traffic between you, Tizzy, and Google's APIs runs over TLS (HTTPS). Our application servers are not exposed directly to the public internet; inbound traffic arrives through a Cloudflare tunnel terminating at our reverse proxy.
  • At rest: your OAuth refresh and access tokens are stored encrypted. They live in our PostgreSQL database, which is encrypted at rest, runs on a private network reachable only by the Tizzy application, and is not exposed to the public internet. Tokens are never sent to the browser and are never written to application logs.
  • Access control: Google data is scoped to the team that owns the connection; every API request is authenticated (session cookie, or a per-team tzm_ API key for MCP access) and authorized against that team's membership before any Google API call is made. Administrative access to production systems and the database is limited to a small number of authorized personnel and requires separate credentials.
  • Least privilege: we request the narrowest set of scopes each product needs — MCP Center, for example, requests only the scopes for the specific Google service you are connecting — and we make write calls to Google only for actions you have requested or approved.
  • Operational practice: dependencies and base images are kept current, secrets are supplied to services as environment configuration rather than committed to source control, and API keys can be rotated or deleted by you at any time.
  • No method of transmission or storage is 100% secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your Google data, we will notify you and the relevant authorities as required by law.

3.5 Retention and deletion of Google user data

  • Tokens and connection details (refresh token, access token, expiry, granted scopes, Google account ID, email, and display name) are retained for as long as the connection exists, because they are what keeps your integration working.
  • Reporting data is fetched live. Google Ads, Search Console, Analytics, and Tag Manager responses are requested from Google at the moment you view a report or the agent runs a tool. We do not build a warehouse or long-term copy of your Google account data.
  • Conversation and run history. Where Google data appears inside an AI conversation or an agent run — because it was the answer to something you asked — that message history is stored so you can return to the conversation later. You can delete a chat or an agent run at any time, which deletes its stored contents.
  • Disconnecting. Removing a connection in Tizzy (Settings → Connections, or MCP Center → Services) deletes the stored tokens and connection record immediately. You can also revoke Tizzy's access directly at myaccount.google.com/permissions at any time; once revoked, we can no longer access your Google data.
  • Account deletion. When you delete your Tizzy account, or email us at privacy@tizzy.tech to request deletion, we delete your account data — including all Google tokens, connection records, and stored conversation history — from our production systems within 30 days.
  • Backups. Encrypted database backups are retained for up to 30 days for disaster recovery and are then overwritten, so deleted data may persist in a backup for up to that period before it ages out.

4. How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve the Service
  • Retrieve data from the ad, analytics, and messaging platforms you connect, and relay it to the AI assistant or to your own AI client via the Model Context Protocol (MCP) when you make a query
  • Carry out actions you request or approve on those platforms
  • Authenticate your identity and manage your account and team
  • Communicate with you about the Service
  • Detect and prevent fraud or abuse

We do not use your data — from any connected platform — to train or improve AI models.

5. Data Sharing

We do not sell your personal information. We may share data with:

  • Ad and analytics platforms (Google, Meta, LinkedIn, and the other services you connect): We exchange data with these platforms via their APIs based on the accounts you connect. Each platform's own privacy policy governs data on their side.
  • Your AI client (e.g. Anthropic's Claude): When you connect MCP Center to an AI client, the data returned by the tools it calls is passed to that client and is subject to that provider's privacy policy.
  • AI inference provider (OpenRouter and the model provider it routes to): Prompts and tool results from the in-app assistant and autonomous agent are processed by a large language model to produce a response. We disable training and data collection on these requests.
  • Analytics providers (Google Analytics, PostHog, Cloudflare): These services process interface usage data on our behalf as described in Section 2. They do not receive data obtained from connected platform APIs.
  • Other service providers: We use third-party services (hosting, infrastructure, Cloudflare) that process data on our behalf.
  • Legal requirements: We may disclose data when required by law or to protect our rights.

6. Cookies & Tracking Technologies

We use the following cookies and tracking technologies:

  • Google Analytics cookies: Used to distinguish users and throttle request rates. These cookies (e.g., _ga, _gid) expire after up to 2 years.
  • PostHog cookies: Used to identify returning users and track product usage across sessions.
  • Authentication cookies: Used to keep you signed in to the Service.

Cloudflare Web Analytics does not use cookies. You can manage cookie preferences through your browser settings. Disabling cookies may affect the functionality of the Service.

7. Data Retention

We retain your account information for as long as your account is active. Platform reporting data is fetched from the provider's API in real time and is not warehoused on our servers; where it appears inside a saved conversation or agent run it is retained until you delete that conversation or run. OAuth tokens are retained for as long as the connection exists and are deleted immediately when you disconnect it. When you delete your Tizzy account, we delete your data from production systems within 30 days; encrypted backups age out within a further 30 days. Section 3.5 describes retention and deletion of Google user data specifically.

8. Security

We implement industry-standard security measures to protect your data: TLS for all traffic in transit, application servers that are not directly exposed to the public internet, a database on a private network that is encrypted at rest, OAuth tokens stored encrypted and never returned to the browser or written to logs, and per-team access controls enforced on every request. Section 3.4 sets these out in more detail for Google user data. However, no method of transmission or storage is 100% secure.

9. Your Rights

Depending on your jurisdiction, you may have the right to:

  • Access, correct, or delete your personal data
  • Withdraw consent for data processing
  • Export your data in a portable format
  • Object to or restrict certain processing activities

To exercise these rights, contact us at privacy@tizzy.tech.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last updated" date.

11. Contact Us

If you have questions about this Privacy Policy, contact us at privacy@tizzy.tech.