Privacy Policy & Data Sovereign Protocol
This specification outlines the dynamic controls, storage encryption perimeters, and cookie telemetry methods managed across Subtle Scale domains. As an enterprise-grade sovereign engineering agency, we enforce strict compliance alignments with GDPR, CCPA, and FIPS-140 standard transit protocols.
1.0 Data Controller Classification
Subtle Scale operations are engineered under strict multi-region containment guidelines. We process data exclusively to support architectural discovery briefs and technical assessments requested by verified enterprise entities. We do not monetize telemetry data or distribute user configuration payloads downstream.
02 // INGESTION_BOUNDS_&_RETENTION
Subtle Scale operates on a strict minimization perimeter. Ingestion is bounded strictly to telemetry parameters explicitly declared by the user during the interactive onboarding wizard and secure handoff vectors. We do not engage in silent cross-domain background tracking or automated identity scraping.
2.1 Scope of Ingestion Parameters
System Configuration Payloads: User-submitted architecture bounds, cloud spending ranges, and target compliance frameworks are parsed and bound to localized database tables.
Infrastructure Telemetry Logs: Diagnostic stream values generated during active sessions in the /discover workspace are captured temporarily in ephemeral memory cache.
2.2 Retention Thresholds and Expungement Matrices
Data payloads are subject to automatic lifecycle expiration to prevent persistent structural vulnerability footprints:
Unverified Onboarding Streams: Any session state data or incomplete wizard inputs that do not resolve to a formal technical sync submission are automatically expunged from primary system memory within forty-eight (48) hours.
Verified Enterprise Briefs: Handshake data that matures into an active consultation pipeline is retained under secure encryption for the active duration of the collaborative contract cycle.
Self-Service purging: Upon terminal command receipt or verified manual email verification, all historical telemetry profiles linked to an organizational domain will be permanently overwritten with cryptographic noise (0x00 wipe protocol) within seventy-two (72) hours.
03 // COOKIE_TELEMETRY_DECLARATION
We utilize localized system cookies exclusively as functional state-machines to protect session continuity and theme parameters. We enforce a zero-tolerance policy against marketing tracker networks, behavioral targeting engines, or third-party advertising scripts.
3.1 Classification of In-Memory Telemetry Blocks
| Token Registry ID | Target Scope | Classification | Lifecycle Bounds | Purpose |
|---|---|---|---|---|
| __SS_SYS_STATE | Operational | Essential | Session Exit | Tracks wizard progress state across /discover page loads. |
| __SS_THEME_MODE | Presentation | Essential | 365 Days | Retains local dark/light UI token render preferences. |
| __SS_AUTH_TUNNEL | Security | Essential | 1 Hour | Validates the integrity of the dynamic FIPS-compliant routing tunnel. |
| __SS_ANALYTICS_TR | Telemetry | Analytic (Opt-in) | 30 Days | Gathers aggregated, low-impact server latency, and routing failures. |
3.2 System Override and Hard Opt-Out
Users reserve absolute, granular state-machine control. Any change submitted via the persistent System Cookie Authorization HUD instantly flushes deactivated cookies from local client storage and halts associated ingestion endpoints server-side.
04 // SOVEREIGN_ENFORCEMENT_RIGHTS
Regardless of geographic origin, Subtle Scale extends premium sovereign data controls to all verified entity domains, aligning with the rigorous procedural standards of CCPA (California Consumer Privacy Act), GDPR (General Data Protection Regulation), and global federated privacy models.
4.1 Global Regulatory Alignment Mapping
Subtle Scale extends premium sovereign data controls to all verified entity domains, aligning with the rigorous procedural standards of CCPA (California Consumer Privacy Act), GDPR (General Data Protection Regulation), and global federated privacy models.
4.2 Available Sovereign Actions
Right of Absolute Portability [GET /api/sovereign/export]: Users may request a clean, standard machine-readable JSON compile containing all telemetry parameters and metadata assets associated with their organizational domain.
Right of Environmental Expungement [DELETE /api/sovereign/purge]: Users can trigger automated systemic deletion across all active databases, backup sectors, and cold-storage vaults.
Right of Parameter Correction [PATCH /api/sovereign/update]: Users retain the ability to instantly modify, right-size, or correct historical environment configurations stored within our master CRM.
4.3 Validation and Verification Protocol
To prevent corporate espionage and unauthorized data leakage, any sovereign action request must pass through a strict DNS domain challenge-handshake or multi-factor authentication (MFA) check before access is granted.
05 // FIPS_DATA_TRANSIT_INTEGRITY
All data ingested by the platform is secured against transport-layer interception using state-of-the-art cryptographic perimeters:
5.1 Perimeter Protection and Encryption Standards
Transit Security: Every connection is bound to Transport Layer Security (TLS 1.3) utilizing federal FIPS 140-3 validated cryptographic modules. Any legacy connection using obsolete cipher suites (such as TLS 1.0 or 1.1) is actively dropped at our load balancer edge.
At-Rest Isolation: Ingested database nodes are secured using continuous AES-256 bit column-level encryption. Encryption keys are managed inside isolated Azure Key Vault modules under active corporate security officer (CSO) audit tracking.
5.2 Network Isolation Control
Physical and logical database perimeters are fully micro-segmented. No external web-facing portal holds direct query access to master client architecture models. All internal routing occurs over secure private endpoint tunnels monitored by automated intrusion detection engines.