> For the complete documentation index, see [llms.txt](https://trust.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trust.impact.com/transparency.md).

# Transparency

We believe in showing our work. This page explains how we keep our AI understandable and verifiable, so you always know when you're using AI, how it works, and where its answers come from.

## Model cards

Think of a model card as a "nutrition label" for an AI feature: a short, readable document covering what it does, how it works, the data it uses, and its limitations. We're committed to publishing a model card for our AI features, following recognized industry standards.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>💬 Conversational AI &#x26; Content Generation</strong></td><td>Anthropic Claude and Google Gemini models, orchestrated through a multi-agent system, powering the ask impact chat interface.</td><td><a href="/pages/0a9999f7510a7f2c786a464a56f96a9fbc4bb339">/pages/0a9999f7510a7f2c786a464a56f96a9fbc4bb339</a></td></tr><tr><td><strong>🤝 Partner Recommendation Engine</strong></td><td>Our proprietary machine-learning model for discovering new partners.</td><td><a href="/pages/c7035afaf882b60d20df4ada62816851e1cb9911">/pages/c7035afaf882b60d20df4ada62816851e1cb9911</a></td></tr><tr><td><strong>📧 Newsletter Generation</strong></td><td>Drafts partner-facing marketing newsletters, including subject lines, email body content, and tone variants.</td><td><a href="/pages/xtxgje2pC9OYeVzhxy91">/pages/xtxgje2pC9OYeVzhxy91</a></td></tr><tr><td><strong>Social Listening Sentiment Summary</strong></td><td>Summarizes the dominant sentiment around your listener keywords from monitored social posts.</td><td><a href="/pages/TnSVFBriCto4Ap0zQXXO">/pages/TnSVFBriCto4Ap0zQXXO</a></td></tr></tbody></table>

## Our AI partners (sub-processors)

For our in-platform AI, we partner with leading technology providers that meet our strict security, privacy and accountability standards. Every sub-processor goes through our vendor vetting process before integration.

{% hint style="info" %}
**Google:** We use Google's infrastructure, including Anthropic's Claude models accessed within Google Cloud Vertex AI. Anthropic is not a separate sub-processor and does not receive your data. Our agreement with Google contractually restricts the use of your data and aligns with Google's AI data governance. Learn more at [Google's AI Principles](https://ai.google/responsibility/principles/).
{% endhint %}

## In-product transparency

We build transparency directly into the product experience:

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>🏷️ Clear AI identification</strong></td><td>A unique, consistent icon marks every feature and response generated by AI, so you always know when you're working with AI.</td></tr><tr><td><strong>🔗 In-product traceability</strong></td><td>Wherever possible, AI-generated insights include citations or links back to the source data inside your impact.com account, so you can verify any answer for yourself.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://trust.impact.com/transparency.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.