Saltar al contenido principal

Privacy & Security

Appilot is built with privacy by design. Your personal information is protected at every level, from the browser to the backend.

How your data is handled​

What Appilot captures​

  • Page structure: Form fields, labels, placeholders, field types (structural information, not your personal entries)
  • Page URL and title: To match against the organization's knowledge base
  • Your questions: What you type in the assistant chat

What Appilot does NOT capture​

  • Form values you've entered: Your actual data in form fields is not sent unless you explicitly include it in a question
  • Passwords or credentials: Never captured or transmitted
  • Browsing history: Appilot only activates when you open the panel

PII masking​

When your organization uses a third-party AI provider (for example a cloud model), Appilot automatically masks sensitive details in your message before they reach that provider. It detects and replaces patterns such as:

  • Email addresses
  • Phone numbers
  • Social security numbers
  • Credit card numbers
  • Street addresses

Each masked value is replaced with a neutral placeholder, so the provider receives your question without the sensitive detail.

When you see a "hidden for privacy" marker​

If a value in your message was masked, the assistant shows a small 🛡️ hidden for privacy marker where that value used to be, with a short note beneath the message. This is intentional and explains why part of your wording was set aside before the question was sent to the AI provider. It is also visible to your administrators when they review a conversation, so a masked value is never a silent change.

If you ever notice the assistant ignoring part of your request, check for this marker: a detail you typed may have matched a sensitive pattern and been masked.

Sovereign / on-premise deployments​

When your organization runs Appilot against its own on-premise AI model (sovereign mode), your message never leaves your organization's infrastructure. In that case there is no third party to shield, so masking is skipped entirely and the assistant works with your exact wording. You will not see "hidden for privacy" markers on these deployments.

Detection is conservative. Masking only triggers on clearly sensitive patterns: it will not hide an ordinary number such as "reply in under 40 words" or "wait 5 minutes". Only structured data (a full email, a street address with a street name, a card number) is masked.

Privacy controls​

In the extension settings, you can:

  • Enable or disable PII masking (on by default, but configurable)
  • Review what's captured: see the page context that Appilot detects
  • Control activity tracking: choose what interaction data is shared

Data isolation​

Appilot uses multi-tenant architecture:

  • Your organization's data is completely isolated from other organizations
  • Your personal conversations are private to you
  • Organization admins can see aggregated analytics but not individual chat content

Enterprise compliance​

For organizations with strict compliance needs, Appilot supports:

  • Configurable AI providers (choose where AI processing happens)
  • Data residency considerations
  • Audit-ready activity logging
  • Role-based access controls