Frog

Privacy policy

Last updated: 3 October 2026.

Who operates Frog

Frog is operated by Makxime HUYNH, 130 Boulevard Massena, 75013 Paris, France. Contact for privacy and support: makxime.huynh@gmail.com.

This policy covers usefrog.tech, app.usefrog.tech and Frog's account, workspace, agent and optional connector features. Makxime HUYNH is responsible for account administration and service security data. Your organisation determines why its own content and connected business data are used; Frog processes those data to provide the workspace features you request.

Data we process and why

  • Account and workspace data: email address, supplied profile information, account identifiers, memberships and roles. These let us authenticate you, manage access and provide support.
  • Product and work content: website URLs, product profiles, topics, questions, chat messages, sources, AI answers, drafts, approvals and execution receipts. These support the GEO work you request and its saved history.
  • Connected account data: provider account identifiers, OAuth permissions, encrypted authorization credentials and selected properties or content destinations. These let Frog access the tools you authorize.
  • Google reports: selected Search Console search queries, page paths, dates, clicks, impressions and position; or selected GA4 traffic sources, landing pages, sessions, key events and revenue. These are imported only through supported, explicitly requested report workflows.
  • Technical and support data: requests, errors, security events, device/browser information, page visits and performance measurements, and information you send to support. These help operate, protect and troubleshoot the service.

Account information needed for sign-in is required to provide an account. Connectors and report imports are optional; refusing them prevents only the features that need those data. Do not submit passwords, API secrets, special-category personal data or information you are not authorized to share in chat or support messages.

For account and requested service functions, our legal basis is providing the service contract. For fraud prevention, access control and essential diagnostics, it is our legitimate interest in operating a secure service. Where consent is required for optional processing, you can withdraw it. A provider's OAuth permission is an access authorization, not a replacement for your organisation's legal basis or notices to people whose data are involved. Legally required retention or disclosures use the applicable legal obligation.

Google access, use and sharing

Search Console uses webmasters.readonly. GA4 uses analytics.readonly. Frog lists accessible properties and reads reports; it does not change Analytics settings, submit URLs to Google or edit your site through these Google connections.

Only a workspace owner can connect an account and choose a property. Property selection requires an explicit confirmation of workspace sharing and agent use. Imported reports are available to authorized workspace members. Navigation alone does not import reports.

When the agent answers a workspace request using a saved report, relevant report data are sent to OpenAI. This can include queries, page paths, sources and business performance metrics. Google authorization credentials are server-only and are not sent to the model.

Frog follows the Google API Services User Data Policy, including its Limited Use requirements. Google API data and derived results are used for the visible reporting and agent features you request, not sold, used for advertising, data brokerage or credit decisions, or used by Frog to train general-purpose AI models. Human access by the operator is limited to your explicit authorization, necessary security/bug investigation, legal obligations or permitted aggregated internal operations. Workspace members receive access under your explicit workspace-sharing choice.

AI and connected tools

OpenAI processes the messages and relevant product, source and report context needed for requested AI features. Frog retains its own workspace history and uses API requests configured not to store Responses application state at OpenAI. This is not a zero-retention promise: provider security retention and applicable service settings still apply.

Connecting GitHub or Webflow shares the provider-authorized account and content information needed for the selected repository or CMS workflow. A connection is not authorization to publish. Supported external changes require the application's scope, destination and approval checks. The provider's own service and privacy rules also apply.

Recipients and processing locations

Service providers include Supabase for authentication and database storage, Vercel for application hosting, operational logs, Web Analytics and Speed Insights, and OpenAI for AI processing and requested search-backed features. Google, GitHub and Webflow process connection requests and their own service data when you use those integrations. Authorized workspace members see the content shared with their workspace.

Processing is not guaranteed to remain solely in France or the European Economic Area. Our providers' data-processing terms describe their international transfer safeguards, including standard contractual clauses where applicable: Supabase, Vercel, and OpenAI. Contact us for the safeguards applicable to your request. We do not claim provider certifications or regional settings that have not been verified for this deployment.

Cookies and measurement

Frog uses authentication cookies to maintain your session. The application includes Vercel Web Analytics and Speed Insights for site usage and performance. It does not install GA4 tracking on your website when you connect a GA4 property. Connecting GA4 reads your existing property's reports instead.

Retention, disconnection and deletion

Workspace content, reports, approvals and receipts remain available as saved history while needed to provide the workspace service. Disconnecting a Google account removes Frog's saved credentials for that connection and stops new imports; it does not delete saved reports or prior chat answers. Revoking a provider grant does not erase copies already saved in Frog.

There is no automatic short-term purge of workspace history in the current early-access service. To close an account or request deletion of specific records, email the privacy contact with your account/workspace identity. Requests are handled manually after checking your authority; do not send identity documents unless a necessary secure verification process is agreed. We delete data that are no longer needed following a valid request, subject to legal obligations, necessary security evidence and other members' legitimate workspace rights. We identify any applicable exception in our response.

Support and security records are retained only for the support, incident, legal or dispute purpose for which they remain necessary. Hosting logs and provider backups follow the relevant service's retention and deletion cycle, so removal from the active database is not a promise of immediate deletion from every backup. Contact us for the criteria applicable to a particular record.

Your rights and contact

Depending on the processing and applicable law, you can request access, correction, deletion, restriction, portability or object to processing. You can withdraw consent where processing relies on consent without affecting its previous lawfulness. Send requests to makxime.huynh@gmail.com. If your organisation controls the workspace data, we may need its instructions to act on those records.

You can complain to the French data protection authority, CNIL. Frog does not make automated decisions about an individual's legal or similarly significant eligibility; its AI output is assistance for your work, not such a decision.

Changes

The date above identifies this version. Material changes to purposes, recipients or access require updated information and any necessary consent before the new processing. This policy does not claim that every optional connector has completed provider review; see the connection guide for availability.