The details, clearly set out
Privacy Policy
Development placeholder. The final legal text has not been published.
UptimeOwl is a monitoring and incident-management SaaS platform operated by Blastup Single Member P.C. (“Blastup”, “we”, “us”). This policy explains how personal data is handled when you visit uptimeowl.online, register or use an account, receive notifications, view status content, contact us or use related applications and integrations.
Our legal information is available at https://blastup.digital/en/legal-notice. For privacy questions and requests, contact [email protected].
1. Scope and our role
This policy covers UptimeOwl's monitoring, incident, reporting, status-publication, billing and support services. It also explains data handling associated with mobile applications, regional and private probes, additional monitor types, on-call routing, messaging and enterprise features when those capabilities are available and enabled. Their inclusion here does not mean every feature is currently released or active in your account.
Blastup acts as a controller for personal data used to administer its customer relationships, accounts, billing, legal records, website security and business communications. Where we process personal data contained in monitoring configurations, check results, incident content, recipient lists or other workspace materials on a customer's instructions, we generally act as that customer's processor. If the customer is itself a processor, we may act as a subprocessor under the applicable arrangement.
The customer determines why and how personal data is included in its use of the service and must provide appropriate notices and establish a lawful basis. Our Data Processing Addendum at https://uptimeowl.online/data-processing-addendum governs processing on the customer's behalf. A customer's privacy notice governs its own collection and use of information through monitored systems or published status services.
Acknowledging this policy or accepting our Terms does not provide blanket consent to advertising, optional tracking or every possible use of personal data.
2. Information we receive and its sources
We receive information directly from you, from workspace owners and other authorised users, from your browser or device, from monitored endpoints and configured integrations, and from service providers involved in delivering the features you use. Public business or technical registries may also provide information needed for validation and monitoring.
Account and access information
This can include your name or username, email address, workspace identity, invitations, role and resource permissions, email-verification state, session and sign-in records, and the time and context of relevant account actions. Magic links and access tokens support authentication. Normal production sign-in also requires an authenticator-app code or an unused backup code after the email link. We process encrypted authenticator setup and active secrets, hashed single-use backup codes, enrollment state, verification times and security-action records to protect account access. Backup codes are shown once; we do not email them or retain a retrievable copy. Setup QR codes are generated within UptimeOwl without sending the secret to a third-party QR service. You choose the authenticator app that holds your copy of the secret. Where an enterprise identity integration is enabled, we may receive identity attributes and provisioning instructions from the organisation's identity provider.
Billing, tax and contract information
This can include billing name or company, address, country, VAT or tax identifier, billing notification email, selected plan, custom Enterprise arrangements, subscription periods, payment and outstanding-invoice status, and accounting-document references. We retain relevant legal acceptance records, document versions, contract records and billing changes.
Stripe collects full payment-card details through its payment interface. UptimeOwl does not store full card numbers or card security codes. We receive payment-method identifiers and limited details such as card brand, last four digits and expiry for display and management, together with transaction and subscription status.
VAT or business-identity checks can involve VIES and, for Greek businesses, AADE registry services. Returned information can include validation results, company name and address. Elorus receives the billing information required to issue the appropriate accounting documents.
Monitoring and incident information
Customers can provide endpoint addresses, hostnames, IP addresses, request settings, credentials, headers, bodies, rules, schedules, tags and groups. Depending on the monitor type, results may include timestamps, status codes, latency, errors, certificate or domain information, DNS records, heartbeat events, network responses and permitted response samples or logs.
Browser journeys, private agents and diagnostic functions may process additional target content or action results when enabled. Incident collaboration can include assignments, acknowledgments, severity, notes, runbook links, maintenance messages and post-incident reviews. Such information can contain personal data if the customer includes it or the monitored system returns it.
Notifications, schedules and device information
Where relevant, we process recipient email addresses, mobile numbers, third-party channel identifiers, push subscription or device tokens, selected monitor subscriptions, on-call schedules, time zones, overrides and escalation settings. Delivery records can include provider message identifiers, timestamps, outcome or error information and usage or SMS-credit charges.
Mobile and web-push features may use device or browser information and permission settings needed to deliver notifications. Selecting a monitoring region is not the same as collecting a user's precise device location; any feature requesting an additional device permission must explain its purpose when requested.
Website, security and support information
Requests can provide IP address, browser or user-agent information, requested resources, timestamps, response information and connection metadata. We also process support correspondence, information you choose to attach, and relevant audit and security records. Public-page visitors need not create an account, but technical request information is still processed to deliver and protect the page.
3. Purposes and legal bases
Where Blastup acts as controller, the legal basis depends on the particular activity:
• Contract or requested pre-contract steps: creating and administering a subscription, supplying requested features, providing support and managing payments where the individual is a party to the contract.
• Legitimate interests: administering an organisation's users and business contacts, protecting accounts, preventing abuse, maintaining reliability, resolving disputes and improving service operation. We assess necessity and balance these interests against individuals' rights and reasonable expectations.
• Legal obligations: keeping required accounting and tax records, responding to valid legal requirements and fulfilling applicable data-protection duties.
• Consent: optional marketing or other activities for which consent is required. Consent must be specific and can be withdrawn without affecting earlier lawful processing.
Processing customer-controlled workspace data follows the customer's documented instructions and applicable Data Processing Addendum. The customer is responsible for its own legal basis. We do not assume that every user is personally a party to the customer's subscription contract.
Required fields are identified in the relevant flow. If necessary information is not provided, we may be unable to create an account, provide the requested feature, validate billing details or respond fully to a request. Optional information and permissions should not be supplied unless relevant to the feature you want to use.
4. Workspace access and customer responsibilities
Each account belongs to one tenant workspace. Authorised owners and administrators can manage the workspace and may see relevant user identities, permissions, operational information and audit records according to their role. Resource permissions further determine access to monitors, widgets and other data. A separate workspace requires a separate account; information is not made available to unrelated tenants merely because they use UptimeOwl.
Customers must be authorised to monitor their targets and send notifications to selected recipients. They should use appropriately scoped test credentials and minimise personal data in URLs, request bodies, responses, screenshots, incident notes and public fields.
The service is not designed as a repository for unnecessary sensitive personal data. Do not deliberately submit special-category data or similarly restricted information unless its processing is expressly covered by an appropriate arrangement and lawful safeguards. A person's consent is not automatically the correct basis for every workplace or sensitive-data use.
If you are a recipient, employee or other person whose information a customer processes using UptimeOwl, contact that customer about its purposes, settings and instructions. If you contact us instead, we will help identify the appropriate route and assist the customer as required by our obligations.
5. Public widgets, status pages and subscribers
Customers choose which monitor names, statuses, incident updates, branding and other content to publish. Public widgets and status pages can be viewed without a UptimeOwl account. Information published publicly can be copied, indexed or cached by others. A hard-to-guess identifier or an unlisted link is not a substitute for an available privacy or access-control setting.
Where private pages, custom domains or subscriber features are available, we process the access and subscription information needed to provide them. A status subscriber's contact details and preferences are used to deliver the updates they request on the customer's behalf. Subscription management or withdrawal is handled through the feature's controls or the customer responsible for the page.
A website embedding an UptimeOwl widget may separately collect information through its own cookies or services. Its privacy notice governs those activities. Viewing a public widget does not itself create an UptimeOwl sign-in session.
6. Alerts, mobile access and connected services
When you or your administrator enables a notification channel or integration, relevant recipient and event information is sent to that service. Examples include email delivery, Slack and Microsoft Teams, OneSignal web or app push, Twilio SMS or voice, signed webhooks and ticketing connections. The information sent depends on the selected feature and message configuration.
Delivery receipts, failed attempts, acknowledgments and escalation outcomes help operate and troubleshoot the notification workflow. Message recipients and external providers may retain messages independently after delivery. Removing a connection or revoking access stops subsequent authorised use through that connection, but does not recall copies already delivered.
Mobile applications use account permissions and device settings to provide access and, where enabled, push notifications. Operational information may be temporarily stored for a session or offline view. Mobile sign-in credentials and pending sign-in proof use the operating system’s secure Keychain or Keystore. Verified mobile sessions persist until sign-out, revocation or loss of access, rather than expiring after 24 hours. Authenticator setup keys and newly displayed backup codes are held in app memory, not saved automatically to this credential store; an explicit save or share action uses the destination you choose. You can manage device permissions in the operating system and revoke account sessions through the controls available to you.
On-call schedules, incident assignments, response metrics and reports are intended to support the customer's operational process. Customers are responsible for any employment-related use and any additional notice, consultation or legal basis that such use requires.
7. Who receives personal data
Access and disclosure are limited to the purposes described in this policy, customer instructions and applicable law. Relevant recipients can include:
• Authorised Blastup personnel and professional advisers who need access for support, security, billing, accounting, legal obligations or service operation.
• Infrastructure and storage providers, including UpCloud for hosting and managed services, Google Cloud Storage for uploaded assets and applicable private documents, and Cloudflare for delivery and security.
• Stripe for payment processing, Elorus for accounting-document workflows, and relevant tax or business-validation services for the information needed to validate and document transactions.
• Mandrill/Mailchimp Transactional for email delivery, and messaging or integration providers used by enabled features, including OneSignal, Twilio, Slack and Microsoft Teams where applicable.
• The customer's authorised users, configured recipients, connected systems and, for content deliberately published, the public.
• Authorities or other parties where disclosure is required by law or necessary and lawful to establish, exercise or defend legal claims. A business reorganisation may involve relevant information subject to appropriate safeguards and notice where required.
Providers may act as processors for some activities and independent controllers for others, such as their own regulated payment, fraud-prevention or compliance functions. Their role and notices depend on the service. A customer's separately selected integration is not automatically a Blastup subprocessor for every activity.
The applicable Data Processing Addendum and subprocessor information govern processing on a customer's behalf. You may request information about relevant recipients and safeguards at [email protected]. Naming a planned provider does not mean it receives your data before the corresponding feature is activated.
Where a paid-plan contract PDF is generated, the customer receives a copy and a separate copy goes to Blastup's [email protected] inbox for contract administration and accounting. That workflow is separate from marketing communications.
8. International processing and regional monitoring
Hosting, delivery, notifications, support and integrated providers can involve processing in more than one country, including countries outside the European Economic Area. A selected probe region identifies where an observation is made; it does not establish that all account information, message delivery or provider support remains in that region.
For transfers subject to GDPR international-transfer requirements, the relevant arrangement must use an applicable adequacy decision or another valid mechanism, such as appropriate Standard Contractual Clauses with necessary assessments and supplementary safeguards. The mechanism depends on the destination, recipient and service. We do not assume that all providers in a country have the same transfer status.
You can request information about the safeguards applicable to your data, and a copy where appropriate, at [email protected]. Customer-specific residency commitments apply only where expressly agreed and supported by the relevant service configuration.
9. Cookies, browser storage and optional tracking
The Cookie Policy at https://uptimeowl.online/cookie-policy explains the sign-in cookie, temporary browser storage and relevant third-party technologies. Browser sign-in sessions last up to 24 hours and can end earlier through logout, revocation or security controls. Mobile sessions use persistent, revocable credentials in secure device storage. A separate essential verification cookie supports the restricted browser sign-in step for up to ten minutes; it does not grant workspace access.
Temporary storage supports functions such as workspace context, invitations and authorised support visits. Browsers provide controls to inspect, delete or restrict cookies and site data, although doing so can affect sign-in or other features.
With your optional permission, we use Google Analytics on production marketing, help, legal and signup pages, and limited plan events on the Billing tab of your account to understand visits, registration steps and plan choices. We keep Google Analytics blocked until you select “Allow analytics”; you can decline or withdraw through “Analytics preferences” in the footer without affecting your account. We remember that choice in browser storage for up to 180 days.
Our analytics events exclude form entries, names, email addresses, workspace identifiers, billing details, authentication tokens and URL queries/fragments. Google still receives technical information associated with an analytics request, such as network and browser information, and may use permitted analytics cookies. See the Cookie Policy and https://policies.google.com/privacy. Google signals and advertising personalisation are disabled in our tag. General authenticated dashboard activity and tenant-hosted status pages/widgets are outside this platform analytics scope. Withdrawing permission stops future platform analytics; it does not erase information already received. A browser's “Do Not Track” setting is not a universal substitute for these choices.
With analytics permission, plan events contain a standard plan label (Free, Starter, Team, Business or Enterprise), the activation category and an opaque event identifier. They never contain prices, card or invoice details, custom Enterprise revision identifiers or workspace identifiers. Paid activations are reported only after the application confirms the change. A minimal internal receipt prevents duplicates; essential billing records remain separate. No billing-page view is sent. Analytics remains optional and does not affect signup or billing.
10. Communications and marketing choices
Sign-in messages, invitations, security alerts, billing reminders, payment and document notifications, and customer-configured operational alerts serve the account or requested feature. They are distinct from promotional messages.
If we offer optional newsletters, promotional communications, surveys or events, we will explain the information required and the applicable choice or legal basis at collection. Signing up for UptimeOwl does not automatically subscribe you to marketing. You can withdraw marketing consent or object to direct marketing by the provided mechanism or by contacting [email protected].
We will disclose any optional message-opening or click-tracking used for those communications rather than assuming all service emails use it. Declining marketing does not stop essential contractual or security communications or change the recipient instructions supplied by your workspace administrator.
11. Security and support access
We use technical and organisational safeguards appropriate to the service and the risks, including access controls, tenant separation, protected authentication mechanisms, audit records and protection of sensitive credentials. Security measures reduce risk but do not make a system immune to every incident.
Authorised support access to a tenant workspace is permission-controlled, time-limited and auditable according to the feature. Platform administrators may also process relevant account and billing information for their authorised responsibilities. Support access is not permission to use customer data for unrelated purposes.
Protect your inbox, sign-in links, devices, integration tokens and monitor credentials. Contact [email protected] promptly if you suspect an unauthorised disclosure or account compromise. Where a personal-data breach occurs, we follow applicable notification duties and the relevant Data Processing Addendum.
12. Retention, suspension and deletion
Retention depends on the purpose, the type of information, the applicable service arrangement, legal obligations and whether a dispute or security issue requires preservation. A plan's visible history window is not a promise that all underlying information is deleted at that boundary.
Monitoring history outside a plan allowance is hidden under the current product policy; permanent deletion of that history is deferred. During billing or voluntary suspension, tenant data is preserved and monitoring-history cleanup is paused. Suspension and the removal of a user's access are not permanent account deletion. These operational rules do not override valid legal obligations or applicable data-subject rights.
Email sign-in links and pending verification proofs expire; browser sessions last up to 24 hours, while mobile sessions remain revocable and persistent. Pending sign-in verification lasts ten minutes and pending authenticator replacement lasts five minutes. Expired temporary authentication information is removed through bounded operational cleanup. Active encrypted authenticator secrets and unused backup-code hashes are retained to operate account security until replaced or removed with the account. Security, audit and delivery records may be retained for the period needed to investigate incidents, provide support and demonstrate appropriate processing. Financial, tax, contractual and legal-acceptance records can be retained beyond account closure where required or justified for their stated purpose.
After permanent closure, data return, deletion and remaining retention are handled under the applicable agreement, Data Processing Addendum and legal requirements. Backups and copies already delivered to customers or third-party recipients may follow separate arrangements; account closure does not mean every copy disappears immediately. Contact us for the retention criteria or closure arrangements relevant to your information. We do not claim a fixed universal deletion period that has not been established for the data concerned.
13. Automated workflows and optional AI assistance
UptimeOwl automates checks, thresholds, incident transitions, notification routing, quotas and billing-status controls using the relevant configuration and service rules. For example, an unresolved payment failure can lead to suspension under the published billing terms. If you believe an automated account or billing action is incorrect, contact [email protected] to request review.
This policy does not waive rights that apply to a solely automated decision with legal or similarly significant effects. If a feature involves such processing, the required information and safeguards must be provided for that feature.
Optional AI-assisted summaries, diagnostics or suggestions may involve processing the information you choose to submit. Before enabling such a feature, we will explain the applicable provider, data use and choices. There is no blanket permission in this policy for training third-party models on your confidential workspace content. Review outputs before relying on them, and do not submit data you are not authorised to share.
14. Your rights and how to exercise them
Depending on the circumstances and applicable law, you may request access to your personal data, correction, erasure, restriction of processing or portability. You may object to processing based on legitimate interests and to direct marketing. Where processing relies on consent, you may withdraw it for the future without changing the lawfulness of earlier processing.
Send requests to [email protected]. We may ask for proportionate information to verify identity or authority and locate the relevant data. If we process the information only on a customer's behalf, we will refer or assist the request through that customer as appropriate. Rights are subject to applicable conditions and exceptions, including obligations to retain certain records; we will explain an applicable restriction when responding.
You may complain to a competent data-protection authority, including the Hellenic Data Protection Authority in Greece or the authority for your habitual residence, place of work or alleged infringement. Information about complaints in Greece is available at https://www.dpa.gr/en/individuals/complaint-to-the-hellenic-dpa. Contacting us first can help resolve a concern but is not a condition on a legal right to complain.
15. Children and sensitive information
UptimeOwl accounts are intended for adult business and professional users. The service is not directed at children. Customers must not deliberately use it to collect children's information or sensitive personal data without an appropriate, expressly supported arrangement and the safeguards required by applicable law.
If you believe a child has provided account information or that unsuitable sensitive information has been included in the service, contact [email protected] so the matter can be assessed and addressed.
16. Changes and contact
We may update this policy as UptimeOwl develops or processing arrangements change. Material changes will be communicated by appropriate means and additional information or consent will be provided where required. An updated notice does not retroactively create consent or rewrite a previously recorded agreement.
For questions, privacy requests or information about applicable safeguards, contact Blastup at [email protected]. Our legal contact information is available at https://blastup.digital/en/legal-notice.