Scope of Policy
This Privacy Policy applies to theRuntimeHQ.com, the RuntimeHQ control dashboards, operational APIs, customer-facing SDKs, technical onboarding channels, and active SRE support workflows.
Information We Collect
RuntimeHQ processes several technical, administrative, and operational datasets to maintain secure edges and rapid incident propagation flows:
1. Organizational & Admin Details
- Organization and company names
- System administrator and operator names
- Corporate work email addresses
- Operational session contact parameters
- Cryptographic credential tokens & metadata
- Runtime configurations and app IDs
2. Operational State Logs
- Runtime severity state values
- Customer outage or maintenance banner strings
- Incident tracking reference logs
- Maintenance window timing arrays
- Administrative audit-trail records
- Applicable application routing targets
3. Technical Edge Metadata
- Operator routing IP addresses
- Agent browser or terminal user-agents
- Request HTTP header footprints
- Administrative authentication logs
- Operational action histories
4. Usage Analytics
- Google Analytics tracking integration
- Web discovery and journey behaviors
- Documentation engagement rates
- Technical resource and SDK usage metrics
Information We Do Not Intentionally Collect
Our engineering systems are designed to minimize data collection. RuntimeHQ does not require nor intentionally process:
How We Use Information
We process, map, and store collected technical details exclusively to sustain and secure operational workflows:
✓ RuntimeHQ does not sell, lease, or distribute customer information to external advertising systems.
Authentication & Session Management
RuntimeHQ deploys session management mechanisms, session cookies, local browser storage states, and cryptographic credential validations to protect dashboard access, sustain operator authorization statuses, and enforce platform-wide SRE boundary protections. Disabling session assets inside browsers may prevent active system controls from loading correctly.
Infrastructure & Subprocessors
1. Infrastructure Data Hosting
By default, RuntimeHQ processes and stores operational database targets using secure enterprise infrastructure providers located in the United States (unless regional boundaries are designated under dedicated enterprise SLA plans). Primary cloud assets are provided by:
2. Trusted Subprocessors
We coordinate with subprocessors to run infrastructure, analytics, and billing pipelines:
| Subprocessor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Primary Cloud Compute & Secure Database Hosting | United States / Regional Options |
| Cloudflare | Global Edge State CDN Propagation & Firewall Systems | Global Network |
| Razorpay | Subscription Billing & Invoicing Engine | India |
| Google Analytics | Marketing Discovery & Documentation Metrics | Global Network |
3. Subscription Payments
RuntimeHQ relies on Razorpay to execute payment transactions and corporate invoice pipelines. RuntimeHQ never directly hosts, processes, or captures full credit card credentials or payment matrices on our core systems. All billing transactions are bound by Razorpay's security standards.
Retention & Security Protocols
1. Data Retention Guidelines
We maintain active audit history records, state transitions, incident notes, and operational logs to provide complete timelines for compliance and operational transparency. Historic records are stored in high-reliability archival storage formats to preserve timeline integrity.
2. Platform Security Safeguards
We apply comprehensive SRE boundaries to safeguard integration flows:
Your Privacy Rights
Based on your company's jurisdiction, you may hold rights to review, correct, restrict, or initiate deletion logs for administrative personal datasets. Compliance inquiries, data processing requests (DPAs), and general disclosures can be directed straight to our privacy team:
[email protected]Discuss Data Processing Agreements
Connect with our compliance engineers to evaluate regional replication parameters, dedicated storage boundaries, or execute customized enterprise DPA clauses.
Book technical discussion
No sales pitch. Connect directly with our platform SREs to evaluate integration feasibility.
To help us prepare for our discussion, please share some context on your current outage banner workflow, such as:
- Hardcoded banner deployments
- Toggling CMS content manually
- Editing feature flags during active incidents