How can we help?

Yes. The app is free to download and use across every editor. AI and a few add-on features draw on your monthly allowance — every account gets a free one, and you can buy more or subscribe if you need a larger one. See the pricing page.

Published installers are available for macOS 13 or newer (Apple Silicon and Intel), Windows 10 or newer (x64 and ARM64) and Linux. There is also a signed-in mobile companion app. The download page shows current release availability for each.

Yes, for everything local. Opening, editing, saving and exporting your own files needs no connection at all, because LumenQube is local-first. Features that are cloud features by nature — AI, sharing, publishing, connectors, account and allowance — need a connection, and the app tells you when one of those is unavailable rather than failing silently.

The app checks for updates and will let you download and install the latest version. Some releases are marked required when they carry a security or compatibility fix, in which case you will be prompted to update before continuing. Installers come from our published release channel; a build from anywhere else is not ours.

The interface and our support are currently in English. AI features can read and write in many languages, so you can work in your own language inside a document even though the app's own labels are in English.

Yes — a free account, with no card, is needed to use the app. Signing in does not upload your documents: ordinary editing stays on your own files and device. The account is what AI features, sharing, web publishing, connected services and your allowance run on. You can create one with an email address and password, or sign in with Google.

On the sign-in screen, choose Forgot password? We email a 6-digit code to your account address so you can set a new one. If it does not arrive, check spam first, then see the email troubleshooting note or write to support@lumenqube.com.

Yes. Sign in on each device you use — the desktop app on more than one computer, plus the mobile app. Sessions are independent, and you can sign out of one without affecting the others. If you think a session is not yours, change your password: that revokes tokens account-wide.

LumenQube shows AI usage as a percentage of your month, so there is no unit to learn. Your free monthly allowance refreshes on a regular cycle and does not roll over. A purchased top-up stays available subject to our Terms of Service. Allowances have no cash value and are non-transferable.

You can cancel at any time from your account; access continues to the end of the current billing period. For a refund, or a charge you do not recognize, email support@lumenqube.com with the transaction details and we will review it in good faith. See Cancellation & refunds.

Prices are quoted in USD on our pricing page. Our merchant-of-record presents in Canadian dollars, so the amount charged to your card may be shown in CAD. The checkout screen states the currency and the exact amount before you confirm, and applicable taxes are calculated there too.

Yes. Seats, administration and policy controls are described on the business page. To request a proposed purchase order or written agreement, including data-processing terms where applicable, email legal@lumenqube.com; for anything about seats or billing, email support@lumenqube.com. No separate agreement or transfer mechanism applies unless authorized representatives execute or otherwise validly accept it.

LumenQube does not use your content to train a generalized AI model as a product purpose. A selected provider processes a request under the service, account terms and settings that apply to that path, including permitted security, abuse-prevention or legal processing. Provider selection, fallback and retention are described in Privacy Policy §7.

Treat AI output as a draft. It can be inaccurate or incomplete, and it is not professional advice — review it before you rely on it. If a result is badly wrong in a way that looks like a product defect rather than a model limitation, send us the prompt and the output at support@lumenqube.com; that is genuinely useful to us.

A connection grants the provider scopes you approve. Consequential first-party actions — such as sending an email, posting a message or writing a file — require the applicable explicit action or approval gate. Review an action before approving it. Disconnecting deletes LumenQube's stored authorization record and asks the provider to revoke its grant where the provider offers that: Google once no other Google service you connected relies on it, Dropbox, Slack user tokens, and hub apps that publish revocation. Microsoft access and Slack workspace installs are revoked in the provider's own account controls. Neither step undoes completed actions or deletes remote copies. See Terms §11.

You can share a document with named people and roles — viewer, commenter, editor — or publish a view-only web link. Access is yours to change: revoke a link, remove a collaborator, or rotate the document key at any time. A copy someone already downloaded is outside anyone's control, so treat a published link as public unless you are sure it has not spread.

Data in transit is encrypted with TLS. Shared and published documents are encrypted at rest on our servers with server-managed keys — that is not end-to-end encryption, and we will not describe it as such. On your device, sensitive local data such as notes and audio can be encrypted at rest using your operating system's secure keychain. Details are in the Security Centre.

By default, no. LumenQube is local-first: the files you open and edit live on your device and are not uploaded in the background. Content is transmitted only when you choose a cloud feature — AI, sharing, web publishing, a connector, or a support report with attachments — and only the content that feature needs. Our Privacy Policy explains each case.

The fastest way is from inside the app: press ⌘⇧P (or use the Help button) to file a report — relevant diagnostic logs are attached automatically so we can investigate. You can also email support@lumenqube.com. Tell us what you expected, what happened, and roughly when.

This is almost always Gatekeeper reacting to a freshly downloaded application rather than a broken build. The launch troubleshooting note walks through it step by step, including what a legitimate first-run prompt looks like.

Check that you are signed in and that your allowance is not exhausted, then see AI features are unavailable. If a model provider is having an incident, the app will say the request could not be completed rather than pretending it worked — retry shortly, and email us if it persists.

Often, yes. Autosave and crash recovery are designed for exactly this — recovering after a crash or forced restart explains where to look. Because LumenQube is local-first, recovery happens on your machine, so do not reinstall or clear application data before you have checked.

Not today. If hosted features are failing, the desktop app keeps working on your local files. Email support@lumenqube.com with the time, what you were doing and any error text; any response is subject to review and available coverage.

Your local files are ordinary files on your device and are not included in the cloud export. The account portal can download an account summary with specified profile fields, account activity, receipts and “shared with you” index metadata; it does not include document contents and is not a complete legal access or portability response. For a verified request covering other personal information, email privacy@lumenqube.com from your account address. We will verify identity, search the applicable records, protect other people's information and explain any provider, backup, legal-retention or local-device limits.

Email privacy@lumenqube.com from your account address. The in-app account-close flow removes the records and stored objects reached by that automated flow, but it is not proof of universal erasure of top-level support, diagnostic, audit or payment records, shared-user records, provider grants or copies, remote deployments, local files, object versions or backups. A verified request inventories those boundaries and explains what was deleted, de-identified, retained with a reason, or outside LumenQube's control. See Privacy Policy §20.

Uninstalling removes the application. It does not delete your documents — those are your own files, wherever you saved them — and it does not close your account. If you want both, uninstall and then request account deletion as above.

Two separate things: a local context graph built only from files already on your computer, and durable memory — facts you told it to keep. Both are readable, both can be switched off, and both can be erased. Memory & context shows the controls; Security Centre §06 explains where each part is actually kept.

Only if you turn it on. Share anonymous product trends is off by default; when enabled it records a service category, a visit count, capped active time, platform and a pseudonym that rotates monthly — never your account ID, filenames, document content or prompts. Turn it off at any time in Settings → Privacy & data. Separately, Share anonymous run outcomes in LumenAgent settings → Devices is also off by default, and is set on each computer: when enabled it sends counts about each LumenAgent run — whether it finished and why it stopped, time taken, allowance used, model tier, approval decisions — and the names of tools the AI asked for but did not have. It is stored only as daily totals, never with your account, kept 90 days, and never includes your messages, documents or files.

Email security@lumenqube.com with the affected product or URL, reproduction steps and impact. The address routes to the Support Inbox for classification and assignment; no acknowledgement or assessment time is promised. Follow the safe-testing boundaries in our disclosure policy.