Security & Trust

Effective Date: July 9, 2026

Last Updated: July 9, 2026

Summary

BotStacks is designed to help small and mid-sized businesses create, manage, and deploy AI assistants with practical security controls.

We know customers may use BotStacks to store knowledge sources, configure assistants, process chatbot conversations, and deploy AI experiences on websites. Protecting that information is important to us.

This page summarizes BotStacks’ current security approach. As BotStacks grows, we will continue improving our security practices, infrastructure, monitoring, and compliance readiness.

1. Platform Security

BotStacks uses cloud-based infrastructure to operate the platform, host customer workspaces, process assistant configurations, and support chatbot deployments.

Our security approach includes:

  • Secure cloud infrastructure

  • Encrypted connections where supported

  • Account-based access controls

  • Workspace-level organization

  • Protected API keys and platform credentials

  • Monitoring and logging

  • Backups and recovery planning

  • Limited internal access to customer data

  • Use of trusted infrastructure and service providers

2. Access Controls

BotStacks uses access controls to help protect accounts and workspaces.

Customers are responsible for:

  • Using strong passwords

  • Keeping login credentials secure

  • Managing invited users

  • Removing users who no longer need access

  • Protecting API keys and embed credentials

  • Reviewing workspace permissions

BotStacks may add or improve role-based access, two-factor authentication, and other access controls as the platform evolves.

3. Customer Data

BotStacks may process customer data such as:

  • Uploaded files

  • Website URLs

  • Website content

  • Knowledge sources

  • Assistant prompts and instructions

  • Assistant configurations

  • Chatbot conversations

  • Chat transcripts

  • Retrieved knowledge snippets

  • Usage and analytics data

BotStacks uses this data to provide the platform and power customer-configured assistants.

4. Knowledge Sources and AI Retrieval

BotStacks may process customer knowledge sources so assistants can retrieve relevant information during conversations.

This may include indexing, chunking, embedding, storing, and retrieving content from customer-provided sources.

Customers are responsible for ensuring they have the rights to upload, connect, crawl, or process the content they add to BotStacks.

5. Third-Party Providers

BotStacks may use third-party providers for infrastructure, AI model processing, vector databases, payments, monitoring, analytics, support, email, and other services.

Depending on customer configuration, chatbot conversations, prompts, retrieved content, and assistant context may be processed by third-party providers as needed to provide the service.

BotStacks aims to use reputable providers and limit provider access to what is needed for the service.

6. Data Protection Practices

BotStacks’ security practices may include:

  • Encryption in transit where supported

  • Access limitations for internal team members

  • Infrastructure monitoring

  • Error and performance monitoring

  • Backup practices

  • Security review of key vendors

  • Separation of customer workspaces

  • Administrative controls

  • Review of suspicious or abusive activity

No online service can guarantee absolute security, but BotStacks works to reduce risk and improve protections over time.

7. Responsible Use of AI Assistants

Customers should test and monitor assistants before deploying them publicly.

Customers should avoid configuring assistants to collect sensitive personal information unless they have the required legal basis, consent, and safeguards.

Customers should not use BotStacks assistants as the sole basis for high-impact decisions involving legal, medical, financial, employment, housing, insurance, safety, or similar regulated matters.

8. Incident Response

If BotStacks becomes aware of a security incident affecting customer data, we will take reasonable steps to investigate, contain, and address the issue.

Where appropriate, BotStacks will notify affected customers in accordance with applicable obligations.

9. Security Roadmap

As BotStacks grows, we may continue improving security through areas such as:

  • Stronger role-based access controls

  • Two-factor authentication

  • Expanded audit logs

  • Improved backup and recovery processes

  • More detailed vendor review

  • Improved API security

  • Rate limiting and abuse prevention

  • Security documentation for larger customers

  • Compliance readiness as customer needs mature

10. Reporting Security Issues

If you believe you have found a security issue involving BotStacks, contact [email protected] or use our security report page at /security-report.

Please include:

  • A description of the issue

  • Steps to reproduce, if available

  • Affected URLs or accounts, if known

  • Your contact information

BotStacks asks that security researchers act in good faith, avoid accessing or modifying customer data, and give us a reasonable opportunity to investigate and resolve reported issues.

11. Contact

Security questions may be sent to:

[email protected]

BotStacks Inc., 5150 Mae Anne Ave, Suite 550, Reno, NV 89523, United States

BotStacks