---
title: "Static IP Proxy Security and Zero-Knowledge"
description: "How the Fixedmark static IP proxy protects traffic: zero-knowledge TLS passthrough, no content logging, a TLS-wrapped proxy endpoint, and per-token allowlists."
canonical: https://fixedmark.com/security
updated: 2026-11-03
source: Fixedmark (https://fixedmark.com), BitMask LLP
---

Security

# Static IP proxy security

Fixedmark passes your TLS traffic through without decrypting it and never logs request content. The TLS proxy endpoints on ports 443 and 1443 keep your proxy credentials encrypted, and per-token destination allowlists limit what a leaked token can reach.

Draft for legal review.

This page describes what the Fixedmark service does today. It is not yet in force, and the highlighted fields are filled in after review.

Fixedmark is in development with an early-access list. This page describes the security design for launch. Fixedmark is operated by BitMask LLP.

- ## Zero-knowledge passthrough

  HTTP CONNECT and SOCKS5 relay your TLS connection byte for byte. The proxy never holds your destination's certificate keys and cannot read requests, responses, headers, or bodies.

- ## No content logging

  No request or response content is logged on any plan. Connection metadata (time, client IP, host, port, SNI, bytes, egress IP, result) goes to your connection logs for your plan's retention, and to Fixedmark's operational logs for 30 days.

- ## TLS-wrapped proxy endpoint

  Your app connects to the proxy over TLS: HTTP CONNECT on port 443, or SOCKS5 over TLS on port 1443, which fm tunnel uses. Proxy credentials are encrypted in transit. The plain HTTP proxy on port 8080 and plain SOCKS5 on port 1080 send the token in cleartext, so use them only where a client cannot speak TLS to a proxy, and scope those tokens with destination allowlists.

- ## Per-token destination allowlists

  Limit each token to the hosts and ports it needs, such as api.razorpay.com:443 and db.example.com:5432. A leaked token cannot reach anything else.

## Destination allowlists

Each token can carry its own list of allowed destinations. The proxy refuses connections to anything outside the list.

**Example**

```yaml
token: payouts-prod
allow:
  - api.razorpay.com:443
  - db.example.com:5432
```

Illustrative. The final configuration format is set at launch.

## Abuse policy

Static IPs only work if partners trust them. One abusive account can get a shared IP blocklisted for every customer on it, so these uses are not allowed:

- No web scraping or crawling.
- No rotating or residential proxy use. Fixedmark sells fixed IPs only.
- No outbound mail on port 25. See the support docs for mail ports.
- No spam, credential stuffing, or attacks on third parties.

Retention

## What we keep, and for how long

Fixedmark never stores the content of your traffic. Connection logs hold metadata only, and are deleted after the number of days your plan includes. Operational logs, which also record each connection's metadata, and database backups are kept for 30 days. The [data processing agreement](https://fixedmark.com/dpa) lists everything we keep and every sub-processor.

| Plan     | Connection logs kept |
| -------- | -------------------- |
| Starter  | 1 day                |
| Pro      | 7 days               |
| Business | 30 days              |
| Scale    | 30 days              |

Compliance

## Compliance roadmap

Fixedmark does not hold a SOC 2 report today. We will update this table when that changes.

| Item                            | Status                  |
| ------------------------------- | ----------------------- |
| Public security page            | Now (this page)         |
| Data processing agreement (DPA) | Draft published at /dpa |
| SOC 2 Type I                    | Planned after launch    |
| SOC 2 Type II                   | Planned after Type I    |

## Who operates Fixedmark

Fixedmark is built and operated by [BitMask LLP](https://bitmask.in/), based in India. Read more [about Fixedmark](https://fixedmark.com/about) and the [website privacy policy](https://fixedmark.com/privacy).

Report an issue

## Vulnerability disclosure

- ### Contact

  Email <support@fixedmark.com> with what you found, the steps to reproduce it, and how to reach you. The same contact is in [security.txt](https://fixedmark.com/.well-known/security.txt).

- ### Scope

  fixedmark.com, the dashboard, the API, the status page, the proxy endpoints of your own account, and the `fm` CLI. Out of scope: other customers' accounts and traffic, denial of service, spam, social engineering, and our providers' own platforms.

- ### Response target

  We acknowledge every report within 2 business days, tell you our assessment within 10 business days, and keep you updated until it is fixed. Give us reasonable time to fix an issue before you disclose it, and test only against your own account.

## Related

- [Data processing agreement](https://fixedmark.com/dpa)
- [Terms of service](https://fixedmark.com/terms)
- [All features, at launch and on the roadmap](https://fixedmark.com/features)
- [Docs quickstart](https://fixedmark.com/docs)
- [Static IPs for bank and UPI partner APIs](https://fixedmark.com/use-cases/bank-and-upi-apis)

## Frequently asked questions

### Does Fixedmark decrypt or log my traffic?

No. HTTPS traffic passes through the proxy as an encrypted TLS tunnel and is never decrypted. Fixedmark does not log request or response content on any plan.

### What does Fixedmark log?

Only connection metadata, never content: time, your client IP, destination host and port, TLS SNI, bytes sent and received, the egress IP used, and the result. The connection logs in your dashboard keep it for your plan's retention, and Fixedmark's operational logs keep it for 30 days to run and secure the service.

### Why is the proxy endpoint TLS-wrapped?

A plain HTTP proxy sends your proxy credentials in a Basic auth header that anyone on the path can read. Fixedmark's HTTPS proxy endpoint on port 443 and its SOCKS5 over TLS on port 1443 use TLS, so the credentials are encrypted between your app and the proxy.

### Is Fixedmark SOC 2 certified?

No. Fixedmark is in early access. A SOC 2 Type I report is planned after launch. Today we publish this security page and offer a data processing agreement on request.

### How do I report a security issue?

Email support\@fixedmark.com with the details and steps to reproduce. We acknowledge every report within 2 business days. The vulnerability disclosure section on this page has the scope and the rules, and fixedmark.com/.well-known/security.txt carries the same contact.
