SSQ.AISSQ.AI
English
help!

Privacy Risk Analysis

Risks in how personal data is processed, used and moved

We follow personal data from the apps, web pages and IoT devices your customers use to your servers and outside services, and find where it could leak.

An analysis for organisations that run customer-facing services such as shopping, banking or booking, or that build apps and IoT products.

Where in our service could personal data leak out?

We find where it could leak today and the risks not yet visible, and set out what to fix first and how.

Expert reviewed

DATA How personal data moves IoT devices Apps Web pages Servers & cloud Third parties Ad & analytics tools Bypassing your servers RULE ‘Nothing reaches ad or analytics tools without consent’
Ad and analytics tools placed in a web page can take personal data straight from the browser, without it ever passing your servers. Flows like this show up only when you check in the browser and the app themselves.

When it fits

  • You run a service your customers use directly

    If customers sign up to and use your service, as with shopping, banking, booking or a community, we start with whether customer data could be getting out now and where trouble could start later. If you handle data that does real harm once exposed, such as health, financial or location data, its protection comes first.

  • You build apps or products your customers use

    If you make products that end up in customers' hands, such as mobile apps, IoT devices like wearables and smart-home kit, or SDKs, we check before release or once live that customer data is not slipping out through them.

  • You use customer data for analytics, AI or new business

    You move data into analytics and development environments, or use it to train AI, in outside AI services or in a data business, and want to see that pseudonymisation and access control actually hold.

  • You want the real state, not just the paperwork

    Your policies and documents are in place for privacy rules, and you want to know your systems and data actually behave that way. If you outsource processing or process data for another company, we also look at what changes hands between you and how.

The SAFE SQUARE approach

What actually happens

We analyse the apps and web pages your customers use, and the firmware and traffic of their devices, and find even the data that goes straight out from the browser or the device.

Whether the data can really be reached

Where needed, we test, as in a penetration test, whether someone without the rights can actually reach the data, so each risk comes with proof.

Paper against practice

We compare the flows described in your privacy notice, consent screens and internal documents with how data really moves, and find where it differs from what customers were told.

What we look at

Every service holds personal data in different places, and it can slip out by different routes, so we look across the whole service for what needs checking. Below are some of the things we often look at in each area.

  • APPMobile apps
    • Personal data and sign-in details left unprotected on the phone
    • Data taken by the advertising and analytics SDKs inside the app, or through permissions beyond what it needs
    • Server data that keys and connection details inside the app open up
  • WEBWeb pages
    • What the advertising and analytics tags and third-party scripts on your pages take
    • Data riding along in page addresses (URLs) or server responses
  • DEVICEIoT devices and wearables
    • The video, audio, location and health data the device sends to its app and the cloud
    • What survives a factory reset, or shows to others sharing the device
  • SERVERServers and internal systems
    • Personal data piling up in logs and backups
    • Data open wider than needed, as on support and admin screens
    • Access that has slipped out of management, such as leavers' accounts or public share links
  • FLOWUse, transfer and deletion
    • Data moving into analytics and AI environments, to processors or abroad
    • Data still there after it should have been deleted
Conditions we might test

‘The app does not collect location while it is not in use’
‘After a factory reset, no recordings or account details are left’
‘A leaver's account cannot reach customer data’

How it runs

  1. Map the service

    Together we map how the service is built and what personal data it handles, then set the conditions that must hold.

  2. Agree access and safety

    We agree how far we go, the material we need and how we will work.

  3. Analyse and verify

    We examine how the apps, pages and devices really behave and how the servers are set up, who can reach what and what is kept, and record the evidence for each risk.

  4. Explain the results

    We take your privacy team and the people who build and run the service through each risk and how to fix it, together.

How any personal data we see along the way is handled, and how much of it appears in the results, is agreed with you before we start.

What you receive

Where personal data is and where it goes

Where personal data actually sits and where it goes, from apps, pages and devices to your servers and outside services. Anything that differs from what customers were told and agreed to is marked separately.

Present and latent risks

We separate risks that could lead to a leak now from those that would grow alongside another problem or as the service changes. For each, the evidence we found and whose data, and what kind, would be affected.

Priorities and how to improve

What to fix first, with specific proposals for changing the rules on collection, retention, access and deletion and the settings in your apps, devices and servers.

What was left out

The data and systems outside this round, written down so they can be picked up next time.

A sample analysis resultFictional example
What we looked at

A members' shopping app and website

Covering: the Android and iOS apps, the website, the order and customer service systems, and outside integrations

WhereFindingEvidence
Website order confirmation pageRisk nowAn ad analytics tag takes the whole address (URL), which carries the customer's name and phone number.
Android appRisk nowDelivery addresses and order history stay on the phone, unencrypted, after logging out.
Customer service admin screenLatent riskAny agent can download the full customer list. Nobody has yet, but one stolen agent account would mean a mass leak.
Outside AI chat toolLatent riskChat transcripts go to an outside AI service without pseudonymisation. Today they are only order queries; widen the service and sensitive details would go too.
Account deletionNo issueA former member's data is removed from the order database and the backups once the set period has passed.
Data affected
Customers' names and phone numbers are already reaching an ad company, and the admin screen lets a single account take out every customer's data.
Fix first
Take the personal data out of the confirmation URL and fix which values the ad tag receives. In the app, encrypt what is stored on the phone and clear it on logout. On the admin screen, limit who can download and how much, and log it.
Scope

This is a technical analysis of how your systems and data really are. A statutory privacy impact assessment, ISMS-P or other certification audits, and legal advice follow their own processes. Whether data has already leaked is checked in Leaked Information Analysis.

  1. Tell us what worries you, or what you want checked. A few lines are enough.

  2. We reply with a proposed scope, schedule and cost, and settle them with you.

  3. Once agreed, the work begins. Results and next steps come to you as it runs.