Before you download anything like this, there's one thing you actually want to know: if you swipe on a card, is your partner going to see it? You've been the one doing the reaching in this relationship, and you know how a single "not tonight" can land like a verdict. So the thought of them scrolling a list of everything you were and weren't into feels like the opposite of safe.
Here's the honest answer: no. On peek your partner cannot see what you swiped. Every swipe you make stays private between you and the app. They only ever see a card when you both independently swipe "yum" on the same one, and that becomes a match. Every "ick", every "maybe", every card you were curious about but weren't sure of stays yours. Nothing you swipe on your own is ever shown to them, and that list you're dreading doesn't exist for them to read.
What exactly stays private, and what becomes a match?
Here's the honest breakdown of who sees what. This is the whole mechanic, and it's simpler than you'd think.
| What you do | Who can see it |
|---|---|
| Swipe "yum" on a card | Only you, unless your partner also yums it |
| Swipe "ick" on a card | Only you, always. Never shared |
| Swipe "maybe" on a card | Only you, always. Never shared |
| Both of you "yum" the same card | Both of you: it becomes a match |
So the only thing that ever crosses over is a mutual yes. You both had to say it, separately, in the dark, before either of you finds out. There's no feed of your solo swipes, no "here's what your partner passed on", no scorecard. If you loved a card and they didn't, they'll never know you loved it. If they loved one and you didn't, you'll never know either. The passes stay quiet. Only the overlap lights up.
That's not a privacy setting you have to switch on. It's how peek is built. Your reactions stay private until you both match, by design, not by preference.
Why does keeping my swipes private actually help us?
Because privacy is what makes honesty possible. This is the part that sounds counterintuitive and turns out to be the whole point.
When you think your answer might get read, judged or thrown back at you later, you don't answer honestly. You answer safely. You round yourself down. Half the reason the two of you stopped bringing this stuff up out loud is that saying it first, to a face, means risking a flinch. Take the flinch off the table and something loosens. You can finally be honest about what you're curious about, because nobody's watching you be curious.
Desire doesn't just switch on to order. It needs to feel safe first, and nothing shuts it off faster than the fear of being turned down or leaned on. That's the brake. Take it off and there's finally room for the other half of the equation: the novelty of a card neither of you has thought about in years, the small thrill of finding out you both said yes, the feeling of being wanted without anyone having to ask for it. Nobody goes first, nobody gets rejected and the reveal only happens on a mutual yes. If you've been stuck in the loop where every attempt to talk about it ends the same tired way, this is a different mechanism, not another version of the same conversation. It's the same reason a private swipe can take the sting out of initiating when a "not tonight" keeps landing hard.
Won't my partner feel ambushed if I bring them an app?
It's a fair worry, and worth naming, because if you're reading this you're probably the one who'd download it first. The fear is that handing your partner an app reads as a campaign: proof you've been keeping a tally, one more bit of pressure dressed up as fun.
Here's why the privacy design defuses that. peek doesn't ask your partner to respond to you. It asks them to answer for themselves, on their own phone, with the same privacy you have. They're not reacting to your list. They don't have a list. They swipe honestly in the dark exactly like you do, and the only thing either of you learns is what you both already said yes to. That symmetry is what keeps it from feeling like a scorecard. It lands as a game you're playing together, not a demand you're making. If the space between you has been quietly widening for a while, this is a small, low-stakes way to find out what's still there. It works whether the drift crept in over years or arrived with everything else after kids.
Key takeaways
- Your partner cannot see what you swiped on peek. Every swipe stays private between you and the app.
- Only a mutual "yum", where you both independently like the same card, becomes a match you see together.
- Your "ick" and "maybe" swipes are never shared with your partner, ever.
- Privacy is the feature, not a setting: removing the fear of being read is what lets both of you answer honestly.
- Because your partner answers for themselves in private too, it feels like a shared game, not a demand or a scorecard.
If talking about it keeps hitting the same wall and you want a different way in, peek gives you one where nobody has to expose themselves first. You can download peek on the App Store or Google Play, swipe privately tonight and only ever surface what you both want.
Frequently asked questions
Can my partner see what I swiped before we match?
No. Your swipes stay between you and the app until you both like the same card. That's the moment it becomes a match you can see together. Nothing you swipe on your own is shown to them before then.
Does peek tell my partner which cards I passed on?
No. Your "ick" and "maybe" swipes are never shared. If you pass on a card, your partner never sees that you saw it, let alone how you reacted. Only mutual yeses ever surface.
Do we both need the app for this to work?
Yes. You each use peek on your own phone. That's exactly how your swipes stay private until you both match. It's the mechanism that makes the privacy real.
Will my partner know if we don't match on something?
No. There's no notification, no list and no scorecard for the cards you don't both like. A card that only one of you yummed simply never comes up. You only ever find out about the overlap.
