AppsSecurity & Compliance

Security & Compliance · topic

Data protection

Row rules decide which records each person sees, column rules mask or hide fields, per-company keys encrypt sensitive data, and personal data can be stripped before any AI model reads it.

Protect data in Autessa: row-level security, column masking, per-company AES-256 encryption, PII and PHI stripping for AI, and placeholders for card numbers.

Start free
AutessaDB role · Regional managerstable: accountsSample
ROW RULE
region IN $CURRENT_USER_TEAMS
writeCheck: SAME_AS_READ
Assigned toTeam · West, Team · East
Closed by default (rlsEnforced)On
Default role for new granteesRegional managers

Ana · team West

312 rows

No matching role

0 rows

How it fits together

How does data protection work in Autessa?

Data protection in Autessa works at every grain. The company boundary and per-company AES-256 keys separate you from everyone else; row and column rules separate people inside your company; and stripping and placeholders keep personal data out of AI models and transcripts.

IN THIS AREA

  • Row-level security for people, apps and API keys
  • Column masking: redact, last four or hash
  • Per-company AES-256 encryption keys
  • PII and PHI stripping before any model

In this area

Every data protection feature

01Row-level security (RLS)Autessa includes row-level security: AutessaDB roles filter which rows each person, app visitor or API key sees, with placeholders like $CURRENT_USER_TEAMS so one rule works for everyone.→02Column-level security and maskingAutessa includes column-level security: each role sees a column in full, masked (redacted, last four or a stable hash) or not at all, and masked columns can be stored encrypted.→03Tenant isolation and encryptionEvery Autessa company is cryptographically separated: sensitive data is encrypted at rest with AES-256 using keys unique to your company, inside storage that is itself encrypted.→04PII and PHI stripping for AIWith PII and PHI stripping on, personal and health data in every prompt becomes a numbered placeholder such as [SSN_1] before it reaches any model, and the real values return in the answer.→05Sensitive data in conversationsTurn on Protect sensitive data for an agent and card numbers, bank details and Social Security numbers become placeholders the AI works with, while allowed tools can still use the real value.→

Other areas

The rest of Autessa Security & Compliance

FAQ

Data protection: questions

Does row-level security apply to AI agents?

Yes. Every request, whether from a person, tool, agent, script, app or API key, is evaluated against the roles of whoever it acts as.

Can I show only the last four digits of a field?

Yes. Set the column to MASKED with LAST_FOUR for that role.

Is my data encrypted at rest?

Yes. Sensitive data is encrypted with AES-256 using keys unique to your company, and all storage is also encrypted at rest at the infrastructure level.

Does stripping work with my own OpenAI or Anthropic key?

Yes. It applies whether the model is yours or Autessa’s.

Does the AI ever see the full card number?

No. It works with the placeholder. Only the tools you allow receive the real value.

Data protection, built in

Row rules decide which records each person sees, column rules mask or hide fields, per-company keys encrypt sensitive data, and personal data can be stripped before any AI model reads it.

Start free

Reports, policies and questionnaires live on the Autessa Trust Center.

100% customizable, code and all

Make Autessa Security & Compliance fully your own.

Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.

Start free and make it yours