AI.Support built for Magento
Iniciar sesión Solicitar demo Prueba gratuita

Seguridad / Confianza

Build buying confidence with clear security, privacy, and billing signals.

For many prospects, trust is not one section. It is the combined effect of contact visibility, policy clarity, billing predictability, and responsible AI positioning.

Public support contacts Policy visibility Human control
Visible support, billing, and legal routes
Aligned site copy and Stripe checkout expectations
Responsible AI outputs with escalation controls

Trust signals

What prospects and customers should be able to verify quickly.

These details reduce friction before checkout and confusion after billing begins.

Company identity

AI.Support B.V., Herengracht 420, 1017 BZ Amsterdam, The Netherlands

Statement descriptor target

AISUPPORT

Verification controls

Verified customer sessions can require email one-time passcodes and, when enabled, optional phone verification before protected account or order help is shown.

Scoped personalization

When personalization is enabled, the product can rely on minimized customer or order projections instead of exposing full raw store records in replies.

Legal links

Terms, Privacy Policy, and Refund Policy are public and linked in checkout-adjacent flows.

Responsible AI

The AI position is practical and controlled.

That is better for merchants, customers, and internal reviewers.

Approved sources first

Support and policy answers should be grounded in merchant-controlled content.

Verified customer sessions

Protected account-aware or order-aware answers can stay locked until the customer completes the supported verification flow.

Human handoff

The team stays in control when the request is sensitive, policy-heavy, or uncertain.

Plan and role controls

Verification channels, workflow automation, analytics depth, and other runtime capabilities can vary by plan, add-on, and user role.

Use public trust content to reduce support friction and billing disputes later.

The Security / Trust page should support the rest of the site, not live as a disconnected compliance token.