Complete guide to HaptiQ Couples Play. Learn how to pair devices, create shared sessions with session codes, sync haptics over long distance, and customize partner experiences.
Haptic devices have traditionally been a solo experience: one person, one device, one video. HaptiQ's Couples Play changes that by letting two people share synchronized haptic experiences, whether they are in the same room or on opposite sides of the world. This guide covers everything from initial setup to advanced customization, showing you how to create shared sessions that deliver coordinated haptic feedback to both partners simultaneously.
Couples Play is HaptiQ's real-time device synchronization feature that lets two users share a haptic session. When one partner starts a session, the other joins using a session code. Both partners' devices then receive synchronized haptic commands derived from the same funscript, with optional per-partner customization for intensity, axis mapping, and device-specific settings.
The feature works over the internet using HaptiQ's WebSocket infrastructure, which means distance is not a factor. Partners in the same room or thousands of miles apart get the same low-latency synchronized experience. The session is encrypted end-to-end, and no video or audio is transmitted through HaptiQ -- only haptic position commands.
The Couples Play architecture is built on three components:
One partner creates a Couples Play session in HaptiQ. This generates a unique 6-character session code (e.g., "HX7K2M") and designates this partner as the session host. The host selects the funscript (or video + AI-generated script) that will drive the session and connects their device.
The second partner opens HaptiQ's Couples Play page and enters the session code. This connects them to the host's session via a secure WebSocket channel. The joining partner connects their own device and configures their personal settings.
When the host starts playback, both partners' devices receive haptic commands simultaneously. The host's device follows the funscript directly, while the guest's device receives transformed commands based on their personal settings (intensity, inversion, axis mapping). The WebSocket connection maintains sub-100ms synchronization between both devices.
One of Couples Play's strengths is that partners do not need matching devices. The host might use a Kiiroo Keon while the guest uses a Lovense Nora, and HaptiQ translates the funscript commands appropriately for each device type. Here is how different device combinations work:
| Host Device | Guest Device | How Commands Map |
|---|---|---|
| Stroker (Handy, Keon) | Stroker (Handy, Keon) | Direct position mapping (identical motion) |
| Stroker | Vibrator (Lovense, WeVibe) | Position mapped to vibration intensity |
| Vibrator | Stroker | Intensity mapped to stroke position |
| Stroker | Multi-axis (OSR2+) | L0 direct, secondary axes derived |
| Vibrator | Vibrator | Direct intensity mapping |
Both partners can customize how they experience the shared session without affecting the other person's experience. Available customization options include:
Each partner can adjust their device's intensity from 10% to 200% of the base script. If the script says position 80, an intensity setting of 50% translates that to 40 for that partner's device. This lets partners with different sensitivity preferences share the same session comfortably.
The guest can optionally invert their device's motion so that when the host's device moves up, theirs moves down. This creates a complementary sensation rather than a mirrored one, which some couples prefer for certain content types.
A configurable time offset (in milliseconds) lets the guest's device respond slightly ahead of or behind the host's device. Small offsets of 50-200ms can create interesting lead/follow dynamics, while larger offsets can compensate for network latency in high-ping situations.
If either partner uses a multi-axis device, they can customize which axes receive commands and how secondary axes are derived. For example, the guest might want stronger twist (R0) and no vibration (V0), while the host prefers full vibration and gentle twist.
Couples Play was designed with long-distance relationships in mind. The feature works over any internet connection, with the following technical characteristics:
HaptiQ synchronizes the haptic commands but does not stream video between partners. For video synchronization, partners can use a separate video-calling platform (FaceTime, Zoom, Discord) alongside HaptiQ, or agree to start the same video at the same time using a countdown. The haptic synchronization is independent of video -- as long as both partners start playback within a few seconds of each other, the experience works well.
Couples Play supports three session modes, each designed for a different type of shared experience:
Both devices follow the same funscript simultaneously. This is the default mode and works best when both partners are watching the same video content. Each partner's device receives the same position commands (adjusted for their personal intensity and customization settings).
One partner's device mirrors the other's in real-time. In this mode, there is no pre-scripted content -- instead, the host manually controls their device (or it follows a script), and the guest's device copies those movements with minimal latency. This creates a direct physical connection between partners where one person's device movements drive the other's.
The guest's device receives the inverse of the host's commands. When the host's device is at position 80, the guest's is at position 20. This creates a push/pull dynamic that some couples find more engaging than synchronized movement.
Any device that works with HaptiQ works with Couples Play. The full list of 870+ supported devices is available on the Devices page. The most popular pairings include:
Couples Play is designed with privacy as a first principle:
Create a shared haptic session in under a minute. One Pro account is all you need -- your partner can join for free.
Couples Play creates a synchronized session between two HaptiQ accounts. One partner starts a session and gets a 6-character session code. The other partner enters that code and both devices connect to the same WebSocket channel on the HaptiQ backend. When one partner plays a video, haptic commands stream to both connected devices in real time with latency typically under 150ms end-to-end, including internet round-trip. Both partners can see shared playback state, each can adjust their own intensity scaling, and either can pause or scrub. Sessions persist for 24 hours or until both partners disconnect. Partner devices do not need to be identical — a Handy on one end and a Lovense Max 2 on the other will both receive the same underlying funscript data, each scaled to that device capabilities.
Yes. Couples Play works over any internet connection — same room, same country, or opposite sides of the world. The HaptiQ backend uses WebSocket relay hosted on Render with global edge routing, so two partners connecting from North America and Europe typically see 100–200ms total sync latency, well within the human perception threshold for rhythmic haptic content. The session code is the only thing partners need to share; no account linking or contact permission is required. The connection is end-to-end encrypted over TLS 1.3. For partners in particularly distant regions (Asia to Americas), latency may reach 300ms but HaptiQ applies small predictive timing adjustments so haptic output still feels locked to the shared video timeline. Same-region partners typically experience sub-100ms sync.
Any of the 872 supported devices works in a couples session — including mixed-device pairings. Common setups are a Lovense Max 2 with a Lovense Lush 3 or Gush (most common same-manufacturer couples pair), a Handy with a Lovense Nora, or a Kiiroo Keon with a WeVibe Chorus. Devices do not need to match: HaptiQ maps funscript values appropriately for each — linear stroke devices get position data, vibrators get intensity-mapped vibration, multi-axis rigs get axis-derived output. Each partner can also connect multiple devices. Connection methods mix freely: one partner on Web Bluetooth in Chrome, the other on Buttplug.io via Intiface Central in Firefox, both in the same session. The iOS app fully supports Couples Play with the same session code system as web.
Yes. Session codes are 6-character random strings generated server-side with cryptographic randomness, giving over 2 billion possible combinations per active session — guessing a valid code is practically impossible. All WebSocket traffic uses TLS 1.3 and JWT authentication. Sessions auto-expire after 24 hours of inactivity. HaptiQ does not log haptic command content, only metadata (session start time, partner count, duration) for admin diagnostics. No video content is transmitted between partners — each partner plays their own copy locally and only the funscript command stream is shared. Couples Play is available on the free tier with a 60-minute session limit; HaptiQ Pro at $9.99/month removes the time limit and adds custom session codes, saved partner pairings, and priority WebSocket routing for lowest latency.
Create a free HaptiQ account to generate a funscript from your own video.