What leaves your device
This page is about technology and practice. The legal side is in the privacy policy. Here we describe what is actually sent, why, and what never is.
The protection does not need your data
Many security products have to read through what you are working on in order to do their job. A file scanner has to open the files. An email filter has to read the messages.
WF SecurityCloud builds on the opposite logic. Knowledge of what is dangerous comes from the outside — from attack attempts against the sensor network. Your device only needs to know which addresses to say no to, and it can learn that without telling us anything about you.
What we handle, and what we do not
Details we handle
- Addresses and domains known for attacking
- Events about what was blocked: address, type and time
- Which of your devices reported the event
- Account details: name, email, company and billing information
- Licence details: how many licences you hold and where they are used
Details we never touch
- The contents of your files and documents
- The contents of your email
- Which websites you visit that are not blocked
- What you write, open or save
- The contents of traffic — only that a connection was stopped
Why the events are needed
When your device stops something, an event is sent in. That is the only ongoing reporting from the device, and it exists for two reasons.
The first is yours: without the events the panel would be empty, and you could not tell whether the protection was doing anything or whether something was wrong. The second is shared: repeated hits against the same address confirm that it is still active.
An event contains the address that was blocked, what type of event it was, the time, and which of your devices it concerned. Not what the connection would have contained.
- The address that was blocked
- Event type, for example brute force or known malicious address
- Time
- Which of your devices it concerned
Operation and storage
The service is run by Webbfabriken AB. Account details and blocking events are stored in our own operating environment. Payments are handled by Stripe, which receives the details required to complete the transaction — we store no card details.
If you want to know exactly what is held about your account, have it disclosed or erased, get in touch. The procedures are described in the privacy policy and on the GDPR page.
Questions about data handling?
We would rather answer concretely than generally. Describe what you need to know and we will go through it.