Effective date: 2026-09-12 · Last updated: 15 October 2026
MOSS is a personal AI concierge. This policy explains what information we use to remember what matters to you, respond to you, and deliver reminders.
MOSS is operated by Lim Jin Shao (trading as MOSS), registered in Malaysia. For help, privacy requests, or anything about your information, write to support@mossconcierge.com. For general questions, write to hello@mossconcierge.com. Our website is https://mossconcierge.com.
We do not access your contacts database, photo library, browsing history or device's precise location. Information you include in a message or calendar event may still contain such details. Wellness information you provide is treated as your content.
Optional wellness features store the profile and meal information you choose to provide, such as height, weight, activity level, dietary notes, and nutrition goals. Renewal and obligation features may store amounts, currencies, and renewal dates you enter. These records are linked to your account and used for the features and suggestions you request.
Calendar access is optional. When connected, MOSS reads events through Apple's EventKit and syncs a limited snapshot of upcoming events with your MOSS account. The snapshot contains event identifiers, titles, start and end times, attendee display names, and whether events are all-day. It does not include event notes, locations, attendee email addresses or calendar names.
The snapshot covers up to the next 14 days and is limited to 500 events. Later successful syncs replace the previous snapshot. MOSS uses it for meeting context, scheduling and reminders. MOSS meeting notifications stay off until you enable them. Notifications may display an event title on your lock screen. All-day events do not receive these timed meeting notifications.
When you ask MOSS to add an event or an Apple Calendar alert, the app writes it to Apple Calendar on your device. Proposed scheduling holds may also be stored with your MOSS account. Existing Apple Calendar alerts are preserved.
Revoking Calendar access or signing out triggers removal of the server snapshot and cancellation of planned MOSS meeting reminders. If the device is offline, server cleanup can only complete when it reconnects. Deleting your MOSS account also deletes its related calendar records. None of these actions deletes the events in Apple Calendar.
AI processing requires an explicit account permission in MOSS. You can review the named providers and data before continuing, choose Not now, or turn AI processing off in Settings. Turning it off blocks new AI work on that device immediately. If the account update cannot reach MOSS while offline, the app shows that revocation is pending and retries when connected. Data already sent to a provider cannot be recalled.
Voice capture: holding to capture records and transcribes on your iPhone using Apple's on-device speech recognition. MOSS syncs the resulting text and capture metadata, not the raw capture recording. If on-device transcription is unavailable, this path does not silently upload the recording for cloud transcription.
Live conversation: when you start a live conversation, microphone audio is sent through LiveKit to Google Gemini Live, and the spoken response is returned to your device. Conversation transcripts and session events may be stored with your MOSS account. MOSS does not store the audio itself; LiveKit and Google process it under their own terms. This is a separate service from on-device voice capture.
The invite-only beta does not send saved memory, upcoming Calendar details, or daily tasks into live voice unless a separate personal-context offer is enabled for that build. When a live session has personal context enabled, MOSS can send selected saved memory, upcoming Calendar details, and daily tasks or follow-ups to Google Gemini to answer your question. The app can show the sources used for these personal answers. Once account revocation is saved, new context reads are denied; information already sent to a provider cannot be recalled. Offline account updates can remain pending as described above.
Text processing: MOSS sends captured or typed text and relevant context to Anthropic's Claude APIs for features such as extraction, briefs and other requested tasks. We do not train our own models on your content. Processing and retention by third-party providers are governed by their applicable service terms and privacy policies. Web research is unavailable in this beta.
We do not use your information for third-party advertising or sell it.
The invite-only beta includes Connections for private requests between connected MOSS accounts. Both people confirm the connection. A connection does not grant access to the other person's unrelated memory, Calendar, contacts or private tasks.
You choose which actions to allow for a person or a circle. Send once applies to the request and recipients shown. Ask me every time keeps asking. Always allow covers future matching actions for that person, or the circle members you reviewed. Adding a circle member requires permission again. You can revoke a standing permission; revoking does not recall a request already delivered. Accept and share-completion are separate explicit actions.
When you ask Moss to draft a Connections request, Anthropic receives your instruction, display name, request type or context and due time; for a single recipient it also receives that recipient's display name. Recipients receive the approved request, due time or status and connection identity; the separate owner instruction and model-drafting metadata stay on the sender side. Text you supply in a request can itself contain personal details.
Connections stores operation receipts for actions such as send, accept, decline, cancel and done. A matching receipt means MOSS recorded that action. If the app cannot confirm the outcome yet, it may show an uncertain state and keep a recovery copy rather than inventing a new attempt. A sent or stored-for-their-MOSS outcome means the request was saved for the recipient's account; it does not mean they have heard, opened or acted on it.
Moss keeps pending Connections requests, permission changes and their operation identifiers and retry payloads or recovery records on this iPhone to recover when a reply is lost. Pending payloads can include request text, selected recipients and permission or circle details. These recovery records use device-only Keychain storage tied to the signed-in account and API. On account exit, MOSS retires these recovery operations and attempts to remove their Keychain records. On-device reminder records separately keep identifiers needed to open the correct request. Deleting the app removes ordinary app storage; uninstall alone is not promised to clear Keychain items, and MOSS does not promise durable erase of those records.
You can remove or block a connection to stop further coordination. This does not erase the other person's copies of requests already received. Account deletion also leaves those recipient-owned copies in place. Do not share information you do not want the recipient to retain.
Shared requests may be checked by Anthropic for abusive or disallowed content before being sent. This check uses the request's text and type, rather than your unrelated private memory or Calendar.
If you report a shared request or connection, MOSS stores the reason, any note you add, relevant request details, and account identifiers for safety review. These report records can remain after account deletion. They expire 90 days after submission and are removed by scheduled maintenance after expiry. Backups may have separate retention periods.
Arrival and completion notifications for Connections require a separate opt-in. Their remote push alerts and on-device due reminders use generic wording and request identifiers, rather than shared request text. Notification settings determine whether alerts appear on your lock screen. A remote alert already accepted by Apple for delivery cannot be recalled.
These services may process data outside your country. We may also disclose information when required by law and will notify you unless prohibited.
MOSS is currently an invite-only beta distributed through Apple's TestFlight. If you ask to join, for example by replying to a post or writing to us, we receive and keep the contact details you give us, such as your email address and your public X handle. We use them to send your invitation and to write to you about the beta.
TestFlight also gives us information about testers and their devices: the name and email address of your Apple Account, device and operating-system details, session and usage information, crash logs, and any written feedback and screenshots you send through TestFlight. We use this to run the beta, fix problems and reply to you. We do not use it for advertising. A screenshot can show anything on your screen, so leave out information you do not want us to see.
We keep invitation details and beta feedback while the beta runs and for as long afterwards as we need to follow up. Write to support@mossconcierge.com to ask us to delete them. Messages you send to support@ or hello@ are kept so that we can answer you and keep a record of your request. Apple's own handling of TestFlight data is described in Apple's privacy policy.
Your account content remains available until you delete it or your account, subject to feature-specific expiry and replacement. Calendar snapshots are replaced on successful sync and can be removed by revoking access. Sign-in sessions expire or can be revoked.
You can delete your account in Settings → Delete Account. This removes your account and the records it owns from the active MOSS database. People you shared requests with keep their received copies, as described above. Local captures that have not synced may remain on the phone; deleting the app removes its local storage. Apple Calendar events stay in Apple Calendar. There is no App Store subscription to cancel while paid plans are off. If Apple later bills a paid plan, deleting your MOSS account does not cancel that subscription.
Some records are not removed when you delete your account.
Write to support@mossconcierge.com and we will remove records tied to your email address on request, including sign-in request records and rate-limit records that contain it, and rate-limit records for an IP address you tell us. Operational backups and service-provider records may have separate retention periods. Contact support@mossconcierge.com for questions about retained information or a data access request.
Traffic between the app and MOSS uses transport encryption. Account credentials are kept in the device Keychain and session tokens are stored hashed on the server. No system is perfectly secure. We will respond to and notify you of breaches as required by applicable law.
You can decline optional permissions, disable MOSS meeting notifications, revoke Calendar access, change Connections permissions and notifications where available, remove or block a connection, sign out or delete your account. Depending on your jurisdiction, you may have rights to access, correct, export, restrict or delete your data. Email support@mossconcierge.com to make a request. You may also contact your local data-protection authority.
Do Not Track: MOSS does not track you across other companies' websites or apps, and no third party collects personal information through MOSS for advertising. Because MOSS does not track, it does not change how it works in response to browser "Do Not Track" signals.
MOSS is intended for adults aged 18 and older and is not offered to children. If you believe a child has provided personal information, contact us so we can investigate and remove it where appropriate.
We will update this policy when our practices change. Material changes will be communicated through the service. The last-updated date above identifies the current policy.