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

# Security & privacy

> How your data is protected, who can reach it, and your obligations as the data controller.

Recepta.ai holds customer personal data on your behalf — names, phone numbers, addresses, call recordings, and transcripts. This page covers how that's protected and what remains your responsibility.

## Access control

Access is layered, so you can grant exactly what a person or system needs:

<AccordionGroup>
  <Accordion title="Workspace isolation" icon="building-lock">
    Every request — dashboard, API, or MCP — is scoped to one workspace. Data never crosses workspace boundaries.
  </Accordion>

  <Accordion title="User roles" icon="users-gear">
    Team members get standard or custom roles controlling what they can see and change. Recording and transcript access can be granted separately from general call access. See [Team & roles](/account/team-and-roles).
  </Accordion>

  <Accordion title="API key permissions" icon="key">
    Keys carry granular scopes — `calls:read` without `calls:recording`, for example. Give each integration its own key with the minimum it needs. See [Authentication](/api-reference/authentication).
  </Accordion>

  <Accordion title="Location scoping" icon="location-dot">
    Multi-location workspaces can restrict staff to their own branch's data. See [Locations](/account/locations).
  </Accordion>
</AccordionGroup>

## In transit and at rest

All API and dashboard traffic runs over HTTPS; plain HTTP is not accepted. API keys are stored hashed, not in plaintext, and are shown to you once at creation. Webhook payloads are signed so your endpoint can verify they came from Recepta.ai — see [Webhooks](/api-reference/webhooks).

## What you're responsible for

You are the data controller for your customers' information. Recepta.ai processes it on your instructions.

<Warning>
  Recording law, consent, and marketing rules are yours to comply with. See [Recording & consent](/phone/recording-and-consent), [SMS](/channels/sms), and [A2P 10DLC](/phone/a2p-10dlc). Recepta.ai gives you the controls; it can't make the calls lawful for you.
</Warning>

Practical obligations:

<Steps>
  <Step title="Disclose recording">
    Announce it on every call if you record. Assume the strictest applicable rule.
  </Step>

  <Step title="Capture and keep consent">
    For calling, texting, and emailing. Keep a record of where and when it was given — that's what a carrier or regulator asks for.
  </Step>

  <Step title="Honor opt-outs and deletion requests">
    Suppression is automatic; a request to delete a record is something you action.
  </Step>

  <Step title="Publish terms and a privacy policy">
    Required by carriers for A2P approval, by payment providers, and by privacy law.
  </Step>

  <Step title="Manage access hygiene">
    Remove departed staff the same day, rotate API keys they created, and re-authorize integrations they owned.
  </Step>
</Steps>

## Deletion and export

Contacts and call records can be deleted from the dashboard and over the API. Deletion is not reversible — restrict the permission accordingly.

If a customer exercises a right to access or erasure, or you need a bulk export for migration, contact [info@recepta.ai](mailto:info@recepta.ai) with the specifics.

## Subprocessors

Recepta.ai relies on third-party providers for telephony, AI model inference, payments, and hosting. For the current subprocessor list, a DPA, or a security questionnaire, contact [info@recepta.ai](mailto:info@recepta.ai).

## Reporting a vulnerability

Email [info@recepta.ai](mailto:info@recepta.ai) with reproduction steps. Please don't test against other customers' workspaces or use live customer data in a proof of concept.