1. Identity and scope
XUELONG YU is the developer and website operator. Clip and Tempo use the copyright notice “© 2026 XUELONG YU”; TSX uses the copyright notice in its MIT license. Lumax is the product brand, not a separate company. In this policy, “we” and “us” refer to XUELONG YU. This policy covers TSX, Lumax Tempo, Lumax Clip, lumaxspace.com, and messages sent to hello@lumaxspace.com or support@lumaxspace.com.
2. What Lumax Clip keeps locally
Lumax Clip has no Lumax account, cloud sync, OCR, or AI feature. Clipboard history and activity data are processed on your Mac, and the app has no feature that uploads clipboard content or local activity data to the developer.
Depending on what you copy and the settings you choose, local data can include:
- Clipboard text and URLs, PNG or TIFF images, supported audio data, and local file URLs.
- A reference to an original local file. The reference is not a copy or backup of that file, and it can stop working if the original is moved, renamed, deleted, or becomes unavailable.
- Source-app metadata, timestamps, favourites, local activity data, and the information needed to preview and search saved history.
- Local preferences such as language, appearance, shortcuts, interface state, launch at login, privacy exclusions, and retention choices.
3. Clip Basic capacity and Pro retention
The free Basic version has a total capacity of 500 history entries, including favourites. At the normal 500-entry limit, saving a new entry replaces the oldest non-favourite entry. Favourites are not removed by this capacity rotation.
If all 500 entries are favourites, Lumax Clip pauses saving new history because there is no eligible entry to replace. If an existing library already contains more than 500 entries, those entries are kept and new history is paused until you actively reduce the total to within the Basic capacity. A history-saving pause does not disable the macOS system clipboard.
Pro removes the Basic version’s fixed 500-entry capacity and adds retention by count, by time, or permanently. Count- and time-based automatic cleanup protect favourites. “Permanent” retention remains subject to available disk space, your own deletions, and privacy settings; it is not unlimited storage or a backup guarantee.
4. Clip privacy controls and deletion
Basic includes privacy exclusions, sensitive-content filtering, pause and resume controls, manual deletion, and clear-history controls. These tools reduce unwanted capture but cannot identify every password or every other kind of sensitive information. Review what you copy and use pause or deletion when appropriate.
Deleting history removes the corresponding records and associated local app data through the app’s normal deletion process. Lumax Clip does not claim forensic erasure from storage media or operating-system backups, and it does not claim that its database has separate application-level encryption.
5. What Lumax Tempo keeps locally
Lumax Tempo is a calendar, reminder, world-clock, countdown, and desktop-note app. It does not require a Lumax account or operate a Lumax cloud-sync service. It has no advertising or third-party usage-analytics SDK, and it does not send your calendar, reminder, countdown, or note content to the developer.
App-managed records and preferences are stored locally on your Mac. Retention depends on the record type: notes and countdowns remain until you remove them, preferences remain until changed or removed, and older reminder-allowance records are rotated automatically. Deletion from the app does not promise forensic erasure or removal from operating-system backups. Depending on the features you use, local records include:
- Custom countdown titles, dates, pinning choices, and links to system reminders.
- Desktop-note text, links to calendar events or reminders, ordering, visibility, and window preferences.
- Selected world-clock cities and preferences such as language, appearance, menu-bar format, calendar sources, and category or item colours.
- Dates and successful-creation counts used for the free daily reminder allowance. These quota records contain no reminder titles, text, or identifiers. They are local to each Mac, not an account-based activity profile.
6. Tempo calendar and reminder access
Tempo requests macOS Calendar and Reminders access when you enable the corresponding features. With your permission, it reads information needed to display and manage your events, reminder lists, tasks, dates, completion state, and related details. Creating, editing, completing, or deleting an item changes the system calendar or reminder source you select, subject to that source’s permissions.
Apple EventKit provides this access. Calendars and reminders may sync through iCloud or another account you configured in macOS; that synchronisation is handled by the system and your chosen provider under their policies, not a Lumax server. System reminder delivery also depends on macOS and the source account.
You can decline access or change the relevant Calendar and Reminders permissions in macOS System Settings. Features that depend on that access will be unavailable. Revoking access does not delete items from the system source or erase existing local notes and countdowns. The calendar grid, local date calculations, and other independent features remain available.
Local notes and countdowns are not a separate backup of system calendars or reminders. Removing a countdown link removes the local association; editing or deleting the linked system item is a separate action that can affect your other synced devices.
7. Tempo feedback drafts
The in-app feedback form keeps an unfinished draft in memory for the current settings session. It is not saved to a Lumax server, written to diagnostics, or retained across an app restart. You can optionally include the Tempo version/build and macOS version; the app does not automatically attach event content, reminder content, logs, or files.
“Continue in Mail” opens a draft in your mail app. Tempo does not send it for you: you review and send it there. The copy option writes the draft to the macOS clipboard at your request. Once you send a message, the email handling described below applies.
8. Purchases and Apple
Purchases, Restore Purchases, and transaction verification use Apple StoreKit and communicate with the App Store. Apple handles the Apple Account, payment, storefront, and transaction information under Apple’s policies; each app uses transaction information needed to determine whether its own Pro features are available.
This purchase-related communication does not upload clipboard history, local activity data, calendars, reminders, notes, or countdown content to the developer. Clip Pro Activity Analysis is a local product feature, not a third-party usage-analytics or telemetry service.
9. Website data
lumaxspace.com is a static website hosted through Cloudflare. It has no website account, contact form, or advertising. The site source does not include an analytics beacon or code intended to set advertising or analytics cookies.
Cloudflare may process technical request and security information needed to deliver and protect the site, such as IP address, request time, requested page, browser or device information, routing data, and security logs, under Cloudflare’s policies.
10. Email correspondence
If you write to hello@lumaxspace.com or support@lumaxspace.com, the developer receives your email address, message, attachments, and standard email metadata. That information is used to respond, troubleshoot, maintain security, and meet applicable obligations.
Correspondence is kept only as long as reasonably needed for those purposes and applicable recordkeeping or legal requirements. Do not send passwords, an entire clipboard database, full calendar or reminder exports, or unrelated sensitive information.
11. Sharing and service providers
The developer does not sell or rent personal information and does not use it for advertising. Limited information may be processed by Cloudflare for website delivery and security, by the email provider used to receive support messages, and by Apple for App Store distribution, purchases, restores, and transaction verification.
Neither Lumax Clip nor Lumax Tempo contains a third-party advertising or usage-analytics SDK. Open-source libraries used for local app functions are not used to send clipboard content to their authors.
12. Your choices, rights, and security
The developer cannot remotely view, recover, synchronise, or delete clipboard history stored on your Mac. You control it through the app’s local settings and deletion tools. The developer likewise cannot remotely view, recover, or delete Tempo’s local records or your system calendar and reminder data. Manage system items through Tempo with permission, or through the corresponding system app; manage local notes, countdowns, and preferences in Tempo.
For website or support information held by the developer, you may ask for access, correction, or deletion by emailing support@lumaxspace.com. Available rights depend on applicable law. The developer uses reasonable safeguards for information received, but no storage or transmission method can be guaranteed completely secure. Service providers may process information in the locations where they operate, subject to their policies and applicable law.
13. Changes and contact
This policy may change as Lumax Tempo, Lumax Clip, the website, or applicable requirements evolve. Material changes will be posted here with a revised date.
Privacy and product-support questions: support@lumaxspace.com.
TSX — translation and updates
TSX is a free, MIT-licensed macOS translation app. Apple translation is the default and may require language downloads. Screenshot recognition runs locally; when you choose an external service, the request text and instructions go to that service under its own policies. TSX does not save translation text or screenshots as history or upload them to Lumax.
Local usage records are enabled by default, retain up to 10,000 numeric request records for 30 days, and can be disabled or cleared. They contain no translation text or screenshots. API keys are stored in macOS Keychain; optional account sign-in uses separate local credential storage. Update checks connect to lumaxspace.com and downloads use GitHub; automatic checks and downloads are opt-in. Hosting providers receive normal connection metadata, including IP address and app version; translation text is not part of update requests.