Data transparency
What the platform sees, and what it never sees
The box and the virtual appliance run at your venue; hotspot-box.com only manages the licence, health and SMS credits. Every data field that travels between us is listed below. In the SaaS cloud service verification happens in the cloud; the difference is spelled out separately.
Data that reaches the platform
| Data | Purpose | Safeguard |
|---|---|---|
| Device identity and hardware summary | Binding the licence to the right device | A hash; a fingerprint rather than a serial number |
| Software version | Update notices | Version number only |
| Health (disk, clock, timestamp service, SMS balance) | Alarms and support | Status codes; no record content |
| Resource usage (CPU, memory, disk) | Capacity warnings | Percentages |
| Session and SMS counters | Credit deduction and statistics | Counts only; no numbers or MACs |
| The box's public IP and location | Licensing and support | Belongs to the box, not to a guest |
| Signed request envelope | Proving the message came from the box | HMAC-SHA256 signature, per-device secret |
Never reaches the platform
- Guest phone numbers, e-mails or coupon codes
- Guest device MAC addresses or internal IPs
- Internal IP distribution records and the signed archive
- SMS text and verification codes
- Visited sites or traffic content
- Consent records given on the portal
What changes with the SaaS cloud service?
With SaaS there is no box on site, so the portal and SMS verification run in the cloud: the guest's phone number is processed by the cloud service only to send and verify the one-time code. No Law 5651 records are kept; internal IP allocation records, MAC addresses and traffic content still never reach the platform. The "never reaches us" list above applies to the Box and the Virtual Appliance.
SMS flow: where does the number go?
The platform only hands out API credentials and counts credits; the message travels between the box and the provider.
- 1
The box generates the code
The one-time code is created and verified on the box.
- 2
The box sends to the provider
The message goes straight to the SMS provider; it does not pass through the platform.
- 3
The platform counts the credit
The box only reports "1 SMS sent".
- 4
Providers can change
The backup provider chain lives on the box; the number never reaches us at any stage.
Controls on the box and the platform
Only a digest goes to the timestamp service
The day's SHA-256 digest is sent to the RFC 3161 service; the record files stay on the box.
Role-based access
Every panel user sees only what their role allows; guest numbers are masked and the full number needs a specific permission.
Audit trail
Who viewed or exported which record, and when, is written on the box and on the platform separately.
Encrypted storage
Phone numbers are stored encrypted on the box; the device secret is stored encrypted.
Second archive copy goes where you choose
You set the SFTP/FTPS target; it is not sent to us.
Two-step platform sign-in
The admin panel needs a password plus an e-mailed code; device trust is limited to 24 hours.
Who is the data controller?
The business processes and stores guest data; because the platform never sees guest data it is not even a processor for that data. Get legal advice on how to word this split in your own documents (inventory, clarification text).
This page is a technical description, not legal advice.