ob.Pal · Trust
Know your
ob.Pal.
Check where it came from.
Compare the seal on both screens.
Illustration · no active connection
01 · The source
Check where it came from.
- Website
- Check the address bar: obpal.blackboxes.net.
- ob.Pal Link
- Use the Chrome Web Store listing. Its item ID is
jnnpcnoilofjaffabnhecfokjjknlemg. - Code and packages
- Axialon/obpal on GitHub, in the Axialon organization. On npm: @obpal/core and @obpal/host.
02 · The connection
Check both screens show the same seal.
Especially when you type a code: compare all three symbols and their names on your phone and the screen you intend to control. If they differ, disconnect and pair again.
The seal is a short, 18-bit comparison aid for this connection. It is not proof that a site or build is legitimate. How it works.
03 · The promises
Words you can check.
- No accounts.Pair a phone with a screen. Connection service
- No ads or tracking.No advertising or analytics scripts. Page security policy
- No automatic user telemetry.Request invocation logs are disabled; operational error logs remain. Logging configuration
- Feedback is your choice.Contact us only if you choose to. What contact involves
- Camera frames stay on the capturing device.Tracking can send landmarks to your paired screen. Camera code · Tests
- Open source.The code is MIT licensed. The name and logo have separate terms.
Control input is not stored by ob.Pal. Saved screens and preferences stay on this device. Local pairing storage · Privacy policy
04 · Copies and forks
A label has limits.
A fork or mirror can show an origin marker so you know you opened a different deployment. This helps honest forks explain themselves. A malicious copy can remove the marker. Check the domain and compare the connection seal yourself.