Cortex
PrivacyTermsData processing

Terms of service · last updated August 30, 2026

Pre-release terms that do not outrun the product.

These terms describe access to the Cortex design-partner service operated by Ben Kilby. If the company and operator sign an order, design-partner agreement, or data-processing agreement, that executed document controls wherever it conflicts with this page.

Release stageDesign partner

The service can change while product, reliability, and operating evidence mature.

Default action modeDraft only

New agents do not get implied authority to perform final external actions.

Commercial proofNo result guarantee

Estimates, previews, and illustrative Meridian data are not promised customer outcomes.

Contract statusCounsel review still required

This page does not claim a signed DPA, negotiated liability term, or governing law.

01

Who may use Cortex

A user must be authorized to act for the business they join and must keep account access secure. The business is responsible for its members, connected accounts, instructions, approvals, and the legality of data it directs Cortex to process. Do not connect an account or supply content the business lacks authority to use.

02

What the service does

Cortex connects owner-selected business systems, creates company-isolated searchable memory, answers questions with sources, prepares briefs and drafts, and runs configured agents. Availability depends on the connected provider, the selected history window, model route, budget, and feature configuration. A parked, paused, preview, or needs-configuration state is not completed work.

03

External actions and approvals

New partner agents start Draft only. The owner may later choose stricter approvals or grant a bounded autonomy mode where the product offers it. Every provider mutation still passes through the audited write gateway, owner guardrails, and standing instructions. Users must review recipients, facts, amounts, and attachments before approving an external action.

04

AI output and business decisions

Model output can be incomplete or wrong. Source links, confidence, owner verification, approval controls, and dispute paths support review; they do not replace it. Cortex does not provide legal, tax, accounting, employment, lending, or other professional advice, and a user remains responsible for decisions and communications made for the business.

05

Company data and privacy

The business keeps its rights in the data it supplies. It instructs Cortex to process that data to provide, secure, and operate the service. The privacy notice explains connected-service access and controls; the data-processing page identifies the current technical service chain. Final controller, processor, retention, transfer, and notice commitments belong in the executed agreement rather than being invented here.

06

Acceptable use

Do not use Cortex to violate law or another person’s rights; gain unauthorized access; evade provider limits; distribute spam, malware, or deceptive content; make prohibited credit decisions; train models from Google user data; or weaken company isolation, approvals, audit, rate limits, or security controls. The operator may pause an unsafe route or access while investigating a credible risk.

07

Fees and value records

Any fee owed by a design partner is the fee in its executed order. Public pricing and the ROI calculator describe product mechanics but are not an invoice. Estimated value and time saved remain separate from settled value; Cortex does not bill an estimate as a cash outcome.

08

Ending use, export, and deletion

A business may stop using connected sources and may request a complete company export through the authenticated owner or admin path. A company owner may use the exact-company confirmation flow for deletion. Connection revocation stops future access but is not the same operation as deletion of synchronized Cortex records. Executed agreements and applicable law may add notice, legal-hold, return, or backup obligations.

09

Pre-release legal boundary

Cortex does not use this page to fabricate a warranty, service level, indemnity, liability cap, dispute forum, governing law, or certification. Those terms require the identified legal operator, counsel review, and an executed agreement. Until then, a founder must not describe the design-partner service as carrying those commitments.

Terms contact

Questions go to the configured privacy and legal channel.

Contact bkwhop@bkwhop.com.

Read the privacy notice

Cortex