AI Agent
Privacy & Security Policy
Overview
BioFuze AI is a software that provides a secure, private and white labeled interface for building and selling custom AI agents.
​
The following information will go through the details of BioFuze AI's Data Privacy and Security and the differences in each subscription plan/ tier.
​
BioFuze AI Platform Security Details
At BioFuze AI, we prioritize the safety and confidentiality of your data. Here are the key security measures we implement to ensure a robust and secure platform:
​​
1. Secure Hosting
-
Our platform is hosted securely on DigitalOcean, a trusted provider known for its advanced infrastructure and stringent security protocols.
2. Two-Factor Authentication (2FA)
-
To enhance account login security, we enforce the use of two-factor authentication (2FA), adding an extra layer of protection against unauthorized access.
3. Cloudflare Protection
-
We leverage Cloudflare services to protect our platform against DDoS attacks and ensure secure data transmission.
4. 256-Bit Encrypted Database
-
Our database is secured with 256-bit encryption, providing a high level of security for stored data.
5. GDPR-Compliant Data Management
-
Conversation data is managed in full compliance with the General Data Protection Regulation (GDPR), reflecting our and commitment to data privacy and user rights.
6. Secure API Connections
-
Specific query data is passed to OpenAI via secure API connections, maintaining the highest level of security during data transmission.​
Types Of Data
When using the chat interface, the following types of data are entered by the End Users:
-
Email: Collected only when the user logs in to authenticate. If Google Auth or External Authentication is used, the email will be optional.
-
Chat Messages: Collected when the user sends messages to the AI.
-
Prompts, AI Settings, Integrations: Users can create a custom prompt for each specific agent/ client.
-
User Preferences: Includes settings like colors, sizes, font size, links, and animations to improve user experience.
-
Training Data: Includes uploaded documents (DOC, TXT, PDF, etc.) and connected online data sources (e.g., scraped website data, Notion, Google Drive).
Data Flow
This section outlines the flow of data from its creation, where it's sent, and where it's stored.
Type of Data | Created/Collected Where? | Sent Where? | Stored Where? |
|---|---|---|---|
Training Data | When the user uploads training documents or connects to online training data sources | Sent to the Knowledge Database for processing and chunking | Stored in the Knowledge Database |
User Preferences | When the user uses the corresponding feature in the chat interface | Only to the App Server | Only in the App Database |
Prompts, AI Characters, Plugins | When the user uses the corresponding feature in the chat interface | Sent to the App Server, possibly to the AI Service Provider if used in a specific chat | Only in the App Database |
Chat Messages | When the user starts sending messages in the chat interface | Sent to the App Server, then to the AI Service Provider | Only in the App Database |
Email | When the user logs in or the Admin User sends an invitation | Only to the App Server | Only in the App Database |