---
title: "Privacy and data rights"
description: "Framework defaults and operator responsibilities for GDPR and CCPA data requests."
---

# Privacy and data rights

Agent-Native includes a privacy-request surface in the default Account settings. It gives a signed-in person a clear way to request a copy of their personal data or request deletion of it.

This is an implementation baseline, not legal advice or a compliance certification. The organization operating an app decides whether it is a controller, business, processor, or service provider, and must publish the notices and processes that fit its deployment.

## What users can do

Open **Settings > Account > Security** and use its **Your data** group to:

- Request a copy of personal data for access or portability review.
- Request deletion of personal data for erasure review.
- Correct account details through the existing profile and email controls.

Requests are durable, idempotent, and audited. The request action stores only the request type, status, and timestamp. It does not return a data dump, accept another person's email or user ID, or delete data immediately.

## What agents cannot do

Privacy requests are submitted through the Account settings UI. The `request-privacy-right` action is authenticated, hidden from in-app agent tools and MCP/A2A discovery, blocked from the sandboxed tools bridge, and authorized only for the frontend caller.

The core `offboard-member` action has the same UI-only boundary. Offboarding a member is an organization operation that transfers owned rows and revokes access; it is not account erasure. Organization deletion also remains behind the existing owner-only UI confirmation.

Human approval prompts are not a security boundary. For a custom app action that can erase data, revoke identity, change membership, or modify authentication, use an explicit UI-only action boundary and derive identity from the verified request context.

## Operator fulfillment

The framework records the request. The deployment operator must own the queue and:

1. Verify the requester's identity and determine the applicable organization and legal scope.
2. For access or portability, collect the data the deployment controls and deliver it through a private, access-controlled channel.
3. For deletion, delete or anonymize app rows and private blobs, revoke sessions and credentials where appropriate, and coordinate cleanup with connected providers and processors.
4. Apply the deployment's retention schedule to backups, security logs, audit history, fraud prevention, and other records that may need a documented exception.
5. Record completion, partial fulfillment, or the reason a request is blocked, and communicate the result to the requester.

Do not claim that a request is complete because one organization row or one setting was removed. Hosted providers, uploaded files, connected services, caches, backups, and immutable audit records can have separate retention and deletion paths.

## Default privacy posture

New shareable resources are private by default. The framework's browser analytics defaults keep DOM and network autocapture off, and session replay is opt-in and signed-in-only by default when configured. These defaults reduce collection; they do not replace a privacy notice, lawful-basis analysis, retention policy, or consent and opt-out controls required by a particular deployment.

If a deployment sells or shares personal information, it must provide the applicable CCPA opt-out and Global Privacy Control handling. The framework does not create a sale or sharing program for an app.

## Deployment checklist

- Publish a privacy notice that names the data categories, purposes, recipients, retention, rights, and contact channel.
- Decide and document lawful bases, consent requirements, sensitive-data restrictions, and age-related requirements.
- Assign an owner and response workflow for access, correction, deletion, portability, objection, and opt-out requests.
- Map every app table, private blob, analytics provider, connected service, email system, cache, log, backup, and subprocessor involved in fulfillment.
- Define verification, response deadlines, retention exceptions, deletion evidence, and appeal handling.
- Keep custom high-consequence actions UI-only and test that agent, MCP, A2A, CLI, HTTP, and tools-iframe callers cannot invoke them.

## References

- [GDPR text](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng/)
- [European Commission: handling individual requests](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/dealing-requests-individuals_en)
- [California Attorney General: CCPA](https://www.oag.ca.gov/privacy/ccpa)
- [California Attorney General: CCPA regulations](https://www.oag.ca.gov/privacy/ccpa/regs)
- [Hosted Agent-Native privacy policy](/privacy)