Skip to content
Legal

Legal

Research Mode policy

Research Mode is approval for higher-risk project scopes on our production models, granted for verified lawful research and scoped to an approved project. This policy sets out who qualifies, what we verify before granting access, the bounds of an entitlement, and the conditions under which access expires or is revoked. It supplements the Terms of Service and the Acceptable Use Policy; it does not replace them.

Last updated: June 23, 2026. This Research Mode Policy is incorporated into the Terms of Service. All use under an approved scope remains subject to the Acceptable Use Policy. For a task-oriented walkthrough of how to apply, see the Research Mode documentation.

What Research Mode is

Every model on AdvancedMind AI is standard and available to any paid account with credits. Research Mode is approval for higher-risk project scopes on those models. It reduces generic refusals on legitimate technical work within an approved project scope, and approved organizations receive first access to gated routes if and when such routes launch. It does not change what the Acceptable Use Policy permits.

Eligibility

To apply for Research Mode, you must:

  • Hold a paid account on a plan that is eligible for Research Mode. Plans differ in eligibility and in review priority, compare them on the pricing page.
  • Apply on behalf of an organization. Approval is tied to your organization and a project scope, not to an individual login or seat.
  • Describe authorized, lawful research. The work must be lawful where it is conducted and authorized by whoever owns the systems, data, or institutional context it touches.
  • Provide a verifiable identity sufficient for us to confirm who you are and that the requested access matches the project.

You may have one active application at a time. Approval is per organization and per project scope; a new project generally needs its own application.

What we verify

Every application is reviewed by a person before access is granted. We verify:

  • Identity: your name, role, country, and a verifiable professional or institutional profile. We use this to establish accountability for the access.
  • Organization: the organization the work is for, and your association with it. The entitlement is granted to the organization.
  • Project scope and intended use: a concrete description of the project, what you will actually do with the models, and the specific models you request. We also record the data sensitivity and risk tier you declare. Vague scope, or a mismatch between the stated use and the requested models, is the most common reason an application is sent back for more information.

You attest that the work is authorized and lawful and accept this policy as part of the application. A false attestation is itself a policy violation.

Project-scoped entitlements

When granted, an approval produces an entitlement bound to your organization with explicit limits:

  • Allowed models: a named list of the models the approval covers. The approved scope applies only to models on the list.
  • Project scope: the entitlement carries the scope you were approved for. Using the access for unrelated work is outside the grant.
  • Risk tier: recorded on the entitlement and reflected in how the access is monitored.
  • Expiry: every entitlement has an expiry date.

You can review your current entitlement, allowed models, scope, risk tier, and expiry, in Research Mode in the app. An entitlement never waives metering: requests made under an approved scope bill against your credit balance at published rates. If gated routes launch, entitled organizations receive first access to them.

Expiry and renewal

Entitlements are time-bound by design. When an entitlement reaches its expiry date, its status moves to expired and the approval lapses automatically; the approved higher-risk scope no longer applies until access is restored. Expiry keeps approved access current with the project it was granted for.

To continue approved work past expiry, submit a renewal or a new application from Research Mode describing the current project scope and the models you still need. We may renew on the existing scope, adjust the allowed models, or ask for more information before renewing.

Revocation triggers

An entitlement can be revoked before its expiry date. Revocation moves the entitlement to revoked and ends the approval immediately. We revoke when:

  • Scope drift: the access is being used for work materially different from the approved project scope.
  • Misuse: use that violates the Acceptable Use Policy, including any attempt to use approved access for operational harm or prohibited activity.
  • Verification failure: the identity, organization, or attestations in the application are found to be false or can no longer be confirmed.
  • Account or billing state: the underlying account is suspended, or otherwise loses eligibility for Research Mode.

Revocation is recorded, and high-risk access is reviewed on an ongoing basis so that misuse can be caught and stopped. Clear abuse is blocked regardless of any active entitlement.

Data handling

Research work often involves sensitive material, so data handling is explicit and the same on every route. Our models run under 30_day_ops retention: request and response content may be retained for up to 30 days for debugging, abuse detection, and reliability, then deleted, and it is never used to train or improve any model, by us or our providers. Each model declares its retention mode, shown on the models page, so you can confirm how a route is handled before you run it. The full commitment, including what metadata we keep and how to request deletion, is in the No-Training Policy.

Appeals and needs-info

Applications move through a defined lifecycle: pending on submission, then either approved, rejected, or needs_info. An entitlement that has been granted can later become expired or revoked.

  • Needs more information. If your application is marked needs_info, the reviewer needs something clarified, usually a sharper project scope, a closer match between intended use and requested models, or stronger identity verification. Update and resubmit your application from Research Mode; the reviewer's note explains what is required.
  • Rejected. A rejection comes with a reviewer note. You may submit a new application that addresses the reason for rejection. Rejection of an application is not an account-level penalty.
  • Appealing a revocation. If you believe an entitlement was revoked in error, contact us at [email protected] with your organization and the entitlement details. We will review the revocation and the evidence behind it.

We aim to act on applications and appeals promptly; eligible plans receive priority review. We do not grant access where we cannot verify identity, organization, and a lawful, in-scope use.


Related