Questions and answers
Not yet. You can use Wingman! in your browser or install it as a progressive web app (PWA) for quick access from your home screen or desktop.
Choose your device or browser below for official installation instructions. These links open in a new tab. Installing Wingman! does not enable offline matching or guarantee that your device will keep it running in the background.
Wingman! helps adults 18 and older find platonic company for real-world plans. Find a wingperson, concert buddy, coffee companion, or someone to join another activity. Describe what you have in mind so others can decide whether it sounds like their kind of plan.
Yes. Wingman! uses the familiar, common-use term for someone who has your back. The name is not a restriction on who belongs here: finding a wingperson to hang out with should be open to people of every gender.
We welcome women, men, non-binary, genderqueer, genderfluid, agender, bigender, pangender and demigender people, including trans and cis people. You do not need to use any of these labels to belong.
This list is not exhaustive. We do not know every gender identity or the language each person uses, and we are sorry if yours is not included. Email Todd at todd@hendricks.cc if you would like another identity added to this FAQ. Those additions are for the FAQ only; the dropdown will continue to offer Self-described.
Wingman! is currently free to use, with no account registration or app download required. You can browse available plans before posting your own request.
Choose an eligible public meeting spot, set your time and travel preferences, and describe your plan. Post your request. If several requests fit, choose a person from the potential-matches list; one candidate opens the wingmatch workflow directly. With none, your request stays active on the radar.
An invitation starts the conversation. For ordinary matches, both people agree to the wingmatch, settle on a meeting spot and confirm readiness. A Wingfam owner can instead explicitly enable auto-allow for compatible guests using fixed, disclosed meetup details.
A Wingfam lets the owner of a posted request welcome additional wingmatchers to the same meetup after finalizing their first match. Only the owner of the request that received the invitation can enable it; the matching person cannot enable it on their behalf.
The owner chooses whether to approve later matches individually or enable auto-allow. Wingfam is for platonic company. Membership does not prove that someone has arrived or guarantee attendance.
After finalizing the first wingmatch, the posted-request owner can use the Wingfam setup in their meeting-details view. Confirm the public meetup address, review the sharing notice and choose manual approval or auto-allow.
The meeting spot must pass the location checks and be within 50 miles of the supplied device location. Once the Wingfam is open, its address is fixed. Auto-allow also fixes the shared meetup details; close that Wingfam and submit a new request to replace them.
Closing the ordinary request without activating Wingfam ends its activation permission. Keeping an open, connected page matters even if the first matcher has already closed their details.
With manual approval, later wingmatchers send an invitation and the owner approves each match. They use the Wingfam’s meeting spot and complete the applicable agreement and readiness steps.
With auto-allow, the owner consents in advance to compatible new wingmatches. Joining guests receive the fixed meetup details immediately and see that they were automatically allowed. Multiple guests can join without waiting for the owner to approve each one, but each guest can still have only one active wingmatch.
Both Wingfam modes require your selected meeting pin to be identical to the host’s. Both meeting times must be Now or within the next hour from the current time, including any relative travel allowance. A similar address, a nearby pin or a later time keeps your request separate. Auto-allow is optional and never automatically saves meetup details.
For a manually approved Wingfam match, the owner agrees to share the supplied meetup description and phone number with approved guests, even if a guest provides no phone number.
Auto-allow makes the owner’s selected address, meeting time, written recognition description and any supplied phone number visible to everyone browsing that live Wingfam, including the current wingmatch. The owner must acknowledge this before enabling it. Supplying a phone number is optional.
Auto-allow requires a written description of how to recognize the owner. “Meet outside the front door” and “I’ll find you” cannot be used for auto-allow. Public sharing stops when the host request closes or expires, but information already copied cannot be recalled.
One ordinary wingmatch reserves the request. Later compatible attempts are told another match is in progress and are placed in a waiting line. The owner sees the number waiting.
When the owner closes or cancels with people waiting, they can keep the current match, cancel that one and move to the next eligible person, or cancel all and close the request. Moving to the next person requires the owner’s fresh approval. Cancelling all closes your request and requires a new submission. Ending an unfinished attempt keeps your request active, even if nobody else is eligible. Cancelling a finalized ordinary wingmatch closes your request.
After finalization, enabling manual Wingfam tells waiters they can send an invitation to the new host request. Enabling auto-allow admits compatible, still-live waiters automatically. If the owner explicitly closes without Wingfam, waiters are notified on a successful check-in. Waiting is not a guaranteed place.
Yes. Keep the main Wingman page open and connected to continue allowing wingmatches. The host request expires after 90 seconds without a successful check-in. Locking a phone, switching apps, losing connection or browser suspension can interrupt those checks.
Closing the auto-allow window explicitly stops that Wingfam. Leaving the page attempts to stop it too, but browsers do not reliably deliver page-close actions; expiry is the fallback. An installed app has the same browser restrictions.
A page may still check in while unattended, and another open tab can affect session activity. A live label does not guarantee that the owner is watching.
Each auto-allowed wingmatch creates a persistent notification showing that person’s quick-info details. The notification stays until dismissed. If more are waiting, a card below shows the number of additional match notifications.
Dismissing shows the next notification and does not remove the person from the Wingfam. The members list keeps that connection accessible even after the notification is dismissed or the guest closes their modal.
Notifications appear when the open page receives updated state. Wingman does not send background push notifications, so a closed or suspended browser may not receive them promptly.
The owner sees a compact, scrollable list of finalized connections for that Wingfam, including the original match and later admitted wingmatchers. Each row shows the name, a cautious session-status label and an Unmatch control.
The list is independent of unread notifications and saved meetup cards. You do not need to save someone’s details to manage their membership. A member remains listed after closing their details or timing out, until that connection is ended or the owner’s session expires.
An active session means the browser has checked in recently; it does not verify attention or physical attendance. An expired session means current availability is unknown.
No. Saving is optional for both people, whether a match was manually approved or auto-allowed. In finalized details, Save wingmatch details changes to Saved and keeps the view open. The other person receives a notice that the details were saved in your browser.
A Previous wingmatch card on your radar opens your saved copy. Dismiss keeps it; Delete or the card’s trash icon deletes only your local copy. Closing an unsaved final view first offers Save or Delete, followed by any applicable request-close decision.
Up to 30 copies are kept in that browser. They expire with the posted-request owner’s session, not simply because either person closes a modal. A closed browser clears expired stored values when Wingman next runs. Saving is not a permanent archive or cross-device account.
Either person can choose Unmatch in finalized or saved details and confirm the action. Owners can also use Unmatch beside a person in the Wingfam members list. Keep wingmatch backs out of the confirmation.
Unmatch ends that connection, closes its details view and removes any saved copy on each updated browser when it receives the change. It leaves the Wingfam host and other members available. Deleting a saved card alone does not unmatch.
The unmatched session cannot rejoin that same Wingfam request. This is not an identity-based ban: a different browser or new session can evade it. Auto-allow details remain publicly visible in the live listing; unmatching cannot retract public information or copies made outside Wingman.
Yes. When your updated browser receives the removal, a persistent notice says the owner removed you from their Wingfam. That wingmatch’s details view closes, its saved copy is deleted, and there is no Save option for the ended connection. The server rejects attempts to save it from an old screen.
If you are offline or your browser is suspended, removal is applied when Wingman next runs and checks the server. The notice itself can be missed if the owner-session record expires before you return; saved copies still follow their expiry rules.
Wingman cannot immediately erase an offline or outdated browser, a screenshot, a copied phone number or a device backup. Removing the connection also does not make publicly shared auto-allow information private.
If the matcher’s session expires, the requestor’s saved details remain while the requestor’s own session is active. The saved view explains that the matcher’s session has ended and their current availability is unknown. Normal modal closure alone does not mean their session expired.
If Wingman cannot check the other person’s status, it says so rather than assuming they went offline. An active session label does not confirm that they are watching or still available.
When the posted-request owner’s session expires, both people’s saved entries expire. Actual removal from a closed browser happens when Wingman next runs. Explicit Unmatch is different: it deliberately ends the connection and removes the saved copies when each updated browser receives the change.
The owner can withdraw their live Wingfam request. For auto-allow, use Close Wingfam & stop auto-allow, or close that hosting window. This stops new admissions and removes the host’s unread admission notifications. Ordinary guest request rows are also cleaned up.
Closing the whole Wingfam is different from Unmatch beside a member, which ends only that connection. Closing a hosting window does not revoke every already-received or saved copy: saved entries still follow the posted-request owner’s session lifetime. Use Unmatch when you mean to end an individual connection and remove its saved copies.
To host again after closing or expiry, submit a new request and go through the matching and Wingfam setup flow again.
Decline skips that Wingfam and keeps your posted request active. You return to the remaining potential matches: a list for several, the wingmatch workflow for one, or your active request on the main screen for none.
If the Wingfam uses manual approval, its owner receives a dismissible notice naming you and saying you declined. Their Wingfam stays open. With auto-allow, the owner receives no decline notice; an unused admission notification and that connection are removed quietly if you had already been admitted.
Declining after receiving details closes that connection and removes its saved copies when updated browsers receive the change. Dismiss or Close alone is different: it only follows the usual details-close flow. Notices require a successful check-in; closed or suspended browsers may not see them before the host expires.
Availability depends on who has a live request in your area. You may be the first person looking, or nearby requests may not fit your preferences, timing, or travel distance.
Try a wider radius if you can travel farther, post a clear plan, or check again later. Sharing Wingman! with your local community can help more people discover it.
The map can show requests beyond your selected radius, and gray radar cards remain available to inspect. Seeing a request does not necessarily mean you can match with it.
Matching also checks both people’s preferences, meeting times, and whether an available meeting spot fits the relevant travel limits.
People can browse Wingman! without posting a request, and worldwide viewers may be far outside your search area.
The worldwide viewer count can also include people who have an active request, so the viewer and request counts should not be added together. Viewer counts estimate recently active browsers; they do not guarantee that someone is watching or available to meet.
Search for an address or business, choose from nearby businesses, or double-click the map to drop a pin. On a touchscreen, double-tap instead.
Wingman! checks the selected point before you can post. Choose a recognizable public venue and check that it will be open when you plan to meet.
Wingman! screens meeting spots using map data. Homes, private-access locations, and other unsuitable or unclassified places may be rejected.
An unavailable check means the location could not be confirmed; it does not necessarily mean the place itself is unsuitable. Try another nearby public venue or retry when the lookup is available. A successful check does not verify opening hours or current conditions.
Device location can be imprecise. When it is unavailable, Wingman! may use an approximate area based on your internet connection, which can be inaccurate on mobile networks or VPNs.
Check your browser’s location permission and your device’s location settings. You can also search for a public meeting spot directly. Review the selected address and pin before posting.
Yes. Choose a specific meeting time up to 12 hours ahead, using the 15-minute time controls.
For a flexible plan, choose Now / travel time and allow time to get there. The available travel-time choices depend on the selected transportation mode and distance. Check the displayed date and time before posting.
Keep the main Wingman! page open, visible, and connected while waiting for a match. Your request normally expires after 90 seconds without a successful check-in.
Switching apps, locking your phone, losing connectivity, or closing the page can interrupt check-ins. Installing Wingman! on your home screen does not remove those limits.
A request can expire after it stops checking in. Scheduled requests can also become too old, and completing a match or choosing to withdraw can remove a request from the available list.
If you still want company, review your saved details and post again. A previous request helps refill the form; it does not automatically restore an expired live request.
Yes. Previous requests keeps up to five saved requests in this browser. Select one to refill the form, then review the plan, location, and timing before posting.
Reusing a request does not publish it automatically. Saved history belongs to that browser and is not a cross-device account.
Request age shows how long the request has existed.
Last check-in shows the latest availability renewal observed by the server.
Last browser activity shows the latest reported interaction with the Wingman! page.
These indicators describe different things. A page can keep checking in while unattended, and recent activity does not guarantee that someone is watching or will respond immediately.
A posted request is public. Other visitors can see the details you provide, including your display name, age, preferences, plan, meeting time, chosen meeting spot, and optional photo.
Treat your meeting pin as public. Keep your home address, phone number, and other sensitive information out of public fields. See the Privacy Policy for details about sharing and storage.
No. Both are optional.
You can use recognition details to help find your partner without uploading a photo or exchanging numbers. For ordinary pairs, numbers are revealed only when both provide one. Wingfam owners agree to share their supplied number with approved guests; auto-allow makes the provided meetup details and number public while that Wingfam is live.
Phone-number validation does not verify ownership or identity.
Yes. You can decline an invitation, cancel a match, or withdraw your request using the available controls. Cancelling asks for confirmation. If people are waiting, the request owner can cancel one match and move to the next eligible person, or cancel all and close the request. Ending an unfinished attempt keeps your request active. You return to a list for several remaining candidates, directly to the wingmatch workflow for one, or to your active request when none remain. The failed pair is skipped until a request is updated or reposted. Cancel-all and cancellation of a finalized ordinary match close your request and require a new submission.
You can also leave a meeting at any time. Agreeing to a plan or sharing a phone number does not create an obligation to stay. Respect the other person’s boundaries and changes of mind, too.
Wingman! does not independently verify identities or conduct background checks. Names, ages, photos, and other personal details are self-reported.
Meet at a busy public place, check the venue yourself, and tell someone you trust about your plan. Read How we help protect your safety for the available safeguards and their limits.
Wingman! shows notifications while you use the page and can play sounds. Supported browsers can also provide vibration. You can adjust these preferences and test them in the connection diagnostics panel.
Wingman! currently does not send background push notifications. Keep the page open and check it regularly while waiting for a match.
Live requests, matching, and meeting coordination require an internet connection. The installed web app may show an offline page, but it cannot continue matching without reaching the service.
Saved drafts are not automatically posted when you reconnect.
When Wingman! detects an update, it offers a refresh button. Use it when you are ready to load the latest version.
A normal refresh preserves saved browser information. If something looks out of date, try refreshing or reopening Wingman! first. The version badge opens the changelog so you can see what changed.
Use Report abuse or request image removal for reporting instructions.
A visible request photo also has a Photo options menu for reporting a rights or legal concern and requesting its removal. Removing a photo from Wingman! cannot erase screenshots or copies someone has already saved.
Reporting is not an emergency response service. If you are in immediate danger, contact local emergency services.
Wingman! is not affiliated with wingman.app or wingman-live.com. Those are separate services.
Not yet. We plan to add business sponsorship opportunities if demand grows. Sponsorship is not currently available, and there is no announced launch date.