Privacy policy

Last updated 14 October 2026

Moss is a personal assistant built by Alya for personal use. It is not a public service: it only answers its owner's Telegram account and ignores everyone else. This page explains what Moss handles and how.

What Moss stores

• Messages, photos and voice notes the owner sends to Moss in Telegram, and Moss's replies (recent chat history only).
• What the owner asks it to track: food, water, supplements, workouts, steps, sleep, cycle, weight, spending, budgets, bills, tasks, work notes and settings.
• Purchases from the owner's own receipt emails and Apple Pay taps, when the owner has set those up.

Google user data

If the owner connects Google Calendar, Moss uses the calendar events permission only to show, add, change and delete events when the owner asks, and to send reminders before them. The sign-in token is stored in Moss's own database.

Receipt emails are read by a script in the owner's own Google account and only receipt-like emails are sent to Moss.

Moss's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never shared with anyone except as described on this page.

Where data goes

• Google Cloud (Cloud Run and Firestore, Singapore region): where Moss runs and where its data is stored.
• Google Gemini API: reads each message, photo or voice note to understand it and reply.
• TypeSafe (Jev): receives the text of each message to decide which tools Moss needs.
• Telegram: delivers messages between the owner and Moss.

Nothing is shared with anyone else, and the web dashboard is private, behind a one-time login link.

Deleting data

The owner can ask Moss to delete any entry, clear its chat memory with /reset, disconnect Google Calendar at myaccount.google.com/permissions, and delete all stored data from Google Cloud at any time.

Contact

Questions about this policy: alyajejai@gmail.com