Cruxwing

Trust

Security

Last updated 9 September 2026

Cruxwing handles meeting audio, transcripts and team decisions. This page explains where processing happens, how access is controlled, and what your deletion controls cover.

Transcription and recording

On-device transcription is the default in the standard app when you have not saved a different engine choice, whether signed in or signed out. With that engine, transcription runs on your Mac. Choosing an available cloud engine, such as Deepgram, sends audio to the service that transcribes it; a saved choice carries over to later calls.

No meeting bot joins the call. That describes how Cruxwing captures audio, not whether every feature runs locally: cloud transcription, AI features and connected apps can send content off your Mac. The app asks you to confirm recording consent before your first recording. You are responsible for obtaining any consent required from participants.

Cloud AI and local models

Managed AI features send the relevant transcript and context through our backend to model providers. This includes enabled background features during a call. Provider routing can depend on the selected model, service configuration and availability. See the Privacy Policy for the processing paths and providers.

If you enable LM Studio and select one of its models, those model requests go directly to the server address you configure. The default address is on your Mac; a remote address sends the request to that machine. Choosing a local model does not change the processing path of other features you use.

Credentials and transport

The standard distributed app does not contain our AI-provider API keys. Our managed AI requests use credentials held by the backend. Connections to our hosted API use HTTPS/TLS to protect data in transit. Cloud processing requires the relevant content to be available to our service and the providers that process it.

Team access and sharing

The backend checks team membership and permissions for team data. A decision shared through a share link can also be accessed by someone holding that link, within its scope and expiry. Treat a share link as access to the material it exposes, and revoke it when that access is no longer needed.

History and deletion

Meeting history is stored locally on your Mac. You can export transcripts and clear the current account or local profile's history in the app. Local history files are separate from account records on our servers; deleting an account does not erase every local file, export or backup. Clear or export the local history you need before deleting your account.

Account deletion removes your account, sign-in sessions and account-owned server transcripts. Shared team decisions and their content can remain, along with audit records, deletion-recovery proofs and records that must be retained for billing or legal purposes. See the Privacy Policy for retention details and deletion requests.

Website privacy

Website analytics, contact forms and the Calendly booking calendar have separate data flows from the Mac app. Their loading behavior, consent controls and recipients are described in the Privacy Policy.

Reporting a vulnerability

Please report suspected security issues to artem@cruxwing.ai, with the affected feature and steps to reproduce. We welcome good-faith reports. Use accounts and data you control, avoid accessing other people's information or disrupting the service, and do not include credentials or meeting content in your report. If you encounter someone else's data, stop testing and tell us how it occurred.

Company and contact

Cruxwing Inc. is a Delaware corporation, file number 10729495. Its registered office is 16192 Coastal Highway, Lewes, Delaware 19958, United States, through registered agent Harvard Business Services, Inc.

Correspondence address: Cruxwing Inc., 5700 Central Gardens Way, Apt 202, Palm Beach Gardens, FL 33418, United States. Contact: artem@cruxwing.ai.