Security & Privacy
MagenTrust is designed to be compliant with modern privacy expectations and regulatory environments.
Privacy by Design
No Fingerprinting
MagenTrust does not use browser fingerprinting techniques.
No Biometrics Required or Stored
No biometrics required or stored. Integrates with existing biometric systems when needed.
No Cross-Site Tracking
Sessions are isolated per site. No cross-domain tracking.
First-Party Context Only
All signals are collected in first-party context only.
Edge Processing
Signals are processed at the edge to minimize data retention.
No Cookies Required
Works without cookies or persistent storage.
Data Handling
What We Collect
- • Session-level behavioral context (anonymous)
- • API request metadata (timestamps, response codes)
- • Site identifiers for multi-tenant isolation
What We Don't Collect
- • Personal identifiable information (PII)
- • IP addresses (not stored)
- • Browser fingerprints
- • Cross-site behavioral data
- • Form input content
Data Retention
Session context is processed at the edge and not persisted beyond the verification lifecycle. Aggregated analytics are retained for reporting purposes only.
Security Measures
API Key Authorization
All requests require valid API keys with domain restrictions and rate limiting.
Domain Allowlisting
API keys are bound to specific domains to prevent unauthorized usage.
TLS Encryption
All communication is encrypted in transit using TLS 1.3.
Stateless Architecture
Edge processing is stateless. No long-term session storage.
Rate Limiting
Built-in rate limiting protects against abuse and ensures fair usage.
Multi-Tenant Isolation
Site IDs ensure complete data isolation between clients.
Compliance Considerations
MagenTrust's privacy-first architecture is designed to align with modern regulatory requirements:
No PII collection, legitimate interest basis
No personal information sale or sharing
No cookies or persistent identifiers
Note: Compliance depends on your specific use case and jurisdiction. Consult with legal counsel for your implementation.
Our Approach
MagenTrust provides funnel integrity and human-verification infrastructure—not "perfect bot detection." We focus on verifiable vs unverifiable traffic,confidence-based assessment, and attribution and insight rather than enforcement.
Transport and data handling
All connections require TLS 1.2 or higher, and TLS 1.3 is preferred. Cipher suites follow NIST SP 800-52 Rev. 2 guidance.
Behavioral signals are processed ephemerally into scores. No raw behavioral data or biometric templates are stored.
If MagenTrust is unreachable
Customers choose how each protected action behaves if a decision can't be returned in time. Fail-closed blocks the action until MagenTrust responds, which suits high-consequence actions. Fail-open lets the action proceed and logs it for review, which suits lower-risk workflows. The setting is part of policy, so different actions can use different modes.