Lunes Privacy Policy

Updated and effective: October 5, 2026 · Version 1.0

Operator: 江梦琦 (Jiang Mengqi). Privacy contact: [email protected].

This policy covers the Lunes website, central account and instance connection services, and iPhone, iPad and Mac clients. Independently deployed Agent instances are controlled by their operators. If you connect to someone else's instance, review that operator's data practices as well.

1. Where processing happens

The central service manages accounts, login identities, instance ownership, connection authorization and necessary service records. Conversations, memories, files, tasks and tool results are primarily stored on your connected Agent instance. Clients store credentials, preferences and necessary caches.

Independent deployment does not mean all processing stays on your device. Remote models, search, MCP, the WeChat bridge and public relays involve other services. Proxies and relays may process connection metadata and requests passing through them. We do not claim end-to-end encryption across all connections.

2. Information and purposes

• Accounts: usernames, internal identifiers, creation times, password hashes when applicable, sessions, and Apple or Google identity verification information support registration, authentication, linking and account security. Authorization may supply a name and email you permit the provider to share; account linking currently primarily uses the provider's identity identifier. We do not receive your Apple or Google password.
• Instances and devices: names, versions, private and public addresses, binding relationships, availability and connection credentials support discovery and connection. Private network addresses are also submitted to the account service so your other signed-in devices can connect.
• Work content: messages, images, audio, video, files, context, memories, rules, tasks, tool arguments, results and deliverables enable responses, delegated actions, continuity and personalization. Models may process this content for summaries, memories and preference analysis.
• Notifications: push tokens, preferences, session/task identifiers and notification excerpts enable completion alerts, task updates, approvals and proactive messages. Previews may include conversation content; system settings control previews and notification permission.
• Operations and security: login and administrative events, request times, IP and connection information, and error logs support authentication, troubleshooting and abuse prevention. Instance logs may include tool output or error context. Avoid including unnecessary credentials or sensitive information.

3. Permissions and optional capabilities

The microphone supports voice input or phone mode when you enable it. Current Apple-client voice input uses on-device recognition; transcribed text is sent to the instance as a message. Audio you deliberately attach, or send through a selected server-side voice feature, goes to the corresponding instance/service. Downloading voice models contacts their resource servers.

Camera access supports scanning and deliberate capture. Photos and files support selected attachments or avatars. You may revoke permissions in system settings. Refusal affects the corresponding capability; text chat does not require unrelated permissions.

Calendar, reminders, contacts, alarms and shortcuts connectors run after the relevant system and operation permissions allow them. Read results, including event details, contact names, phone numbers or email addresses, may return to your Agent instance and enter model context as tool results. System authorization does not mean information remains only on your phone. AI approval and full-control modes may approve subsequent actions automatically; adjust conversation permissions and revoke connector access in system settings as needed.

4. Models, tools and other services

The instance sends information necessary for AI requests to its configured model providers: messages, relevant history, memory, attachments and tool results. Recipients depend on the instance's configuration, rather than one fixed vendor. Review the actual provider, processing location, retention and model-improvement policies before enabling it. Self-hosting an instance does not guarantee zero retention by external providers.

Search services receive queries and necessary parameters. Installed or registered Skills, tools and MCP servers may access workspace content or external services. A bound WeChat bridge processes relevant messages, attachments, binding credentials and proactive notifications. Valid conversation-share or Playground links may expose published content to anyone holding the link; use expiry and revocation where available and avoid publishing others' personal information.

Apple and Google verify sign-in. Apple's APNs processes device tokens and notification payloads. Hosting, domain/network and relay providers supply infrastructure. We do not sell personal information or use it for cross-app advertising tracking. The current official client contains no third-party advertising or behavioral analytics SDK. This does not provide a privacy guarantee for user-installed extensions.

We require appropriate data protection from providers processing personal information on our behalf. Operators of independently selected instances, models and extensions are responsible for their services; review their protection before sending sensitive content.

5. Retention and deletion

Central account data, bindings and necessary security records are retained for service and security needs; credentials have their respective validity periods. This preview does not yet implement one automatic cleanup period for all account and audit data. We therefore do not promise their automatic deletion after a fixed number of days.

Instance conversations, memories, files, execution records and backups follow operator configuration; some records have no automatic expiry. Archiving, removing a conversation from a list, clearing its visible content or signing out may leave underlying history, memories, derived summaries, attachments and backups. Specify these categories when requesting complete deletion.

Backups may retain earlier data within their retention cycle; relevant backups and restoration processes must also be addressed. Deleting a central account does not automatically erase independently deployed instances, or vice versa. One personal instance's backup count or retention settings are not a service-wide guarantee.

6. Your choices and requests

Use available interfaces to inspect or change accounts, connections, conversations, memories and preferences; unlink third-party identities in the App account page; revoke system permissions; disable notifications or proactive features; and stop using optional tools. Revocation does not automatically retrieve data previously sent to an instance or another provider.

To request access, correction, export, complete deletion of information we control, or central account closure, contact [email protected] with your account and requested scope. Do not send passwords or private keys. We will verify identity, process the request and explain handling of independent instances, backups or any legally required retention. Also contact the operator if someone else runs your instance. Other applicable privacy rights may be exercised through the same channel.

Signing out or unbinding is not account deletion. This policy does not imply that an unimplemented self-service account-deletion feature is already available.

7. Security and international processing

The central account service uses HTTPS and password hashing. Apple clients use the system Keychain for login/pairing credentials. Independent instances support configured HTTP or HTTPS; plain HTTP does not provide HTTPS transport protection and should only be used in trusted environments. Operators must protect instances, credentials, backups and devices.

Infrastructure, models and tool providers may operate in a different country or region from you. Locations depend on the connected instance and providers; do not assume all processing stays in China or on Apple devices. Applicable notices, permissions and safeguards must be addressed before the corresponding processing occurs.

8. Minors, changes and contact

Lunes is a general-audience service, not specifically designed for children. Minors should meet applicable local age requirements and obtain parental consent where required. Avoid providing unnecessary sensitive information about yourself or others. Contact us about children's information processed without appropriate authorization.

We will update this page and its version date when practices change. New purposes or permission scopes require appropriate notice and authorization; changing this policy does not replace system permission or explicit consent needed to share personal information with third-party AI.

Privacy questions and requests: 江梦琦 (Jiang Mengqi) · [email protected].