These terms describe the rules for using the public handbook, activation flow, member dashboard, validation, waitlist, pilot, and admin-controlled product surfaces, including planned features as they become available.
Last updated: October 5, 2026
You may use the platform only in lawful ways and only for legitimate learning, evaluation, product-design, and workflow-improvement purposes. You must not misuse authentication, automated access, protected content, or operational tooling.
You are responsible for the accuracy of your account information, for protecting access to your sign-in methods, and for activity that occurs through your account. Access may be suspended, limited, or terminated when misuse, fraud, impersonation, policy abuse, or security risk is detected.
Activation recommendations, route suggestions, evaluation summaries, and lead or product insights are provided to help users move through the platform and improve workflows. They do not constitute legal, financial, regulatory, medical, or employment advice, and they may change as models, prompts, and platform logic evolve.
Public pages are provided for discovery and learning. Member features, progress state, certification paths, validation, waitlists, and pilot workflows are planned features that may change as the platform evolves. Access to any feature does not guarantee permanent availability, permanent pricing, or guaranteed outcomes.
You must not attempt to bypass access controls, abuse waitlists, scrape protected member data, interfere with platform availability, reverse engineer restricted admin surfaces, upload malicious material, or submit misleading activation, pilot, validation, or certification evidence.
Your use of the platform is also governed by the privacy policy. Signed-in users can manage optional privacy settings, request a data export, and request account deletion from the Privacy & data management section. Deletion removes the live account and may retain a time-boxed backup for the selected number of days before purge.
When you use AIDB Studio, your conversations are saved to your account so you can leave and pick them back up, and so they follow you across your devices. They are stored only for you (the AIDB Studio team does not read them) in our database in the UK, the same region as the rest of your account data. Generating each reply sends the conversation to a model provider: OpenAI (US) within your plan's included allowance, under the EU Standard Contractual Clauses and UK Addendum and on a no-training basis; OpenRouter (US) on the Basic plan and once any plan's included allowance is used, which we ask to pass it only to a provider it lists as not collecting user data; or, when you choose to run it on your own OpenAI or OpenRouter key, that service under your own account. Only the stored at-rest copy stays in the UK. You stay in control. From the conversation menu you can clear a conversation's messages while keeping the conversation itself, delete any single conversation, or delete all of them, at any time; deletion is immediate and cannot be undone, and deleting your account removes every conversation with it. To keep storage bounded, we keep your 200 most recent conversations, and any conversation you pin is always kept. By using AIDB Studio you accept this and the privacy policy.
The MCP exposes two feedback tools with different access levels. signals.feedback is open to all callers (including unauthenticated agents) but must only be called when the user explicitly requests it; only the fields you pass are stored, including any free text. signals.feedback sends its free-text fields to OpenAI (US) for triage only when permission_to_follow_up=true and a valid contact email is given, which also opens a support ticket; the email itself is never sent, and, separately, feedback linked to an account may appear, pseudonymised and shortened, in the extract our weekly lead-intelligence report sends to OpenAI (US). signals.report requires a signed-in Pro, Pro Plus, Teams, Enterprise, beta, or trial plan; records are linked to your authenticated user ID and plan tier, the event fields you pass are stored as written (the event type, which is required, and optionally the surface, a rating, workflow stage, whether you'd recommend it, team size, and a free-text brief_context note), with your plan and calling client. The tool reads only the arguments you pass, never your prompts, code, or files; brief_context may appear, pseudonymised, in our weekly lead-intelligence extract to OpenAI (US). You are responsible for ensuring brief_context fields do not contain sensitive content. contact_email is stored only when permission_to_follow_up is true. Signal records tied to your account can be deleted on request. The platform also issues long-lived MCP Bearer tokens (via OAuth 2.1 PKCE or manual generation from the Profile page) linked to your user ID; these can be revoked by deleting your account or generating a replacement token from your profile.
Beta access is granted by invitation only and is managed via an internal invite list tied to your email address. A beta invite grants temporary platform access under the beta membership plan. Beta access may be modified, extended, or revoked at any time. Beta users are subject to the same acceptable-use requirements as all other users, and to additional feedback obligations communicated at onboarding.
Using the platform does not guarantee certification, employment, funding, revenue, product success, or any commercial or technical outcome. Any future certification or pilot decisions will depend on published criteria, internal review processes, and any applicable manual review steps.
We may update the service, these terms, public curriculum, activation logic, membership features, or pricing over time. Material changes should be reflected on this page with an updated effective date.
