# Redactly — full content index

> Redactly is a PII detection and redaction API for text, JSON, and CSV. 30+ entity types, one HTTP call, no training or configuration. This file contains every public page concatenated in reading order.

Generated: 2026-10-26
Compact index: https://bitbanger.in/llms.txt
Machine-readable catalog: https://bitbanger.in/api/md/_catalog

---

<!-- source: https://bitbanger.in/ -->

# Redactly — PII detection and redaction API

> Redactly detects and redacts personally identifiable information in text, JSON, and CSV files. One API call returns your content with names, emails, phone numbers, SSNs, addresses, card numbers, and other entity types replaced, masked, or removed — no training or configuration required.

Canonical: https://bitbanger.in/
Last updated: 2026-10-26

## What is Redactly?

**Redactly** is a PII detection and redaction API for teams that handle sensitive text, JSON, and CSV data. It uses a custom model fine-tuned for AI labs to find 30+ entity types — names, emails, phone numbers, SSNs, addresses, card numbers — and redacts them in a single HTTP call, with no training, regex, or configuration required.

## At a glance

| Attribute | Value |
| :--- | :--- |
| Category | PII detection and redaction API |
| Input formats | Plain text, JSON, CSV |
| Entity types | 30+ (names, emails, phones, SSNs, addresses, IBANs, IPs, medical IDs) |
| Redaction styles | Replace, mask, or remove |
| Output | Redacted text plus entity list with character spans and confidence scores |
| Model | Custom model fine-tuned for AI labs |
| Interfaces | REST API, Python SDK, MCP server, CLI |
| Pricing | From $24/month, self-serve |
| Compliance | Designed for GDPR, HIPAA, and CCPA workflows |

## How it works

1. Send text to `POST https://api.bitbanger.in/v1/redact`, or send a `.json` or `.csv` file to `POST https://api.bitbanger.in/v1/redact/file`.
2. Redactly runs the detection model and returns every entity it found, with the character span and a confidence score.
3. The response contains your text with each span replaced by its label, masked with block characters, or removed entirely.

JSON input is walked recursively so string values at any depth are redacted. CSV input is redacted cell by cell with the table structure preserved.

## Capabilities

- **Detection** — 30+ entity types across personal identifiers, contact details, financial data, government identifiers, digital identifiers, and medical data.
- **Redaction styles** — `replace` turns `John Smith` into `[PERSON]`; `mask` overwrites with block characters matching the original length; `remove` deletes the span.
- **Confidence control** — set a threshold between 0 and 1 to trade precision for recall, per request or per entity type.
- **Audit output** — every response includes the entity list with type, matched text, span, and score, ready to log or export.
- **Webhooks** — pass `webhook_url` to have the result POSTed to your endpoint after redaction.
- **Integrations** — Slack, Notion, Google Workspace, Microsoft Teams, GitHub, Jira, Linear, Asana, a Python SDK, a CLI, and an MCP server.

## How does Redactly compare?

Three alternatives come up in every evaluation: an open-source framework, a cloud NLP service, and hand-written rules. Each one leaves you maintaining something.

- **Microsoft Presidio** — self-hosted means self-maintained. You own the inference service, its upgrades, and its on-call; it is Python only, so every other caller needs a wrapper you write; and JSON and CSV parsing is your code to build and keep tested.
- **AWS Comprehend Medical** — it finds PHI, then hands the problem back to you. `DetectPHI` returns character offsets rather than redacted text, caps calls at 20,000 characters of English clinical text, and covers medical notes only — no customer, HR, or financial records.
- **Hand-written regex rules** — patterns match shapes, so the rule set never ends. Rules cannot find names, addresses, or free-form record numbers, miss formatting variants while over-redacting lookalike IDs, and turn every new format into another rule, a test, and a regression.

Redactly runs a custom model fine-tuned for AI labs — nothing to deploy, no rules to maintain.

## Pricing

| Plan | Price | Includes |
| :--- | :--- | :--- |
| Starter | $24/month | Core detection, basic compliance reporting, email support, monthly redaction summary |
| Growth | $79/month | Everything in Starter, 30+ entity types, team collaboration, priority Slack support, analytics dashboard |
| Scale | $199/month | Everything in Growth, custom entity training, dedicated compliance manager, 4-hour SLA, on-premise deployment option |

All plans are billed monthly and cancellable at any time.

## Frequently asked questions

### Can Redactly integrate with our existing tools?

Yes. Redactly works with Slack, Notion, Google Workspace, Microsoft Teams, and more. The REST API and webhooks make connecting to any tool straightforward.

### What types of PII does Redactly detect?

Redactly detects names, email addresses, phone numbers, social security numbers, home addresses, dates of birth, IBANs, IP addresses, and dozens more entity types — out of the box, no training required.

### How long does it take to see results?

Most teams process their first documents within minutes of signing up. The API is ready immediately — no configuration or model training required.

### What types of companies work with Redactly?

Startups and enterprises across healthcare, finance, legal, and tech. If your team handles personal data, Redactly adapts to your compliance requirements.

### Does Redactly offer one-time use or ongoing plans?

Both. Use the API per request, or subscribe for volume discounts, priority support, and dedicated compliance features.

### What does onboarding look like?

It is self-serve. Create an account, get your API key, and POST your first document. Enterprise teams get a kickoff session and a tailored compliance roadmap.

## Contact

- Email: albie.dev422@gmail.com
- Phone: +91 94074 59327
- [API reference](https://bitbanger.in/docs)
- [Security and data handling](https://bitbanger.in/security)

## Related

- [API reference](https://bitbanger.in/docs) — endpoints, request fields, response shape, error codes
- [Security and data handling](https://bitbanger.in/security) — in-memory processing, key handling, compliance
- [Privacy policy](https://bitbanger.in/privacy)
- [Terms of service](https://bitbanger.in/terms)
- [Full content index](https://bitbanger.in/llms-full.txt)

---

<!-- source: https://bitbanger.in/docs -->

# Redactly API reference

> The Redactly API detects and redacts personally identifiable information in text, JSON, and CSV. Every request is authenticated with an API key and returns the redacted output together with the entities that were found.

Canonical: https://bitbanger.in/docs
Last updated: 2026-10-26

## Base URL

```
https://api.bitbanger.in
```

## Authentication

Every redaction endpoint requires an API key in the `X-API-Key` header. Keys start with `rdct_`. They are shown once at creation and only a SHA-256 hash is stored server-side, so a lost key has to be replaced rather than recovered.

```
X-API-Key: rdct_your_key_here
```

A missing, invalid, or revoked key returns `401`.

## POST /v1/redact

Redacts PII from a string. The response contains the original text, the redacted text, the entity list with character spans and confidence scores, and a count.

### Request body

| Field | Type | Required | Default | Description |
| :--- | :--- | :--- | :--- | :--- |
| `text` | string | yes | — | Text to redact. Must not be empty. |
| `style` | string | no | `replace` | One of `replace`, `mask`, or `remove`. |
| `threshold` | number | no | `0.5` | Minimum confidence between 0 and 1. |
| `entities` | string[] | no | all types | Restrict detection to specific labels, for example `["PERSON","EMAIL"]`. |
| `webhook_url` | URL | no | — | If set, the result is also POSTed to this URL after redaction. |

### Example request

```bash
curl -X POST https://api.bitbanger.in/v1/redact \
  -H "X-API-Key: rdct_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Call John Smith at 555-867-5309 or john@acme.com",
    "style": "replace",
    "threshold": 0.5
  }'
```

### Response

```json
{
  "original": "Call John Smith at 555-867-5309 or john@acme.com",
  "redacted": "Call [PERSON] at [PHONE] or [EMAIL]",
  "entities": [
    {
      "entity": "PERSON",
      "text": "John Smith",
      "start": 5,
      "end": 15,
      "score": 0.998
    }
  ],
  "entity_count": 3
}
```

| Field | Type | Description |
| :--- | :--- | :--- |
| `original` | string | The input text, unchanged. |
| `redacted` | string | The same text with detected spans transformed by the chosen style. |
| `entities` | array | One object per hit: `entity`, `text`, `start`, `end`, `score`. |
| `entity_count` | integer | Number of entities redacted. |

## POST /v1/redact/file

Redacts a `.json` or `.csv` upload and returns a redacted file. JSON is walked recursively so every string value at any depth is redacted; CSV is redacted cell by cell with the structure preserved.

### Form fields

| Field | Type | Required | Default | Description |
| :--- | :--- | :--- | :--- | :--- |
| `file` | file | yes | — | A `.json` or `.csv` file. Other extensions return `422`. |
| `style` | string | no | `replace` | `replace`, `mask`, or `remove`. |
| `threshold` | number | no | `0.5` | Minimum confidence between 0 and 1. |

### Example request

```bash
curl -X POST https://api.bitbanger.in/v1/redact/file \
  -H "X-API-Key: rdct_your_key_here" \
  -F "file=@customers.csv" \
  -F "style=mask" \
  -F "threshold=0.6" \
  --output customers_redacted.csv
```

JSON input returns `application/json` with the filename suffix `_redacted.json`. CSV input returns `text/csv`.

## GET /health

Returns service status and the identifier of the detector build currently loaded. The identifier is opaque and changes when the detector is upgraded; treat it as a version string rather than a product name.

```bash
curl https://api.bitbanger.in/health
```

```json
{"status":"ok","model":"redactly-pii-encoder-v1"}
```

## Redaction styles

| Style | Output | Use when |
| :--- | :--- | :--- |
| `replace` | `John Smith` becomes `[PERSON]` | You need the document to stay readable for a human reviewer. |
| `mask` | Block characters matching the original length | You want to preserve layout and character counts. |
| `remove` | Deleted entirely | You want no trace of the value in the output. |

## Entity types

Redactly detects 30+ entity types out of the box, grouped into personal identifiers (names, usernames, dates of birth), contact details (emails, phone numbers, addresses), financial data (card numbers, IBANs, bank accounts), government identifiers (SSNs, passport and driver's licence numbers), digital identifiers (IP and MAC addresses), and medical data (record and health plan numbers).

Use the `entities` field on `/v1/redact` to restrict a request to specific labels.

## Errors

| Status | Cause |
| :--- | :--- |
| `401` | Missing, invalid, or revoked API key. |
| `422` | Empty `text`, an unsupported file extension, or malformed JSON or CSV. |
| `503` | The model is still loading. Retry shortly. |

## Related

- [Home](https://bitbanger.in/) — product overview, comparison, pricing, FAQ
- [Security and data handling](https://bitbanger.in/security)
- [llms.txt](https://bitbanger.in/llms.txt) — compact index for language models
- [llms-full.txt](https://bitbanger.in/llms-full.txt) — every page concatenated

---

<!-- source: https://bitbanger.in/security -->

# Security and data handling

> Redactly processes documents that contain personal data, so the security model is deliberately small: text is redacted in memory, responses are returned synchronously, and request bodies are not written to storage.

Canonical: https://bitbanger.in/security
Last updated: 2026-10-26

## How your data is handled

- **In memory only.** Request bodies are redacted in the running process and returned in the response. Redactly does not persist submitted text or files.
- **No training on customer data.** Documents you send are not used to fine-tune or otherwise train the detection model.
- **API keys are hashed.** Keys are generated with 192 bits of randomness, prefixed `rdct_`, shown once, and stored only as a SHA-256 hash. Revoking a key takes effect immediately.
- **Output is irreversible.** Replaced, masked, and removed spans cannot be recovered from the redacted output. If you need reversibility, keep the original in your own system.

## Transport and infrastructure

- The marketing site is served by Cloudflare Pages with HSTS enabled, `X-Frame-Options: DENY`, `X-Content-Type-Options: nosniff`, and a restrictive Content Security Policy.
- All traffic is served over HTTPS. Plain HTTP requests are redirected to HTTPS with a 301.
- The API runs as a container behind an HTTPS proxy with a health check and automatic restart on failure.
- The API only accepts cross-origin browser requests from the Redactly domains. Other origins are rejected by CORS.

## Compliance frameworks

Redactly is designed for teams operating under GDPR, HIPAA, and CCPA, and maps its controls to SOC 2 and ISO 27001.

- **GDPR** — data minimisation by design: only the text you submit is processed, and nothing is retained.
- **HIPAA** — redaction of the 18 identifier categories before data reaches analytics or downstream systems.
- **CCPA** — removal of personal information from datasets before sharing or export.

Enterprise plans include a Data Processing Agreement and a configurable retention policy. Ask for the current security documentation before your procurement review.

## Responsible disclosure

If you believe you have found a vulnerability, email albie.dev422@gmail.com with steps to reproduce. Please do not open a public issue or test against data that is not yours. Reports are acknowledged within two business days.

## Contact

- Email: albie.dev422@gmail.com
- Phone: +91 94074 59327

## Related

- [Home](https://bitbanger.in/)
- [API reference](https://bitbanger.in/docs)
- [Privacy policy](https://bitbanger.in/privacy)
- [Terms of service](https://bitbanger.in/terms)

---

<!-- source: https://bitbanger.in/privacy -->

# Privacy policy

> This policy explains what Redactly collects, why, and how long it is kept. It covers the website at bitbanger.in and the API at api.bitbanger.in.

Canonical: https://bitbanger.in/privacy
Effective: 2026-10-26

## Who we are

Redactly is a PII detection and redaction service. For the purposes of the GDPR, Redactly acts as a data processor for the documents you submit through the API, and as a controller for the limited website data described below.

## What we collect

| Data | When | Purpose |
| :--- | :--- | :--- |
| Name, email address, and message | When you use the contact form | To reply to your enquiry. The form opens your own email client — nothing is sent to or stored on our servers. |
| Text, JSON, or CSV you submit to the API | On each API request | To perform redaction and return the result. Processed in memory and not retained. |
| API key and plan | When a key is issued | To authenticate requests. Only a hash of the key is stored. |
| IP address and request metadata | On any request | Handled by our infrastructure providers for delivery, abuse prevention, and error diagnostics. |

We do not use advertising cookies, and we do not run third-party analytics or tracking pixels on this site.

## Third-party services

- **Cloudflare** — hosts the website and provides DNS, TLS, and network protection.
- **Railway** — hosts the API container and forwards requests to it.
- **Google Fonts** — serves the Inter typeface. Your browser requests the font directly from Google, which receives your IP address.

We do not sell personal data and do not share it with anyone else except where required by law.

## Retention

Redacted documents are not stored. API key records are kept while the key is active and for as long as needed to prevent re-use after revocation. Email correspondence is kept for up to 24 months.

## International transfers

Our infrastructure providers operate globally, so requests may be processed outside your country. Transfers rely on the providers' standard contractual clauses and equivalent safeguards.

## Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict, or port your personal data, to object to processing, and to withdraw consent. To exercise any of these, email albie.dev422@gmail.com. You can also complain to your local data protection authority.

## Children

The service is intended for business use and is not directed at anyone under 16. We do not knowingly collect data from children.

## Changes

We will update the effective date above when this policy changes. Material changes will be announced on this page.

## Contact

- Email: albie.dev422@gmail.com
- Phone: +91 94074 59327

## Related

- [Home](https://bitbanger.in/)
- [Security and data handling](https://bitbanger.in/security)
- [Terms of service](https://bitbanger.in/terms)

---

<!-- source: https://bitbanger.in/terms -->

# Terms of service

> These terms govern your use of the Redactly website and API. By creating a key or sending a request, you agree to them.

Canonical: https://bitbanger.in/terms
Effective: 2026-10-26

## 1. The service

Redactly detects and redacts personal information in text, JSON, and CSV. Detection is probabilistic: the service returns entity spans with confidence scores, and you decide what threshold is appropriate for your use case.

## 2. Accounts and API keys

- You are responsible for keeping your API key confidential and for all requests made with it.
- Keys are shown once. If a key is lost, request a replacement; it cannot be recovered.
- Notify us promptly if you believe a key has been compromised so it can be revoked.

## 3. Acceptable use

You agree not to use the service to process data you are not lawfully entitled to process, to attempt to extract the underlying model, to resell raw API access without a written agreement, or to interfere with the availability of the service for others.

## 4. Plans and billing

Plans are billed monthly in advance. Published prices are in US dollars and exclude applicable taxes. You can cancel at any time; access continues to the end of the paid period. We do not provide refunds for partial periods unless required by law.

## 5. Availability

We aim to keep the API available continuously and will give notice of planned maintenance where practical. The free and self-serve tiers are provided without an uptime commitment. An SLA is available on the Scale plan.

## 6. Your data

You keep all rights to the content you submit. You grant us only the temporary right to process it in order to return a redacted result. We do not use submitted content to train models. See the privacy policy for details.

## 7. Intellectual property

The service, including its model configuration, documentation, and site content, remains our property. These terms do not transfer any ownership to you.

## 8. Disclaimers

The service is provided "as is". Automated detection can miss entities or flag text incorrectly. You are responsible for reviewing output before relying on it for a regulatory, legal, or clinical decision.

## 9. Limitation of liability

To the maximum extent permitted by law, we are not liable for indirect, incidental, or consequential damages, or for lost profits or lost data. Our total liability for any claim is limited to the amount you paid us in the twelve months before the claim.

## 10. Termination

You may stop using the service at any time. We may suspend or terminate access if these terms are breached or if required by law.

## 11. Changes

We may update these terms and will change the effective date above. Continued use after an update means you accept the revised terms.

## 12. Contact

- Email: albie.dev422@gmail.com
- Phone: +91 94074 59327

## Related

- [Home](https://bitbanger.in/)
- [Privacy policy](https://bitbanger.in/privacy)
- [Security and data handling](https://bitbanger.in/security)

---