Privacy Policy

Introduction

Jumon Inc ("Jumon Intelligence," "Jumon," "we," "us," or "our") provides a service that lets you connect advertising platforms to AI assistants through the Model Context Protocol (MCP) and an optional in-app AI agent. This Privacy Policy explains how we collect, use, store, and share information when you use our marketing website, web application, and related services (collectively, the "Service").

By using the Service, you agree to this Privacy Policy. If you do not agree, do not use the Service. For questions, contact us at juan@jumonintelligence.com.

Information we collect

We collect the following categories of information:

• Account information: When you sign in, our authentication provider (Clerk) processes identifiers such as your email address, name, and session data linked to your account.
• OAuth connection data: When you connect LinkedIn Ads, Google Ads, Reddit Ads, Meta Ads, Microsoft Advertising, and Google Analytics 4, we receive OAuth tokens and metadata such as granted scopes, connection status, token expiration times, and (for Microsoft Advertising) which sign-in provider you used. When a platform grants identity-related scopes, we may also receive and store a limited identity snapshot (for example email, username, or display name, plus a provider subject id) so we can show which account you connected in the Jumon dashboard.
• Operational logs: When MCP tools or the in-app agent invoke advertising APIs through our gateway, we log metadata such as your user identifier, organization identifier (when applicable), provider name, MCP tool name, HTTP method, response status code, outcome, request duration, and sanitized request arguments.
• MCP and advertising API response data: To provide customer service history, audit, support, and Service features for both remote MCP clients and the in-app AI agent, we may store encrypted copies of provider API response bodies (and related tool outputs) returned through our gateway. Payloads are redacted for obvious secrets, size-capped, encrypted at rest, and retained only for limited periods as described in Retention.
• In-app AI chat data: When you use the Jumon AI agent, we store conversation messages, tool-call UI state, artifacts, and related session metadata in your workspace (personal or organization).
• Account change log: For successful write mutations made through MCP write tools, we store a normalized audit record (for example, before/after values for budget or status changes).
• OAuth security state: Short-lived state values used to protect OAuth flows until authorization completes.
• Technical data: Our hosting provider (Vercel) and analytics providers (PostHog, and Google Analytics on the marketing site) may collect standard web logs and product analytics on our marketing site and web application (for example, IP address, browser type, pages visited, named interaction events, and — when enabled — session replay recordings of the marketing site and authenticated app UI). Session replay is used to understand how visitors use the landing page and complete signup; we do not use it to train third-party AI models.

How we use information

We use collected information to:

• Authenticate you and provide access to the Service.
• Initiate, maintain, and refresh OAuth connections to advertising platforms you authorize.
• Display which advertising platform account you connected (for example email or username) in your Jumon Connections dashboard. Platform identity is not used as your Jumon login; Clerk remains our authentication provider.
• Proxy API requests to LinkedIn, Google, Reddit, Meta, Microsoft, and Google Analytics 4 on your behalf when you, your MCP-enabled assistant, or the in-app AI agent invoke supported tools.
• Provide customer service history, usage reporting, audit trails, debugging, and support for MCP and agent activity.
• Operate, secure, and improve the Service, including abuse prevention, billing administration, and product analytics (such as understanding marketing-site conversion funnels).
• Comply with legal obligations and enforce our Terms of Service.

Google Ads user data

When you connect Google Ads, you authorize Jumon via Google OAuth using scopes such as https://www.googleapis.com/auth/adwords (Google Ads API) together with openid, email, and profile so we can identify the Google account you connected.

Depending on the tools you use, we may access Google user data and Google Ads account data such as customer IDs, campaign structure, ad groups, ads, keywords, budgets, bid targets, and performance metrics. We use this data only to provide features you request through Jumon and compatible MCP clients (for example, listing accessible accounts, searching campaigns, or making a Search change you ask for and approve, such as creating a paused campaign, pausing or resuming campaigns, ad groups or ads, adding keywords, or adjusting budgets and bids). When a write succeeds, we store a change-log record of that mutation. Performance Max remains available for reporting.

Jumon makes a change to your Google Ads account only when you ask for it and approve it in your AI assistant. Jumon does not change your Google Ads account on its own. We use the adwords scope for these changes because Google provides no narrower scope for the Google Ads API. Google Analytics access remains read-only.

After you connect, we may call Google's OpenID userinfo endpoint once and store a limited identity snapshot (subject id, email, and/or name) with your connection metadata so Connections can show which Google account is linked. We do not use Google Sign-In as Jumon's login method.

We store OAuth tokens encrypted at rest. We store connection metadata, operational logs, and—when enabled—encrypted, time-limited copies of advertising API / MCP response data as described in this policy, solely to provide Service features you request (including remote MCP, the in-app agent, usage history, audit, and support). We do not sell Google user data or use it for advertising unrelated to your use of the Service.

You may disconnect Google Ads in your Jumon dashboard at any time. Disconnecting removes stored OAuth tokens and the identity snapshot for that connection. You may also revoke Jumon's access in your Google Account permissions at https://myaccount.google.com/permissions.

Google API Services — Limited Use

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

Google user data is used only to provide or improve user-facing features you request, for security and abuse prevention, to comply with applicable law, or with your consent. Human access to Google user data is limited to what is necessary for these purposes (for example, support at your request, security investigations, or legal compliance).

We do not use Google user data for serving advertisements, sell Google user data to third parties, or use it for purposes unrelated to the Service's functionality.

We do not use your Google Ads, Google Analytics, or other Google user data to train or fine-tune general-purpose AI models.

For more information, see the Google API Services User Data Policy at https://developers.google.com/terms/api-services-user-data-policy.

Google Analytics data

When you connect Google Analytics 4, you authorize Jumon via a separate Google OAuth client using the read-only scope https://www.googleapis.com/auth/analytics.readonly together with openid, email, and profile so we can identify the Google account you connected. This connection is independent of Google Ads in Jumon.

Depending on the tools you use, we may access GA4 account, property, configuration, and reporting data such as account and property identifiers and names, data streams, key events, custom dimensions and metrics, Google Ads links, Data API metadata, and reporting metrics (for example sessions, key events, and revenue). We access this data only to provide features you request through Jumon and compatible MCP clients (for example, listing properties or running a traffic-acquisition report).

After you connect, we may call Google's OpenID userinfo endpoint once and store a limited identity snapshot (subject id, email, and/or name) with your connection metadata so Connections can show which Google account is linked. We do not use Google Sign-In as Jumon's login method.

We store OAuth tokens encrypted at rest. We store connection metadata, operational logs, and—when enabled—encrypted, time-limited copies of Analytics API / MCP response data as described in this policy, solely to provide Service features you request (including remote MCP, the in-app agent, usage history, audit, and support). We do not sell Google user data or use it for advertising unrelated to your use of the Service.

Jumon's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements, as described in the Google API Services — Limited Use section of this policy.

You may disconnect Google Analytics in your Jumon dashboard at any time. Disconnecting removes stored OAuth tokens and the identity snapshot for that connection. You may also revoke Jumon's access in your Google Account permissions at https://myaccount.google.com/permissions.

LinkedIn Ads data

When you connect LinkedIn Ads, you authorize Jumon via LinkedIn OAuth. Depending on the scopes you approve, we may access (a) LinkedIn advertising account data via Marketing API scopes such as r_ads, r_ads_reporting, rw_ads, r_organization_admin, w_organization_social, r_organization_social, and rw_dmp_segments (account identifiers, campaigns, creatives, reporting metrics, organization name/website lookups, organization-owned image upload / sponsored content needed for supported MCP tools, reading organization posts used as ads to show their copy, and matched audiences), and (b) limited member identity via Sign In with LinkedIn using OpenID Connect scopes openid, profile, and email.

After you connect, we may call LinkedIn's OpenID Connect userinfo endpoint once and store a limited identity snapshot (subject id, email, and/or name) with your connection metadata so the Connections page can show which LinkedIn member account authorized the ads connection. We do not use Sign In with LinkedIn as Jumon's login method, and we do not market LinkedIn OpenID Connect as identity verification.

When you ask Jumon to upload an ad image, we fetch the image from a URL you provide, upload it to LinkedIn on your behalf under w_organization_social, and do not retain the image bytes after the upload completes. When you ask Jumon to upload an ad document (PDF, PowerPoint, or Word), we fetch the file from a URL you provide, upload it to LinkedIn on your behalf under w_organization_social, and do not retain the document bytes after the upload completes. When you ask Jumon to create a matched audience, we stream hashed email identifiers or company identifiers you supply to LinkedIn under rw_dmp_segments and do not retain those identifiers after the request completes. We reject raw email addresses. Adding rw_dmp_segments does not update a token you already granted; disconnect and reconnect LinkedIn in Jumon so the new scope is included. We use LinkedIn data only to provide features you request, store OAuth tokens encrypted at rest, and retain connection metadata, operational logs, and encrypted MCP/API response payloads as described in this policy. Advertising account administration and reporting data we store is retained no longer than one year, consistent with LinkedIn Marketing API data storage requirements. We do not sell LinkedIn data, and we do not use LinkedIn Content to target advertisements to individuals.

When you ask Jumon to retrieve LinkedIn Lead Gen Form responses, we retrieve the responses submitted on your own LinkedIn ad accounts and return them only to you, the authenticated user who asked. We do not store those lead form responses. We drop the submitter's LinkedIn member identifier and do not return it. We do not sell lead data, share it with third parties, or use it for advertising or to train AI models.

When you ask Jumon to send offline conversions to LinkedIn, we create conversion rules, associate those rules with campaigns, and upload conversion events to LinkedIn on your behalf. Email addresses are normalized and hashed with SHA-256 inside Jumon's service before transmission. We never send plaintext email addresses to LinkedIn, and we do not log or store plaintext email addresses or conversion event payloads. You are responsible for having a lawful basis, including any consent the law requires, to upload your customers' data as conversions.

You may disconnect LinkedIn in Jumon at any time. Disconnecting deletes that connection's OAuth tokens and stored identity snapshot. You may also revoke Jumon's access through your LinkedIn account settings. To request deletion of other LinkedIn-derived data we retain, email juan@jumonintelligence.com.

Reddit Ads data

When you connect Reddit Ads, you authorize Jumon via Reddit OAuth. Depending on the scopes you approve (such as adsread and identity), we may access Reddit advertising data including businesses, ad accounts, campaigns, ad groups, ads, audiences, and reporting needed for supported MCP tools, and may receive your Reddit username and account id to show which Reddit account you connected.

After you connect, we may call Reddit's identity API once and store a limited identity snapshot (account id and/or username) with your connection metadata for the Connections dashboard. We do not use Reddit as Jumon's login method.

We use Reddit data only to provide features you request, store OAuth tokens encrypted at rest, and retain connection metadata, operational logs, and encrypted MCP/API response payloads as described in this policy. We do not sell Reddit data.

You may disconnect Reddit in Jumon at any time. Disconnecting removes stored OAuth tokens and the identity snapshot for that connection. You may also revoke access through your Reddit account or application permissions.

Meta Ads data

When you connect Meta Ads, you authorize Jumon via Facebook Login OAuth. Depending on the scopes you approve (such as ads_read, business_management, pages_show_list, and email), we may access Meta advertising data including ad accounts, campaigns, ad sets, ads, creatives, and performance insights across Meta technologies (including Facebook and Instagram placements) needed for supported MCP tools, and may receive your Meta user id, name, and/or email to show which Meta account you connected.

After you connect, we may call Meta's Graph /me endpoint once and store a limited identity snapshot with your connection metadata for the Connections dashboard. We do not use Meta Login as Jumon's login method.

We use Meta data only to provide features you request, store OAuth tokens encrypted at rest, and retain connection metadata, operational logs, and encrypted MCP/API response payloads as described in this policy. We do not sell Meta data.

You may disconnect Meta in Jumon at any time. Disconnecting removes stored OAuth tokens and the identity snapshot for that connection. You may also revoke access through your Facebook account settings or Meta Business integrations.

Microsoft Advertising data

When you connect Microsoft Advertising, you authorize Jumon via OAuth using the sign-in method that matches your ads.microsoft.com account: Microsoft account sign-in (Microsoft Entra ID OAuth with scopes such as openid, offline_access, and https://ads.microsoft.com/msads.manage), or Google account sign-in (Google OAuth with profile and email scopes only).

Google sign-in for Microsoft Advertising is separate from connecting Google Ads in Jumon. It does not grant the Google Ads API scope and is not described in the Google Ads user data section above.

Depending on the tools you use, we may access Microsoft Advertising data such as customer and account identifiers, campaigns, ad groups, ads, keywords, audiences, conversion goals, reporting metrics, and related account structure needed for supported MCP tools.

After you connect, we may call Microsoft Advertising User/Query once and store a limited identity snapshot (user id, username, name, and/or email) with your connection metadata so Connections can show which Microsoft Advertising user authorized the connection. We do not use Microsoft or Google sign-in for Microsoft Advertising as Jumon's login method.

We use Microsoft Advertising data only to provide features you request, store OAuth tokens encrypted at rest, and retain connection metadata, operational logs, and encrypted MCP/API response payloads as described in this policy. We do not sell Microsoft Advertising data.

You may disconnect Microsoft Advertising in Jumon at any time. Disconnecting removes stored OAuth tokens and the identity snapshot for that connection. You may also revoke access through your Microsoft account app permissions or, if you connected with Google sign-in, your Google Account permissions at https://myaccount.google.com/permissions.

MCP, in-app AI agent, and third-party AI clients

Jumon exposes an MCP endpoint that compatible assistants (such as Claude, ChatGPT, Cursor, or VS Code) can call after you authenticate with Clerk. Jumon brokers API requests to advertising platforms and may retain encrypted tool/API response data as described above. We do not control how third-party assistants process, display, or retain prompts, tool outputs, or conversation history beyond what Jumon stores.

When you use Jumon's in-app AI agent, conversation content and tool results may be sent to the model provider you configure (bring-your-own Anthropic API key) for real-time inference to generate responses. We do not use your advertising platform data or chat content to train or fine-tune general-purpose AI models.

Review the privacy policies of any third-party AI client you connect to Jumon. Data those clients retain is governed by their terms, not this policy.

Subprocessors

We use trusted service providers to operate the Service. They process data on our behalf under contractual obligations:

Security

OAuth access and refresh tokens are encrypted at rest using industry-standard symmetric encryption. Tokens are decrypted only on our servers to perform API requests you authorize.

Stored MCP and advertising API response payloads are redacted for obvious secrets, encrypted at rest, and associated with your user and (when applicable) organization identifiers. Human access is limited to support, security, and compliance needs.

Internal gateway endpoints that proxy provider APIs require a shared secret and are not exposed to end users. We apply access controls, monitor for abuse, and follow security practices appropriate to the sensitivity of the data we process.

No method of transmission or storage is completely secure. If you believe your account has been compromised, contact us at juan@jumonintelligence.com and disconnect affected providers.

Retention

We retain account and connection data while your account is active and as needed to provide the Service. When you disconnect a provider, we delete that connection record (including OAuth tokens and any stored platform identity snapshot such as email or username) and update connection status. Encrypted MCP/API response payloads for that connection are kept for a short grace period (30 days) so that reconnecting after a temporary disconnect does not erase recent history; if you do not reconnect, those payloads are then deleted. Payloads may also expire earlier under the retention periods below.

Operational usage metadata is retained for a limited period for security, billing, and product analytics, then deleted or aggregated.

Encrypted MCP/API response payloads are retained by default for up to six months. For LinkedIn advertising account administration and reporting data, retention does not exceed one year. LinkedIn lead form responses and offline conversion event uploads are not stored, so neither retention period applies to them. Usage metadata for those requests, such as tool name, status, and timestamps, is still logged. Expired payloads are deleted automatically.

In-app chat messages and artifacts are retained while your account (or organization workspace) remains active unless you delete them or request deletion.

We may retain certain records longer where required by law or to resolve disputes.

To request account deletion or purge of stored advertising data, email juan@jumonintelligence.com.

Your rights

Depending on your location, you may have rights to access, correct, delete, or export personal data, or to object to or restrict certain processing.

You can disconnect advertising platforms in the Jumon web app and revoke OAuth access with each platform directly. To request account deletion or exercise privacy rights, email juan@jumonintelligence.com. We will respond within the timeframes required by applicable law.

International transfers

We and our subprocessors may process data in the United States and other countries. Where required, we rely on appropriate safeguards for cross-border transfers.

Children

The Service is not directed to children under 16, and we do not knowingly collect personal information from children. Contact us if you believe we have collected such information.

Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated policy on this page with a revised "Last updated" date. Material changes that affect how we use advertising platform data will be reflected here before or when those changes take effect, and where required we will obtain your consent.

Continued use of the Service after an update constitutes acceptance of the revised policy.

Contact

Jumon Inc

Email: juan@jumonintelligence.com

For OAuth or advertising data questions, reference this Privacy Policy URL when contacting us.