HushAbout the Hush blog
Who publishes it
The Hush blog is published by MYRIADLOOP PTE. LTD., the Singapore company that makes Hush, a messenger whose home screen is a keypad: each six-digit code opens one chat or one private space of your own photos and videos. The blog exists to answer phone-privacy questions honestly and to show where Hush fits, including where it does not.
Why we write
People arrive here asking practical questions: whether an iPhone can hide one conversation, what a notification setting really changes, where a hidden photo still shows up. Most of the answer is usually a built-in setting on your phone, so that comes first. Then the limit of that setting. Then, where it is relevant, how Hush handles the same problem. A post has to be useful even if you never install Hush.
How posts are made
Posts here are researched, written and fact-checked by AI systems operated by MYRIADLOOP PTE. LTD., the Singapore company that makes Hush. No person writes a post, and no person reads a post before it is published.
What people do: we wrote the rules every post must follow; we keep the list of what Hush does and does not do that every sentence about Hush is checked against; we correct or remove anything wrong and record the change on the post; and we answer for every word here.
What the automated check does: a second AI system, given none of the writer's notes, reopens every cited source it can fetch and marks each factual sentence as supported, unsupported or opinion; a post is not published while any sentence is marked unsupported. This is an automated check, not a human review; it is good at catching a wrong citation and worse at catching a subtle misreading.
Every post lists its sources and the date they were read. We read documentation; we do not test other companies' apps on devices, and menus vary by version, device and region. Where we describe Hush, we describe it from its own source code and say when a behaviour has not been verified on a released build.
This disclosure is also how we meet transparency rules for AI-generated text, including the EU AI Act.
What we will never claim
- That Hush, or any setting, makes something impossible to find. Hush is built for one situation: someone picks up your unlocked phone. Hush provides code-based access and a discreet keypad interface; it is not end-to-end encrypted. We say so on every page that mentions it.
- That an account cannot be linked to a person, that a code is a security guarantee, or that any allowance has no limit.
- Prices or trial offers. Those live in the app and the stores, where they are current.
- Anything about catching or monitoring another person. We write to the owner of the phone, never to someone looking through another person's phone, and never to children about getting around supervision.
- Anything about relationships. The blog is about phones and settings.
Sources
Facts about other apps and operating systems come only from their makers' own documentation: help centres, release notes and developer documentation. Facts about Hush come from its source code, qualified by platform and release where that matters. We quote sparingly, with attribution and a link. Lists and community forums are read to understand what people ask, never cited as evidence.
Title cards
The image on each post is a template-generated title card, not a photograph or a screenshot. Screenshots inside posts come from a fixed set of captures whose origin is recorded in the repository.
Corrections and contact
If you find an error, write to help@myriadloop.com. We correct or remove anything wrong and record the change on the post, with the date.
