Precyz
Sign inStart free

PRIVACY

What Precyz collects, field by field.

The field catalogue is generated from the enforced schema. Coverage limits, retention, and deletion behaviour are stated alongside each data class.

Trust version 2026.11.3 · generated 2026-11-14T09:12:04Z

Proof

What this page is for

This is the complete list. It is generated from the schema the software enforces, not written from memory, and it is republished on every release with a diff showing what changed.

Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.

On this page

What you get from this

Personal stores no history

Personal keeps a short in-memory live window. Nothing is stored as telemetry history.

Pro keeps 30 days

Pro retains connection metadata for 30 days, then purges it.

Team keeps 90 days

Team retains connection metadata for 90 days, with a separate audit history.

Enterprise is quoted

Retention is part of the quote. Collection stays connection metadata only.

Collection boundary

The boundary

We observe here

Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.

We never collect here

Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.

Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.

Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.

Availability across plans

Personal

Included

Pro

Included

Team

Included

Enterprise

Included