SYNC Signal Technology
Proof of exposure, not proof of delivery
Imperceptible engineered signal fragments are embedded in audio and video content, or transmitted through approved hardware in physical environments. With explicit permission, a SYNC-enabled property detects the signal and creates a deterministic, timestamped event.
How a signal travels
Four components, one event
A signal is placed, detected, resolved, and acted on — with consent checked at every step.
Signal Tags
Engineered signal fragments embedded in approved audio or video content. Imperceptible in normal listening, deterministic on detection.
Signal SDK
Embedded detection for host apps and web properties. Runs on-device, under explicit permission, reporting only designated sequences.
Signal Cloud
Resolves a detection into a campaign event, applying consent, eligibility, location, frequency, and offer rules before any activation.
Signal Emitters
Approved hardware for silent physical placements — retail floors, venues, signage, and events where no media stream exists.
Live detection
Hear what a signal sounds like — or rather, don't
Both demos run the production SYNC Signal detector in your browser. Detected sequences appear in real time.
Event model
Every class of event carries its own control
Data minimisation, purpose limitation, and audit requirements are defined per event class rather than applied as a blanket policy.
| Event class | Illustrative fields | Control requirement |
|---|---|---|
| Exposure | Campaign ID, Signal Tag ID, timestamp, channel, coarse location, device context, consent state | Data minimisation, permission record, retention limit, frequency controls |
| Activation | Offer or content ID, eligibility rule, delivery time, view and claim status | Purpose limitation, preference enforcement, suppression and opt-out |
| Financial intent | Amount, asset and rail, recipient, quote, fee, authentication level | Explicit confirmation, sanctions and fraud screening, immutable audit record |
| Settlement | Provider reference, blockchain signature or bank trace, status, timestamps, reversals | Webhook authentication, reconciliation, exception handling, ledger integrity |
| Outcome | Redemption, purchase, loyalty event, refund, value, source exposure | Attribution window, deduplication, holdout logic, access controls |
Privacy commitments
Consent is the product, not a checkbox
- Affirmative opt-in before any signal detection or microphone-related processing.
- Clear notice that the technology detects designated SYNC Signals — it is not designed to record conversations or identify spoken words.
- Easy permission withdrawal, marketing opt-out, and data access, correction, and deletion processes where applicable.
- Separate consent for financial services, marketing, geolocation, biometrics, and cross-context data uses when required.
- Pseudonymous identifiers, encryption, role-based access, bounded retention, vendor controls, and privacy impact assessments.
Questions
What people ask first
No. The detector listens only for designated SYNC Signals — engineered frequency sequences. It is not designed to record conversations, identify spoken words, or transmit ambient audio. Microphone access is requested explicitly and can be withdrawn at any time.
See it detect in your own environment
We run controlled pilots that validate detection quality, false-positive rate, deduplicated reach, and consent integrity before anything scales.