Trust Center

Privacy and data handling

Kryptx Technologies LLC operates TrapLayer and publishes aggregate AI-agent threat activity while keeping raw honeypot evidence, customer data, and sensitive request details private.

What We Collect

TrapLayer collects security telemetry from decoy websites, APIs, documents, login pages, fake secrets, and canary artifacts.

MVP policy
Honeypot events
Request path, method, timestamp, classification, risk score, coarse geography, network attribution, client type, and privacy-preserving request fingerprints.
Private evidence
Operators may review request headers, payload snippets, canary identifiers, session context, and user-agent details in the private admin interface.
Service operator
Kryptx Technologies LLC operates the TrapLayer product under d.b.a. TrapLayer.
Customer accounts
Customer contact details, API-key metadata, feed usage, billing metadata, notification preferences, and account activity are stored for service operation.
Signup requests
Company name, contact name, email address, plan interest, and submitted use-case notes are stored as product leads.

Public Data Rules

The public dashboard, event summaries, reports, and unauthenticated APIs show sanitized aggregate data only.

Shown publiclyGreen data: counts, trends, severity, category, coarse country/network context, and normalized client type.
Kept privateRaw IP hashes, request headers, payloads, canary tokens, session IDs, full user agents, customer details, and API keys.
Paid defensive feedsYellow_1+ IOC feeds may include source IP indicators with confidence, context, TTL, and recommended defensive action. Yellow_2+ payload-intelligence feeds may include payload hashes, command-pattern labels, extracted payload URLs/domains, richer payload context, and related source IPs. Yellow_3 may include full ordered behavior timelines. These feeds exclude raw headers, payload bodies, tokens, credentials, red evidence, and private source IP hashes.
Map dataAttack-map locations are approximate and may use country-level or trusted edge-header attribution.

Retention and Controls

Retention is operator-configurable. Admin tools support event pruning, taxonomy backfills, feed auditing, and customer account control.

API keysCustomer API keys are hashed at rest and plaintext keys are shown only when issued.
Password resetsReset links use time-limited tokens and are audited separately from honeypot traffic.
Abuse handlingTrapLayer may rate limit, block, or investigate activity that threatens the service or its customers.

Security Contact

For privacy, security, or data-handling questions, contact Kryptx Technologies LLC through the TrapLayer customer or admin support channel configured for your deployment.

Intelligence summary

Summary