---
title: "General-Purpose Starter Policy"
description: "Stop sending sensitive data to third-party APIs. Philterd ships open source PII and PHI redaction that runs inside your cloud. For HIPAA, GDPR, and CCPA work."
url: "https://philterd.ai/policies/general/general-purpose/"
---

[← All policies](https://philterd.ai/policies/)

General · Philterd

# General-Purpose Starter Policy

A balanced starting policy covering common PII types — names, contact info, government IDs, payment data — with no vertical-specific tuning.

[View policy →](https://philterd.ai/policies/general/general-purpose/#policy-json) [Download JSON →](https://raw.githubusercontent.com/philterd/pii-redaction-policies/main/policies/philterd/general/general-purpose.json) [View source on GitHub](https://github.com/philterd/pii-redaction-policies/blob/main/policies/philterd/general/general-purpose.md)

**v2.0.0** Updated 2026-10-26 Philter `>=4.0.0` By Philterd

starter general default

## The policy

The full `general-purpose.json` file. The same content you’d get by downloading. Copy any part of it, or use the buttons in the hero to grab the whole file.

```
{
  "config": {
    "splitting": {
      "enabled": false,
      "threshold": 4000
    }
  },
  "ignored": [],
  "identifiers": {
    "person": {
      "phEyeConfiguration": {
        "modelPath": "ph-eye-pii-en-small",
        "labels": [
          "name"
        ]
      },
      "phEyeFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}",
          "condition": "confidence > 0.70"
        }
      ]
    },
    "phoneNumber": {
      "phoneNumberFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "emailAddress": {
      "emailAddressFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "ssn": {
      "ssnFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "creditCard": {
      "onlyValidCreditCardNumbers": true,
      "creditCardFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "ipAddress": {
      "ipAddressFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "url": {
      "urlFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "ibanCode": {
      "ibanCodeFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "passportNumber": {
      "passportNumberFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    },
    "driversLicense": {
      "driversLicenseFilterStrategies": [
        {
          "strategy": "REDACT",
          "redactionFormat": "{{{REDACTED-%t}}}"
        }
      ]
    }
  }
}
```

## Example

Input

```
Contact Jane Doe at jane@example.com or 555-867-5309. Card 4111111111111111 on file. License #D1234567.
```

Output

```
Contact {{{REDACTED-name}}} at {{{REDACTED-email-address}}} or {{{REDACTED-phone-number}}}. Card {{{REDACTED-credit-card}}} on file. License #{{{REDACTED-drivers-license}}}.
```

## Entities this policy acts on

NAME PHONE EMAIL SSN CREDIT\_CARD IP URL IBAN PASSPORT DRIVERS\_LICENSE

## What this policy does

A reasonable default for “I just want to redact common PII without thinking about it too hard.” Catches:

- **Personal identity**: names (confidence-gated to reduce false positives), passport numbers, driver’s license numbers
- **Contact info**: phone numbers, email addresses, URLs, IP addresses
- **Government identifiers**: SSNs
- **Financial**: credit cards (Luhn-validated), IBANs

Does **not** cover:

- Healthcare-specific identifiers (MRN, hospital names) — use a [healthcare policy](https://philterd.ai/policies/healthcare/) instead
- PCI-specific masking (this policy fully redacts cards; for PCI scope reduction with last-4 visible, use [pci-dss-scope-reduction.json](https://philterd.ai/policies/finance/pci-dss-scope-reduction/))
- Court-filing rules (use [legal policies](https://philterd.ai/policies/legal/))
- Custom identifiers (MRNs, account numbers, internal IDs) — add `identifiers` patterns for your domain

## When to use this

- **Quick starts** when you’re evaluating Philter against your data
- **Catch-all log scrubbing** in non-regulated environments
- **Default-deny** posture: redact aggressively, then loosen specific entity types as your use case clarifies

## When NOT to use this

- **Regulated workloads.** HIPAA, PCI, GDPR, FERPA, and similar regimes have specific requirements — use a policy designed for that framework.
- **Datasets where over-redaction breaks downstream value.** This policy is biased toward over-redaction. For research, ML, or analytics use cases, see the date-shifted clinical-notes policy or build a domain-specific one.

## When to customize

- **Name confidence.** Default `> 0.70` is moderately conservative. Lower to `> 0.50` for higher recall (catches more rare/foreign names at the cost of false positives on capitalized common words). Raise to `> 0.85` for higher precision.
- **URL and IP redaction.** Some applications need to retain these for analytics. Remove the `url` or `ipAddress` entries if so.
- **Add custom identifiers** for any deployment-specific patterns: internal customer IDs, ticket numbers, employee badges, etc.

## Tuning workflow

1. Run this policy against a representative sample of your data.
2. Inspect the redactions. Note any over-redaction (legitimate text caught) or under-redaction (PII missed).
3. Tighten thresholds, add `ignored` terms, or add custom `identifiers` patterns based on what you find.
4. Re-evaluate. Repeat until precision and recall meet your bar.

[Philter Scope](https://philterd.ai/philter-scope/) automates step 3 — score policy changes against a gold-standard test set so you can measure regressions instead of guessing at them.

## Using this policy with Phileas

The name filter names `ph-eye-pii-en-small`, the model bundled with Philter 4.0. With Phileas, set its `modelPath` to the directory of a downloaded copy of the model, [philterd/ph-eye-pii-en-small](https://huggingface.co/philterd/ph-eye-pii-en-small).

## Use this policy

Download and load into your running Philter instance:

```
# Download the policy
curl -O https://raw.githubusercontent.com/philterd/pii-redaction-policies/main/policies/philterd/general/general-purpose.json

# Upload it to Philter as general-purpose
curl -sk -X POST "https://localhost:8080/api/policies?name=general-purpose" \
     -H "Authorization: Bearer $PHILTER_API_KEY" \
     -H "Content-Type: application/json" \
     --data @general-purpose.json

# Redact text with it
curl -sk "https://localhost:8080/api/filter?p=general-purpose" \
     -H "Authorization: Bearer $PHILTER_API_KEY" \
     -H "Content-Type: text/plain" \
     --data-binary "your text here"
```

For Philter 4.0. No Philter instance yet? The [quick start](https://philterd.ai/dev/start/) runs one and shows where `PHILTER_API_KEY` comes from · Want to tune this policy against your data? [Talk to the team](https://philterd.ai/policies/general/general-purpose/#).

[← All policies](https://philterd.ai/policies/)
