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

# Data & Privacy

> Understand data-handling considerations when using Starfire AI.

# Data & privacy

Starfire AI can process conversations, files, project material, Knowledge sources, research sources, developer requests, and organization-owned resources. Use the platform with the same data-discipline you would apply to any hosted AI or SaaS system.

## Only provide what the task needs

Before sending content to Starfire, consider whether the task actually requires:

* passwords or access tokens
* private keys
* payment details
* confidential customer information
* employee records
* regulated data
* unpublished intellectual property
* proprietary source code

Remove or redact information that is not necessary.

## Context has scope

Data can exist in different contexts:

* one conversation
* a personal project
* an organization project
* persistent Knowledge
* an artifact
* developer/API usage

Those contexts can have different ownership, retention, and sharing rules.

## Organization data

Joining an organization does not automatically mean every member should access every project, file, Knowledge source, or developer resource. Access should follow roles, policies, and resource permissions.

## Persistent Knowledge

Adding a source to Knowledge is different from attaching it to a one-time chat. Knowledge is intended for reuse and retrieval over time, so make sure the source belongs in that durable context.

## Logs and operational metadata

Starfire needs operational metadata to support health, usage, billing, diagnostics, and security. Operational logging should avoid creating unnecessary permanent copies of sensitive message bodies or file content.

## Administrators

Control Center can expose account, usage, security, billing, run, and storage metadata to authorized operators. Administrative access does not automatically imply unrestricted access to private content.

## Developer integrations

An external integration can receive data or events through APIs and webhooks. Once data leaves Starfire for a system you control, that system's own retention and security practices matter too.

## Formal policies

This documentation explains product behavior and recommended usage practices. It is not a replacement for Starfire AI's formal privacy policy, terms, security documentation, or contractual data-processing commitments where those documents apply.

<Warning>
  Do not use prompts, custom-agent instructions, workflow memory, or Knowledge as a credential vault. Secrets require dedicated secure storage and access controls.
</Warning>