InSync
SyncField™ presence layer

Mutual presence, not a people map.

SyncField™ is the anonymous proximity layer behind InSync Dating. It does not map people. It maps mutual presence zones: field on/off, local profile, private overlap and consent before reveal.

See how SyncField works Try the visual preview
Two people in a modern café with subtle private blue presence fields around them.
No GPS map. No people radar.
You choose when your field becomes discoverable. Only mutual overlap and consent can unlock the next step.
Core proposition

SyncField turns people into presence signals — without turning them into dots on a map.

The field is not a tracker. It is a consent-first layer for anonymous mutual presence: a temporary, local, opt-in signal that can be felt before anything personal is revealed.

Field control

The field is not always on. You control it.

SyncField should feel safe before it feels magical. The first rule is simple: field off means no availability signal. Field on means your local profile may become a short-lived, anonymous signal — still protected by consent rules.

Field off Your local profile stays private. No availability signal, no proximity feedback, no reveal.
Local profile example

Mode: calm connection

Stored locally: current intent, energy, pace and boundaries. This is not a public dating profile. It becomes useful only when the field is turned on and consent rules allow anonymous overlap to become a signal.

IntentBoundariesContextTemporary
Visual explanation

The images explain the whole proposition.

SyncField is abstract until you see it: a switchable field, a local profile, private overlap and mutual opt-in. These visuals stay central because they show the difference between a dating radar and a consent-first presence layer.

Field off and field on comparison showing a private signal field around a person.
1. Field on / field off You choose when your field is active. Off means no availability signal, no proximity feedback and no social pressure.
A local profile interface stored privately on a smartphone.
2. Local profile Your intent, pace, boundaries and context start locally on your own device — not as a public profile feed.
Two private fields overlap with mutual opt-in before a connection can happen.
3. Anonymous overlap Two fields can overlap, but only mutual opt-in can turn a nearby signal into a possible connection.
How it fits the InSync system

SyncField is one layer, not the whole product.

The new proposition works best when the roles are separated: SyncField detects anonymous overlap, InSync handles consent and signal logic, and SyncSense carries the interaction after a signal.

SyncField™
Presence layer Anonymous field overlap, local profile, field on/off and proximity state. No GPS people map.
InSync
Consent & signal layer Checks intent, timing, context and mutual choice before anything can reveal or continue.
SyncSense™
Ambient interaction layer Turns signals into haptics, earbuds and glasses cues so the moment can stay in the real world.
Plain-language idea

You carry a private field — only when you turn it on.

The idea is simple: your phone holds a local profile with temporary intent, pace and boundaries. When you turn SyncField on, that profile can become a short-lived, anonymous presence signal. When you turn it off, nothing participates.

On / offYou decide when your field is active. Off means no signal, no availability and no social pressure.
Local profileYour intent, mode and boundaries start on your device first — not as a public dating profile.
Subtle feedbackIf a compatible field is nearby, the signal can be felt softly through haptics, sound or future wearables — without showing a live people map.
Opt-in layer

Consent decides what the field is allowed to reveal.

A field is only useful if people stay in control. SyncField stays private-first: no public profile, no hidden scan, no face targeting, no forced reveal and no pressure to act.

Private profileYour intent layer starts locally and privately. Turning the field on does not expose your identity.
Mutual opt-inSignals can become stronger only when both sides are open in a compatible way.
Soft revealThe field may guide attention, but identity, profile details or action should never be forced.
Trust guardrails

What SyncField should never become.

The proposition only works if the trust line is clear. SyncField is not a dating radar. It is not a public map. It is not a way to identify strangers.

No GPS people mapSyncField should not show exact people, exact location or a live radar of nearby users.
No face targetingThe field should not scan faces, label strangers or place names above people in the real world.
No forced revealA nearby overlap is not permission. Identity and profile details stay locked until mutual consent allows more.
Roadmap

From visual concept to real-world presence test.

The roadmap starts simple: local profile, manual field switch, consent rules, then proximity feedback. The public page explains the product direction without publishing the full technical playbook.

01

Local profile

The first layer is a private profile on your device: intent, mode, pace and boundaries.

02

Field on / off

The user must be able to activate or deactivate the field clearly. Off means no participation.

03

Mutual opt-in

Only compatible openness can turn anonymous overlap into a possible signal. Fit alone is not permission.

04

Felt feedback

Distance and proximity can become subtle feedback through vibration, sound or SyncSense wearable cues.

05

Connection choice

The user still chooses: ignore, reveal more or connect. The field never decides for you.

What we are not publishing here: the full implementation design, pairing flow, signal logic or build details. This page explains the product direction, not the private engineering plan.
SEO / AI search clarity

Clear answers about SyncField.

These answers explain SyncField in direct language for visitors, Google Search and AI Overviews — especially the difference between mutual presence and live people tracking.

What is SyncField?

SyncField is the anonymous mutual presence layer behind InSync Dating. It lets a person turn a local field on or off, carry a local profile and only allow signals through mutual opt-in.

What does “Feel who is near you” mean?

It means future connection interfaces could use anonymous presence zones and subtle feedback, such as haptics, sound or wearable cues, instead of only screen-based swiping.

Is SyncField always on?

No. SyncField is designed around field control. Field off means no availability signal, no proximity feedback and no reveal.

What is a local profile?

A local profile is a private profile stored on the user's device. It can contain temporary intent, pace, boundaries and context without becoming a public dating profile.

What is mutual opt-in?

Mutual opt-in means both people must choose compatible openness before a nearby signal can reveal more or become a possible connection.

Does SyncField identify or scan strangers?

No. SyncField should not identify strangers, scan faces, create a live people map or expose identities without permission. It is built around private signals, local profiles and consent.

How is SyncField related to InSync?

InSync is the broader consent-and-signal layer for meeting after the smartphone. SyncField is the presence layer that explains how anonymous field overlap, private proximity and consent could work.

SyncField™ — mutual presence, not a people map.