Privacy policy
Last updated: November 2026
1. Who we are
StatusPulse is a service operated by 3D Tesla LLC ("3D Tesla"), a company organized in the United States (State of Delaware). StatusPulse is a product of 3D Tesla. When we say "we", "us", or "StatusPulse", we mean the company providing the monitoring and status page service at statuspulse.ai and at any custom domains you configure on your status pages.
For the purposes of the EU General Data Protection Regulation (GDPR), 3D Tesla is the data controller for data about our account holders (you) and the data processor for data you upload into StatusPulse about the people and services you probe. You remain the controller for that data.
Contact for anything in this policy: privacy@statuspulse.ai.
2. What this policy covers
This policy explains:
- The personal data we collect, and why.
- The legal basis we rely on under GDPR.
- Who we share it with (our sub-processors).
- How long we keep it.
- Your rights, and how to exercise them.
It covers the StatusPulse website, the authenticated dashboard, the public status pages hosted by us on behalf of our customers, and the email / SMS notifications we send on behalf of our customers.
3. Data we collect
3.1 Account data
When you sign up, we collect:
- Email address (used to log in and to receive service-related emails).
- Display name.
- Company / tenant name.
- Password — never stored in plaintext; authentication is handled by Microsoft Entra External ID (CIAM), which stores only a salted hash.
- Plan selection and billing status.
3.2 Probe configuration
You create probes that describe what services to watch. We store:
- The probe name, type (HTTP, ping, TCP, etc.), and target URL or host.
- Check interval, expected response codes, HTTP headers and request body (which may contain API keys you add — treat the probe configuration as confidential).
- Check results: timestamp, status, latency, error messages. Historical check results are retained according to your plan's history retention limit.
3.3 Incident recipients ("Persons" and "Groups")
To alert the right people when a probe fails, you add Persons. For each person you add, we store:
- Name and email address (always).
- Phone number and country code (only if you configure SMS alerts for that person).
- An unsubscribe token tied to that person.
- Their subscription preferences (which probes, which events).
- Whether they're blocked from receiving emails or SMS (hard opt-out).
You are the controller for this data. When you add someone as a Person, you are representing that you have a lawful basis to contact them about incidents on the services you probe (for example: they are on-call, they work at a company whose service you've agreed to probe, or they are a customer who asked to be alerted).
3.4 Status page subscribers
When a public status page offers email subscriptions, subscribers enter their email address. We store the email, the status page they subscribed to, and an unsubscribe token. They are the controller of their own subscription; we are the processor.
3.5 Notification log
For every email or SMS we send (incident alerts and test messages), we log: timestamp, recipient name / email / phone (as it was at send time), channel, outcome (sent or failed), and the error reason if it failed. This is an audit trail for you — it answers "did we actually send that alert?" — and is accessible to our support team to help you diagnose delivery problems.
3.6 Technical and usage data
- IP addresses — where we store them (abuse prevention, rate limiting), we store only a salted hash, not the raw address.
- Browser user-agent string, on the waitlist signup and sign-in.
- Basic web server logs (request path, response code, timestamp) retained for a limited period for debugging and security monitoring.
- Error logs when something breaks in the app, including the relevant user id and request path.
3.7 Payment data
Payments are processed by Stripe, a PCI-DSS Level 1 payment provider. Your card details go straight to Stripe; we never see or store your full card number. We store the plan you selected, your billing status, and the references Stripe gives us for your customer record, subscription and invoices.
3.8 Cookies and local storage
Essential, first-party:
- Authentication cookies to keep you signed in.
- Theme preference (light/dark).
- Anti-forgery tokens for form submissions.
Analytics and advertising measurement:
- HeyCatch product analytics, on the public website pages only (home, pricing, features, guides, blog and sign-up) — not once you are signed in, not on the dashboard, and not on the status pages we host for customers. It stores a random visitor id in a first-party cookie and in local storage, and records the pages you view and what you click, with your IP address and device details. These events are never linked to your account. We use them to see which pages help visitors and which get in the way.
- LinkedIn Insight Tag, on the public website pages only — not the dashboard, and not the status pages we host for customers. It tells us which of our LinkedIn ads led to visits and sign-ups. LinkedIn sets its own cookies for this.
Third-party content: the “Featured on PostYourStartup” badge on our home and pricing pages is an image loaded from postyourstartup.co, whose server may try to set its own cookies (section 5).
You can block or clear these in your browser settings at any time; the site keeps working without them. LinkedIn's own controls are in your LinkedIn ad settings.
3.9 AI features
Some features use Anthropic's Claude models: drafting incident updates and post-mortems, suggesting branding from a website address, the executive summary in PDF reports, the Setup Agent's review of the probes it proposes for a domain you enter, and the incident copilot's analysis of an incident. They run only when you use them (the copilot also runs once by itself when you first open an incident StatusPulse opened automatically). The data the request needs — for example probe names, recent check results and error messages, incident text, the website address you entered, the public DNS records, page titles and homepage text the Setup Agent found, or the display names of the people on call for a status page — is sent to Anthropic, which returns the text. Nothing is published, created or paged until you review it.
An Owner or Admin can switch every AI feature off for a workspace under Account → Data use. From then on nothing from that workspace is sent to Anthropic; the Setup Agent still works, using its built-in rules only.
3.10 Anomaly forecast models
The anomaly forecast (Business plan) uses models shared by every workspace. They are trained in our own infrastructure, not by a third party, on the last 30 days of check results — when each check ran, response time, status code, packet loss and the Up / Degraded / Down outcome — of HTTP, Ping, TCP and Heartbeat probes in every workspace that hasn't opted out, on every plan. Hostnames enter only as a hash, and probe names, request bodies and headers are never used.
You can opt out in one click. A workspace Owner or Admin switches off model training under Account → Data use, on any plan. From the next training run (they run hourly) the workspace's check history is left out, and its failures stop counting in the shared failure rates other workspaces' forecasts use. Models trained before the switch aren't retrained; newer ones replace them. The workspace's own forecasts keep working.
Replaced models are deleted. Models trained while your workspace was in are deleted, with their files, at most 30 days after they're replaced. A model that never goes into use (because it didn't pass our quality check) is deleted at most 30 days after it was trained. We keep no copy of the data a model was trained on.
4. Why we use your data (purposes and legal basis)
Under GDPR Article 6, each processing activity needs a legal basis. Here's ours:
- Providing the service (running your probes, storing results, sending alerts, hosting status pages): performance of contract (Art. 6(1)(b)).
- Billing and account management: performance of contract and legal obligation (Art. 6(1)(b) and 6(1)(c)) — we need to keep invoicing records for tax purposes.
- Service-related emails (password resets, plan changes, incident alerts): performance of contract (Art. 6(1)(b)).
- Abuse prevention, rate limiting, security monitoring: legitimate interest (Art. 6(1)(f)) — keeping the service up for everyone.
- AI features you use (section 3.9): performance of contract (Art. 6(1)(b)).
- Product improvement and debugging based on usage analytics (section 3.8) and error logs: legitimate interest (Art. 6(1)(f)).
- Training the shared anomaly forecast models (section 3.10): legitimate interest (Art. 6(1)(f)) in better uptime predictions for every customer. Object at any time with the model-training switch under Account → Data use.
- Measuring our LinkedIn ads (section 3.8): legitimate interest (Art. 6(1)(f)).
- Showing where StatusPulse is listed, including the PostYourStartup badge (sections 3.8 and 5): legitimate interest (Art. 6(1)(f)).
- Marketing email from us to our own customers: legitimate interest, with an unsubscribe link in every email.
- Waitlist emails before sign-up: consent (Art. 6(1)(a)) given when you joined the list.
5. Who we share data with (sub-processors)
We keep the list of sub-processors short. The current list:
- Microsoft Azure — hosting infrastructure (App Service, Azure SQL, storage). Customer data is stored in Azure West Europe.
- Microsoft Entra External ID (CIAM) — user authentication, password storage.
- Azure Communication Services — delivery of outbound email and SMS (including international SMS via local carriers).
- Stripe — payments, invoices and tax. Card data is processed directly by Stripe.
- Anthropic — the AI features in section 3.9, when you use them. United States.
- HeyCatch — product analytics (section 3.8). United States.
LinkedIn is not our sub-processor: the Insight Tag sends visit data from our public website pages to LinkedIn, which processes it as a separate controller under its own privacy policy.
PostYourStartup isn't our sub-processor either. The badge on our home and pricing pages is an image served by postyourstartup.co, so when one of those pages loads, your browser sends PostYourStartup your IP address, browser details and our site's address, and its server may try to set its own cookies, including a visitor id. PostYourStartup handles that as a separate controller under its own privacy policy; we receive none of it.
When you configure a Slack, Microsoft Teams, or webhook integration, incident data is sent to the URL you provided. Those services are not our sub-processors — you control the destination. The webhook URL itself is stored as-is because it's the delivery address.
We will update this list before adding a new sub-processor that touches personal data, and will give existing customers reasonable notice and an opportunity to object.
6. International data transfers
Your account and monitoring data is stored in the EU, in Azure West Europe. Some processing happens in the United States: checks from the US probe location on Business plans (their results are stored in the EU database), Anthropic for the AI features you use, HeyCatch for product analytics, and Stripe and Microsoft for parts of their own operations (for example support staff in other regions). Those transfers are covered by the EU Standard Contractual Clauses (SCCs) in each provider's data processing agreement or, where the provider is certified, the EU–US Data Privacy Framework.
SMS delivery is intrinsically international: a recipient in Brazil or the United States receives the message via local carriers. We limit what we send to the minimum required (recipient phone number and the alert body).
7. How long we keep your data
- Account data: while your workspace is open. Cancelling a paid plan doesn't close it: the workspace moves to the free plan and nothing is deleted. When an Owner closes the workspace (Account → Close workspace), everything in it stops at once and our support can reopen it for 30 days; after that everything in it — probes and their history, status pages, incidents, subscribers, watchers, on-call schedules, reports, members and its audit log — is deleted, and the workspace record is anonymised (we keep only its id, plan, dates and Stripe references, so invoices stay traceable). Your sign-in account is kept until you ask us to delete it. Tax records: up to 10 years.
- Check results: up to your plan's history retention window (7 days on Free, 365 days on Business).
- Anomaly forecast models (section 3.10): while in use; deleted at most 30 days after a newer model replaces them, or 30 days after training for a model that never goes into use.
- Notification logs: 12 months, then pruned.
- Error logs and web server logs: up to 90 days.
- Waitlist entries: until you're invited and sign up, or until you unsubscribe — whichever comes first.
- Billing records: as required by applicable U.S. tax law.
8. Your rights under GDPR
If you are in the EU/EEA, UK, or a country with comparable rights, you can:
- Access the personal data we hold about you.
- Rectify inaccurate data (most of this you can do yourself in the dashboard).
- Erase your account and associated data. A workspace Owner can do this themselves from Account → Close workspace: the workspace is deleted 30 days later, and support can reopen it until then. For anything else — your sign-in account, or your data in a workspace you don't own — email us and we'll delete or anonymise it within 30 days unless a legal obligation requires longer.
- Export your data in a machine-readable format (JSON / CSV).
- Object to processing based on legitimate interest, including marketing. For model training (section 3.10) you can do it yourself, under Account → Data use.
- Restrict processing while a dispute is being resolved.
- Withdraw consent for anything we process on that basis, at any time.
To exercise any of these, email privacy@statuspulse.ai. We'll respond within 30 days (usually faster).
If you believe we've mishandled your data, you have the right to complain to your local data protection authority — for EU/EEA residents, your national supervisory authority; for UK residents, the Information Commissioner's Office (ICO).
9. Notifications sent to third parties on your behalf
When you configure StatusPulse to email or SMS someone who is not the account holder (a "Person" in our system, or a status page subscriber), the legal responsibility to have a lawful basis for that contact rests with you as the controller of that relationship. In practice:
- Every email we send on your behalf includes an unsubscribe link that honours the opt-out immediately and permanently (stored as EmailsBlocked on the recipient).
- SMS recipients can reply STOP to opt out at the carrier level; we also offer a per-person SmsBlocked toggle.
- If a recipient asks us directly to stop, we will honour the request and notify you.
10. Security
We describe our security posture in detail on the Security page. The short version: HTTPS everywhere with HSTS, encryption at rest, Microsoft Entra for authentication, salted IP hashes, least-privilege access controls, and an audit log for privileged actions.
If we become aware of a personal data breach likely to result in risk to individuals, we will notify the relevant supervisory authority within 72 hours, and affected users as soon as reasonably possible, as required by GDPR Article 33 / 34.
11. Children
StatusPulse is a B2B service for engineers and operators. It is not intended for, and should not be used by, children under 16. We do not knowingly collect data from children. If we learn that we have, we will delete it.
12. Changes to this policy
We'll update this page when our practices change. Material changes (new sub-processors, new purposes for existing data, changes to retention) will be announced to account holders by email at least 30 days before they take effect, except where the change is required sooner by law.
The date at the top of this page always reflects the last modification.
13. Contact
For privacy questions, data subject requests, or to report a concern: privacy@statuspulse.ai.
For billing or account issues: support@statuspulse.ai.