
Privacy Policy
B2B Campus Device Verification (browser extension) and B2B Campus Device Helper
Effective date: 23 October 2026
1. Purpose
The B2B Campus Device Verification extension for Google Chrome and Microsoft Edge, together with the B2B Campus Device Helper installed on a Windows computer, has a single purpose: to confirm that a B2B Campus Staff or Admin user signs in to the B2B Campus Exam Portal from a computer that B2B Campus has approved.
It is used only during Staff/Admin sign-in. Students do not need it. The extension has no other features, does not show advertising and does not track browsing.
2. When it runs and what it can access
- The extension only responds to requests from approved B2B Campus portal pages (the b2bcampus.com website and its subdomains). The browser blocks all other websites from contacting it, and the extension checks the website address again itself.
- It has no content scripts and no access to the pages you visit, your browsing history, form fields, passwords, one-time codes (OTPs) or cookies.
- It only works after you enter your password and OTP on the portal, when the portal asks it to verify the device.
3. Information collected on your computer
When the portal asks for verification, the Device Helper reads the following on your computer:
- MAC addresses of the computer's physical network adapters (for example Wi-Fi and Ethernet). Virtual, VPN and similar adapters are ignored.
- Computer name (the Windows host name) and the operating-system platform (for example Windows).
- A device key: the first time it runs, the Helper creates a private/public key pair and stores it on the computer (in the current Windows user's local application-data folder). The private key never leaves the computer. Only the public key and a digital signature are sent.
- The version number of the Device Helper.
4. Communication between the extension and the Device Helper
The extension talks to the Device Helper through the browser's built-in Native Messaging feature, which only connects the extension with a program on the same computer. The Device Helper does not connect to the internet itself. The extension passes the portal's one-time verification code to the Helper, and returns the Helper's signed answer (MAC addresses, computer name, platform, public key, signature and Helper version) to the B2B Campus portal page that asked.
The extension and the Helper do not download or run code from the internet.
5. How the information is used
The information is used only to verify devices for B2B Campus Staff/Admin sign-in:
- The portal issues a one-time, short-lived verification code. The device signs it with its private key, and the portal checks the signature. A copied MAC address without the device key cannot pass.
- The reported MAC addresses are compared with the adapters recorded for that device, so switching between Wi-Fi and Ethernet on the same computer keeps working.
- Pending: a computer used for the first time by an account is recorded as pending until an authorised B2B Campus administrator approves it.
- Approved: sign-in from that computer is allowed for that account.
- Blocked: sign-in from that computer is refused. Authorised administrators can also rename or remove a device record. If a computer's network adapters change completely, the device may need to be approved again.
6. Information stored by B2B Campus
Device records. For each account and device, the B2B Campus portal stores:
- a fingerprint of the device’s public key, and the public key itself;
- the MAC addresses, kept as keyed hashes for matching, in a partly hidden form, and in full for authorised administrators;
- the computer name, platform and browser name;
- the device status (pending, approved or blocked), when it was added, approved and last seen, who approved it, and the IP address of the last sign-in from it.
Security logs. When a sign-in or device verification fails or is refused, the portal records a security log entry: the time, the event and reason, the account involved (with the username partly hidden), the role, the IP address, browser, operating system and device type, screen size, the portal page address, and an approximate location where the hosting platform provides one. Successful sign-ins are not logged.
7. Who can see it
Device records can be viewed and managed only by authorised B2B Campus administrators (Admin and Super Admin). Security logs can be viewed only by users whom B2B Campus has authorised to review security logs.
9. No advertising, marketing or credit use
The information is not used for advertising or marketing, and it is not used to determine creditworthiness or for lending purposes.
10. Data security
- Communication between your browser and the portal uses HTTPS.
- Verification codes are single-use and expire after a few minutes, so a recorded answer cannot be replayed.
- The private device key stays on your computer; the portal only receives the public key and signatures.
- MAC addresses are matched using keyed hashes, and access to device records and security logs is limited to authorised users.
11. Data retention
Device records are kept until an authorised administrator removes the device. Security log entries are kept until an authorised user deletes them. There is currently no automatic deletion.
On your computer, uninstalling the Device Helper removes it and its browser registration. During uninstall you can also choose to delete the device key; if you keep it, a reinstalled Helper is recognised as the same device.
12. Your choices
You can remove the extension from your browser and uninstall the Device Helper at any time. B2B Campus may require approved-device verification for Staff/Admin sign-in, so removing them may prevent signing in until they are installed again.
13. Changes to this policy
If this policy changes, the updated version will be published on this page with a new effective date.
14. Contact
For questions about this policy or about your device information, please contact B2B Campus at hello@b2bcampus.com. B2B Campus Exam Portal: exam.b2bcampus.com