Who's behind this
Three engineers and a shadchan.
JCard was built by four people who love this world. We are not building a dating app and we are not in a rush. This page tells you who we are, who advises us, and how to reach us.
The team.
Four people, three offices, one project.
R
Rivky Klein
Shadchan-in-residence · Brooklyn
Twelve years as a shadchan. Forty-seven shidduchim closed. The reason this product exists; the reason it stays modest. She holds every decision against the question: would this be honoring or embarrassing for a kallah?
M
Moshe
Engineering · Brooklyn
Built the privacy model and the schema. Cares about cryptography in the way one is supposed to care about Torah — line by line, no shortcuts. Wrote the covenant.
A
Avi
Design · Los Angeles
Drew every screen in this product, twice. Believes Newsreader and Hanken Grotesk can together do most of the work of any interface. Quietly stubborn about whitespace.
S
Shulamis
Community & conversation · Jerusalem
Talks to rabbanim, shadchanim, parents, and singles — sometimes thirty in a week. Brings their reactions back into the product. Will tell you when you're wrong before anyone else does.
Our circle of consultation.
We don't move on something serious without these conversations.
Eleven people we don't name publicly.
By their request — the consultation is the point, not the credit.
-
3
Three rabbanim. One Chabad, one Yeshivish, one Modern Orthodox. They read every line of the covenant before we published it. We bring them every new feature before it ships.
-
4
Four working shadchanim across Brooklyn, Lakewood, Teaneck, and Miami. They told us when we were re-inventing problems shadchanim already solved, and when we were finally helping with something real.
-
2
Two mothers of singles, who have done this twice and four times respectively. They told us, in private, what gets gossiped about and what should never reach a card.
-
1
A retired chief privacy officer from a Fortune 500. She reviewed our data architecture pro bono and refused to be paid because "shidduchim are sacred."
-
1
One single, currently in the parsha. She is the reason the on-interest default exists.
Why we built it.
A short, honest answer.
One of us has a sister. She is twenty-seven, brilliant, in the parsha for three years. The thing that wears her down isn't the dates — it's the document. Every shadchan reformats it. Every family asks for a different version. Her photo travels in group chats she didn't authorize. Family details get summarized in ways that aren't her.
We thought: the resume isn't the problem; it's the format. The single document. The standard. The thing that doesn't change shape every time it crosses a kitchen table. We started sketching what that would look like in Elul of 5784. We have been showing it to people, quietly, ever since.
"The product is supposed to be invisible most of the time. The shadchan should still be the shadchan. The single should still be the single. JCard is the scaffolding that disappears once it's doing its job."
We are not in a rush to be famous. Our first hundred users will be onboarded by hand, by Rivky. We will say not yet to features more often than yes. If we get the foundation right, the rest follows.
Questions people actually ask us.
If yours isn't here, write to us.
Is JCard a dating app?
No. There is no carousel, no algorithm matching singles to other singles, no search across profiles. Every shidduch passes through a human shadchan. The covenant says it; the product enforces it. If we ever start to look like a dating app, leave.
Can a shadchan I've never met see my card?
Only if you choose to share it with them. The card is not public, not browsable, not searchable. You send a link; only that recipient can open it.
What does my rabbi need to bless this?
Show him
the covenant. It's nine promises in writing, signed by the founders. We've designed the product specifically to be defensible by a careful rav: no algorithmic matching, no public profiles, no data sale, no fees to families, and an absolute right to delete.
Will dating sites scrape this?
No. Cards are never indexed; the URLs are unguessable and per-recipient. Even if a URL leaked, only the person it was created for can open it. There is no public profile to scrape.
What happens if you go out of business?
Every card is exportable to a PDF by the single, at any time, with one click. If we ever wind down, we will give 90 days' notice, export every card, and delete everything. Our covenant requires this.
Do you ever delete data?
Yes. When you delete your card, we delete it — the data, the URLs, the activity log, all of it. No soft delete, no archive, no retention. Within seven days the data is gone from our backups too.
Can my parents see my card?
Only if you share the link with them. You can give them the same access as a shadchan, or a more limited view, or no view at all. Adult singles control their own card; family access is a choice, not a default.
Why now?
Because the resume has been getting worse for fifteen years and the platforms that have tried to fix it have all chosen to look like dating apps. The community deserves better infrastructure that respects how it actually works. We waited longer than we should have to build it.
Real humans answer.
+
We're not hiring right now.
If you're a shadchan, a designer, or an engineer who reads this page and feels at home — write anyway. We'd rather know you when the time comes.