Privacy Policy

At Goodie AI Inc. (“Goodie”, “we”, “us”, or “our”), we are committed to protecting your privacy. This Privacy Policy (“Policy”) describes how we collect, use, disclose, and safeguard your personal information when you access our websites (including higoodie.com), applications, tools, APIs, and services (collectively, the “Services”).

By accessing or using the Services, you agree to this Policy. If you do not agree, please discontinue use immediately. For privacy inquiries or requests, contact us at hello@higoodie.com.

1. When We Collect Personal Information

We collect personal information when you:

• Create an account or sign in
• Use our website, application, or services
• Submit forms, feedback, surveys, or support requests
• Upload data, content, or prompts
• Interact with us on third-party platforms (e.g., LinkedIn)
• Register through a third-party login (e.g., Google)
• Apply for employment or submit a resume

2. What Personal Information We Collect

A. Information You Provide Directly

• Name, email, phone, company, job title, industry
• Account credentials or authentication tokens
• Uploaded content: URLs, metadata, brand domains
• Billing/payment details (processed securely by third parties)
• Applicant data (resume, education, employment history)

B. Information We Collect Automatically

• IP address, device ID, browser, OS version, resolution
• Usage logs (pages visited, session length, referrer)
• Interaction events (e.g., clicks, form engagement)
• Mobile diagnostics (OS, device type, network)

C. Information from Third Parties

• Enriched business data (from data partners)
• Marketing and CRM signals (LinkedIn, Google Ads)
• Outputs from AI services (e.g., OpenAI, Anthropic)

We do not knowingly collect sensitive personal information (e.g., biometrics, race, health data) or use data for behavioral profiling.

3. How We Use Personal Information

We use your information to:

• Deliver, secure, and maintain our Services
• Personalize dashboards and AI-generated insights
• Respond to support inquiries and process transactions
• Improve platform features through analytics
• Enforce contracts, comply with laws, and resolve disputes
• Send service updates, notices, and relevant offers (with opt-out)
• For recruitment and application review

We do not use automated decision-making with legal or similarly significant effects without user notice and opt-out.

4. How We Share Personal Information

We may share data with:

• Service providers (see categories of sub-processors below)
• AI infrastructure vendors (e.g., OpenAI, Perplexity), limited to aggregated or de-identified data used to operate and improve in-product AI features. We do not share Customer Personal Data with these vendors, and this data is not used for model training.
• AI assistant connectors (MCP): When you connect Goodie MCP to an AI client such as Anthropic’s Claude or OpenAI’s ChatGPT, we share authorized Goodie API responses – and the tool arguments needed to retrieve them – with that AI client provider, at your direction, so it can answer your questions. This sharing is distinct from the AI infrastructure vendors listed above, which Goodie uses as its own service providers to fulfill in-product requests. See Section 7 for the complete list of tool inputs, outputs, recipients, retention, and controls.
• Affiliates or acquirers during corporate transactions.
• Law enforcement or regulators, as required by law.

Our Sub-processors by Category:

We use the following categories of sub-processors who may have access to personal information:

• Analytics: to processes usage data and metrics
• Authentication: to process login credentials and authentication data
• Communication and Collaboration: to process emails and internal communications
• CRM/marketing tool: to process form submissions and customer data for communications and remarketing
• Recruitment: to processes applicant data and resumes
• Server Infrastructure: to store data
• Billing: to process payment information and invoices

We may share aggregate, de-identified data without restriction.

5. Your Rights and Choices

Depending on your location, you may have rights to:

• Access and review your personal data
• Correct inaccuracies
• Request deletion (subject to exceptions)
• Object to or restrict processing
• Withdraw consent where applicable
• Request data portability
• Opt out of marketing communications

You may access, update, or delete your account information from your account settings or by emailing hello@higoodie.com. We may verify your identity before fulfilling certain requests.

6. Cookies and Online Tracking Technologies

We use cookies, tags, and web beacons to:

• Authenticate sessions
• Track analytics and performance
• Personalize experience and remember preferences
• Run remarketing campaigns (e.g. through Google, LinkedIn)

Your options:

• Set your browser to reject cookies
• Use tools like optout.aboutads.info
• Manage cookie preferences through our banner (European Union (“EU”)/ United Kingdom (“UK”))

7. AI Assistant Integration

Goodie MCP Server (Claude, ChatGPT, and Other MCP Clients)

Goodie offers an optional Model Context Protocol (“MCP”) server (“Goodie MCP“) that lets authorized Users connect an AI assistant – including Anthropic’s Claude and OpenAI’s ChatGPT Apps/connectors – to query brand analytics and configuration stored in their organization’s Goodie account. In this Section, “you” means the individual User connecting an AI client under your organization’s Goodie account (as defined in our Service Agreement).

This section describes what data is collected, used, shared, retained, and how you can control it when you connect Goodie MCP to an AI client.

7.1 What the integration does

When connected, the AI client can:

1. Discover which Goodie API operations are available (search tool and catalog resources).
2. Retrieve your active brand/organization context (execute the context-retrieve operation).
3. Invoke allowlisted Goodie API operations on your behalf (execute with any catalog operation_id).

Goodie MCP acts as a stateless proxy: it validates your connection, forwards authorized requests to the Goodie backend API, and returns JSON responses to the AI client. It does not persist the content of your requests or the data returned in response beyond what’s needed to complete that single request. Goodie MCP does not accept authentication tokens inside tool arguments; credentials are bound to the MCP connection (Section 7.4).

Operations catalog: Goodie MCP exposes an allowlisted catalog of backend operations that map one-to-one to API endpoints available in the Goodie web application, spanning product domains such as Monitor, Agents, Commerce, Brand DNA, Prompt Research, Analytics, Accounts, and Integrations. The catalog is read-only today, matching the “Read-only” access shown on our public Goodie MCP page. If we later add write operations (e.g., create, update, delete) that mirror actions you can already take in the Goodie dashboard, we will update this Section and our public MCP documentation at the same time, and where required by law, give advance notice before the change takes effect. Every operation, read or write, is subject to the same authentication, authorization, and privacy rules as the equivalent dashboard feature.

7.2 MCP tools – inputs and outputs

Goodie MCP exposes exactly two tools. Plain-language summaries appear first; the tables are the full technical contract, and a supplemental, always-current field-level reference is also published at our MCP documentation page.

Tool: search – plain-language summary

Lets the AI client look up which Goodie operation to call, by keyword. It only searches a static list of operation descriptions – it does not touch your account data.

Direction	Field	Description
Input	query (string, required)	Natural-language or keyword search over the Goodie API catalog
Input	limit (integer, optional, default 5, max 20)	Maximum number of ranked results
Input	tags (string array, optional)	Filter by tag (e.g., “Brand Visibility“)
Output	query, result_count, fallback_used	Echo of search parameters and match metadata
Output	results[]	Ranked catalog entries, each including operation_id, method, path, summary, description, score, tags, parameters[], and example_execute
Output	hint (optional)	Guidance when no strong matches are found

Data collected via this tool: only the search query string and optional tag filter. No customer account data is read by search itself.

Tool: execute – plain-language summary

Runs one specific, allowlisted Goodie operation and returns the result – this is the tool that actually reads your brand/account data.

Direction	Field	Description
Input	operation_id (string, required)	Stable identifier for one catalog operation
Input	path_params (object, optional)	URL path parameters (commonly brand_id)
Input	query_params (object, optional)	Query parameters (commonly start_date, end_date, page, page_size, filters)
Input	body (object, optional)	Request body for operations that require one
Output (success)	ok: true, operation_id, status_code, data	data contains the upstream Goodie API JSON response for the requested operation
Output (error)	ok: false, error.code, error.details	Structured error codes such as UNKNOWN_OPERATION, VALIDATION_ERROR, UNSUPPORTED_METHOD, UPSTREAM_TRANSPORT_ERROR, UPSTREAM_HTTP_ERROR

Non-JSON upstream bodies are truncated to 1,000 characters in tool responses.

Bootstrap operation (required first call): execute(operation_id="mcp_session_context_retrieve") returns:

{

  "tenant": {

    "brand_id": "<integer>",

    "brand_name": "<string>",

    "organization_id": "<organization ID>"

  },

  "workos_user_id": "<authenticated user ID or null>"

}

This response does not include your email address or name.

7.3 MCP resources (read-only reference data)

Resource URI	Content
mcp://goodie/identity	Server identity, behavior guidelines, product brief, operation overview
mcp://goodie/context/default	Default runtime context from server configuration
mcp://goodie/product/context	Goodie product model (Research → Monitor → Actions → Measure)
mcp://goodie/api-catalog/domain-overview	Domain map, tag keywords, operation counts
mcp://goodie/api-catalog/overview	Map of operation_id → description
mcp://goodie/api-catalog	Full compact operation index
mcp://goodie/api-catalog/operation/{operation_id}	Full contract for one operation

These resources contain API documentation metadata only, not live customer records (except the bootstrap session context above).

7.4 Authentication and access control

You authenticate via OAuth when connecting Goodie MCP in your AI client, using the same Goodie account as the web dashboard.

• Goodie validates your authenticated session on each upstream request.
• Data access is limited to brands you are authorized to access through your organization membership.
• Cross-brand and cross-customer access is blocked at the Goodie API layer – a connected AI client can never see another Goodie customer’s data, or a brand within your own organization you aren’t authorized to view.
• Do not pass session tokens in search or execute arguments – authentication is inherited from the MCP connection.

7.5 Categories of data that may be returned through execute

Depending on which operations the AI client calls, tool outputs (data) may include:

Category	Examples of fields returned	Notes
Account/tenant context	brand_id, brand_name, organization_id, authenticated user ID	Bootstrap context only
Brand profile & configuration	Brand name, website, country, languages, voice, personas, topics, prompts, competitors, tags	Business/marketing configuration
Monitor analytics	Visibility scores, share of voice, rankings, brand mentions, sentiment labels, cited domains/URLs, AI prompt text and AI-generated answer snippets	May include third-party web content cited in AI answers
Prompt research	Topic clusters, trending prompts, watchlist items, search history metadata	Research/planning data
Agent recommendations & actions	Optimization suggestions, content recommendations, outreach/social action items, tracked page URLs, status fields	Operational workflow data
Commerce analytics	Product names, merchant names, prices, shopping visibility metrics	Commercial/product data
Measure / analytics integrations	GA4 sessions, conversions, revenue, pages, countries, channels; Search Console/Bing metrics; AI bot crawl counts and page URLs	Aggregated site analytics when integrations are connected; no raw visitor identifiers in standard API responses
Integrations	Platform name, connection status, configuration metadata; in some records, installer email (installed_by_email)	Limited workspace-member PII
Billing & subscription	Plan name, subscription status, trial dates, Stripe invoice IDs, amounts, invoice PDF/hosted URLs	Billing metadata, not full payment card numbers
Usage	Feature credit consumption counts	Account usage metrics

Goodie MCP does not expose your password, full payment card numbers, or authentication secrets through tool outputs.

7.6 How we use MCP-related data

We use data processed through Goodie MCP to:

1. Authenticate and authorize your MCP connection (via OAuth).
2. Fulfill your requests by retrieving the Goodie data you ask the AI assistant to query.
3. Operate, secure, and troubleshoot the MCP service (e.g., error logging, abuse prevention).
4. Maintain and improve the Goodie platform in accordance with this Policy and our Service Agreement.

We do not use MCP tool inputs or outputs to train AI models. We do not sell MCP-derived personal information. If we later introduce a feature that uses your MCP request history to personalize your experience, we will update this Section and obtain your consent before turning it on for your account. 

7.7 Who receives MCP-related data (recipients)

When you use Goodie MCP through an AI client such as Claude or ChatGPT, data may be shared with:

Recipient	Role	Data shared
Anthropic, OpenAI, or your chosen AI client provider	Hosts your conversation and invokes MCP tools at your direction	Your natural-language prompts, tool call arguments (query, operation_id, date ranges, filters, brand_id, etc.), and tool results (data JSON returned from Goodie)
OAuth authentication provider	Validates sign-in and session for MCP connections	Login and session validation data (organization ID, user ID); not tool payloads
Goodie platform infrastructure	Authoritative data store and API	All authorized execute requests and responses
Connected analytics & billing providers (when applicable)	Source systems for live Measure/billing data	Goodie retrieves aggregated analytics from Google (GA4, Search Console), Microsoft Bing Webmaster, and billing data from Stripe when your brand has those integrations enabled; results are returned to the AI client via MCP
Cloud/infrastructure subprocessors	Hosting, logging, CDN	Standard service-provider processing under our sub-processor program (Section 4)

Sharing with your chosen AI client happens because you directed the client to call Goodie MCP – it is not a sale, and Anthropic/OpenAI act as your instructed recipient, not as Goodie’s subprocessor. Because you (not Goodie) initiate and control this transfer, the AI client provider is not engaged by Goodie to process Personal Data on Goodie’s behalf, and the subprocessor notice and objection provisions of the DPA do not apply to it. Important: once tool results reach your AI client, they are also subject to that provider’s own privacy policy and data-use settings – Goodie does not control retention on the AI client’s side. Review and configure those settings separately.

International transfers: For customers in the EU, UK, or other regions with cross-border transfer requirements, sending prompts and tool results to an AI client provider (such as Anthropic or OpenAI, which may process data in the United States) is a transfer you initiate and control. Because it is a customer-directed transfer to your instructed recipient rather than a transfer to a Goodie subprocessor, it is not covered by Goodie’s own Standard Contractual Clauses or the transfer mechanisms in the DPA; you are responsible for establishing an appropriate transfer basis with your chosen AI client provider under your agreement with that provider.

7.8 Retention

Data type	Retention
Goodie MCP server process	Stateless – the MCP server does not store the content of tool inputs or outputs today. Requests and responses exist only for the duration needed to complete the call.
Future MCP content storage	We do not currently store the content of search or execute requests/responses beyond the single request. If we introduce persistent storage of this content in the future, we will: (a) cap retention to a defined period rather than keeping it indefinitely, (b) delete it for inactive or closed accounts, and (c) update this Section and, where required by law or our Data Processing Addendum, obtain your consent before the change takes effect.
In-memory catalog	OpenAPI catalog metadata only; regenerated from schema at startup
Goodie platform records	Retained according to your subscription, account settings, and our general platform retention practices while your account remains active, unless you delete data or close your account. Deletion or return of Personal Data upon termination is governed by Section 10.2 of the DPA, under which Goodie will delete Personal Data as instructed by Customer, except where retention is required by applicable law.
Server logs	Operational logs (errors, request metadata) retained for a limited period for security and troubleshooting – typically up to 90 days, unless a longer period is required by law or an active investigation. Where you instruct deletion upon termination, Goodie will delete or isolate log data containing Personal Data except where retention is required by applicable law, consistent with Section 10.2 of the DPA.
OAuth session cache	Validated sessions cached up to 45 seconds on the Goodie API to reduce authentication overhead
AI client provider	Governed by the AI provider’s own retention settings, not by Goodie

7.9 Your choices and controls

You can control MCP-related processing by:

1. Disconnecting the Goodie MCP connector in ChatGPT, Claude, or your AI client at any time.
2. Signing out of Goodie or revoking authorization for the MCP connection in your AI client.
3. Managing integrations in Goodie (e.g., disconnecting GA4, Search Console, Bing, etc.) to limit categories of data retrievable via MCP.
4. Limiting prompts you send to the AI client – the AI client decides which tools to call based on your instructions.
5. Exercising privacy rights under Sections 5 and 9 (access, correction, deletion) by contacting hello@higoodie.com or using account settings.

Deleting your Goodie account or revoking authorization stops future MCP data access; it does not automatically delete data already retained by your AI client provider under their own policies.

7.10 Other AI uses (non-MCP)

Outside of the MCP connector described above, Goodie may use third-party AI providers (e.g., OpenAI, Anthropic, Perplexity) to generate in-product insights when you use Goodie directly in our web application. For those uses:

1. We send content to AI services only to fulfill specific in-product requests.
2. We do not allow those providers to train on your data under our vendor agreements.
3. We do not retain user prompts for unrelated analytics or model retraining.

AI outputs are informational and are not legal, financial, or business advice.

8. Processor vs. Controller Roles

We act as:

1. Controller for website usage, marketing, platform analytics
2. Processor for customer-uploaded content, AI prompts, and structured data under customer direction

Customers are responsible for any end-user rights related to their uploaded data when Goodie acts as a processor.

9. U.S. State Privacy Rights

Depending on your state of residence, consumer privacy laws may provide their residents with additional rights regarding our use of their personal information and require specific disclosures (“State Privacy Laws”). In particular, because the Nebraska Data Privacy Act (NDPA) and Texas Data Privacy and Security Act (TDPSA) apply regardless of business size or data volume thresholds, Goodie complies with these laws to the extent we process personal information of Nebraska or Texas residents. While Goodie does not meet the thresholds that would require compliance with the California Consumer Privacy Act (CCPA/CPRA), Virginia Consumer Data Protection Act (VCDPA), or other applicable U.S. state privacy laws, we voluntarily provide the following rights to individuals whose personal information we collect. We do not sell your personal data. We may share personal data for remarketing and advertising purposes as described in Section 6.

Your Rights

Depending on your state of residence, you may have the right to:

1. Access: Request a list of data collected
2. Delete: Request deletion of personal information (subject to exceptions)
3. Correct: Request correction of inaccurate data
4. Opt-Out: Opt-out of our sharing data

How to Exercise Your Rights

You may access, update, or delete your account information from your account settings or by emailing hello@higoodie.com. We may verify your identity before fulfilling certain requests.

Non-Discrimination

We will not discriminate against you for exercising your privacy rights.

Global Privacy Control (GPC)

We honor Global Privacy Control (GPC) opt-out signals.

Appeals

If we deny your request, you may appeal our decision by contacting us at hello@higoodie.com. If you have concerns about the results of an appeal, you may contact the attorney general in the state where you reside.

Authorized Agents

If you are an authorized agent seeking to make a request on behalf of a consumer, please contact us at hello@higoodie.com.

10. UK, EEA, and International Users

Legal Basis for Processing:

Activity	Legal Basis
Cookies and tracking	Consent
Service delivery & security	Legitimate Interest
Communications	Consent / Legitimate Interest
Billing and access	Contractual Necessity
Recruitment	Legitimate Interest / Consent
AI infrastructure vendors (to fulfill request)	Legitimate Interest / Contractual Necessity

Cross-Border Transfers: We may transfer data to the U.S. or other countries using Standard Contractual Clauses or similar safeguards.

Data Storage Location: Our primary data storage is in the United States (“U.S.”). For EU/UK users, this constitutes a cross-border transfer protected by appropriate safeguards as described above.

You may lodge complaints with your national supervisory authority. UK users may contact the ICO at ico.org.uk.