Quick follow-up from Cedar Labs
heldCedar Labs · team@cedarlabs.io
Hi Ayush, a quick note from our side — the review is taking a little longer than planned this cycle. Nothing is needed from you right now, and we appreciate your patience.
You don't lose the offer. You lose the email.
An interview invite lands at 2am, under sixty other things, and never surfaces again. Applied moves the row for you. No AI reads your mail, and the message body is never stored.
Sample data, the real board. Not a video: drag a card, open a row.Open the full demo →
- applied
Waypoint Robotics
Software Engineer, Controls
Thanks for applying
- assessment
Kestrel Dynamics
Software Engineer, Simulation
Next step: online assessment (90 min)
- interviewing
Northstar Systems
ML Engineer
Interview availability — technical round
- offered
Larkspur Systems
Staff Software Engineer
Your offer from Larkspur Systems
- rejected
Atlas Freight
Software Engineer II
Moving forward with other candidates
Larkspur Systems
Staff Software Engineer
appliedoffered
What it reads
The preview ends before the verdict. Applied reads past it.
An interview invitation spends its first two hundred characters being polite. Gmail's preview ends right where the inviting begins, and for most tools the preview is all there ever is.
So Applied reads it twice, live in your tab: once on the preview alone, once on the whole body. The preview reads as a routine acknowledgment. The body holds the invitation.
So the invitation surfaces on your board instead of under sixty other things.
The same body, classified twice
Your application to Northstar Systems
Northstar Systems Talent · talent@northstarsystems.dev
Hi Ayush, thank you for applying to the ML Engineer position at Northstar Systems, and for the detail you shared about your work. We have been reviewing applications carefully over the past two weeks,
and we would like to invite you for an interview with the team. The technical round runs about an hour, and we can work around your schedule — could you share your availability for next week? We look forward to speaking with you.
preview only
applied0.90
a routine acknowledgment, just as surely. Wrong.
whole body
interview0.90
the invitation, found
A synthetic email. The verdicts are computed live in this tab.
The tally behind each verdict
preview only
- interview
- 0
- applied
- 6
whole body
- interview
- 9
- applied
- 6
Two readings of one mail, and only the text differs. A phrase can only count toward a verdict if the reading can see it, which is why these two columns do not agree.
Live verdict, computed in your tab
One mail, read past its preview, then reduced to the record.
Your application to Northstar Systems
Northstar Systems Talent · talent@northstarsystems.dev
Hi Ayush, thank you for applying to the ML Engineer position at Northstar Systems, and for the detail you shared about your work. We have been reviewing applications carefully over the past two weeks,
and we would like to invite you for an interview with the team. The technical round runs about an hour, and we can work around your schedule — could you share your availability for next week? We look forward to speaking with you.
preview only
applied0.90
a routine acknowledgment, just as surely. Wrong.
whole body
interview0.90
the invitation, found
A synthetic email. The verdicts are computed live in this tab.
Recorded in the app
How it reads
Nothing is filed on a subject line.
A rejection can open like a thank you. An invitation can open like a formality. So Applied reads the whole message and files it on what it says, not on how it starts.
So when a row moves on your board, you can see the mail that moved it.
The sandbox on the demo page runs the same reading this page runs, in your own browser, and you can hand it any mail you like.
When it isn't sure
Not every mail gets a verdict. That's the point.
Cedar's note commits to nothing: no next step, no decision, just patience requested. Applied reads it whole and comes back unsure, and unsure is not a verdict.
A mail Applied will not guess about
So the mail is held, not filed: it joins the review queue on your board, question still open. Your decision files it, and the record keeps that it was your decision and not a guess.
And what it holds is the mail you would have wanted to read yourself.
The real review queue, the one on your board
A held mail doesn't disappear; watch where it goes.
Quick follow-up from Cedar Labs
heldCedar Labs · team@cedarlabs.io
Recorded in the app
What you see
The mail becomes the move.
An assessment invitation, already read, and the row it left behind: already sitting in the board's assessment group, carrying the deadline the message named. Applied moves the row for you, and this is what that looks like.
The same invitation, already read, and the row it left behind: out of applied and into the board's interviewing group, on what the message said. Applied moves the row for you, and this is what that looks like.
Recorded in the app
The row that mail left behind
Northstar Systems
ML Engineer
applied
The mail that moved it stays one click away, behind the row it moved. That is the trail this recording opens on.
You check one board, not sixty threads.
Privacy
Read in flight. Never kept.
Applied connects with one Google permission, gmail.readonly. It can read your mail; the grant carries no right to send, delete or change anything.
Applied reads a message's body to classify it, then discards it. No body is stored, sent back to your browser, or written to a log. What is kept: a subject line, a sender, a date, Gmail's own short preview, and the verdict.
The same email, as the database keeps it
Your application to Northstar Systems
Northstar Systems Talent · talent@northstarsystems.dev
- subject
- Your application to Northstar Systems
- sender_email
- talent@northstarsystems.dev
- body_snippet
- Hi Ayush, thank you for applying to the ML Engineer position at Northstar System…
- classified_as
- interview
- body_text
- never written
- body_html
- never written
A synthetic email. The verdicts are computed live in this tab.
That is a claim about code, so code enforces it. A test feeds Applied mail whose bodies carry a marker string, then hunts for that marker everywhere a body could have left a trace: every column of every table, every log record, and every response handed back to it, the one that does the reading included. If it turns up anywhere, the build fails. The check runs on every change to the part of Applied that reads your Gmail. backend/tests/test_body_is_never_persisted.py
The System Card is the full walkthrough: how it reads, how it is tested, and what it keeps: read it. The privacy policy states what every sentence here describes: what Applied reads, and what it keeps.
Recorded in the app
Access
One hundred seats.
A seat means the filing stops being your job.
Google caps an app awaiting verification at 100 Gmail accounts. Those are Applied's seats while the review runs, and Applied fills them one at a time.
No seat? Run it on your own exported mail instead. Ask Google for a Takeout .mbox, and when the archive lands in your inbox, drop it in: it is read and filed in your browser. Nothing uploads.
Your inbox already holds the verdict.