StatusPulse StatusPulse
Product ▾
Features Detection, status pages, incidents, notifications, reports Probes HTTP, SSL, DNS, gRPC, WebSocket, Database, mail, and more AI agents & MCP Run pages and incidents from Claude Code, Cursor or VS Code
Pricing
Resources ▾
Guides How to monitor HTTP, databases, gRPC, email, cron jobs and more Changelog Everything shipped, dated Blog Notes on uptime, incidents and status pages
Contact Status SSO Login
← Back to home |

GDPR compliance

Last updated: November 2026

What this page is. A feature-by-feature mapping of how StatusPulse meets the EU General Data Protection Regulation (Regulation 2016/679). It complements the privacy policy (which covers the legal basics) and the security posture (which covers the technical controls). Read this page if you need to evaluate StatusPulse for procurement, fill in a vendor risk questionnaire, or sign a Data Processing Agreement.

1. Why this page exists

Most "GDPR compliance" pages are vague marketing copy. This one tries to be the opposite: every claim below corresponds to a real control in the running product or a real operational practice we'll defend in writing. Where a control isn't yet shipped, we say so plainly.

3D Tesla LLC, the company behind StatusPulse, is organized in the United States (State of Delaware). Because we offer StatusPulse to customers and data subjects in the EU/EEA, our processing of their personal data falls within the territorial scope of the GDPR under Article 3(2). EU/EEA residents can complain to their national data protection authority, and UK residents to the Information Commissioner's Office (ICO) — see section 17.

2. Roles — controller and processor

GDPR splits the world into controllers (who decide what to do with personal data) and processors (who act on the controller's instructions). StatusPulse operates in both roles depending on the data:

DataStatusPulse roleCustomer role
Account holder identity (your email, sign-in records, billing details) Controller —
Persons / Groups you add as alert recipients (their name, email, phone) Processor Controller
Status page subscribers (visitors who entered an email to get incident updates) Processor (on behalf of the page owner) Controller
Probe configuration (URLs, headers, request bodies, credentials) Processor Controller
Probe results (latency, status codes, error messages) Processor Controller
Service / web logs about you (request paths, error stack traces, IPs) Controller (legitimate interest) —

For data where we are the processor, a Data Processing Agreement (DPA) is available on request — see section 12.

3. Lawful bases (Art. 6)

Every processing activity is anchored to one of the six Article 6 bases. The full list is in the privacy policy; the short version per surface:

  • Running probes, sending alerts, hosting status pages: Art. 6(1)(b) — performance of contract with the account holder.
  • Billing, invoicing, tax records: Art. 6(1)(b) and 6(1)(c) — contract + legal obligation (retention periods set by applicable U.S. tax law).
  • Rate limiting, abuse prevention, error logs: Art. 6(1)(f) — legitimate interest in keeping the service available and secure for everyone.
  • Waitlist sign-up emails: Art. 6(1)(a) — explicit consent, withdrawable any time via the unsubscribe link.
  • Anomaly forecasting model: Art. 6(1)(f) — legitimate interest in improving uptime predictions; data minimised so no individual customer's URLs are recoverable from the model (see section 7). Any workspace can object in one click: an Owner or Admin switches off model training under Account → Data use, on any plan, and the next training run leaves the workspace's check history out.

We do not rely on consent for anything that is essential to providing the service — that keeps the consent withdrawal right meaningful (you can refuse marketing emails without breaking your account).

4. Data minimisation (Art. 5(1)(c)) — concrete examples

Article 5(1)(c) requires that personal data be "adequate, relevant and limited to what is necessary." We enforce this in code, not just in policy:

  • Waitlist IPs are hashed at the edge. The raw IP is read once for rate-limiting, then converted to a SHA-256 digest with a per-deployment salt before any database write. The salted hash is irreversible without the salt and the salt never leaves Key Vault.
  • Rate-limit partition uses the TCP socket IP, not the X-Forwarded-For header. The socket IP stays in request-scope memory for the duration of the request and is never persisted; the header would be spoofable and was deliberately not trusted.
  • Application error logs are sanitised before write. Stripe identifiers (cus_, sub_, pi_, etc.), Stripe secret keys (sk_live_, whsec_), and email addresses are stripped from the message column. If the userId on an error row looks like an email, it is replaced with a 12-character SHA-256 prefix prefixed by email:. Raw stack traces are reduced to an 8-character hash for de-duplication; the full trace flows only to Application Insights, where access is gated to the operator role.
  • Anomaly detection never sees hostnames or request bodies. Probe targets enter the cross-tenant training set as a SHA-256 hash truncated to 12 characters, and only when at least five distinct probes share that hash. Single-probe hashes are suppressed so an individual customer URL cannot be fingerprinted from the feature space. The model learns time-of-day seasonality and latency drift patterns — not your URLs, not your content. A workspace that switches off model training (Account → Data use) is left out of every training run from the next one, and its failures stop counting in the shared failure rates other workspaces' forecasts use; models trained before the switch are replaced, not retrained, and each is deleted with its file at most 30 days after it's replaced.
  • Probe credentials are encrypted at rest with AES-GCM. SMTP passwords, IMAP/POP3 passwords, database passwords, WebSocket auth headers, gRPC mTLS client certificates, and gRPC auth headers are stored in the format v1.{nonce}.{tag}.{ciphertext} using a 256-bit master key resolved from Azure Key Vault at process start. The plaintext is held only in memory during a probe execution.

5. Encryption (Art. 32(1)(a)) — at rest and in transit

5.1 In transit

  • HTTPS everywhere with HSTS (Strict-Transport-Security with includeSubDomains and preload). The marketing site, dashboard, public status pages, and custom-domain status pages all redirect HTTP → HTTPS at the edge.
  • TLS terminated by Azure Front Door / App Service with Azure-managed certificates; minimum protocol pinned to TLS 1.2.
  • Outbound probe traffic to your endpoints uses the protocol you configured (HTTP/HTTPS, TCP, ICMP, DNS, IMAP-SSL, POP3-SSL, SMTP-STARTTLS, MySQL/PG/SQL Server/Redis with TLS, WebSocket Secure, gRPC over HTTP/2 or HTTP/3).
  • For database probes, a TLS misconfiguration on the target produces a down status with the TLS error preserved — we never silently downgrade.

5.2 At rest

  • The Azure SQL database backing StatusPulse uses Transparent Data Encryption (TDE) with platform-managed keys.
  • Azure Blob Storage (used for generated PDF reports) uses server-side encryption with platform-managed keys.
  • Azure Key Vault holds the AES-GCM master key for the application-layer encryption described in section 4. The master key is read once at process start by the App Service and Function App managed identities (no human user has Key Vault Secrets User on the production vault).
  • The encrypted-string format includes a version tag (v1) so we can rotate the master key in future without having to schema-migrate every row.

6. EU hosting and international transfers (Chapter V)

All customer data is stored in the EU, in Azure West Europe. Customers do not choose a region; every account is hosted the same way. Specifically:

  • Azure resources: the single Azure SQL database that holds all customer data, the web app and the public status pages run in Azure West Europe. Probes run from West Europe; on Business plans they also run from a US location, and those check results are stored in the same EU database.
  • Microsoft Entra External ID uses one directory for all customers.
  • Azure SQL backups stay in the EU — no replication outside the EEA is enabled.

Where a transfer outside the EEA is unavoidable, we rely on:

  • Stripe (payment processing): Stripe's intra-group transfers are governed by the EU Standard Contractual Clauses; Stripe maintains an EU data residency option and we use it.
  • Anthropic / Claude API (used by the optional AI incident drafter, the AI branding analysis, the AI executive summary in PDF reports, the Setup Agent's review and the incident copilot): inference happens on US infrastructure. We disclose this here and in the in-app feature copy. Opt-out per workspace: an Owner or Admin switches AI assistance off under Account → Data use, and from then on no data from that workspace leaves the EU through this channel. AI output is also not the source of truth — every AI-drafted update is editable and requires a human click to publish, and every probe the Setup Agent proposes is reviewed before it is created.
  • HeyCatch (product analytics on the public website pages, never once you are signed in, section 15): events are processed in the United States under HeyCatch's DPA, which incorporates the SCCs (Module Two).
  • Microsoft Azure: on Business plans the US probe location reads each probe's configuration from the EU database and writes check results back to it, and Microsoft staff outside the EU may exceptionally access platform diagnostics. Both fall under the Microsoft Online Services Data Protection Addendum, which incorporates the SCCs.

We do not use US-only sub-processors for any core processing other than the AI features and product analytics. The list in section 8 below is exhaustive.

7. Automated decision-making and profiling (Art. 22)

StatusPulse does not make decisions that produce legal or similarly significant effects on a person without human involvement. Specifically:

  • The anomaly forecast is informational. It writes a probability score back to your own probe row and may surface an anomaly badge in the dashboard. It does not pause monitors or charge money, and it contacts recipients only on probes where you switch on Anomaly alerts, and only the watchers who opted into forecast notices. The decision to act on the prediction stays with you.
  • The AI incident drafter proposes wording for an incident update. The wording is editable and never publishes without a human click.
  • The AI executive summary in PDF reports describes patterns in your data. It does not feed back into any automated control.
  • Hard opt-out toggles (EmailsBlocked, SmsBlocked on a Person) are checked by the dispatcher before every send and override every other rule, including escalations.

8. Sub-processors (Art. 28(2))

Each sub-processor we use, the data they touch, and the lawful basis for the transfer:

Sub-processor Purpose Personal data Region Transfer basis
Microsoft Azure Hosting (App Service, Functions, SQL, Storage, KV, Insights) All data described in this page EU (West Europe). Business-plan checks also run from a US location; their results are stored in the EU. Intra-EEA for stored data; SCCs cover the US probe location and residual platform-support access.
Microsoft Entra External ID Account authentication, password storage Account email, display name, password hash One directory for all customers SCCs (Microsoft Data Protection Addendum)
Microsoft Graph (External ID) Provisioning a user before first sign-in (onboarding) Account email, display name Same directory as above SCCs (Microsoft Data Protection Addendum)
Azure Communication Services — Email Outbound transactional email (alerts, status page subscriptions, billing receipts) Recipient email + alert body One Communication Services resource for all customers SCCs (Microsoft Data Protection Addendum)
Azure Communication Services — SMS Outbound SMS (alerts only) Recipient phone number, country code, message body Same Communication Services resource; carrier delivery is intrinsically international At our edge: SCCs (Microsoft Data Protection Addendum). Downstream carrier governed by recipient-country telecoms law.
Stripe Payment processing, invoices, tax Customer email, billing address, last-4 of card (we never see the PAN) Stripe-internal transfers governed by SCCs. SCCs (Stripe DPA)
Anthropic (Claude API) Optional AI incident drafter, AI branding analysis, AI report summary, Setup Agent review and incident copilot Whatever you submit when you click "draft with AI" — typically a probe summary, recent error message, and incident metadata; for branding, the website address you enter; for the Setup Agent, the public DNS records, page titles and homepage text found for the domain you enter; for the incident copilot, the incident, its probes' recent results and the display names of the people on call United States SCCs; per-workspace opt-out (Account → Data use)
HeyCatch Product analytics on the public website pages (not the dashboard) Random visitor id, pages viewed, clicks, IP address and device details; never linked to an account United States SCCs (HeyCatch DPA, Module Two)
LinkedIn (Insight Tag) Measuring our own LinkedIn ads, on public website pages only Visit data and LinkedIn's own cookies LinkedIn's infrastructure Not our sub-processor: LinkedIn processes this data as a separate controller under its own privacy policy
PostYourStartup (badge) The “Featured on PostYourStartup” badge on our home and pricing pages, loaded from postyourstartup.co IP address, browser details and our site's address when the badge loads; its own cookies, including a visitor id PostYourStartup's infrastructure Not our sub-processor: PostYourStartup processes this data as a separate controller under its own privacy policy
Slack / Microsoft Teams Webhook delivery to a destination you configured Whatever the alert payload contains You control the destination URL You are the controller for the destination; we are not your sub-processor for that delivery
Generic webhook subscriber Webhook delivery to a destination you configured Whatever the subscriber payload contains You control the destination URL Same as above

We will give existing customers 30 days' advance notice by email before adding a sub-processor that touches personal data, with an opportunity to object before the change takes effect.

9. Data subject rights (Art. 12–22) — how to exercise each one

RightHow to exerciseSelf-serve in dashboard?
Access (Art. 15) — copy of what we hold Email privacy@statuspulse.ai from the address on file. Response within 30 days. Partly: Owners and Admins can download the workspace (probes, status pages, subscribers, incidents, daily uptime) as JSON from Account → Export workspace. Anything else, on request.
Rectification (Art. 16) — correct inaccurate data Most account fields are editable in the dashboard (Account, Persons, Status pages). For anything not editable, email privacy@statuspulse.ai. Yes, for editable fields.
Erasure (Art. 17) — "right to be forgotten" Workspace Owners: Account → Close workspace. Everything stops at once; support can reopen the workspace for 30 days; then every row of it is deleted and the workspace record is anonymised (id, plan, dates and Stripe references kept for invoices). Anything else — a sign-in account, one person's data inside a workspace — email privacy@statuspulse.ai. We delete or anonymise within 30 days, except where a legal obligation requires retention (tax records: up to 10 years; in that case, the data is locked from further use). Yes, for a whole workspace (Owners): Account → Close workspace. Sign-in accounts and individual records, on request.
Restriction (Art. 18) — pause processing pending a dispute Email privacy@statuspulse.ai. We can flag your tenant as restricted within one business day. —
Portability (Art. 20) — machine-readable export On request, JSON / CSV export of: account, probes, probe results, persons, groups, incidents, status pages, notification log. Yes, for the workspace: Account → Export workspace (JSON). Raw probe results and the notification log, on request.
Object (Art. 21) — including marketing Every marketing email has an unsubscribe link that takes effect immediately. Training the shared anomaly models: switch it off under Account → Data use. For other legitimate-interest processing (rate limiting, security logs), email privacy@statuspulse.ai. Yes: marketing unsubscribe and the model-training switch are one click each.
Withdraw consent (Art. 7(3)) For consent-based processing (waitlist email primarily): one-click unsubscribe. Yes.
Not be subject to automated decisions (Art. 22) Not applicable — see section 7. There are no qualifying automated decisions. —

For Persons and status page subscribers (where you are the controller), each notification we send carries an unsubscribe token that lands on a public unsubscribe page; one click hard-blocks future sends and is recorded as EmailsBlocked / SmsBlocked on the recipient. Subsequent attempts to email or SMS that recipient short-circuit at the dispatcher before the message is built.

10. Retention (Art. 5(1)(e))

DataRetentionTrigger for deletion
Account data (TenantMember, Tenant)While the workspace is open, + 30 days after an Owner closes it. Cancelling a paid plan moves the workspace to the free plan and deletes nothing.Workspace closure (Account → Close workspace) + 30 days in which support can reopen it; then a daily sweep deletes every row of the workspace and anonymises the workspace record (id, plan, dates and Stripe references kept)
Probe configurationSame as accountDeleted with the workspace (30 days after closure) or with its status page (30 days after the page is deleted)
Probe check resultsPlan-tier window (Free: 7 days; Pro: 90 days; Business: 365 days)Time-windowed sweep
Notification log12 monthsTime-windowed sweep
Generated PDF reports90 days (configurable)Weekly retention sweep (Sunday 03:00 UTC)
Application error log90 daysTime-windowed sweep
Web server / request logs (Application Insights)90 daysApplication Insights retention
Waitlist entriesUntil invited and signed up, or until unsubscribeConversion or opt-out
Onboarding attempt records (rate-limit ledger)30 daysBackground sweep
Billing records (invoices, charges)As required by applicable U.S. tax lawLegal-obligation retention
Anomaly detection training setNot kept: each training run reads the last 30 days of check results (7 days for the hourly run) and stores only the trained modelsEach run reads the window afresh; workspaces that switched off model training are left out from the next run
Anomaly forecast modelsWhile in use, then at most 30 days after a newer model replaces them; a model that never goes into use, at most 30 days after trainingEach training run (hourly) deletes the models past that point, with their files

11. Breach notification (Art. 33 / 34)

If we become aware of a personal data breach likely to result in a risk to the rights and freedoms of natural persons, we will:

  • Notify the relevant EU/EEA supervisory authority(ies) within 72 hours of becoming aware, where we are required to do so under Art. 33(1).
  • Notify affected account holders by email without undue delay where the breach is likely to result in high risk (Art. 34(1)).
  • Document the breach in our internal incident log regardless of severity (Art. 33(5)).

For account holders acting as controllers (Persons, status page subscribers, probe configuration), we will notify you as the affected controller without undue delay (Art. 33(2)) and provide enough information for you to fulfil your own Article 33 / 34 obligations.

12. Data Processing Agreement (Art. 28(3))

For customers who need a signed DPA — typically B2B accounts processing personal data of their own end-users through StatusPulse — we provide a DPA on request. Email privacy@statuspulse.ai with your tenant identifier and the DPA will be sent within two business days. Once signed, it forms part of the terms of service.

The DPA covers Article 28(3) requirements: subject matter, duration, nature and purpose, type of personal data, categories of data subjects, controller and processor obligations, sub-processor authorisation (with the list in section 8 above), security measures, audit rights, and return / deletion at end of processing.

13. Records of processing activities (Art. 30) and DPIA (Art. 35)

We maintain an internal Record of Processing Activities (ROPA) covering each processing purpose, the legal basis, the data categories, the recipients, the retention period, and the security measures. The ROPA is available to supervisory authorities on request and in summary form to customers under a signed DPA.

StatusPulse does not currently perform any processing that triggers a mandatory Data Protection Impact Assessment under Article 35: we do not engage in large-scale systematic monitoring of publicly accessible areas, we do not process special-category data (Art. 9), we do not profile individuals to make decisions about them, and our scale is below the DPIA thresholds published by the relevant EU/EEA supervisory authorities. We will revisit this if any of those facts change.

14. Children (Art. 8)

StatusPulse is a B2B service for engineers and operators. It is not intended for, and should not be used by, individuals under 16. We do not knowingly collect personal data from children. If we learn that we have, we will delete the data promptly. Please contact privacy@statuspulse.ai if you believe a child has used the service.

15. Cookies and trackers

Essential, first-party — no consent needed:

  • Authentication cookie — Secure, HttpOnly, SameSite=Lax; required for the dashboard.
  • Antiforgery token — Secure, set per request to defend against CSRF on form submissions.
  • Theme preference — first-party cookie remembering your light/dark choice; Secure, SameSite=Lax, 1-year expiry. Not used for tracking.

Non-essential:

  • HeyCatch product analytics — on the public website pages only (home, pricing, features, guides, blog and sign-up), never once you are signed in and never on the dashboard. A random visitor id in a first-party cookie and in local storage; page views and clicks; never linked to an account. Processor, listed in section 8.
  • LinkedIn Insight Tag — on the public website pages only, never on the dashboard or the status pages we host. Measures which of our LinkedIn ads led to visits and sign-ups; LinkedIn sets its own cookies.
  • PostYourStartup badge — an image on our home and pricing pages, loaded from postyourstartup.co; its server may try to set its own cookies, including a visitor id. Not our sub-processor (section 8).

Status pages hosted for our customers carry none of these. You can block or clear them in your browser settings; the site works without them.

16. Security controls referenced in this page

The technical controls supporting the above (TLS configuration, encryption format, key management, audit logging, network controls) are described in the security posture. Recent independent reviews:

  • Code-level security audit, April 2026 — 20 findings, all closed.
  • Code-level security audit follow-up, May 2026 — 28 findings, 26 closed and 2 risk-accepted with documented compensating controls.

17. Complaints

If you believe we have mishandled your personal data, please contact us first at privacy@statuspulse.ai — we'd rather fix it than have you escalate. You also have the right at any time to complain to:

  • The supervisory authority of the EU/EEA member state where you live, work, or where the alleged infringement took place — the list is maintained by the European Data Protection Board.
  • For UK residents, the Information Commissioner's Office (ICO): ico.org.uk.

18. Contact

For anything on this page, data subject requests, or DPA requests: privacy@statuspulse.ai.

For billing or account issues: support@statuspulse.ai.

See also: Privacy policy · Terms of service · Security posture.

StatusPulse

Uptime monitoring and status pages.

Latest update: 5 Nov 2026 — Short videos of the product at work

Compare

  • vs Statuspage.io
  • vs Uptime Kuma
  • vs UptimeRobot
  • vs BetterStack
  • vs Pingdom
  • All comparisons →

Features

  • AI agents & MCP
  • Probes
  • Status pages
  • Incidents & alerts
  • Anomaly detection
  • Outbound webhooks
  • All features →
  • Probe types →

Resources

  • Guides
  • Changelog
  • Blog
  • Status
  • Pricing
  • Contact
© 2026 StatusPulse by 3D Tesla · Built and answered by Marcelo Jarretta
Privacy · Terms · Security · GDPR