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

# Security and your data

> Keep access narrow, protect secrets, and understand how files and resources are kept or removed.

Good security in Vecbase starts with clear access and simple habits. Give each
Agent only what it needs, then
[review that access](/administration/access-approvals) as work changes.

## Control access

Keep sensitive work in the correct workspace and file space. Give each Agent
specific access to the resources its responsibility requires.

Before adding access, ask:

1. Does this Agent need the resource for its current responsibility?
2. Is read access enough?
3. Does a person need to approve changes or deletion?
4. When should this access be removed?

## Protect secrets

Use Vecbase's [Connection](/workspace/connectors) and credential screens for
private account details. Do not place passwords, secret keys, access tokens, or
one-time codes in:

* Agent instructions;
* task messages;
* files intended for broad sharing;
* screenshots;
* support requests.

If a secret was exposed, revoke or replace it at the source, then update the
Connection.

## Understand where data stays

Different places have different lifetimes:

* the [**File Library**](/agents/files) keeps shared files until you or an
  Agent with delete access removes them;
* a [**Dedicated cloud computer**](/agents/work-environments) keeps that Agent's
  working files while the resource exists;
* a **Temporary workspace** starts fresh for a new conversation;
* task messages and delivered results remain part of the workspace history
  according to the product's current controls.

Move important shared work to the File Library. Do not rely on a temporary
working area as the only copy.

## Suspension and removal

When [billing](/workspace/billing) is suspended, work pauses first. Vecbase
does not immediately remove workspace resources. A recovery period of at least
seven days begins, with notifications to the team before automatic cleanup can
complete if billing is not restored.

Manual deletion is different. Deleting a file, file space, Agent, or workspace
can be permanent. Read the confirmation carefully and move anything the team
needs before approving it.

## A simple safety checklist

* review Agent access after a role or project changes;
* keep delete access uncommon;
* pause unused [Scheduled Tasks](/agents/scheduling) and cloud computers;
* store shared results in the right file space;
* never share secrets in chat or support;
* ask for approval before sensitive or hard-to-reverse work.

If you believe access or data has been exposed, stop the affected task or
Connection and [contact support](/workspace/support) promptly.