Rhythms that reset themselves
Decide how often a relationship deserves attention — every fortnight, every six weeks, twice a year. Record a real conversation and the clock restarts from that day, without you touching it.
personent is a private relationship memory for iPhone and Android. It keeps the people and organisations who matter to you, remembers what was said last, and tells you when someone is due a word — with no account, no server, and nothing ever leaving your phone.
personent has not been released yet — there is nothing to download today, and no date is being promised. Send a blank email and you will hear from me once it is on the App Store and Google Play. Your address is used for that one email and nothing else, then deleted — what happens to it.
The app has to answer three questions in seconds.
Why it exists
You meant to reply. You said you would check in once the funding round closed. You met somebody genuinely interesting at an event in March and you both meant it when you said let's stay in touch.
Then a fortnight went by, and then a quarter, and now getting back in touch feels like an apology. Nothing went wrong. You were busy, and a relationship with nobody holding the thread quietly lapses.
Your phone already remembers where you have to be. It ought to be able to remember who you are losing.
Your Contacts app remembers phone numbers. A CRM manages sales pipelines. personent remembers the relationship itself.
How it works
Everything in personent serves a single cycle. The fifth step is the one that matters: when you record what happened, the next reminder reschedules itself. You never maintain the system that is meant to be maintaining you.
Add someone once — name, where they work, why they matter, and how often the relationship deserves attention. That is the whole of the data entry, and it is designed to be over quickly.
When it has been too long, or you are still waiting on a reply, the app says so. Quietly, on your device, at a time you chose.
You call, you write, you meet. personent does not do this part and never pretends to. It only makes sure you knew to.
Logging what happened is meant to be the quickest thing in the app. "Called Sarah — discussed the pilot." Done. The timeline keeps it for the next time you need the context.
This is the part that makes it work. Logging a real interaction restarts the rhythm from that day automatically. You never reschedule anything by hand.
In the first version
No pipelines, no deal stages, no dashboards measuring your friendships out of a hundred. Six things, done properly.
Decide how often a relationship deserves attention — every fortnight, every six weeks, twice a year. Record a real conversation and the clock restarts from that day, without you touching it.
Sent something and heard nothing back? Mark it as waiting and choose when to be nudged. Log "received reply" and the whole thing closes itself.
The app opens on a short briefing: what is overdue, who is due a catch-up, who you are still waiting on. When there is nothing, it tells you that you are clear and leaves you alone.
Every connection has a timeline — calls, meetings, messages, notes. Start the next conversation already knowing where the last one finished.
A task can stand on its own or hang off a person or an organisation, with a due date, a note and a priority. Complete it, snooze it, move it.
Notifications are scheduled locally by your device — there are no push servers. They are gathered up rather than constant: "four connections need your attention today", not four separate buzzes.
Also in the first version: people linked to the organisations they work for, groups you define yourself, the context note explaining why someone matters, search and filters, archive, light and dark themes, an optional Face ID or fingerprint lock, private notification text, a complete backup file you choose the home of, and CSV export — so you are never locked in.
Privacy
This is not a promise to handle your data carefully. It is an architecture in which we never receive it. Everything below is a property of how the app is built, not a policy we could quietly change.
No sign-up screen, no email address to hand over, no password. You open the app and start using it.
There is no database of your relationships anywhere except your own phone. We could not look at your network if we wanted to.
No analytics SDK, no advertising SDK, no crash reporting, no advertising identifier. We cannot tell whether you use the app, or how.
Not "we promise not to use it" — the app does not request the permission at all, so it has no means of sending anything anywhere.
The app never asks for access to either. Send an event to your calendar and your operating system takes it from there — nothing reads what is already in them.
A full backup file you choose the location of, plus CSV export. Delete the app and the data goes with it — there is nothing left behind for anyone to ask us for.
Where it is
It would be easy to put two store badges here and hope you did not click them. Here is the real position instead.
The product is specified in full, and the design language — colour, type, spacing and the accessibility rules — is settled. The privacy policy you can read today is the one the app is being built to; if it changes before launch, the change is published there with a new date.
The iPhone and Android apps themselves. Both are written natively — Swift and Kotlin — because an app that never touches a network should feel like it belongs on the device it is running on.
A release date. It goes to the App Store and Google Play when it is genuinely good and not a day sooner, and you will not find a countdown on this page.
Free at launch. No subscription, no adverts, and nothing about you sold to anybody, because there is nothing to sell. A paid one-time unlock may follow in a later version; it would be optional, and the free version you already have would not start charging.
One email from a person, not a mailing platform. No list, no newsletter, no tracking pixel — your address sits in one mailbox, is used for that email and nothing else, and is deleted afterwards or sooner if you ask. The policy on that is here.