> ## 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 & Privacy

> How Fanaura handles fan data, ensures GDPR and CCPA compliance, manages consent, and protects sensitive information.

Your fans trust you with their personal information -- their names, email addresses, phone numbers, and locations. That trust is sacred, and Fanaura is built to honor it. This page explains how fan data is stored, how privacy regulations are met, and what protections are in place.

## Data Storage

### Where Your Data Lives

<Info>
  Fanaura stores all data in a **secure, encrypted database** hosted within the **European Union (Frankfurt, Germany)**. EU data residency provides a strong privacy foundation, as EU data protection laws are among the strictest in the world.
</Info>

* All data in transit is encrypted via TLS/SSL.
* Database backups are maintained for disaster recovery.

### What Data Is Stored

| Data Type               | Examples                                        | Where Stored              |
| ----------------------- | ----------------------------------------------- | ------------------------- |
| Fan profiles            | Name, email, phone, location, birthday          | EU (Frankfurt)            |
| Engagement history      | Presaves, email opens, clicks, purchases, RSVPs | EU (Frankfurt)            |
| Campaign data           | Blast content, send history, delivery stats     | EU (Frankfurt)            |
| Flow data               | Flow configurations, execution logs             | EU (Frankfurt)            |
| Integration credentials | API keys, OAuth tokens                          | EU (Frankfurt), encrypted |
| Artist profiles         | Account details, settings, preferences          | EU (Frankfurt)            |
| Asset data              | Music, tour, merch, extra metadata              | EU (Frankfurt)            |

## GDPR Compliance

The **General Data Protection Regulation (GDPR)** is the EU's comprehensive data protection law. Fanaura is designed with GDPR compliance at its core.

<Tabs>
  <Tab title="EU Data Residency">
    All personal data is stored within the EU (Frankfurt, Germany), satisfying GDPR's data residency preferences and avoiding complex cross-border data transfer issues.
  </Tab>

  <Tab title="Lawful Basis">
    Fanaura processes fan data based on **explicit consent**:

    * Fans actively submit their information through smart link data wrappers.
    * Consent is collected at the point of data entry, not assumed or buried in terms of service.
    * Each data collection point clearly explains what data is being collected and why.
  </Tab>

  <Tab title="Right to Access">
    Fans have the right to know what data you hold about them. Fan profiles in Fanaura contain a complete record of all data associated with each fan, making it straightforward to fulfill access requests.
  </Tab>

  <Tab title="Right to Deletion">
    Fans have the right to request deletion of their personal data. Fan records can be deleted from your database, along with associated engagement history, tokens, and activity logs. Deletion is permanent and cannot be undone.
  </Tab>

  <Tab title="Consent Tracking">
    Every piece of data collected through Fanaura tracks:

    * **When** consent was given (timestamp)
    * **How** consent was given (which smart link, which form)
    * **What** was consented to (email marketing, SMS marketing, data collection)

    This audit trail is essential for demonstrating compliance if regulators ask.
  </Tab>
</Tabs>

### Data Minimization

<Note>
  Fanaura's smart link data wrappers are configurable. You can collect only the data you actually need:

  * **Required**: Email address (minimum for communication).
  * **Optional**: First name, last name, phone number, birthday, location.

  You decide which fields are required and which are optional. Collecting less data is both a privacy best practice and a way to reduce friction for fans.
</Note>

## CCPA Compliance

The **California Consumer Privacy Act (CCPA)** gives California residents specific rights over their personal data. Fanaura supports CCPA requirements:

* **Right to Know**: California fans can request a copy of all personal data collected about them.
* **Right to Delete**: California fans can request deletion of their personal data.
* **Right to Opt-Out of Sale**: Fanaura does not sell fan data to third parties. Your fan data belongs to you and is never shared, sold, or monetized by Fanaura.
* **Non-Discrimination**: Fans who exercise their privacy rights are not treated differently.

<Warning>
  Fanaura does not sell fan data to third parties. Your fan data belongs to you and is never shared, sold, or monetized by Fanaura.
</Warning>

## Fan Consent

### Smart Link Data Wrappers

Every smart link in Fanaura includes a **data wrapper** -- a privacy-compliant consent screen:

<Steps>
  <Step title="Fan Visits Smart Link">
    The fan visits your smart link.
  </Step>

  <Step title="Data Wrapper Appears">
    The data wrapper explains what data is being collected, why, and how it will be used.
  </Step>

  <Step title="Fan Submits">
    Fan enters their information and submits. Consent is recorded with a timestamp.
  </Step>

  <Step title="Content Access">
    Fan proceeds to the content (presave, streaming links, merch, etc.).
  </Step>
</Steps>

<Info>
  The data wrapper ensures that every fan interaction begins with informed consent. No data is collected without the fan actively choosing to provide it.
</Info>

### Email and SMS Opt-In

<Tabs>
  <Tab title="Email Opt-In">
    When fans provide their email through a smart link, they are opting in to receive marketing emails from you. The consent is logged and timestamped. You can include an explicit consent checkbox for additional clarity.
  </Tab>

  <Tab title="SMS Opt-In">
    SMS consent requires a separate, explicit opt-in:

    * Fans must actively check an SMS consent box (it is not pre-checked).
    * The consent message explains that they will receive text messages.
    * The SMS opt-in status field in the fan record tracks this consent.
  </Tab>
</Tabs>

## Opt-Out Mechanisms

<Tabs>
  <Tab title="Email Unsubscribe">
    Every marketing email sent through Fanaura includes a **one-click unsubscribe** link in the footer:

    * Fans click the link and are immediately unsubscribed.
    * Their email opt-in status is updated in real time.
    * This complies with CAN-SPAM, GDPR, and CCPA requirements.
  </Tab>

  <Tab title="SMS Opt-Out">
    Fans can opt out of SMS by texting **STOP** to your SMS number:

    * Fanaura automatically processes STOP messages.
    * The fan's SMS opt-in status field is set to false.
    * This complies with TCPA regulations.
  </Tab>
</Tabs>

<Warning>
  When a fan opts out, you cannot manually re-add them to your mailing or SMS list. They must re-subscribe themselves. This protects fans from unwanted re-enrollment and protects you from legal liability.
</Warning>

## Row Level Security (RLS)

<Note>
  Fanaura uses **Row Level Security** at the database level to ensure data isolation between artists:

  * Each artist can only access their own fans, assets, campaigns, and settings.
  * Database queries are automatically filtered by the authenticated artist's ID.
  * Even if two artists share a fan, each artist only sees their own interaction data.
  * RLS is enforced at the database level, meaning it cannot be bypassed by application code. It is the strongest form of data isolation available in a shared database architecture.
</Note>

## Encryption

<Tabs>
  <Tab title="Data at Rest">
    Sensitive data stored in the database is encrypted:

    * **API keys**: All third-party integration credentials are encrypted before storage.
    * **OAuth tokens**: Spotify and Instagram access tokens are encrypted.
    * **Passwords**: User passwords are hashed using industry-standard algorithms (never stored in plain text).
  </Tab>

  <Tab title="Data in Transit">
    All communication between your browser and Fanaura's servers is encrypted:

    * **HTTPS/TLS**: Every request uses encrypted connections.
    * **API calls**: All calls to third-party services use encrypted connections.
  </Tab>
</Tabs>

## Session Management

Fanaura's security model includes active session management:

* **Active session tracking**: See which devices are logged into your account.
* **Device identification**: Each session shows the browser, operating system, and approximate location.
* **Session revocation**: Revoke individual sessions or all sessions at once.
* **Session heartbeat**: Sessions periodically refresh to stay active and provide accurate "last active" timestamps.

See [Security Settings](/settings/security) for full details.

## Data Export

<Info>
  On the **Complete plan**, you can export your complete fan database and engagement data: fan profiles with all fields, engagement history, campaign results, and delivery stats. Export in standard formats (CSV) for use in external tools. Data export gives you full portability -- your data is yours, and you can take it with you.
</Info>

## Third-Party Data Handling

When Fanaura connects with third-party services, data flows in both directions:

| Integration       | Data Sent                  | Data Received                   | Data Stored                    |
| ----------------- | -------------------------- | ------------------------------- | ------------------------------ |
| SMS Provider      | SMS content, phone numbers | Inbound SMS, delivery status    | Message logs, phone numbers    |
| Email Provider    | Email content, fan emails  | Delivery status, opens, clicks  | Email logs, engagement data    |
| Shopify           | None (read-only)           | Products, orders                | Product data, purchase history |
| Instagram         | DM content                 | DM messages, comments, mentions | Message logs, trigger data     |
| Spotify           | Presave commands           | Authorization tokens, metadata  | Tokens, song metadata          |
| Apple Music       | Library additions          | Authorization tokens            | Tokens                         |
| Payment Processor | Subscription data          | Payment status, invoices        | Subscription state             |

<Note>
  Fanaura only shares the minimum data necessary with each service for the integration to function.
</Note>

## Best Practices for Artists

<Tip>
  **Collect only what you need.** Just because you can collect birthday, phone number, and location does not mean you always should. For a simple presave campaign, email might be enough. For a tour campaign, adding location makes sense.
</Tip>

<Tip>
  **Be transparent with fans.** Go further than the data wrapper -- mention in your social posts why you are collecting data: "Sign up so I can send you exclusive content and tour updates." Transparency builds trust.
</Tip>

<Warning>
  **Honor opt-outs immediately.** When a fan unsubscribes or texts STOP, respect it. Fanaura handles this automatically, but make sure your team knows not to manually re-add opted-out fans.
</Warning>

<Note>
  **Secure your account.** Your Fanaura account is the gateway to your fan data. Use a strong password, monitor active sessions, and limit team access to only those who need it.
</Note>

## What Happens Next

Fanaura's privacy infrastructure works quietly in the background. You do not need to configure anything special -- consent tracking, encryption, RLS, and opt-out processing are all built in. Focus on building genuine relationships with your fans, and know that their data is protected by design.

If a fan ever requests their data or asks to be deleted, you can handle it directly from their fan profile in Fanaura. For questions about privacy compliance specific to your situation, consult with your legal team or use the Attorney role to give your counsel direct access to Activity Logs for review.