How Shyne Works

The single greatest barrier to real-world social interaction is not shyness. It is uncertainty.

The uncertainty of whether an approach is welcome. Whether the other person is open, interested, or simply available. The uncertainty that forces the initiator to bear the full social cost of the approach before knowing whether it is wanted.

Dating apps tried to solve this by moving interaction entirely online — but they replaced one problem with another. Endless swiping. Algorithmic sorting. Conversations that never leave the screen. The real-world connection that people actually want gets lost somewhere between a match notification and an unread message.

Shyne takes a different approach. Instead of replacing real-world interaction, it makes it easier.

Shyne is a proximity-based social discovery layer for real-world venues. Users check into a shared physical environment — a bar, a club, a festival, a campus event — and become visible to others in the same space.

From there, you can send structured "approach signals" to people you want to meet. The receiver controls what happens next through a fixed response menu. No unsolicited messages. No unexpected approaches. Every interaction starts with consent.

Shyne is not a dating app, a chat platform, or a social network. It is a real-world interaction layer that makes the hardest part of meeting someone — the first step — structured, low-risk, and consent-first.

Every interaction on Shyne follows the same simple loop. It is designed to move you from digital intent to a real-world conversation as quickly and comfortably as possible.

When you arrive at a venue, you check in by scanning a QR code at the door. Check-in is always explicit — Shyne never adds you to a venue automatically. Before you commit, you can see how many people are already visible at the venue, so you know what to expect.

Once checked in, you appear in the venue view and can see other visible users. You can toggle your visibility off at any moment — one tap, instant effect. From the outside, invisible looks exactly the same as not being there at all.

Your session lasts until you check out or the venue session ends. Everything is scoped to that session — nothing carries over to the next visit.

See someone you want to meet? Send them an approach signal. The signal itself contains no text — the act of signaling is the message. It says: "I noticed you and I would like to say hello."

You can have up to three active signals at a time, which means each one is a considered choice rather than a mass action. If a signal is not responded to within 30 minutes, it expires quietly. No notification to the sender. No awkward follow-up.

Signaling separates intent from action. You express genuine interest without the full social exposure of walking up to a stranger. If the answer is no, you never moved.

When you receive a signal, you are presented with a clear response menu. Each option represents a genuinely different decision — not just variations of yes and no.

When the response is "Yes, come say hi," both people know the approach is welcome. The initiator walks over with confidence. The receiver is glad the interaction is happening. That is the moment Shyne is built for.

There is no algorithm deciding you are a match. No compatibility score. No curated icebreaker. Just two people in the same room who have both explicitly chosen to meet each other.

Shyne is successful when two people who would not have spoken to each other in its absence actually speak to each other — and when the person on the receiving end is glad the interaction happened.

Chat in Shyne is a controlled fallback channel. It opens only when the receiver selects "Message first" — there is no other path to chat. No unilateral messaging. No DMs.

It exists for one narrow purpose: some receivers need one additional exchange before they are comfortable inviting a physical approach. "What is your name? What are you here for?" That is the kind of exchange chat is designed for.

Chat is text-only, first message capped at 200 characters, and it disappears when the venue session ends. There is no inbox. No history across sessions. The value of Shyne's chat is its ephemerality — it exists for exactly as long as the shared context exists.

Chat that does not produce a real-world interaction is still valid — "Message first" converting to a clear no is a better outcome than the receiver feeling pressured into a yes.

Shyne works best in environments where social interaction between strangers is already expected, where density is reliably high, and where ambient noise or crowd dynamics make the physical approach harder.

Safety on Shyne is structural, not reactive. Every interaction is consent-gated at the protocol level. No one approaches you without your prior explicit permission.

Declining a signal ("Not now") permanently blocks that person from re-signaling you for the rest of the session — enforced server-side, not just in the UI. Blocking is one-tap from any interaction point. If a user accumulates blocks across sessions, consequences escalate automatically.

Every signal is logged with full metadata in an immutable audit trail — not visible to users, but accessible for moderation and, if required, for law enforcement. The existence of this log is disclosed in the Terms of Use.

An "I feel unsafe" button is accessible from the venue view. It immediately alerts the venue operator and creates an internal review ticket — no need to identify who you feel unsafe about.

Shyne knows you are at a venue. It does not know where in the venue you are. No sub-venue positioning. No Bluetooth beacons. No WiFi tracking. The location data point is binary: in the venue or not.

Your profile shows a display name (not your legal name), one photo, and one intent tag. No detailed bios. No linked accounts. The profile shown to strangers is the minimum viable social signal, not a full identity.

Visibility is instant and total — one tap and you disappear from the venue view. From the outside, invisible looks exactly the same as not being there at all.

Chat messages are not retained on the server after the session ends. Signal history is private — no one can see who else you have signaled or who has signaled you. Sessions are ephemeral by design.