Data Processing and Protection Policy

1. Introduction

This Data Processing and Data Protection Policy (“Data Policy”) sets forth the data governance protocols, technical safeguards, and operational standards implemented by Stillpoint (“Platform”, “we”, “us”, or “our”), operated by •[LEGAL_ENTITY_NAME].

This document provides transparency regarding how we handle technical surveillance telemetry and customer account records. For institutional customers requiring a standalone bilateral Data Processing Agreement (“DPA”), standard contract terms can be executed upon request.

2. Scope and Application

This Policy governs the processing of all data transmitted to, ingested by, or generated within Stillpoint in connection with synthetic website uptime monitoring, SSL certificate verification, latency logging, incident notification dispatch, and public status page hosting.

3. Categories of Processed Data

We process two primary categories of information:

A. Customer Account and Administrative Data

• User Profiles: Name, work email address, organization name, chosen timezone, and interface preferences.
• Authentication Credentials: One-way salted bcrypt password hashes and cryptographically signed session tokens.
• Commercial Records: Invoices, payment transaction identifiers, plan subscriptions, and tax references.

B. Target Telemetry and Diagnostic Metrics (Processed on Customer Behalf)

• Endpoint Targets: Target URLs, hostnames, IP addresses, and monitoring check parameters submitted by the Customer.
• Probe Metrics: HTTP response codes, latency timings (TCP, DNS, TLS, TTFB), response headers, and network error messages.
• Public Certificate Records: X.509 TLS/SSL certificate validity dates, issuing authorities, and subject names.

4. Data Processing Purposes

Customer data is processed exclusively to deliver agreed-upon observability services, specifically:

• Executing scheduled synthetic health probes from our distributed regional worker nodes.
• Calculating rolling uptime percentiles (24-hour, 7-day, 30-day) and regional latency averages.
• Evaluating incident thresholds and dispatching automated alerts via email, Slack, webhooks, or other configured channels.
• Rendering operational dashboards and hosting customer-authorized public status pages.
• Detecting and preventing abuse, SSRF attempts, and malicious probe manipulation.

5. Roles and Legal Classifications

Under applicable data protection frameworks (such as the EU/UK General Data Protection Regulation and India’s Digital Personal Data Protection Act 2023):

• Customer as Data Controller / Data Fiduciary: The Customer acts as the Data Controller (or Data Fiduciary under India’s DPDP Act) with respect to personal data contained in the Customer’s workspace and endpoints submitted for monitoring. The Customer determines what URLs are monitored and who receives alert dispatches.
• Website Health Monitor as Data Processor: We act as a Data Processor (or Data Processor under DPDP Act) processing synthetic endpoint telemetry solely on the documented instructions of the Customer to fulfill monitoring functions.

6. Customer Responsibilities

The Customer warrants and agrees that:

• It has established all necessary lawful bases and obtained all mandatory consents or statutory permissions before submitting target URLs and email notification recipients to the Platform.
• It will not configure synthetic probes to query endpoints containing sensitive personal data (such as health records, biometric identifiers, or government identity documents) within URL query strings or unencrypted body parameters.
• It will promptly review and adjust workspace alert recipient lists when personnel depart the Customer’s organization.

7. Technical and Organizational Security

Our current technical security controls include:

• Transport Layer Security: Modern TLS 1.3 / HTTPS encryption for all browser-to-application traffic and API interactions.
• SSRF Defense Architecture: Automated URL validation that resolves all target domains and rejects internal RFC-1918 subnets (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), loopbacks (127.0.0.1), and link-local cloud metadata services (169.254.169.254).
• Password Security: User passwords are encrypted using adaptive one-way bcrypt hashing. Raw passwords are never written to disk or logs.
• Network Isolation: Production databases and worker node clusters are deployed within isolated Virtual Private Cloud (VPC) subnets inaccessible directly from the public internet.
• Rate Limiting & Throttling: Dual-tier burst and sustained rate limiters protecting against denial-of-service and brute-force credential stuffing.

8. Access Controls and Personnel

Internal access to production database systems is strictly restricted to designated engineering personnel who require access to maintain system reliability. Administrative access requires hardware multi-factor authentication (MFA) and access logs are recorded for auditability. All personnel with access to customer systems are bound by written confidentiality obligations.

9. Data Retention Lifecycle

Data is retained according to strict operational lifecycles:

• Individual Synthetic Checks: High-frequency check results (individual status codes and latency points) are retained on a rolling window basis (typically 30 to 90 days depending on subscription tier) before being consolidated into statistical hourly aggregates.
• Incident Summaries: Incident timelines and outage duration summaries remain available throughout the lifetime of the active monitor.
• Purging upon Account Deletion: When an account is terminated, customer monitors, alert rules, and telemetry records are permanently scheduled for database purging within thirty (30) days.

10. Authorized Subprocessors

We engage third-party infrastructure subprocessors to provide cloud compute, managed database hosting, and transactional notification routing. Current primary subprocessor classifications include:

11. Data Incident and Breach Management

We maintain an incident response protocol to address suspected security incidents. In the event of a confirmed security breach affecting customer personal data, we will:

• Notify affected workspace administrators without undue delay upon confirming the breach, in accordance with applicable statutory timelines.
• Provide details regarding the nature of the incident, estimated categories of affected data, and remedial actions undertaken.
• Cooperate with customer security teams to mitigate potential impacts and satisfy regulatory breach notification mandates.

12. International Data Transfers

Where personal account information is transferred across international borders, we ensure adequate cross-border transfer protections (such as Standard Contractual Clauses or statutory cross-border data transfer agreements) are in place to safeguard the integrity and confidentiality of customer data.

13. Assisting with Data Subject Requests

Taking into account the nature of the processing, we provide customer administrators with self-service tools within the dashboard to export, modify, or delete monitor data. Where an individual end user submits a data subject request directly to us regarding a customer’s monitored endpoint, we will redirect the requester to the customer as the primary Data Controller.

14. Data Deletion and Return

Upon customer termination of service, we will delete or anonymize all customer personal data and monitoring telemetry in accordance with our retention schedules, except where retention is strictly mandated by applicable commercial or tax legislation.

15. Contact Information & Formal DPA

Enterprise and organizational customers requiring an executed Data Processing Agreement (DPA) incorporating Standard Contractual Clauses may request our standard DPA package through our privacy desk: