Your privacy at Hello Mochi
Hello Mochi is a personal relationship manager operated by Ryu Pradana. Questions and privacy requests can be sent to support@hellomochi.app.
What we store
We store your name and email, your Google account identifier if connected, and a salted password hash if you choose email sign-in; the people, notes, interactions, circles, plans, images, and preferences you choose to save; and subscription identifiers and status. Your address book is private to your account. For uploaded avatars and circle symbols, we keep an optimized image and its crop so you can adjust it later, including the parts outside the displayed crop. Embedded photo metadata and original filenames are discarded. We do not ask for access to Google Contacts, Gmail, Calendar, or Drive.
How your information is used
Your saved information powers your desk, reminders, connection map, and drafts. Messages are sent manually by you. You can sign in with Google or a verified email and password. Stripe handles payment details. Card numbers are not stored by Hello Mochi. We do not sell your address book or use it for advertising.
Storage and service providers
Data is stored in PostgreSQL on our hosted server and in private backups. HTTPS protects data in transit. The operator can access infrastructure for maintenance and support; this is not end-to-end encrypted storage. Google and Stripe process information needed to provide their services under their own privacy policies.
The public demo keeps its sample desk and your demo edits in this browser tab. The contents of demo edits are not uploaded to our server. We collect the same limited usage events and performance measurements described below, without names, notes, or entered values. Resetting the demo replaces that tab’s sample data, and demo data is not copied into your account when you sign in.
Account emails
Our server sends email verification, password recovery, and password-change notices. Pending registrations and their password hashes expire after 24 hours unless verified. Password-reset links expire after 30 minutes. Passwords and verification tokens are excluded from application logs and analytics. The mail service temporarily queues messages for delivery; delivery logs contain sender and recipient addresses and delivery status and are retained for up to seven days.
Usage analytics and public-page recordings
We use self-hosted Umami on our server to understand visits, general feature usage, and loading performance across the public site, demo, and signed-in desk. This includes browser and device information, approximate location, referral origins, generic page names, and actions such as saving a person or opening checkout. Analytics does not include your account identifier, email, contact identifiers, names, notes, messages, uploaded images, filenames, search terms, or other entered values. URL queries and fragments are removed. We do not identify you with an analytics account ID or add analytics cookies or persistent visitor identifiers.
On the landing, pricing, privacy, and terms pages, we also collect click and scroll heatmaps and sample 15% of page visits for session replay, up to five minutes per recording. Text and input contents are masked. Authentication forms, the demo, and the signed-in desk are excluded from heatmaps and replay. Recording stops when you leave those public pages.
Usage statistics and heatmaps are retained to compare long-term trends. Replay visits, including saved recordings, are removed after 30 days by daily cleanup; private backup copies expire with the backup retention schedule. Analytics access is restricted to the operator.
Account reporting
The operator has a private account report showing your account name and email, signup date, and the last time your visible, signed-in desk reported activity. When analytics is enabled, opening the desk or interacting with it can update this last-active timestamp, at most once per minute. Idle or hidden tabs do not keep it active. We store only the latest timestamp; this report does not collect what you type, your address-book contents, or a history of your actions. Activity reporting honors the browser analytics choices below. Signup totals use actual account-creation records, including existing accounts and signups whose browsers block analytics.
Deleting your account removes its name, email, and last-active entry from this report. Anonymous daily signup counts are retained for long-term statistics.
Cookies, logs, and analytics choices
We use an essential session cookie to keep you signed in. We do not add advertising cookies. Analytics honors Do Not Track and Global Privacy Control: enable either browser signal before visiting or reloading to opt out of analytics, last-activity reporting, and recordings. Anonymous signup counts remain based on account registrations. Limited operational logs help diagnose errors and abuse; they should not contain your private notes, passwords, or payment details.
Your choices
You can edit and archive people, export your address book, sign out, or delete your account in Settings. Account deletion removes your app records and cancels remaining subscriptions. Private backups are retained for up to 14 days. Stripe may retain payment records under its own retention requirements. We keep data for active accounts so you can return to your desk.
Updates and contact
This page describes the current service. We will update it when data practices change. Contact support@hellomochi.app for access, correction, deletion, or other privacy questions.