Privacy Policy

What we collect

Account. If you create an account, sign-in is handled by our authentication provider. We receive an account identifier and the profile details you provide, such as your name and email address. We do not store your password.

Workspace. We store the messages you send, the files you upload, and the work produced from them, so you can return to that work and so the workspace can continue it.

Session. You can start without an account. The browser then keeps a session identifier so the same workspace can be opened again on that browser. A prompt you have typed but not yet sent may stay in the browser until it is sent. A preference for how responses are produced may also be stored there.

Where you came from. If the link you arrived by names where it was shared, such as a post on TikTok or Instagram, we keep that name, the website that sent you, and the page you landed on with your workspace when you start one, or with your account when you sign up. It is held in the open page, not stored in your browser. After you sign up we may ask where you heard about Crux; answering is optional. We use these only in aggregate, to see which posts bring people to Crux.

Figma plugin. If you use the Crux plugin for Figma, it reads the text and layer names of the frames you select or ask it to check, and sends them to Crux to find related research and suggest changes. It does not send images of your designs. Research you pin to a frame is saved in that Figma file. So that research can show where it is pinned, the plugin also tells Crux the names of the file, page and frame each pin is on, and we keep them with your project until the pin is removed. The plugin keeps your sign-in in Figma’s storage on your device, and the project you choose is saved on the file.

Usage and payments. If you pay, the payment is handled by our billing provider. We keep your plan, remaining usage, and a payment identifier so the payment is applied once. We do not store card numbers.

Support. If you chat with the team, the chat runs on Crisp. It receives what you write, any email address you give it, the page you are on, device and browser details, and an approximate location derived from your IP address. If you are signed in, it also receives your name and account email once you open the chat, so the team knows who they are talking to. Signing out starts a fresh chat. If you email support@crux-hq.com, we keep your emails so we can answer you.

How we use it

We use this information to run the workspace, produce responses, keep your work available to you, apply usage and payments, protect the service, and learn which places people find Crux from.

To produce a response, the messages, files, and saved work needed for that request are sent to a model provider. Audio you upload may be sent to a transcription provider so it can be turned into text. When a request needs published information, the relevant query may be sent to a web search provider, and public pages may be retrieved.

To find and fix problems and to make Crux better, the Crux team reviews chats: what was asked, what Crux answered, any feedback given, and how long and how much each answer took. Access is limited to named people at Crux. To group what people ask by topic, what you ask is also sent to our model provider to be summarised and labelled.

We do not use your content to train models that we operate. Providers process what they receive under their own terms. We do not control how long they keep it.

Your workspace is private to your account. We do not make it visible to other people using Crux.

Who else handles it

These providers run parts of the service:

• Clerk — sign-in and payments
• Vercel — hosting and private file storage
• Neon — database
• OpenRouter — model responses
• AssemblyAI — transcription of audio you upload
• Tavily — web search when a request needs published sources
• Vercel Web Analytics — cookieless page-view counts
• Google Analytics — how visitors use the site, only if you accept analytics cookies
• Crisp — chat with the team, only once you open it

We do not sell personal information.

Cookies and browser storage

Sign-in uses essential cookies. The browser also stores the session identifier and the small preference described above.

Analytics. We count page views with Vercel Web Analytics, which sets no cookies and does not identify you. With your permission, we also use Google Analytics to understand how visitors find and use the site. It sets cookies (named _ga and _ga_…) that recognise a returning browser for up to two years, and it sends Google your pages visited, the referring site, device and browser details, and an approximate location derived from your IP address. We use this only in aggregate.

Google Analytics cookies are off until you choose Accept in the cookie banner. If you decline or do not choose, Google Analytics sets no cookies and receives only cookieless signals that do not identify a returning browser. Your choice is kept in your browser. You can change it at any time with the Cookies link at the bottom of the page. We do not use advertising cookies.

Support chat. Crisp loads only when you choose to chat with the team, and sets nothing before then. Once it has loaded, it keeps cookies (named crisp-client/…) and some browser storage so the chat is still there when you come back.

How long we keep it

We keep workspace content while the account or session is in use. Deleting an item in the workspace removes that item. Deleting a project removes it from your workspace. Email us if you want the account and the content stored with it deleted. Copies we must keep for security, billing, or legal reasons may remain for a limited time.

Children

Crux is not directed at children under 16. Do not use it if you are under 16.

Changes

We may update this policy. The date at the top will change when we do. If you keep using Crux after an update, the revised policy applies.

Contact

Questions and deletion requests: simon@crux-hq.com. The Terms of Service cover use of the workspace. To report a security problem, see Security.