Activity log
Updated 22 September 2026
What changed, and what is still broken. We keep the open problems here as well as the fixes, because a log that only lists wins is no use to anyone testing against it.
Deleting your account now gives you thirty days to change your mindImproved
Deleting your account used to happen the moment you confirmed it, with no way back. It now takes effect immediately but deletes permanently after thirty days. Everything is hidden straight away - your cards stop opening, and the people you have met see that you have gone - and nothing is actually erased until the thirty days are up. If you change your mind, just sign in again before then: the deletion is cancelled, your cards go live again, and your memories, meetings and follow-ups are exactly where you left them. You will get an email when you delete and another before the deadline, each naming the date, and those are the only emails a closed account receives - no nudges or reminders while you are on your way out. After thirty days it is permanent and cannot be undone, as before. People you connected with still keep their own record of having met you either way.
To test: Delete your account from Settings, confirm the sheet now says thirty days, then sign in again and check that everything is back and you are told the deletion is off.
When someone fixes their name, your list of people shows the correctionFixed
Opening someone's card showed the name they have now, but your list of people still showed the name they had when you met - so a corrected spelling looked wrong in one place and right in the other. The list now reads the card, so an update by them appears for everyone who has connected with them. People you added yourself, or who reached you through a shared card rather than their own, keep exactly the details you saved: those are your record of someone, not theirs to change.
To test: Ask someone you have connected with to correct their name on their card, then open your People list and confirm it reads the new name.
Someone who has left ehllo now says so in your People listFixed
When someone deletes their ehllo account, your record of having met them is kept on purpose - it is your memory of the meeting, not theirs to remove. What you were shown afterwards was a blank: their card was gone and nothing explained why, so the entry looked broken rather than explained. Those connections now read “No longer on ehllo”. Nothing is deleted from your list, and people who are still here are unaffected.
To test: Open People and look at anyone who has deleted their account: the entry reads No longer on ehllo instead of appearing empty.
Signing in no longer gives up on a brief loss of signalFixed
On a phone with a weak or changing connection, signing in could end with you being signed straight back out again, with nothing on screen explaining why. After the code was accepted the app set your account up, and if it could not reach the server it tried again three times over 1.6 seconds and then gave up - long enough for a good connection, not long enough for a phone moving between cells. It now keeps trying for up to 20 seconds before giving up, and when the server does answer and genuinely refuses, it still stops quickly rather than making you wait. The report that went with this had a healthy account behind it; nothing was ever wrong with the account itself. Separately, the check that catches a mistyped email address used to take nearly a minute to decide when the domain's name servers were broken rather than simply absent - so a typo meant a very long wait before anything was said. It now answers in about five seconds and still refuses the address, and a correctly spelled domain is waved through in a fraction of a second as before.
To test: Sign in on a phone with a poor connection and confirm you reach the app rather than the sign-in screen. Sign in normally and confirm the code still arrives as quickly as before.
Sign-in codes are working again on the live siteFixed
Signing in on ehllo.io with an email address failed with "We couldn't send the code. Please try again." for every user. Two problems were stacked on top of each other: the production email rate limit had been left at 2 codes per hour instead of 30, and the backend function that sends the code through Resend had stopped starting up at all after an earlier deploy. Both are fixed - the rate limit is restored and the function redeployed from the same working source staging already runs.
To test: On ehllo.io, enter an email address on the sign-in screen and confirm a 6-digit code arrives.
The website now names EHLLO LTD, and search engines can read itImproved
The public site makes the company behind ehllo verifiable. The footer carries “© 2026 EHLLO LTD. All rights reserved.” and the registered-company line — a company registered in England and Wales, Company No. 17434728, contact product@ehllo.io — and the privacy policy and terms name EHLLO LTD as the operator and data controller. The consumer brand stays “ehllo” everywhere in the marketing copy. On the technical side: a real /sitemap.xml and /robots.txt, canonical URLs, Open Graph and Twitter cards, Organization and SoftwareApplication structured data carrying the company number, a homepage title of “ehllo — Remember Who You Meet”, and www.ehllo.io now redirects to ehllo.io so there is one canonical address. Google Search Console is verified and reading the sitemap. The staging site is set to noindex so it never competes with the live one.
To test: Open the site footer and the privacy / terms pages and confirm EHLLO LTD and Company No. 17434728 appear. Load https://ehllo.io/sitemap.xml and https://ehllo.io/robots.txt directly. Visit https://www.ehllo.io and confirm it lands on https://ehllo.io.
The privacy policy now spells out how your data is protectedImproved
A new "How we protect your data" section describes the actual measures in place: encryption in transit and at rest, a separate encrypted store for connected-account tokens that only a process acting for the owning account can read, per-account isolation at the database, and restricted internal access. "Retention and deletion" now gives a concrete window and states that disconnecting a Google or Microsoft account deletes its stored tokens. The AI section states plainly that data from Google APIs, including Google Workspace APIs such as Calendar, is never used to train non-personalised models.
To test: Open the privacy policy from the site footer and read the "How we protect your data" and "Retention and deletion" sections.
Homepage draft: clearer cards, a mobile-beta section, and the release-checklist link retiredImproved
On the in-progress homepage: the Remember / Understand / Act cards drop the low-contrast emoji for solid icon badges and lose the tiny question labels; the relationship-continuity pair matches height and the meeting card follows the lifecycle-card layout, with the portrait re-cropped to sit properly; the "Wherever people meet" cards get frosted-glass "Next" chips that now link to sign-in; the privacy section swaps its padlock emoji for a real icon and loses most of its empty space; and there is a new section inviting people to join the iOS / Android beta. Separately, the "Consumer release checklist" button has been removed from the top of this page (the checklist itself still lives at /activity/roadmap). None of the homepage changes are on the live site yet.
The consumer release checklist is now visible and accountableNew
The Activity Log now links to one ordered checklist covering new, existing, guest, offline and cross-device users across iOS, Android and the current consumer web. Items are checked only after the required deployment and device or browser evidence exists. Capture recording remains mobile-only; web verifies the saved encounter rather than recreating the recorder.
To test: Open Consumer release checklist at the top of this page and confirm every phase shows its completion state and overall progress.
AI, capture relationships and group follow-ups close their loose endsFixed
A fresh AI chat no longer turns a stray one-word voice result into its opening question, recent chats can be removed across signed-in devices, and relationship history keeps its last good state while refreshing. Captured names now match saved connections despite spacing or punctuation differences. Email and calendar follow-ups can reach every attendee together on mobile and web only when every recipient has a usable email, so nobody is silently left out. Capture itself remains a mobile-only experience; web receives the resulting meetings and follow-ups, not the recording flow.
To test: On mobile, start a fresh voice chat, delete a recent chat by holding it, and open a connection while history loads. From a meeting with two emailed attendees, choose Everyone for an email or calendar follow-up on mobile and web; confirm both recipients are present. Confirm web has no Capture entry point.
Something behaving oddly? Tell us what you did and what happened, and it will appear here.