Security & Trust
The Assistant starts conservatively: company-specific answers are grounded in information the organization has made available to the service. A new pilot begins with public information from the company-authorized website source. Private documents and business applications are added only by explicit company action.
What the Free Pilot accesses
Official public websiteUseful public pages, services, FAQs, products, contact details and other approved public content.
Company communication channelThe company supplies its own Telegram/WhatsApp credentials only when it chooses to connect that channel.
No automatic private accessInternal documents, databases, customer records, ERP/CRM systems and staff systems are not accessed automatically.
Explicit extensions laterThe organization can later add documents, live applications, additional channels and human-support systems.
How company answers are controlled
Evidence before claimsCompany-specific facts require available company evidence. General model memory is not treated as the authority for prices, stock, policies, dates or account status.
Live facts use live sourcesWhen a connected live source exists, changing facts such as inventory or order status should come from that source rather than stale knowledge.
Sources remain visibleGrounded answers retain source URLs or document citation metadata when available.
Humans remain availableWhen reliable evidence is insufficient or a human decision is required, the Assistant offers a controlled human handoff instead of guessing.
Administrator identity and recovery
Verified administrator emailHosted deployments can require email verification before intelligence is activated, reducing unauthorized company setup.
One-time recovery linksA verified administrator can recover access without exposing or reusing the previous administrator key. Recovery rotates the key.
Hash-only administrator keysCompany administrator and integration API keys are shown once and stored as hashes rather than recoverable plaintext.
Rate-limited public entry pointsSignup, authentication, recovery and API traffic have bounded request rates in the one-click deployment. Multi-replica deployments should also enforce shared upstream limits.
Credentials, billing and tenant controls
Channel credentials, Qwen credentials and downstream application secrets are application-encrypted before storage and are not placed in Qwen prompts. Connection secrets can be rotated or disconnected independently. Organization records, evidence and sessions are tenant-scoped by the Gateway.
When hosted billing is enabled, the payment provider receives only billing/customer identifiers and the selected commercial plan needed for payment processing. Company website knowledge, uploaded documents, customer conversations, bot tokens and business-application credentials are not used as billing payloads.
Enterprise deployments should additionally use HTTPS, host-level backups, restricted administrator access, monitored updates, protected metrics/alerts and the production acceptance checklist included with the release.
Free Pilot terms shown up front
The pilot duration and usage limits are displayed before activation. The default package is configured for a 14-day pilot, with no credit card and no automatic charge. Paid continuation is a separate explicit business decision.