How TrapLayer handles public telemetry, customer records, evidence, account data, and retention controls.
Trust Center
Public-safe threat intelligence with clear data boundaries.
TrapLayer separates public observatory telemetry, paid customer intelligence, private evidence, billing records, and operational controls so security teams can use the signal without exposing sensitive collection details.
Defensive-use restrictions, feed licensing, API entitlement boundaries, service limits, and billing terms.
Submit misuse, security, or abuse concerns to TrapLayer operators for review and response.
Start a trial or request paid access to TrapLayer intelligence feeds, reports, dashboards, and API keys.
Authentication, schemas, rate limits, SIEM examples, error codes, versioning, freshness, and cache guidance.
Boundary Model
What public visitors can see
| Public observatory | Aggregated counts, approximate mapped activity, sanitized categories, weekly trends, and public-safe reporting. |
| Customer feeds | Tenant-scoped indicators and reports gated by paid data tier, API key, rate limit, and subscription state. |
| Private evidence | Raw request evidence, payload bodies, canary tokens, operational logs, customer records, and administrative controls stay behind authenticated operator/customer surfaces. |
Buyer Packet
Security, safety, and response contacts
Use this packet during vendor review and early customer due diligence.
| Security overview | TrapLayer separates public observatory data, customer intelligence, billing records, operator controls, and collector evidence. Customer feeds are tenant-scoped and gated by subscription state, API key, data tier, and rate limit. |
| Data handling | Commercial feeds exclude raw payload bodies, raw headers, credentials, canary token values, session IDs, and red evidence unless a separate written agreement and review process authorizes deeper handling. |
| Legal boundaries | TrapLayer intelligence is licensed for defensive use. Public redistribution, resale, hack-back, scanning back, retaliation, unlawful targeting, or attempts to identify individuals are prohibited unless a separate written agreement allows a specific partner use case. |
| DPA template | TrapLayer can provide a data processing addendum for customers that need documented processing roles, retention, security contacts, subprocessors, and deletion obligations before production use. |
| Sensor safety model | Sensors are deception facades. They are designed not to relay outbound abuse, not to expose real customer systems, and not to place raw secrets into ordinary commercial feeds. |
| Abuse contact | Use Report abuse for provider complaints, security reports, or suspected misuse involving TrapLayer infrastructure. |
| Incident-response contact | Existing customers should use their customer support contact and include tenant ID, affected API key label, timestamps, request IDs, and observed impact. |
Critical Infrastructure
Yellow 4 is approval-only
SCADA, OT, and critical-infrastructure intelligence is not implied by public access, trial access, or Enterprise access.
Yellow 4 requires a written use-case description, operator approval record, and customer-specific entitlement enablement. Trial requests for Critical Infrastructure start at Yellow 3 until Yellow 4 is approved.