# Hide small numbers before you share

Count sensitive records by area, hold back the small counts, and check what the map you are about to publish could give away.

- **Who can use it:** Free, Creator and Creator Max
- **You provide:** Your records and the threshold you work to
- **You get:** A map and dataset with the small counts held back

Anyone who maps people meets the same problem before they publish: health, crime, children, benefits, casework. The pattern is the point of the map. But a count of one or two in a small area can point at a person.

The usual answer is called **small-number suppression**: counts below a threshold are not shown. Say the rule you work to, and Mapstack counts your records by area, holds back the small counts, and keeps the individual records out of what you share. Then ask it what else to check before you publish.

One real file runs through this page.

## Count by area, and hold back the small counts

The example here: one year of police incident records in a sensitive category, from the City of Chicago's open data. There are 1,628 records, most with the location of the block. A charity wants to show partners where incidents happen without anyone being able to pick out a household.

**The rule, as the charity gave it.** Count the incidents in each census tract. Show a count of 1 to 4 as "fewer than 5". A tract with none can show 0, because a zero gives nothing away. Show the count from 5 up.

**What came back.** Mapstack fetched the city's 789 census tracts itself and counted the records into them. Then it said how the rule had landed: 449 tracts held back, 247 with none, and 93 showing a count. That sentence is the note under your map.

**The held-back areas stay on the map.** They are their own class in the legend, so a reader sees that an area has something in it and does not read the gap as nothing.

**Records it could not place are reported.** Here 87 records had no location. Mapstack left them out, said so, and suggested a footnote. Leaving them out without saying would bias the map.

![Example: Chicago's 789 census tracts by the number of incidents in 2025. The 449 tracts with 1 to 4 are one class, "Fewer than 5", and no tract shows a count below 5.](/images/docs/hide-small-numbers/chicago-tracts-suppressed.jpeg)

### Count and hold back in one ask

Name the areas, the threshold and the words to show in place of the number.

> Count these incidents by census tract. Show 1 to 4 as "fewer than 5", and let tracts with none show 0

> How many tracts were held back, and how many records had no location?

## Keep the records out of what you share

Holding back the counts is not enough by itself. What matters is what travels with the map.

Say that the shared map and its data should hold the area and its count, and nothing from the individual records: no points, no dates, no descriptions. That is what Mapstack builds. Your records stay in your workspace, and they are not what you publish.

**Check the data behind the map, not only the map.** A column can still carry the true count where the map shows "fewer than 5". Ask what the dataset behind the map holds, and have anything you do not want taken out. In the example, Mapstack found that column, said so, and removed it on asking.

### Build the version you can share

> The shared map and data should hold only the tract and its count, and nothing from the individual records

> What columns does the dataset behind this map hold? Take out the true count

## Ask what it could still give away

The useful question before you publish is the one you have not thought of. So ask it plainly: what else should I check?

Mapstack names real risks. In the example it raised two:

- **The true count was still in the data behind the map.** A reader who downloads the data would see it.
- **A held-back number can be worked out.** If you publish a total for the city and a count for every other area, a reader can subtract.

Both are about arithmetic, not about the map. Ask, and decide what to do about each.

### Have it check before you publish

> What else should I check before I share this?

> Could someone work out a held-back count from this and a published total?

## Publishing it

A map with counts held back is shared like any other. See [Make something public](/docs/share/make-it-public) for the link and what public means, and [Download and export](/docs/share/download-and-export) for what leaves with a file.

**Figures someone else has held back stay held back.** Where a statistics office has already left out its own small counts, Mapstack keeps them as published. It does not fill them in.

## Reference

| | |
|---|---|
| The threshold | Yours. Name it, and the words to show in place of the number |
| Zeros | Shown as zero unless you say otherwise |
| What it reports | How many areas were held back, how many had none, how many show a count, and how many records it could not place |
| The shared dataset | Holds what you say it holds. Ask what is in it before you publish |
| Figures already held back by their publisher | Kept as published |

## What it can't do

- Tell you which threshold to use, or approve a release. It applies your rule and names what it can see. The decision to publish is yours.

## Common questions

**What threshold should we use?**

That is for your organisation, and often its regulator. Mapstack applies the one you name and reports how your data fell against it.

**Will the records themselves be in the published map?**

Only if you leave them there. Say that the shared map and its data should hold the area and its count alone. Then ask what the dataset behind it holds before you publish.

**Can someone work a held-back number out?**

Sometimes, by subtracting the published areas from a published total. Ask Mapstack to check for that against what you plan to publish.

**What about the records with no location?**

They are counted and reported, with a footnote you can use. They are never left out without a word.

## Related

- [Make something public](https://mapstack.io/docs/share/make-it-public.md)
- [Download and export](https://mapstack.io/docs/share/download-and-export.md)
- [Count and summarise by area](https://mapstack.io/docs/answers/count-and-summarise-by-area.md)
- [Check your data for problems](https://mapstack.io/docs/your-data/check-your-data.md)
- [Your data, privacy and security](https://mapstack.io/docs/workspace/your-data-and-privacy.md)
