AISBFPrivacy Policy
AISBF is built around routing control, self-hosting options, and honest disclosure about what the hosted demo does and does not provide.
Privacy Approach
AISBF is designed to give operators more control over how AI traffic is routed, processed, and exposed. That includes support for self-hosting, local-model routing, privacy-conscious deployment, and reduced dependency on any single provider.
Data We Collect
We collect only data needed to operate, secure, and improve the AISBF service. Depending on how the service is configured, this may include:
- Account information and authentication data
- API usage data needed for quotas, rate limiting, abuse prevention, and billing
- Operational data such as logs, metrics, error events, and service diagnostics
- Configuration metadata needed to route requests across models and providers
How Data Is Used
Your data is used only for legitimate service operations, including:
- Authenticating users and API requests
- Routing, failover, and reliability management across AI providers
- Enforcing quotas, rate limits, and other operational controls
- Monitoring performance, debugging failures, and improving service quality
Provider Routing and Exposure
AISBF may forward requests to one or more configured AI providers or local backends in order to serve your request. The exact path depends on your deployment, routing configuration, and provider selection policies. If a request is forwarded to an external provider, that provider may process the request under its own terms and privacy practices.
Self-Hosted and Local-First Deployments
AISBF can be deployed in ways that reduce external exposure, including self-hosted operation, local-model routing, and privacy-conscious network exposure such as TOR. However, the privacy properties of any deployment depend on how the operator configures the system and which providers are enabled.
Data Sharing
We do not sell your personal data. We do not share your data with third parties except where it is necessary to operate the service you requested, such as routing a request to a configured AI provider or infrastructure dependency.
Data Storage and Access
Service data is stored and managed by Nexlab, represented by Stefy Lanza. Access is limited to what is reasonably necessary to operate, secure, maintain, and improve the service.
Contact
For privacy-related inquiries, please contact: stefy@nexlab.net
Questions?
If anything here is unclear, contact the AISBF operator before relying on the hosted demo for sensitive or production workloads.