Bespoke AI
Legal Centre
One place for Bespoke AI terms, privacy, responsible-use, transparency, and accessibility records.
- Version
- 2026.08.1
- Effective
- 28 August 2026
Your agreement with us
Terms of Use explain the agreement between you and Bespoke Technologies when you create an account or use Bespoke AI.
Acceptable Use Policy sets safety and integrity boundaries for prompts, uploads, output, tools, automation, and access to the service.
Privacy and data use
Privacy Policy explains what information Bespoke AI handles, why it is used, provider sharing, transfers, retention, security, and available rights.
Cookie Policy explains authentication cookies, local preferences, privacy-restricted analytics state, and offline browser caches.
Subprocessor List identifies core, conditional, and independently acting connected services represented in the product architecture.
AI and generated output
AI Transparency explains capability routing, context, live response states, tools, citations, providers, limitations, and the need for human review.
Accessibility
Accessibility statement records our working target, current foundations, known limitations, testing approach, and route for requesting help or an alternative format.
Company and product information
About Bespoke AI explains the product purpose and its relationship to Bespoke Technologies. The FAQ answers common product questions, and the Changelog records user-visible releases.
Public regulatory resources
- Nigeria Data Protection Commission resources for data-protection law and guidance.
- Federal Competition and Consumer Protection Commission for consumer information and complaints.
- Nigerian Communications Commission cybersecurity resources for public cybersecurity guidance.
Questions and notices
Submit a legal, privacy, accessibility, or account question through the Bespoke Technologies contact page. Include enough information to route and verify the request, but do not send passwords or one-time codes.
Publication and approval
Repository source, a review branch, or a successful build does not establish legal approval or production publication. The legal owner must approve substantive legal meaning, and deployment evidence must identify the released version separately.