Access control
Protected business information and administrative actions are available only to authorised team members.
Security and privacy
Your business stays in control.
Control who can access protected information, what MAY can use as business knowledge, which actions can run, and how integrations are connected.
Business boundaries
Your data stays tied to your business.
MAY is designed so business information, customer context and integrations are handled within the right account and access context.
Your businessYour information and controls
KnowledgeApproved sources
CustomersCustomer context
IntegrationsProtected credentials
ActionsControlled workflows
separate business context
Other businesses
Not part of your business data or integration context.
Security principles
Clear controls around information and action.
The goal is straightforward: keep business information deliberate, access limited to the right people, credentials protected and automation understandable.
Approved business information
MAY is designed to answer from business-approved knowledge and structured facts rather than treating generic model memory as business truth.
Credential safety
Integration credentials belong in protected configuration, not public code, customer-facing documents or assistant instructions.
Frequently asked
Direct answers for a security review.
For production use, these product principles should be read together with the applicable contractual, privacy and data-protection documentation.
What information does MAY use to answer business questions?
MAY is designed to use approved knowledge and structured business facts when those sources are configured.
How is business data kept separate?
Business data access and integrations are resolved within the relevant business account and authorised user context.
Where should integration credentials be stored?
Credentials should be kept in protected configuration rather than public website code, customer documents or assistant prompts.
Can a person take over a customer conversation?
Yes. Customer channels can move from AI assistance to human handling while preserving useful conversation context for the team.
Security documentation