Privacy Policy

1. Data Collection & Telemetry

Starks operates on a principle of minimalist data ingestion. We collect telemetry necessary to maintain system health and workflow execution, including IP addresses, device metadata, and operational logs. We do not ingest the internal contents of your encrypted payloads unless explicitly required for the execution of a specific logic node authorized by the user.

2. Processing & Operational Logic

Any data gathered is utilized strictly for maintaining the integrity of the Starks OpsOS. This includes performance optimization, predictive maintenance of your automation nodes, and the cryptographic authentication of system handshakes. We do not utilize your operational metadata for profiling or third-party advertising purposes.

3. Cryptographic Safeguards (AES-256)

In alignment with our "Security-First" architecture, all user data is subjected to AES-256 encryption at rest. During transit, we enforce TLS 1.3 protocols to prevent unauthorized interceptions. Access to sensitive raw data within our infrastructure is restricted via zero-trust RBAC (Role-Based Access Control) protocols, ensuring that not even our core engineers can access your private keys.

4. Third-Party Integration Handshakes

When you connect Starks to external stacks—such as Slack, GitHub, or AWS—we act as a secure gateway. Data shared with these platforms is governed by their respective privacy policies. Starks only transmits the specific data packets required to complete the authorized integration trigger, maintaining a "least-privilege" data flow.

5. Data Sovereignty & Global Rights

We respect global data protection standards, including GDPR and CCPA. Users maintain full sovereignty over their data. You have the right to request a complete export of your operational logs, modify your account metadata, or request the permanent deletion of your infrastructure profile from our active clusters at any time.