DaySlice splash - a voice waveform and the words 'Day Slice'
DaySlice - today's actions extracted from a spoken journal, with a day-streak ring
DaySlice Today screen - 'You've spoken today', a mic to add more, and a quiet last-fortnight strip
DaySlice - a year-in-pixels mood history for 2026, on device
DaySlice sign-in - 'Your day, in your voice', a one-time code, no account
DaySlice · a privacy-first personal agent · 2026

I built my own personal agent - so I wouldn’t have to trust someone else’s.

Every personal-AI product wants your whole life: your notes, your calendar, your voice, your patterns. The price is handing all of it to someone else’s cloud, on someone else’s incentives. I didn’t want to pay it. So I’m building DaySlice for myself: a privacy-first personal agent, my data, on my device, owned end to end. It’s in-flight and deliberately small. This is the decision behind it, not the feature list.

My role
End-to-end - design, PM, iOS
Read
7 min
Status
In-flight · on-device

Start reading
The decision
Don’t hand my life to someone else’s product
The bet
An agent is only useful if you trust it
What’s different
Private by default · owned · restrained
Status
In-flight - built slowly, for myself
THE DECISION (01)

Why build my own?

Personal agents are about to be everywhere, and every one of them runs on the same bargain: give us everything you’ve got, and we’ll make your life easier. It’s true that an assistant has to know you to be useful. But “know you” and “own your data” usually come in the same box: hosted on someone else’s servers, tuned to someone else’s business model.

I wasn’t willing to make that trade with the most personal data I have. So I made a different product decision: build the agent myself, for an audience of one. Mine, on my device, answering to me. DaySlice started as a voice-first journal where restraint was the whole point, and grew into the privacy-first personal agent I wanted to exist. No one else was going to build it on my terms.

WHAT MAKES IT MINE WHAT MAKES IT MINE
WHAT MAKES IT MINE (02)

What actually makes it mine

Each of these runs against what the big personal-AI products choose. They aren’t settings you switch on. They’re the premise the whole thing sits on.

DaySlice asking for on-device Speech Recognition access - a system permission dialog over the Today screen
Private by default

My data stays with me.

Built to keep my information on my device, not parked in a cloud I don’t control. Privacy is the starting point everything else has to respect. It’s not a setting buried three menus deep.

Even speech is a permission I grant on my own device. The recording doesn’t leave to be processed somewhere else.

on-device
DaySlice Today screen - almost empty: a line of text, a mic, and a small fortnight strip
Restraint is the product

It does less, on purpose.

It began as a journal where the whole discipline was subtraction, and that stuck. It respects your attention instead of fighting for it.

The everyday screen is almost empty: you’ve spoken today, or you haven’t. Nothing else competes for your attention.

subtraction
DaySlice 2026 history - a year of days as a mood mosaic, all stored on device
Owned end-to-end

It answers to me.

No ad model, no growth team, no roadmap quietly pulling it somewhere I didn’t ask for. The only incentive it serves is mine.

A whole year of my days lives in one place I control.

my incentives only
DaySlice - 'Arunabho95', a 23-day streak, and today's actions pulled from the spoken journal
Built for one

An audience of me.

Designed for a single user, so I never average a decision down to suit everyone. I’m the only user, and I feel every rough edge daily. I can’t lie to myself about whether it’s good.

That’s literally my handle on the screen. It speaks back my day, my streak, and the actions it pulled from it.

user of one
1
The only user it answers to - me
0
Accounts, sign-ups, or cloud logins
on-device
Built to keep my data with me
in-flight
Built slowly, on my own terms
THE TRADE-OFF THE TRADE-OFF
THE TRADE-OFF (03)

What building your own costs

This isn’t free. The big products are polished and full-featured because hundreds of people work on them, and because your data feeds them. Mine is slower and smaller and in-flight. I’m the designer, the PM, and the iOS developer, and I’m the user finding every rough edge myself.

But that’s the point. What I get back is trust. I know exactly what it does with my data, because I built every part of it. For a tool meant to hold your whole life, trust is the feature I actually needed.

DaySlice splash - a voice waveform and the words 'Day Slice', a daily voice journal
Where it startsYour day, in your voice - the whole interaction is talking, then it goes quiet again.
DaySlice sign-in - 'What's your email? We'll send you a 6-digit code' - no account to create
No empireGetting in is a one-time code, not an account in someone else’s growth funnel.
A personal agent is only worth using if you trust it. The most direct way to trust one is to build it yourself. The decision, in one sentence
WHY IT’S WORTH IT WHY IT’S WORTH IT
WHY (04)

Why it’s worth doing slowly

Building it teaches me things using someone else’s never would: on-device constraints, what an agent should and shouldn’t do on your behalf, how little it actually takes to be useful. That learning is half the reason it exists.

DaySlice is still in-flight, and I’m fine with that. Being the only user is an advantage here. I build exactly the agent I’d trust.