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

# FAQ

> Answers to common questions about CREAO.

## Getting Started

<AccordionGroup>
  <Accordion title="Do I need to create a workspace to get started?">
    No. Sign in at [agent.creao.ai](https://agent.creao.ai) and start chatting immediately. Workspaces are an optional way to organize your agents and files as your usage grows.
  </Accordion>

  <Accordion title="Is there a free plan?">
    Yes. Sign up for free and start using the super agent right away. All features
    are available on every plan — plans differ only in the number of credits
    (usage limits) included.
  </Accordion>

  <Accordion title="What can I ask the super agent to do?">
    Anything you'd ask a technical teammate: generate a web app, analyze a dataset, draft a report, scrape a website, create charts, send emails, build PDFs, automate workflows, and more. The super agent runs code in a full Linux sandbox, so it can install packages, call APIs, and produce real files — not just text responses.
  </Accordion>
</AccordionGroup>

## Agents

<AccordionGroup>
  <Accordion title="What is an agent?">
    An agent is a reusable workflow built from a successful chat session. Instead of re-prompting the same task, you save it as an agent with structured input fields. Anyone on your team can run it with different inputs, and every run is tracked with version history.
  </Accordion>

  <Accordion title="How do I create an agent?">
    After a successful chat session, click **Create Agent** in the chat toolbar.
    The super agent analyzes the conversation and extracts the workflow into a
    reusable agent with a structured input form, a skill definition, and version
    control.
  </Accordion>

  <Accordion title="Can I schedule an agent to run automatically?">
    Yes. Open any agent, go to the **Schedule** tab, and configure a recurring schedule — daily, weekly, monthly, or a custom cron expression. Scheduled runs execute autonomously and consume credits like manual runs.
  </Accordion>
</AccordionGroup>

## Skills and Connectors

<AccordionGroup>
  <Accordion title="What is the difference between a skill and a connector?">
    **Skills** are instruction packages that teach the super agent *how* to perform a task (like a recipe). **Connectors** give the super agent *access* to external services via MCP (Model Context Protocol) — Gmail, Slack, Google Sheets, GitHub, and more. Skills define behavior; connectors provide integrations.
  </Accordion>

  <Accordion title="Can I create my own skills?">
    Yes, three ways: install from a public GitHub repo URL, upload a ZIP file
    containing a SKILL.md, or ask the super agent to create one directly in chat.
    Custom skills use a simple markdown format with YAML frontmatter.
  </Accordion>

  <Accordion title="Which connectors are available?">
    CREAO supports 27 connectors including Gmail, Google Calendar, Google Sheets,
    Google Docs, Google Drive, Google Tasks, Google Ads, Google Analytics, Google
    Search Console, Outlook, Microsoft Teams, Asana, Linear, Notion, Slack,
    Discord, Facebook Ads, Reddit, YouTube, GitHub, Semrush, Perplexity,
    Firecrawl, X, Telegram, Shopify, and eBay. More are added regularly — check
    the [Skills and Connectors](/features/skills-and-connectors) page for the
    latest list.
  </Accordion>

  <Accordion title="What can a connector access in my account?">
    A connector can access only the data allowed by the permissions (scopes) you
    approve with that provider. Access is scoped to the connected account and the
    connector's authorized capabilities. See [Connector
    Security](/trust-and-safety/security#connector-security) for an overview.
  </Accordion>

  <Accordion title="Can I revoke connector access?">
    Yes. You can disconnect a connector in CREAO at any time. For complete
    revocation, you can also remove CREAO app access from the provider's own
    security settings.
  </Accordion>

  <Accordion title="What does CREAO read from a connected cloud account (AWS), and how is that data used?">
    When you connect your own AWS account (Bring Your Own Cloud), CREAO does not
    store long-lived cloud credentials. You deploy a CREAO-provided CloudFormation
    stack in your account that creates a cross-account IAM role; CREAO assumes it
    on demand using short-lived STS credentials gated by a per-connection
    ExternalId. The agent reads only what the tool you triggered returns —
    read-only CloudWatch logs, metrics, and alarm states for debugging. Those tool
    results flow into the agent's context, which means they are sent to your
    selected LLM provider as part of the conversation (the same as other connector
    data); CREAO does not bulk-export or continuously ingest your cloud account.
    You can disconnect at any time (which also deletes the stored connection), or
    delete the CloudFormation stack in your own account. See
    [Privacy](/trust-and-safety/privacy) and [Cross-Account Cloud Access
    (BYOC)](/trust-and-safety/security) for details.
  </Accordion>

  <Accordion title="Do built-in skills send data to new third parties?">
    Built-in skills are instruction packages, not standalone third-party services.
    Data is shared externally only when required by model providers or connected
    tools used during execution. See [Skill
    Security](/trust-and-safety/security#skill-security).
  </Accordion>

  <Accordion title="Are custom skills and built-in skills treated the same?">
    They run under the same platform security boundaries, but their trust model differs. Built-in skills are curated by CREAO, while custom skills are user-provided instructions and should be reviewed before enabling.
  </Accordion>
</AccordionGroup>

## Data Privacy

<AccordionGroup>
  <Accordion title="Is my data used to train AI models?">
    CREAO does not train its own models on your conversations, files, or data. Anthropic, OpenAI, Google, MiniMax, Z.AI, xAI, and BytePlus are accessed under API agreements or provider API terms that prohibit training use. MiniMax and Z.AI are reached via OpenRouter, whose API terms prohibit training use. Fugu Ultra via Sakana AI is a qualified exception while governed by Sakana's public Fugu terms: submitted content may be used for Sakana training or improvement unless an opt-out or separate no-training/DPA arrangement is in place, so do not use Fugu Ultra for regulated, sensitive, confidential, or personal data without that confirmation.
  </Accordion>

  <Accordion title="Where is my data stored?">
    Data is stored in cloud infrastructure and protected with encryption in
    transit and at rest. Execution runs in isolated sandbox environments.
  </Accordion>

  <Accordion title="Can I delete my data?">
    Yes. You can delete conversations, files, and memory entries, and request
    account deletion. A limited audit record of a deletion request itself may be
    retained where required for legal, compliance, and security purposes, as
    described in the [Privacy](/trust-and-safety/privacy) policy.
  </Accordion>

  <Accordion title="Do you support GDPR/CCPA workflows?">
    CREAO is designed around core privacy rights including access/export and
    deletion. Enterprise customers can request a DPA. See
    [Privacy](/trust-and-safety/privacy) for details.
  </Accordion>

  <Accordion title="How are API keys and secrets protected?">
    Secrets are encrypted at rest and injected at runtime for execution. Values are not shown in plain text after creation, except through whitelisted and logged campaign audit exports used by authorized admins to verify trading activity.
  </Accordion>
</AccordionGroup>

## Sandbox and Environment

<AccordionGroup>
  <Accordion title="What happens to my sandbox between messages?">
    Your sandbox stays active for the duration of the conversation. Installed packages, created files, and running processes persist between messages. After 30 minutes of inactivity, the sandbox pauses automatically — everything is saved and resumes in about one second.
  </Accordion>

  <Accordion title="Is each chat thread isolated?">
    Yes. Every chat thread gets its own sandbox. Work done in one thread never
    affects another. Agent runs also get isolated sandboxes, created from the
    agent's saved environment snapshot.
  </Accordion>

  <Accordion title="Can I use my own API keys in the sandbox?">
    Yes. Add your API keys as **Secrets** from the Secrets page. They're encrypted at rest and injected into the sandbox as environment variables (`process.env.YOUR_KEY`). The super agent can use them in code execution.
  </Accordion>
</AccordionGroup>

## Memory and Context

<AccordionGroup>
  <Accordion title="Does the super agent remember things across conversations?">
    Yes. **Memory** is cross-thread — when the super agent learns a preference, fact, or decision, it saves it and recalls it in future conversations. You can view, search, and delete memories from the Memory page.
  </Accordion>

  <Accordion title="What is the difference between memory and thread notes?">
    **Memory** persists across all conversations indefinitely — use it for durable
    facts like preferences and decisions. **Thread notes** are scoped to a single
    conversation and help the super agent maintain context during long sessions.
  </Accordion>

  <Accordion title="What is Dream?">
    **Dream** is an automatic profiling feature that consolidates your conversation history into a concise portrait of who you are — your role, preferences, working style, and recent decisions. Like the brain during sleep, Dream replays your past conversations offline and distills patterns into a structured profile. This profile is injected into every new conversation so the super agent already knows you from the first message. You can view your Dream profile, trigger a manual regeneration, and browse previous versions from the **Memory → Dream** tab.
  </Accordion>
</AccordionGroup>

## Pricing and Limits

<AccordionGroup>
  <Accordion title="What plans are available?">
    CREAO offers four plans. Every feature works on every plan — plans differ in the credits included, the support level, and access to premium models (the top-tier Claude models require a paid plan).

    | Plan         | Price (monthly) | Price (annual) | Monthly credits | Daily bonus | Support   |
    | ------------ | --------------- | -------------- | --------------- | ----------- | --------- |
    | **Free**     | \$0             | \$0            | 30 one-time     | 5 / day     | Community |
    | **Pro**      | \$20/mo         | \$16/mo        | 200 / month     | 5 / day     | Community |
    | **Pro Plus** | \$50/mo         | \$40/mo        | 600 / month     | 5 / day     | Priority  |
    | **Max**      | \$150/mo        | \$120/mo       | 2,000 / month   | 5 / day     | Dedicated |

    The Free plan requires no credit card. Every plan includes the full AI super agent — memory, code execution, web search, custom agents, scheduled runs, all connectors, and built-in, custom, and open-source skills; paid plans add more credits, higher support levels, and access to premium models.
  </Accordion>

  <Accordion title="Are any features locked behind a paid plan?">
    Functionality is the same on every plan, including the free tier — chat,
    memory, skills, connectors, scheduled runs, custom agents, and the **API
    Trigger** (programmatic agent runs via API keys) all work everywhere and run on
    credits from your balance. The one paid distinction is **premium models**: the
    top-tier Claude Opus models and Fugu Ultra require a paid plan.
    See [Models](/features/models).
  </Accordion>

  <Accordion title="Can I buy additional credits?">
    Yes. You can purchase credit packs at \$0.15 per credit from the pricing page,
    on top of your plan's monthly allocation.
  </Accordion>

  <Accordion title="Which AI models can I use?">
    CREAO supports multiple models including Claude (Opus, Sonnet, Haiku), Gemini, GPT variants, and Fugu Ultra. Generation-focused models include Veo (video) and BytePlus Seedance / Seedream (video and image). You can select your preferred model from the model selector in the chat interface.
  </Accordion>
</AccordionGroup>

## Data Privacy

<AccordionGroup>
  <Accordion title="Is my data used to train AI models?">
    CREAO does not train its own models on your conversations, files, or data. Anthropic, OpenAI, Google, MiniMax, Z.AI, xAI, and BytePlus are accessed via API agreements or provider API terms that prohibit use of your data for model training. MiniMax and Z.AI are reached via OpenRouter, whose API terms prohibit training use. Providers may retain data briefly for abuse monitoring and safety per their terms, but not for training on those paths. Fugu Ultra via Sakana AI is a qualified exception while governed by Sakana's public Fugu terms: submitted content may be used for Sakana training or improvement unless an opt-out or separate no-training/DPA arrangement is in place.
  </Accordion>

  <Accordion title="Where is my data stored?">
    All data is stored on cloud infrastructure in the United States. Data is
    encrypted at rest using AES-256 encryption and in transit using TLS 1.2+. Each
    chat thread runs in an isolated sandbox that is destroyed after the session
    ends.
  </Accordion>

  <Accordion title="Can I delete my data?">
    Yes. You can delete individual conversations, files, and memory entries at any
    time from the respective pages. To delete your account and its associated
    data, go to your account settings. Account deletion is processed within 30
    days. A limited audit record of the deletion request itself (such as request
    metadata, an email snapshot, and any administrator handling notes) may be
    retained afterward where required for legal, compliance, and security
    purposes, as described in the [Privacy](/trust-and-safety/privacy) policy.
  </Accordion>

  <Accordion title="Is CREAO GDPR and CCPA compliant?">
    CREAO is designed with GDPR and CCPA principles in mind. You have the right to
    access, export, and delete your data. We collect only the minimum data
    necessary to provide the service and do not sell your personal information.
    Enterprise customers can request a Data Processing Agreement (DPA). See the
    [Privacy](/trust-and-safety/privacy) page for full details.
  </Accordion>

  <Accordion title="How are my API keys and secrets protected?">
    Secrets are encrypted at rest and managed via a dedicated secrets store. They
    are injected into your sandbox as environment variables at runtime and are
    never logged, displayed in the UI after creation, or stored in plain text.
  </Accordion>

  <Accordion title="Who can see my conversations?">
    Only you can see your conversations by default. If you use the **Share** feature, a read-only public link is generated — anyone with the link can view that specific thread and download any files or artifacts within it. Shared links can be revoked at any time. Team members in a shared workspace can see workspace-scoped agents and files, but not your private conversations.
  </Accordion>
</AccordionGroup>

## Files and Data

<AccordionGroup>
  <Accordion title="What file types can the super agent generate?">
    HTML pages, PDFs, SVGs, spreadsheets (XLSX, CSV), images, code files, documents, and more. Generated files appear in the artifact preview panel during chat and are saved to your Files page automatically.
  </Accordion>

  <Accordion title="Can I upload files for the super agent to work with?">
    Yes. Drag and drop files into the chat input or click the attachment icon. Supported types include images (PNG, JPG, GIF, WebP), documents (PDF, TXT, CSV), and code files (HTML, CSS, JS, Python, etc.).
  </Accordion>
</AccordionGroup>