Context OSBy Accolade Solutions
Menu

Context OS / Privacy policy

Privacy policy

How Context OS handles your account, project context and connected tools.

Last updated: October 22, 2026

Who we are

Accolade Solutions, Inc., an Illinois corporation, operates Context OS. This policy covers our website, cloud context service, desktop companion and integrations. The initial public offering is for adults aged 18 or older in the United States.

Accolade Solutions, Inc.
1500 Shermer Road, STE 240W
Northbrook, IL 60062, United States
[email protected]

Information we process and why

We do not use customer content to train our own AI models. Context OS does not provide an advertising service. Connected AI providers process returned information under their own terms and account settings.

What stays on your device

The companion stores local folder paths, configuration and local Markdown copies on your device. Credentials use operating-system credential storage. Approved cloud synchronization sends the selected context to Context OS; local-only projects remain local until you enable cloud sync.

Optional session memory starts off. When enabled for a project, supported hooks can capture an agent’s final response and safe filenames from supported edit events. They do not collect full transcripts, source-file contents, shell commands or tool output. Observations are encrypted in companion app data and are not automatically uploaded to Context OS or shared with teammates. A startup hook may supply retained observations to your AI tool, which may process them in its own cloud. A reviewed foundation update may save selected information to shared project context.

You can pause capture, remove hooks, add exclusions and delete observations. Select 7, 30 or 90 days of local retention. Cleanup runs while the companion is running, including startup and wake; it cannot erase data while the device or app is off. Secret filtering is best effort.

Connected tools and sharing

When you connect ChatGPT, Codex, Claude or another compatible tool, it can request information within your account permissions and the connection’s granted scopes. Project membership is separate from organization membership. Writes require applicable permissions and follow the project’s approval policy.

Our initial directory packages request read access to project context. They do not install local capture hooks or collect your chat history. Disconnecting a tool prevents future access through that grant; it does not delete information already returned to that provider or copied elsewhere.

Service providers

We use Cloudflare for application hosting and database services, Microsoft Azure for encrypted cloud content, backups, operational monitoring and companion distribution, and Resend for sign-in and invitation emails. Support uses Microsoft 365. GitHub supports software delivery; a retired private Git export also contains historical service data pending its separate retention review.

Providers process information needed to perform these functions. Your authorized collaborators and connected tools also receive information you permit them to access. We may disclose information to comply with law or address fraud, abuse or security incidents. Our Illinois address is not a guarantee that every provider processes data only in Illinois or only in the United States.

Cookies and device storage

We use authentication cookies and browser storage to maintain sessions and application preferences. Blocking necessary cookies can prevent sign-in. The companion uses local files and operating-system credential storage. This integration does not require advertising tracking.

Retention and deletion

See Retention & deletion for available controls, approved target periods and current limitations. Permanent cloud cleanup is currently disabled while historical copies and provider controls are verified. Deleted projects are hidden from ordinary access, but recoverable copies may remain beyond the target periods until cleanup is activated. Self-service account closure is unavailable during this period.

Contact support to request access, correction, deletion or recovery. We verify identity and authority before acting and explain any technical or legal limitation. A request is not confirmation of completed erasure. Applicable privacy rights are not limited by this policy.

Security and changes

We use access controls and encryption to protect information. No system is risk-free; local Markdown copies may be readable by people or software with access to your device. Avoid placing passwords or access tokens in project documents.

We will update the date on this page when the policy changes and provide additional notice where required. Contact us about privacy at the address above.