Privacy Policy.
1. Introduction
This privacy policy explains which of your personal data we process, for what purposes, and to what extent. It applies to all services operated by us, in particular our websites, mobile applications, and external online presences such as our social media profiles (collectively the "Online Offering").
2. Controller (Verantwortlicher, Art. 13 GDPR)
Timothy Hessel
Kölner Str. 234, 47805 Krefeld, Germany
Email: [email protected]
Phone: +49 15563 116243
Processing on behalf of business customers (Auftragsverarbeitung, Art. 28 GDPR): Where you, as a business customer, use Uptriva to have us process system metrics, server logs, IP addresses, or alert contact data of your own systems and personnel, you remain the controller (Verantwortlicher) within the meaning of the GDPR and we act as a data processor (Auftragsverarbeiter). For such processing a Data Processing Addendum (DPA / AVV — Auftragsverarbeitungsvertrag) is available, which business customers may conclude upon request at [email protected].
3. Data We Collect and Why
3.1 Account Registration
We collect your email address, hashed password, full name (optional), and phone number (optional) when you register.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Retention: Until account deletion, then removed within 30 days.
3.2 Server Logs and IP Addresses
When you access our services, we log your IP address, timestamps, browser user-agent, and accessed URLs in server and audit logs. These logs are automatically purged after 90 days by a daily retention job.
Legal basis: Art. 6(1)(f) GDPR — legitimate interest (security and diagnostics).
Retention: 90 days, automatically purged.
3.3 Billing Data
Payments are processed by Polar.sh. We only store external customer IDs and subscription IDs. Payment card data is handled exclusively by Polar.sh and never stored on our servers.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Third party: Polar.sh Privacy Policy
3.4 Transactional Emails
We send transactional emails (email verification, 2FA codes, alerts) via our own self-hosted SMTP server (Stalwart, running on mail.shxrk.systems in Germany).
Legal basis: Art. 6(1)(b) GDPR — contract performance.
3.5 Two-Factor Authentication
If you enable 2FA, we store an AES-256-GCM encrypted TOTP secret or hardware key credentials (WebAuthn). This data is encrypted at rest and used solely for authentication.
Legal basis: Art. 6(1)(f) GDPR — legitimate interest (account security).
3.6 Monitoring Data
Monitor configurations, check results, latency measurements, status pages, and alert settings are stored. This data belongs to you and is deleted when your account is removed.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
3.7 Uptriva Agent (Self-Hosted)
If you install the Uptriva agent binary on your own servers, the agent collects system-level metrics from your own infrastructure and transmits them to our API over TLS. This includes CPU, RAM, disk, and network usage, load averages, system uptime, disk mount details, the names of running processes, and the status of systemd units (including failed unit names). The agent also reports its version and heartbeat status.
In addition, the agent can act as a private pinger: if you assign monitors to an agent, it executes the configured uptime checks (HTTP, TCP, DNS, ping, databases, and other check types) directly inside your network against the targets you define — including private or internal addresses that are unreachable from the public internet — and transmits the check results (up/down status, latency, and error messages) to our API. Internal hostnames and IP addresses you configure as check targets are stored as part of your monitor configuration.
The agent does not collect personal data — only system-level and check-result data. You control which servers you run the agent on and which targets it checks, and you can uninstall it or unassign monitors at any time.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Retention: Agent metrics and check results follow your plan's monitor-data retention (see section 9) and are removed when the agent or your account is deleted.
3.8 Notify Contacts and Subscribers
If you add notify contacts or status page subscribers, we store the contact information you provide (email, phone number, Slack webhook, Telegram chat ID, Discord user ID, etc.) to deliver alerts and status updates.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Retention: Until the contact is deleted or the associated status page is removed.
3.9 Beta Invite Codes
During the beta phase, registration may require an invite code. We store the code, the staff member who generated it, optional notes, and — once used — the user ID and timestamp of usage. This allows us to track beta tester onboarding and prevent code abuse.
Legal basis: Art. 6(1)(f) GDPR — legitimate interest (beta program management).
Retention: Until 30 days after the beta phase ends.
3.10 Referral Program
If you participate in the referral program, we store your unique referral ID, the users you referred (by referral ID only), and any credits earned. Referral credits have no cash value.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Retention: Until account deletion.
3.11 Company and Tax Information
For business and enterprise billing, you may provide a company name, tax ID, and registration number. This data is used for invoicing and tax compliance purposes.
Legal basis: Art. 6(1)(c) GDPR — legal obligation (tax retention under §147 AO and §257 HGB).
Retention: Up to 10 years as required by tax law.
3.12 Honeypot and Security Logging
We operate honeypot endpoints to detect and block malicious actors. If you trigger a honeypot, we log your IP address, user-agent, timestamp, and the specific endpoint accessed. Banned IPs are retained for up to 90 days and then automatically purged, or until manually unbanned by an administrator.
Legal basis: Art. 6(1)(f) GDPR — legitimate interest (platform security).
Retention: Banned IPs retained for up to 90 days, then automatically purged.
3.13 Social Sign-In (Google and Microsoft)
You may optionally register or log in using your Google or Microsoft account (OAuth 2.0 / OpenID Connect). If you choose this option, the provider transmits your email address, display name, profile picture URL, and a unique provider account ID to us. We use this data exclusively to create or identify your Uptriva account. We never receive your provider password, and we do not access your contacts, files, calendars, or other provider data. If an account with the same email address already exists, the sign-in is linked to that existing account. Email addresses confirmed by the provider are marked as verified on our side. You can revoke access at any time in your Google or Microsoft account settings; this does not delete your Uptriva account and you can continue to sign in with email and password.
Enterprise customers may additionally configure SAML or OIDC single sign-on (SSO) via their own identity provider (e.g. Microsoft Entra ID). In that case, the identity provider operated by your organization supplies your name and email address during login, and SCIM provisioning may be used to create and deactivate accounts.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Third parties: Google Privacy Policy, Microsoft Privacy Statement
3.14 File Uploads and CDN Storage
If you upload files through our services — for example status page logos, profile or brand assets, CMS/blog images, or support ticket attachments — the files are stored in Cloudflare R2 object storage. Public assets (logos, images) are stored in a public bucket and delivered through our content delivery domain cdn.uptriva.com with global edge caching. Support ticket attachments are stored in a private bucket that is not publicly reachable; they can only be downloaded via short-lived, pre-signed URLs that are issued after an authorization check in our API.
When your browser loads fonts, logos, or uploaded images from cdn.uptriva.com, Cloudflare processes the usual technical access data (IP address, timestamp, user-agent) to deliver the file from the nearest edge location.
Legal basis: Art. 6(1)(b) GDPR — contract performance.
Retention: Until the file or the associated content is deleted; uploads are removed when your account is deleted.
Third party: Cloudflare Privacy Policy
3.15 Newsletter and Launch Updates
If you subscribe via the newsletter form in the website footer or the signup form on the maintenance page, we store your email address, an optional name, the signup source, and the IP address and user-agent captured at signup time (used for abuse prevention). We use a double opt-in process: after signing up you receive a confirmation email and only receive newsletters once you confirm the link in it. We use this data exclusively to send you product updates and the beta launch announcement. Every newsletter email contains an unsubscribe link that removes you from the list immediately. We do not share this list with third parties.
Legal basis: Art. 6(1)(a) GDPR — consent. You can withdraw consent at any time via the unsubscribe link, without affecting the lawfulness of processing before withdrawal.
Retention: Until you unsubscribe; the entry is then deleted immediately.
5. Local Storage
We use browser local storage for the following purposes. Local storage is not a cookie and is not transmitted to our servers on every request, but it persists on your device.
| Key | Purpose |
|---|---|
| uptriva_cookie_consent | Cookie consent preference (website) |
| agents-list-view-mode | UI preference: agent list display mode (grid/list) |
| recovery_codes | 2FA recovery codes (sessionStorage only — cleared when browser tab closes) |
| uptriva_status_page_id | Last selected status page ID (UI convenience) |
You can clear local storage at any time via your browser settings. Clearing local storage will log you out and reset UI preferences.
6. Third-Party Services
Fonts and Brand Assets: We use the Geist typeface and our brand assets, all served exclusively from our own content delivery domain cdn.uptriva.com (Cloudflare R2 object storage). No font requests are made to Google Fonts or any other third-party font service at runtime. Loading these assets is covered by section 3.14.
Cloudflare: We use Cloudflare as our DNS provider, CDN edge cache, and object storage provider (R2). Uploaded assets such as status page logos and CMS images are stored in R2 and delivered through cdn.uptriva.com; support ticket attachments are stored in a separate private R2 bucket accessible only via short-lived pre-signed URLs. Cloudflare may process access data at its global edge locations. Cloudflare Privacy Policy
Polar.sh: Payment processing. Polar.sh Privacy Policy
Twilio: SMS and voice call notifications. Twilio processes the recipient phone number and message content on our behalf when you configure call or SMS alerts. Twilio Privacy Notice
Google and Microsoft (OAuth sign-in): Optional social sign-in providers. If you choose to log in with Google or Microsoft, the provider authenticates you and shares your email address, name, and profile picture with us — see section 3.13 for details. Google Privacy Policy / Microsoft Privacy Statement
Discord, Slack, Telegram: When you configure alert channels, we deliver notifications to these platforms using the credentials and identifiers you provide. These are third-party services outside our control and are governed by their own privacy policies. We do not store messages on these platforms beyond what is necessary to deliver the alert.
Hetzner Online GmbH: Hosting infrastructure located exclusively in Germany (Falkenstein, Nuremberg). Hetzner Privacy Policy
7. International Transfers
Our primary infrastructure is hosted with Hetzner in Germany (Falkenstein, Nuremberg); no personal data is processed at Hetzner locations outside the EU. Polar.sh and Twilio are located in the United States; data transfers to them are protected by the EU-US Data Privacy Framework and/or Standard Contractual Clauses (SCC) where required. US-based service providers certified under the EU-US Data Privacy Framework (DPF) are covered by an adequacy decision of the European Commission; transfers to such providers therefore take place on the basis of Art. 45 GDPR and require no additional safeguards. Cloudflare may process edge traffic through global points of presence under its Data Processing Addendum, and uploaded files are stored in Cloudflare R2 object storage (EU jurisdiction) and cached at edge locations worldwide when served through cdn.uptriva.com. Discord, Slack, and Telegram are user-configured destinations outside the EU/EEA; we transmit alerts only when you explicitly configure those channels. If you use Google or Microsoft sign-in, authentication data is processed by those providers in the United States under their respective data processing terms and, where applicable, the EU-US Data Privacy Framework. We do not claim that all data is processed exclusively within the EU.
8. Your Rights (GDPR)
- Access (Art. 15): You may request a copy of the personal data we hold about you.
- Rectification (Art. 16): You may request correction of inaccurate data.
- Erasure (Art. 17): You may request deletion of your personal data ("right to be forgotten").
- Restriction (Art. 18): You may request that we restrict processing of your data.
- Data Portability (Art. 20): You may receive your data in a structured, machine-readable format.
- Objection (Art. 21): You may object to processing based on legitimate interests.
- Withdraw Consent (Art. 7(3)): You may withdraw consent at any time, without affecting the lawfulness of prior processing.
We do not use automated decision-making or profiling within the meaning of Art. 22 GDPR. Automated security responses (for example temporary IP bans after honeypot triggers) have no legal or similarly significant effect on you.
Submit requests to: [email protected]
9. Data Retention
- Account data: Retained until account deletion, then removed within 30 days.
- Server and access logs: Up to 90 days, automatically purged by a daily retention job.
- Audit logs: 7 days (Free), 30 days (Premium), 90 days (Elite), or 365 days (Enterprise), depending on your subscription tier. Enterprise plans may configure unlimited retention.
- Monitor check data: 7 days (Free), 30 days (Premium), 90 days (Elite), or up to 1 year (Enterprise). Automatically purged based on tier.
- Error logs: 90 days, automatically purged.
- Webhook delivery logs: 90 days, automatically purged.
- Referral click data: 365 days, automatically purged.
- Payment records: Retained as long as required by tax law (up to 10 years under §147 AO and §257 HGB).
- Beta invite codes: Retained until 30 days after the beta phase ends.
- Honeypot / security bans: Banned IPs retained for up to 90 days, then automatically purged. Manual unbans are processed immediately.
- Backup copies: Daily database backups are retained for 14 days on encrypted storage. Backups are overwritten on rotation.
Last Updated: September 2026 — DPA, TDDDG and DPF revision