> ## Documentation Index
> Fetch the complete documentation index at: https://help.fanaura.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data and privacy

> What the Fanaura MCP server shares with an assistant, what it never returns, and how each contact detail is labeled.

Your journeys and contacts stay in your Fanaura account. An assistant only sees what a tool returns in that chat, and only for the account you approved.

<CardGroup cols={2}>
  <Card title="Scoped to one account" icon="lock">
    Every token belongs to one Fanaura user and one account. A tool can never read or change another account.
  </Card>

  <Card title="Read on request" icon="eye">
    Nothing is synced to the assistant ahead of time. Data moves only when a tool runs.
  </Card>

  <Card title="No deletes" icon="shield">
    No tool deletes a journey or a contact. Pausing and archiving stay in the Fanaura iPhone app.
  </Card>

  <Card title="No outbound messages" icon="mail-x">
    No tool sends an email, a text, or a blast. Instagram replies go only to people who comment or DM your keyword.
  </Card>
</CardGroup>

## What a tool can return

| Tool group | Returns |
| - | - |
| Journeys | Names, keywords, destinations, replies, capture settings, triggers, public links, and status |
| Contacts | Names, Instagram details, email, phone, location, device, answers to your journey questions, opt-ins, engagement, and a dated timeline |
| Setup | Whether Instagram, texting, and email are connected, and the Instagram username |

## What a tool never returns

<Warning>
  The following are filtered out on Fanaura's side before any result leaves the server. An assistant cannot ask for them.
</Warning>

* Contact session tokens and their expiry times
* One-time sign-in codes
* Instagram, Meta, and other platform access tokens
* Internal markers such as seeded test data flags
* Payment details and billing information
* Prices, upgrades, and store links

## How each detail is labeled

Every contact field carries a `provenance`, so the assistant can tell you how a detail was learned.

| Provenance | Meaning | Examples |
| - | - | - |
| `self_reported` | The contact typed it into your journey. | Name, email, phone, birthday, favorite song |
| `inferred` | Fanaura estimated it from the visit. | City and time zone from the network |
| `enriched` | Fanaura added it from a connected service or from activity. | Instagram handle, follower count, engagement score |
| `imported` | It came from an import or another system. | VIP status, rewards, referral code |

<Info>
  A city the contact typed is labeled `self_reported`. A city estimated from the network is `inferred`.
</Info>

## Missing details

`get_contact` returns a `missing` object with two lists:

<Columns cols={2}>
  <Card title="asked_unanswered" icon="circle-help">
    A journey asked for it, and the contact has not answered yet.
  </Card>

  <Card title="not_asked" icon="circle-dashed">
    No journey has asked this contact for it.
  </Card>
</Columns>

Fields with no stored value are left out of the result. The missing lists name what was asked and left unanswered, and what nobody has asked.

## Times and time zones

Every timestamp comes back twice: `occurred_at` in UTC and `occurred_at_local` in your account's time zone, such as "Tue, Mar 3, 8:14 PM".

## Your assistant's own data rules

Once a result reaches the assistant, it follows that assistant's privacy settings, such as chat history and training controls. Check those settings in Claude, ChatGPT, or your editor. Fanaura does not read your chats.

<Card title="Fanaura privacy policy" icon="file-lock" href="https://www.fanaura.com/privacy">
  How Fanaura handles your account and your contacts' data.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.