An app alone generates no data. Presence is born from the encounter.
An isolated device produces no presence. The event is born when two devices running the Group Link SDK meet by proximity, with no GPS and no physical anchor on site. The only condition is the network: the more apps take part, the more encounters happen and the more coverage everyone gets.
A physical anchor (GL Station, integrated TV or screen) is one way to mark a point in the network. The handshake is the other: device to device. No construction, no installation, no fixed point. It is the lightest way into the Dataoris spatial intelligence network, and the one that grows the most with scale.
Two devices meet. An event is born.
An app on its own generates no data: an isolated device produces no presence. The event is born from the encounter. When two devices running the Group Link SDK come within range of each other (up to 30 meters), they perform a BLE handshake and register presence, with no GPS and no hardware installed on site.
A device with the SDK
A user of your app, with the Group Link SDK active, acting as a sensor even in the background.
Another device in the network
Another nearby device with the SDK: from your app or from any other app in the collaborative network.
Proximity event
The encounter becomes an event indexed in H3 cells and delivered to your endpoint via webhook, in real time.
Every app that joins increases coverage for everyone.
The handshake is collaborative by nature: you contribute the devices in your base and gain access to encounters across the whole network. It is not a sum, it is a multiplication. Value grows with the number of active points.
More points, more encounters
Every new device with the SDK is one more detection point. The density of the network turns into coverage for everyone.
Coverage where there is no anchor
Where you have installed no hardware, the device-to-device handshake covers the space. The network reaches where physical infrastructure does not.
Accuracy that improves with scale
The more encounters, the more signal to calibrate the network. Perception of the physical world gets better as the base grows.
The physical anchor and the handshake add up: where there is a GL Station, presence is anchored to a fixed point; where there is none, the handshake keeps the network alive.
Confirm the encounter happened, without typing a code.
Many apps confirm a delivery or a ride by asking the two people to exchange a code on screen. It is a manual step that stalls the operation at the most sensitive moment, leaves room for error and still depends on goodwill from both sides. The handshake does it on its own: when the two devices meet, the confirmation happens by proximity.
Confirmation by code
- Both parties stop to read and type a code
- Jams under time pressure, weak signal or a hard-to-read screen
- Leaves room for fraud and disputes over what happened
- Friction at the most sensitive moment: the handoff or the pickup
Confirmation by handshake
- The two apps recognize each other by proximity, with no code
- Automatic confirmation when the devices meet
- Proof of presence on both sides, with time and approximate location
- No manual step: the operation never stops
It works for any operation that depends on two parties meeting: delivery to a consumer, passenger pickup, counter pickup, a professional serving a client.
It works for any operation where two parties have to meet.
Wherever value depends on two ends meeting in the physical world, the handshake confirms the encounter by proximity, on its own, with no code and nobody typing anything. A few examples:
Delivery to a consumer
The encounter between courier and customer becomes automatic proof of delivery, with time and approximate location, no code at the door.
Passenger pickup
Driver and passenger recognize each other by proximity. Pickup confirmed without exchanging a code at the busiest moment.
Counter pickup
The customer arrives to collect an order and the app confirms presence at the point, speeding up handoff and cutting the queue.
Field service
A professional and a client meet at the agreed location. The handshake logs the visit, with no manual checklist.
Three ways to detect presence. Only one grows with the network.
GPS is off indoors and drains battery. Beacons require hardware at every point. The handshake is born from the encounter between devices and gets stronger with every app that joins.
GPS / on-device geofence
- Approximate position, off by tens of meters indoors
- Drains battery and needs the app open
- Does not detect encounters between people
Beacons / hardware at every point
- Requires installing and maintaining a device at every location
- Covers only where there is hardware
- Cost and logistics grow with the area
Dataoris handshake
- Presence from the encounter between devices, with nothing to install
- Covers anywhere the network is present
- Gets stronger with every new app in the network
Ready to measure the physical world inside your app?
We design a pilot with you: SDK in the app, an anchor on site and a webhook to your endpoint. In a few weeks you validate before scaling.
The handshake fits those with an app and a moving user base.
It is for you if
- You have your own app with an installed base that moves through the physical world.
- You want presence and proximity without depending on installing hardware at every point.
- It makes sense for your product to join a collaborative network and gain coverage with scale.
Maybe not yet if
- – You do not have your own app to embed the SDK.
- – Your base is small and static, with few possible encounters.
- – No problem: the physical anchor (GL Station) covers the fixed point. Talk to us.
Encounters become events, in real time, inside your stack.
Every handshake between devices becomes a structured event, indexed in H3 cells and delivered to your endpoint via webhook. Just embed the Group Link SDK in the app you already maintain.
- event: handshake · h3: 8a2a1072b59ffff · 14:02:11
- event: proximity 28m · remote_id: usr_8f3a · 14:02:11
- event: dwell 3m40s · 14:05:51
- webhook → your endpoint · 200 OK
Integration: a few lines in the app you already have
// initialize the Group Link SDK
GroupLink.init({
apiKey: SUA_CHAVE,
remoteId: idOpacoDoUsuario,
});The handshake, demystified.
Does the handshake work without installing any hardware?
Yes. The handshake is the encounter between two devices running the Group Link SDK, via BLE proximity, with no physical anchor on site. What it needs is the network: an isolated device generates no presence, the event is born when two devices meet. That is why the more apps take part, the more encounters happen. Where you want to guarantee presence at a fixed point, the GL Station anchor complements the handshake.
Can the handshake replace the confirmation code between two people?
Yes, that is one of the most direct uses. Operations where two parties must confirm an encounter (a delivery to a consumer, a passenger pickup, a counter pickup) usually ask for a code to be exchanged on screen, which creates friction and leaves room for disputes. With both devices running the Group Link SDK, the encounter is recognized via BLE proximity and generates an event with time and approximate location, without anyone typing anything. The code is no longer mandatory and the confirmation becomes automatic.
What is the detection range?
The handshake detects devices up to 30 meters away, via BLE. Each encounter generates a proximity event with the approximate geolocation of the point, without identifying the person.
Does it drain a lot of battery?
No. The Group Link SDK was designed for low consumption and operates over BLE even with the app in the background. That is the difference from GPS, which drains battery and requires the app open.
What about privacy and the LGPD?
The data is anonymous and aggregated. Only the approximate geolocation of the point is known, without identifying the user. The device identifier (remote_id) is opaque, defined by you, and must not contain personal data: only your database links it to the person. Capture is via BLE, with encryption at rest and in transit (TLS 1.2+) and storage in Brazil.
Do I need to integrate with Dataoris or is it automatic?
You embed the Group Link SDK in the app you already maintain, with public documentation (docs.dataoris.com). There is native support (Android and iOS) and for the most-used hybrid frameworks. From there, encounters with the network already generate events, delivered to your endpoint via webhook.
How does the handshake compare with the physical anchor?
They are complementary. The anchor (GL Station, integrated TV or screen) marks a monitored fixed point, ideal for a store, a gas station, a branch. The handshake covers the space between points and grows with the network, with no installation. Together, they give anchored presence where it matters and broad coverage where there is no hardware.
How do I receive the data?
Each event is indexed in H3 cells and delivered in real time to your endpoint via webhook, the recommended method. You follow everything in the self-service dashboard, where you configure the integrations.
Another question? Talk to the team on WhatsApp or write to suporte@dataoris.com.
Join the collaborative network.
Talk to our specialists and find out how the handshake brings presence to your app, without installing hardware.