Lumina
中文EN

Privacy Notice

Last updated: 2026-10-04. This notice describes, by feature, which data Lumina touches, which paths the data takes, and how you can adjust it. Every input has its own switch, so when judging a boundary please look at the features currently enabled, rather than summing it up in one sentence.

1. Scope

This notice covers the Lumina macOS client, the public website, the customer center (Portal) and the answer gateway the client connects to. Answer generation and session memory go through the gateway; only speech recognition in the local tier is completed on the device.

2. Speech and transcription

  • Local tier (default): on an Apple Silicon Mac, transcription runs on the device by default and audio does not leave your machine; manual excerpts are also transcribed on the device. The model is installed once and verified, and after that this step needs no network.
  • Cloud fast / standard tier: chosen by you, or used as an automatic fallback when the local engine is unavailable (unsupported machine, model not installed, load failure). Audio is then forwarded through the gateway to a cloud transcription service for recognition; where the upstream service is located depends on the deployment configuration of the region the account belongs to.
  • Audio content is not stored: in either tier, audio content is not written to the content store and is not used for training; the gateway records only usage (bytes and duration) for billing and troubleshooting.
  • The client suppresses speaker echo (the same sound looping from the speakers back into the microphone) according to your settings; segments judged to be echo are neither recorded nor answered.

3. Answers, sessions and memory

  • When an answer has to be generated, the current question and the context you have enabled (recent content of the current session, a screenshot when screen reading is on, personal knowledge and professional knowledge base retrieval results, account preferences) are sent through the gateway to an upstream model to generate the answer; answer generation going through the gateway is the fixed path of the answer pipeline.
  • Sessions are stored on the gateway side per account: transcript text, questions and answers are used as session memory when generating answers, and are archived into the personal knowledge base (question-bank archive). A session ends automatically after 20 minutes of inactivity.
  • Production does not keep raw-content logs of questions, answers or transcript text; troubleshooting uses only metadata such as usage, duration and error type.
  • "Clear" in the client clears the conversation record in the current interface and starts over; session records on the gateway side are kept and deleted under the rules in section 8 below.

3a. Meeting notes

  • Meeting notes are included from the Standard subscription up. When "Generate meeting notes after the meeting" is on, the client uploads the text transcript of the meeting (not audio) after it ends, and the gateway writes the notes from it.
  • Notes and their transcript are visible only to your account and are deleted automatically after 30 days; you can also delete a meeting in the customer center at any time, and the notes, transcript and Q&A are deleted together.
  • You can turn off the upload after the meeting in the client settings; the free tier and the Basic subscription do not upload meeting transcripts.

4. Screen context

Screen reading is an independent switch, and is up to you by default. When it is on, the client captures the current screen when an answer is needed and uploads it as background for that answer; when it is off, this source no longer takes part and no new screenshots are uploaded. Whether the shared picture shows the overlay is decided by macOS, the meeting app and the share source; please verify with the way you will really share before formal use.

5. Personal knowledge base and shared question bank

  • The personal knowledge base is stored in a partition per account, visible only to you, and used only within the retrieval scope of your own answers; the basic knowledge tier only reads your own material and does not inject it into answers.
  • You can view, edit and delete your own entries in the Portal library; story text import (.txt/.md) is read only on your own computer.
  • The professional knowledge base (finance and technology) is a shared confidential asset: ordinary users cannot browse, search or export the raw material, and it takes part in retrieval by relevance only inside the authorized answer pipeline.

6. Account, device and download

  • Account data includes: the mobile number (verified at registration, used for sign-in, password recovery and identity confirmation), the email (optional, can be used to sign in; once verified it can be used for password recovery and notifications), the sign-in session (cookie), the bound device and rebind records, the hash of the access key, order and usage records, and risk-control and audit records.
  • Sign-in methods: mobile number or email with a password, or mobile number with an SMS verification code; password recovery uses an SMS verification code or a verified email. An unverified email is not used for password recovery or notifications.
  • Access keys are stored only as SHA-256 hashes, never in plain text; client requests carry a device signature and are bound to the device, to prevent sharing and misuse.
  • The installer is downloaded after sign-in through a signed link valid for 5 minutes; where a watermark can be applied it carries a traceable watermark, used to check the source.
  • The public web page offers no anonymous direct links to the installer; the Portal uses a session cookie, CSRF checks and device state to protect sign-in and high-risk actions.

7. Payment and orders

Manually confirmed payment channels are supported at present; orders, payment times and status records are kept on the gateway side, used for fulfilment, renewal and reconciliation. If an online payment channel is connected in the future, payment information is handled by that channel under its own privacy policy, and we keep only the result information needed for fulfilment and reconciliation. Invoices and payment methods are as actually described on the order page.

8. Retention, deletion and export

  • Default retention: session records are kept for 30 days and usage records for 180 days, and are deleted by a cleanup job when they expire (server configuration can adjust this). Questions and answers archived into the personal knowledge base are kept as knowledge base data until you delete them or request deletion.
  • Self-service deletion: personal knowledge base entries can be deleted directly in the Portal library, and deletion takes effect immediately: source files, retrieval indexes and pending jobs are cleaned up together.
  • Manual handling: account data deletion and knowledge base export are submitted through luminameet@gmail.com · WeChat support: luminameet_01; we process them after verifying account ownership and confirm the result by email. The full process is in Support and contact.
  • Disaster-recovery backups: the database and knowledge base are backed up once a day for disaster recovery and rotated within a bounded window (production currently keeps them for no more than 14 days). Deletion takes effect immediately on live data; historical copies in backups leave as they rotate, and we do not promise that deleted data becomes unreadable in every historical backup at once.

9. Your choices and security mechanisms

  • You can adjust at any time: the audio source (microphone / system audio), screen reading, auto answer, clearing the conversation record, and the knowledge feature switch; these choices decide which data goes into answers.
  • Security mechanisms include: keys stored only as hashes, device binding and request signing, encrypted backups, no raw-content logs in production, least privilege and audit records.
  • To deactivate an account or withdraw data, submit a request under section 8; we process it after verification.

10. Contact and changes

Privacy requests and questions: luminameet@gmail.com · WeChat support: luminameet_01. This notice is updated as the implementation changes, and the effective date and version at the top of the page are changed with each update. Applicable law and cross-border transfer terms will be published once confirmed, and this page does not invent them.