> ## 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 Classification Guidance

> Classify information before placing it into Starfire AI chats, Projects, Knowledge, artifacts, organizations, or developer integrations.

# Data classification guidance

Before placing information into Starfire, decide what kind of data it is and whether the selected context is appropriate for it.

## Practical categories

### Public

Information intended for unrestricted public distribution.

Examples: published documentation, public marketing copy, open-source code.

### Internal

Business information intended for authorized team use but not necessarily public.

Examples: internal procedures, draft plans, non-public project notes.

### Confidential

Information whose exposure could cause business, customer, contractual, or privacy impact.

Examples: unpublished product plans, private source code, customer records, sensitive financial information.

### Secret / credential

Information that directly grants access.

Examples: passwords, API keys, tokens, private keys.

Do not place secrets into normal Starfire AI context.

## Choose the context

| Data type         | Appropriate Starfire use                                               |
| ----------------- | ---------------------------------------------------------------------- |
| Public            | Normal Chat/Projects/Knowledge as needed                               |
| Internal          | Authorized personal/organization context                               |
| Confidential      | Only when authorized and necessary; use narrow project/resource access |
| Secret/credential | Dedicated secret/integration storage, not prompts/Knowledge            |

## Durable vs temporary context

A confidential file attached to one chat and the same file indexed into organization Knowledge have different reuse and access implications.

Use the narrowest lifetime and audience required by the task.

## Organization policy

Organizations can apply their own data-handling rules in addition to Starfire product permissions. Team policy should decide which categories are permitted in Projects, Knowledge, integrations, or AI workflows.

## Developer integrations

When an API or webhook sends data from Starfire into another system, the receiving system's security and retention rules matter too.

<Note>
  This page provides product-usage guidance, not a replacement for your organization's legal, regulatory, contractual, or formal information-security classification program.
</Note>