Privacy Policy
Last updated: September 1, 2026
1. Overview
Zeitgeist Confidential (“the Platform”) is a cloud-native B2B Software-as-a-Service (SaaS) platform that provides digital infrastructure for secure, anonymous compliance reporting. This Privacy Policy describes how we handle information across two distinct operational layers: the administrative dashboard used by corporate tenants, and the anonymous reporting portal used by whistleblowers. These layers operate under fundamentally different data handling principles, which are detailed below.
2. Data Collected from Tenants (Corporate Clients)
We collect limited administrative data necessary to establish and maintain corporate subscriptions. This data is strictly utilized for service provisioning, authentication, and subscription management. The following categories of data are collected from tenant administrators:
Identity Data
Names, business email addresses, and corporate domain identifiers of designated administrators.
Authentication Data
Encrypted session tokens used to access the administrative dashboard. Passwords are hashed using industry-standard algorithms and are never stored in plaintext.
Billing Information
Billing contact details and subscription plan selection. Payment card data is never processed, stored, or transmitted through the Platform. All payment processing is handled by independent, PCI-DSS-certified third-party payment processors.
Organisation Configuration
Tenant name, reporting categories, data retention policies, and notification preferences are configured by authorised administrators.
3. Anonymous Reporting Portal — Zero-Identity Logging
Core Architectural Guarantee
Our client-facing reporting portals operate under a strict Zero-Identity Logging architecture. This is not a policy choice that can be changed — it is a structural limitation enforced at the application and infrastructure level.
When a person submits an anonymous report through the reporting portal, the following is not tracked, logged, stored, or processed by the Platform at any point in the request lifecycle:
- IP addresses (neither at the application layer nor at the edge/middleware layer)
- Device identifiers (hardware fingerprints, advertising identifiers, or device UUIDs)
- Browser fingerprints (canvas fingerprinting, WebGL rendering, font enumeration, or plugin lists)
- Geolocation data (GPS coordinates, timezone inference, or language-based location guessing)
- Referrer headers or originating URL chains (blocked via Referrer-Policy: no-referrer at the edge)
- Cookies, localStorage, sessionStorage, or any form of persistent client-side storage
- User-agent strings beyond the current request (never persisted to disk or database)
4. File Attachments & Metadata Stripping
Reporters may attach files as evidence to their submissions. To protect reporter anonymity, all uploaded files pass through an automated metadata sanitisation pipeline at the database perimeter before being stored. This pipeline performs the following operations:
- EXIF data removal (GPS coordinates, camera model, timestamps, software version)
- ICC color profile stripping (which can contain device-specific identifiers)
- XMP metadata removal (author names, editing software signatures, copyright fields)
- IPTC metadata removal (caption metadata, origin information, contact details)
- Document property stripping for PDF and Office files (author, revision history, computer name)
After sanitisation, files are encrypted at rest using AES-256-GCM with tenant-specific encryption keys derived via HKDF-SHA256 from the tenant’s configured master key. The Platform does not retain the original unmodified file at any point in the processing pipeline.
5. Encryption & Tenant-Level Key Isolation
Zeitgeist Confidential employs a per-tenant cryptographic isolation model. Each tenant’s data is encrypted using a unique encryption key derived from the tenant’s configured master encryption key via HKDF-SHA256. This means that even if two tenants use the same infrastructure, their data is cryptographically isolated — no cross-tenant decryption is possible.
Technical Summary
- • At rest: AES-256-GCM with per-tenant HKDF-derived keys
- • In transit: TLS 1.3 enforced on all connections (HSTS preload enabled)
- • Audit trail: SHA-256 hash chain ensuring tamper-evident logging
- • Database: WORM-triggered immutable audit log (no UPDATE or DELETE permitted)
Zeitgeist Confidential personnel, infrastructure operators, and cloud providers do not hold plaintext access keys to tenant data. The provider is structurally and mathematically incapable of reading, recovering, or monitoring data stored within any tenant’s private database environment.
6. Third-Party Sub-processors
To maintain high availability and security, the Platform utilises enterprise-grade global infrastructure providers. We do not sell, rent, or distribute any user or corporate data to third-party marketing, advertising, or data brokerage entities.
7. Data Retention & Automated Erasure
Each tenant configures their own data retention policy via the administrative dashboard (default: 36 months). When the retention period expires, scheduled automated retention jobs purge the expired data:
- Expired report content and associated encrypted fields are permanently overwritten and purged by the retention job
- Audit log entries referencing the purged data remain (immutability preserved) but the referenced content is irrecoverable
- Each purge event is recorded in the immutable audit trail with its timestamp
Tenants may request immediate data erasure at any time by contactingsupport@zeitgeistbusiness.com.
8. International Privacy Compliance
The platform architecture is built from the ground up to support international privacy frameworks. While Zeitgeist Confidential is headquartered in Trinidad and Tobago and primarily serves Caribbean organisations, the platform’s privacy-by-design architecture aligns with the following frameworks:
GDPR (EU)
Data minimisation (only essential data collected), purpose limitation, right to erasure (automated retention jobs + compliance-ready data export), processor/controller separation, and sub-processor transparency.
CARICOM / ISO 37002
Whistleblowing Management Systems standard alignment, supporting protected disclosure frameworks across Caribbean Community member states.
9. Data Breach Protocol
In the event of a security incident affecting the Platform, Zeitgeist Confidential will notify affected Tenants within 72 hours of detection via email to the configured notification address. The notification will include: the nature of the incident, the categories of data potentially affected, the confirmed or suspected scope, and the remediation steps taken.
Report content is encrypted at rest with AES-256-GCM using per-tenant keys. In a worst-case scenario where an unauthorised party gains access to the database, encrypted report content remains protected by those tenant-specific keys. The Platform nevertheless treats any such incident as a reportable breach and will follow the notification process described above.
10. Contact
For privacy-related inquiries, data subject access requests, or sub-processor questions, contact:
support@zeitgeistbusiness.com