Skip to main content

Deliverd Screen for Python

A pre-send check for every prompt. Find and redact personal data, secrets and your own confidential terms before text goes to an AI model.

It runs locally, with no account, no key and no network call. It needs no dependencies and works on Python 3.9 and up. MIT.

pip install deliverd-screen
from deliverd_screen import screen

checked = screen("Reply to mary.byrne@example.ie about IBAN IE29AIBK93115212345678")
checked.verdict  # "redact"
checked.text     # "Reply to [EMAIL_1] about IBAN [IBAN_1]"

answer = model.generate(checked.text)
checked.restore(answer)  # the real values, back in the answer

allow sends the original; redact sends placeholders in place of what the model may not receive; ask means a person has to decide; deny sends nothing. By default a model may receive internal data and no personal data. Pass personal_data=True, classification="confidential" for one approved for more.

Names: plug in a model

from transformers import pipeline
from deliverd_screen.adapters import token_classifier, presidio

ner = pipeline("token-classification", model="dslim/bert-base-NER", aggregation_strategy="simple")
checked = screen(prompt, detectors=[token_classifier(ner)])

# or Presidio, in process:
from presidio_analyzer import AnalyzerEngine
checked = screen(prompt, detectors=[presidio(AnalyzerEngine())])

Any model with the same output works, including Perplexity's PII-Tracer and GLiNER. Check its licence before you ship it.

CLI

cat prompt.txt | deliverd-screen --redact
deliverd-screen --fail --json fixtures/*.json

A net, not a certificate

Structured identifiers are found well. Names are found only as well as the model you plug in, and redacted text about a person is still personal data under GDPR.

When a person has to decide, Deliverd's Data Gate asks them. deliverd.screen() in the deliverd SDK runs these same detectors and sends only counts. It takes the same detectors.

Metadata

Release files for deliverd-screen 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deliverd-screen 0.1.2
File Size Uploaded Provenance
deliverd_screen-0.1.2.tar.gz 14.5 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for deliverd-screen 0.1.2
File Interpreter ABI Platform
deliverd_screen-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 31.7 kB

Release files / deliverd_screen-0.1.2.tar.gz

Download URL deliverd_screen-0.1.2.tar.gz
Size 14.5 kB
Tags Source
SHA-256 checksum
How to use checksums
784e782f18802927cff33604411dc7044c5c5278783d3eed5b33bd2077f7e555
BLAKE2b-256 checksum
How to use checksums
8b24beb576a889d8279cc498d2f7dc3bf7293d7bdf76a5e2fc00764ccb5b3cce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Release files / deliverd_screen-0.1.2-py3-none-any.whl

Download URL deliverd_screen-0.1.2-py3-none-any.whl
Size 17.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
74369594c6a4b78c5793410e0e412b5df8194b945405910a87dd38e7e2bc02de
BLAKE2b-256 checksum
How to use checksums
e0474e1497397f273035e4e0802b5732a6fed0f7c7632d07255211f3afd8bc85
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Security for deliverd-screen 0.1.2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for deliverd_screen-0.1.2.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page