The details, clearly set out
Terms of service
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”). These Terms govern access to UptimeOwl by the customer subscribing to the service (“Customer”, “you”) and the people the Customer authorises to use its workspace. Our legal and contact information is available at https://blastup.digital/en/legal-notice. You can contact us at [email protected].
1. Scope and acceptance
These Terms cover UptimeOwl's website, account dashboard, monitoring services, status widgets and pages, applications, APIs, integrations and related services (“Services”). They also apply to new features when those features become available to you.
The Services can include HTTP and API monitoring; certificate, domain and DNS checks; heartbeat, network and browser checks; regional and private-network monitoring; uptime and service-level reporting; incident collaboration; maintenance planning; status publication; notification delivery; on-call schedules and escalation; and approved diagnostic or remediation tools. Availability depends on the released capabilities, your plan, configuration and any agreed order. Describing a capability here does not promise that it is already released, included in every plan or due on a particular date. Roadmaps and previews are not delivery commitments unless expressly included in an agreed order.
When you complete registration, you accept these Terms and the Data Processing Addendum and acknowledge the Privacy Policy presented with signup. Your use must also comply with our Acceptable Use Policy. Our Cookie Policy explains cookies and related browser technologies. Accepting these documents is not consent to marketing communications or optional tracking.
The accepted subscription offer, these Terms and the applicable Data Processing Addendum form your agreement with Blastup. A specifically negotiated written order takes precedence for the commercial matters it expressly changes. The Data Processing Addendum takes precedence for processing of personal data on your behalf. Mandatory law takes precedence over any conflicting term.
2. Accounts, eligibility and workspace ownership
You must be at least 18, or the age of majority where you live if higher, and have authority to enter into this agreement. The Services are intended primarily for business and professional use. If mandatory consumer protections apply to your purchase, these Terms do not remove them.
If you register on behalf of an organisation, you confirm that you are authorised to bind that organisation. You must provide accurate account and billing information and keep it current. We may seek reasonable evidence of your authority or account ownership and restrict disputed access while ownership is resolved.
Each account may belong to only one tenant workspace. A separate workspace requires a separate account with a different email address. Invitations, delegated administration and any agency features do not create an entitlement to bypass this restriction. Platform administration by authorised Blastup personnel is separate from tenant membership.
Keep control of your registered email inbox and any sign-in links, tokens, devices or identity-provider credentials used to access the Services. Do not share personal login access. Notify us promptly at [email protected] if you suspect unauthorised access. We use your account and designated billing email addresses for operational and contractual communications; keep them monitored and current.
Workspace owners are responsible for invitations, roles, monitor and widget permissions, authorised recipients and the activities of their users. Give users only the access they need and revoke it when no longer required. Removal of a user's access does not by itself cancel the workspace subscription or erase its data.
3. Authorised monitoring and acceptable use
You must own the systems you monitor or have permission from their owner to perform the configured checks. This includes URLs, APIs, domains, certificates, network ports, private endpoints and browser journeys. Choose check frequencies, request bodies and actions that are authorised and suitable for the target system.
Monitoring requests and browser actions can generate traffic, consume third-party quotas, create records or trigger transactions. Use dedicated test accounts and safe test data where appropriate. You remain responsible for permissions and consequences on the monitored system.
Do not use the Services for unlawful surveillance, credential theft, unauthorised scanning, denial-of-service activity, spam or infringement. Do not bypass target restrictions, permission boundaries, rate limits or plan allowances, or attempt to access another tenant's data. Do not use multiple accounts to evade abuse controls or fees.
Where private agents, API tokens, signed webhooks, infrastructure-as-code, single sign-on or automated actions are available, you are responsible for deploying and configuring them securely, restricting their permissions and rotating or revoking credentials when needed. Enabling a diagnostic or remediation action authorises only the actions you explicitly configure. Review their impact and maintain suitable safeguards and recovery procedures.
4. Monitoring results, reports and service limitations
Monitoring is based on observations from configured probes at particular times and locations. A successful check does not guarantee that every user can reach your service, and a failed check may reflect a network, DNS, probe, provider or regional issue rather than a failure of the target itself.
Check intervals, consecutive-failure thresholds, confirmation rules, maintenance windows, pauses, missing results and regional policies affect incident detection and reporting. Reports, uptime percentages, latency summaries, error budgets and service-level objectives follow the calculation method stated for the relevant feature. They are not an independent certification or an uptime guarantee from Blastup.
Paused monitors do not continue normal checking or alerting. Maintenance and suppression settings can prevent or delay notifications. Cached, aggregated, delayed or offline views may not reflect the latest state. Regional probe selection describes the observation location; it does not, by itself, promise that all account data is stored or processed in that region.
UptimeOwl supports your operational processes but does not replace independent backups, security controls, incident response or human judgment. Do not rely on it as the sole safeguard for emergency, life-safety or other situations where a missed or delayed signal could cause serious harm.
No particular response time, monitoring availability, notification delivery time, recovery time or service credit is guaranteed unless an applicable written service-level agreement expressly provides it.
5. Notifications, on-call schedules and integrations
Where available, email, Slack, Microsoft Teams, web push and mobile push are included as notification channels in all plans, including Free. Inclusion does not mean unlimited volume or guaranteed delivery. Published plan limits, provider constraints and reasonable security and abuse protections apply.
You control workspace defaults, per-monitor recipient overrides, quiet hours, escalation paths, repeat alerts and on-call coverage. You are responsible for accurate email addresses and phone numbers, valid third-party connections, required recipient permissions and device notification settings. Obtain the authority and any consent needed to send notifications to recipients.
Notifications can be delayed, filtered, rejected or duplicated by network conditions, recipient settings or external services. A provider's acceptance of a message does not necessarily mean it reached or was read by the intended person. Acknowledgment, assignment or escalation automation does not guarantee that a person will respond. Configure alternative channels and coverage appropriate to your needs.
Connecting an external service authorises UptimeOwl to exchange the information needed for that integration in accordance with your configuration and applicable data-processing terms. External providers have their own terms and availability requirements. Disconnecting an integration prevents future use through that connection but does not necessarily remove information already delivered to the provider or recipient.
6. SMS, voice and usage-based services
SMS is a separately funded usage service and is not an unlimited benefit of any subscription plan. Where SMS credits, voice services or other usage-based features are offered, the applicable prices, destinations, charging units, taxes, spending limits and any credit expiry or refund conditions must be disclosed before purchase or activation.
Message cost can depend on destination, provider, message length, character encoding and the number of billable segments. Whether failed or undelivered attempts incur charges depends on the disclosed charging rules and provider outcome. Subscription fees do not automatically cover these charges.
Automatic top-ups require your separate authorisation and any displayed cap. Purchasing credits does not change the subscription renewal date. Exhausted credits or spending limits can stop further chargeable notifications. Any alternative-channel fallback depends on the options you configure; it is not automatic unless the feature states otherwise.
7. Public status content, branding and customer materials
You retain your rights in monitor configurations, uploaded logos, incident notes, status updates, reports and other materials you provide. You grant Blastup the limited rights necessary to host, process, transmit and display those materials to operate the Services and follow your instructions.
You decide what to publish in public widgets and status pages, including names, incident descriptions, branding, custom domains and translated text. Public content can be accessed, copied or cached by others. A widget identifier or an unlisted link is not a substitute for an available access-control feature. Keep secrets, personal information and internal operational details out of public fields.
Check that you have rights to uploaded branding and other content. You are responsible for your translations and for ensuring that public statements are accurate and appropriate. Removing published content may not remove copies already held by third parties.
Availability of custom branding, localisation, private pages, subscriber functions, custom domains and white labelling depends on your plan and the released feature. You must control any domain you connect and obtain the permissions needed to manage subscribers or publish updates to them.
8. Plans, allowances and Enterprise arrangements
The accepted offer states the price, currency, billing period, included capabilities and allowances. Limits can apply to monitors, users, widgets, check intervals, regions, history visibility, reports, integrations or usage. You are responsible for choosing a plan suitable for your requirements.
A lower allowance may limit new activity, require you to reduce configured usage, or hide history outside the plan's viewing window. A downgrade does not authorise silent deletion of your monitors, widgets or stored history. Older history is hidden where the allowance requires it; permanent deletion is deferred under the current retention policy. Open incidents remain available according to the service's documented access rules.
Enterprise plans may have customer-specific pricing and allowances. A specifically agreed zero-price or non-paying arrangement does not generate a subscription charge or sales invoice merely because a tracked cycle passes. Its agreed scope and duration still apply. If it becomes paid, the new offer and effective date must be communicated and recorded.
An Enterprise price change applies at the next billing cycle without proration. Agreed expiry, replacement or return to a standard plan follows the effective date and conditions shown in the accepted arrangement. No customer is entitled to an unapproved discount, exemption or allowance override.
9. Fees, payment methods and renewal
Unless your written order states otherwise, fees are in euros and exclude VAT. Paid subscriptions renew automatically every 30 days and are billed in advance for the following service period. This is a fixed 30-day cycle, not a calendar month or a common billing date for every customer.
By confirming a paid subscription, you authorise collection of the disclosed recurring charges through the selected payment method. Keep an authorised payment method available and update it when necessary. Stripe provides payment-card collection and payment processing; UptimeOwl does not store full card numbers or card security codes.
The default card you select is used for the applicable subscription collection flow. Additional payment authentication may be required. A browser redirect, payment attempt or pending charge does not establish successful payment; paid activation and related changes depend on verified payment status.
We send an upcoming-renewal notification three days before the scheduled charge. Email delivery is not guaranteed, and failure to receive a reminder does not change the agreed payment date. Your account's billing information shows the applicable amounts and cycle dates.
Provide accurate legal name, address, billing country, notification email and any applicable VAT number, and select the appropriate receipt or invoice details. VAT information may be checked through VIES or, for Greek business information, the relevant AADE service. A failed or unavailable validation may mean that an exemption cannot be applied. The applicable tax and total are displayed before payment; tax treatment remains subject to applicable law and any required correction.
Elorus is used for issuance of the corresponding accounting documents. Payment confirmation and invoice or receipt issuance are separate events; a document can remain pending while issuance is reconciled. Issued documents are made available through the authorised account view and relevant notifications. Changes to billing details do not silently rewrite previously issued documents.
Report suspected billing errors promptly to [email protected]. Reporting an error does not waive any mandatory right or remedy.
10. Plan changes and refunds
A standard-plan upgrade takes effect after successful payment of the displayed prorated amount for the remainder of the current cycle. The existing renewal date remains unchanged. A credit used in a proration calculation is an adjustment within that calculation, not a cash refund.
A downgrade takes effect at the next billing cycle, subject to the published allowance checks and any required reduction in configured usage. It does not retrospectively reduce the price of a period already purchased. Custom Enterprise price changes follow section 8 rather than immediate upgrade proration.
We do not provide ordinary refunds or partial refunds for unused subscription time, voluntary pauses, downgrades or late-payment suspension. This does not exclude refunds, withdrawal rights or other remedies that mandatory law requires. Exceptional authorised corrections or refunds are handled with the corresponding accounting adjustment or credit document. SMS and other prepaid usage balances follow their separately disclosed conditions.
11. Failed payments and recovery
After the first unsuccessful subscription charge, your workspace remains active for a five-day grace period. We send three payment reminders: at the first failure, on day 3 and on day 4. These are reminder times, not a promise of a particular processor retry schedule. Repeated payment failures do not restart the grace period.
If payment remains outstanding when the five-day period ends, the workspace is suspended: monitoring is paused and public widgets and applicable status services are deactivated. Stored tenant data is preserved during suspension, and retention cleanup is stopped. The authorised owner retains access to the billing recovery functions needed to update a card and pay the outstanding invoice.
Verified payment of the oldest overdue subscription invoice restores access that is eligible for restoration under the billing recovery policy. Other outstanding invoices remain payable. Payment does not remove a separate security, administrative or voluntary suspension, and it does not resume monitors you paused yourself.
Late payment settles the period stated on the existing invoice. It does not start a new subscription period, change the renewal anchor or generate a suspension credit. If you pay five days before the next renewal, the next period is still billed five days later. Subscription invoicing continues on the original schedule during a payment-default suspension unless the subscription is separately ended through the applicable process.
12. Voluntary suspension, cancellation and termination
An authorised owner can schedule voluntary suspension from the account's billing controls. If a paid cycle is active, suspension takes effect at the end of that cycle and access continues until then. Canceling the scheduled suspension before that date keeps the existing cycle. Suspension is not account deletion.
After a voluntary suspension has taken effect and the paid period has ended, reactivation starts a new paid 30-day cycle upon the required successful payment. Reactivation does not forgive an earlier debt or bypass an independent access restriction.
To request permanent account closure or contractual termination, contact [email protected]. We will verify your authority and confirm the effective date, the treatment of any remaining billing obligations and applicable export or deletion arrangements. A request to remove an individual user is not a request to terminate the workspace subscription.
We may restrict, suspend or terminate access for unlawful or abusive activity, a material breach, fraud, threats to service security, a binding legal requirement or unresolved account-ownership concerns. Where reasonably possible, we will explain the reason and allow a reasonable opportunity to resolve a remediable issue. Urgent security or legal action may require immediate restriction.
On effective termination, monitoring, notifications and publication services cease, and outstanding amounts properly due remain payable. Future subscription collection must end in accordance with the confirmed termination; previously incurred debts survive. Suspension alone does not authorise automatic destruction of your data. Data return, deletion and any legally required retention after termination follow the applicable Data Processing Addendum, Privacy Policy and confirmed closure arrangements.
13. Privacy, security and confidentiality
Our Privacy Policy explains processing for account administration, billing, security and other purposes for which Blastup determines the purposes and means. The Data Processing Addendum governs personal data we process on your behalf in providing monitoring and related features. You are responsible for the lawfulness of your instructions, the data you submit and required notices or permissions for your users, monitored systems and notification recipients.
Avoid including unnecessary personal data, payment-card data or confidential information in URLs, response samples, public incident descriptions and logs. Use appropriately scoped credentials for authenticated monitors and private agents. Processing locations, subprocessors, transfers, security obligations and data return or deletion are governed by the applicable data-processing documents, not merely by a chosen probe region.
Authorised Blastup personnel may access relevant account information where necessary to provide support, investigate incidents, secure the service or meet legal obligations. Tenant support access must follow the permission, time-limit and audit controls applicable to the feature. A support role does not give unrelated tenants access to your workspace.
Each party must protect the other's non-public business, technical, security and financial information using reasonable safeguards and use it only for the agreement's purposes. Disclosure is limited to personnel or service providers who need it and are bound by appropriate confidentiality obligations, or where law requires disclosure. Where lawful, the receiving party will give notice of compelled disclosure. This restriction does not cover information already lawfully known, independently developed, lawfully received from another source or publicly available without breach.
14. Mobile applications, automation and optional assistance
Where supplied, mobile applications are subject to these Terms and applicable app-store conditions. Device permissions, connectivity and operating-system restrictions can affect push delivery and access. Offline or cached information is not live monitoring data. You remain responsible for device security and for reviewing the current service state before taking action.
Incident collaboration, runbooks, scheduled reports, ticket integrations, automated diagnostics and remediation operate within the permissions and settings you choose. Review potentially disruptive actions before enabling them. No acknowledgment, generated report or automated action guarantees resolution of an incident.
If optional AI-assisted features are offered, their operation, applicable providers and data use must be disclosed before activation. Treat generated explanations, summaries and suggestions as assistance requiring human review. Do not submit data to an optional provider unless authorised to do so. These Terms do not give blanket permission to train third-party models on your confidential data.
15. Intellectual property and permitted access
Blastup and its licensors retain their rights in UptimeOwl's software, designs, documentation, trademarks and other platform materials. Your subscription grants access to the Services within the accepted plan and these Terms; it does not transfer ownership of the platform.
Do not copy, resell or exploit the Services beyond the permission expressly granted by an available embedding, agency, white-label or other agreed feature. Do not misrepresent affiliation with Blastup or misuse its names or trademarks. Customer logos uploaded for a status widget may be used to operate that widget; public use of your name or logo as a promotional endorsement requires separate permission.
16. Availability, support and changes
We will operate the Services with reasonable care, but maintenance, security work, network problems and external-provider failures can interrupt availability. The Services do not guarantee uninterrupted, error-free monitoring or that every incident will be detected. Any separately agreed service-level commitments apply according to their own terms.
Support is available through the channels stated for your plan or at [email protected]. Help-centre articles explain features but do not override your accepted agreement. A fixed response or resolution deadline applies only if specifically agreed.
For a general change to standard subscription prices, we will provide 90 days' advance notice. A price increase will not retrospectively change a period already paid for. You may stop renewal before the change takes effect through the applicable suspension or termination process. A customer-confirmed plan change or specifically agreed Enterprise price schedule follows its disclosed effective date instead.
We may improve or change the Services and will give reasonable notice of a material adverse change to a paid service, except where immediate action is needed for security, law or circumstances outside our reasonable control. Material contractual changes will be communicated with their effective date and any required acceptance process. Posting a new version does not rewrite the legal documents or offers already recorded for a previous acceptance.
17. Beta features
Features expressly labelled beta, preview or experimental may be incomplete, change or be withdrawn. Participation may have additional disclosed conditions. Do not rely on a beta feature as your only monitoring or recovery mechanism. A beta invitation does not promise general availability or inclusion in a future plan. Confidentiality obligations apply to non-public information supplied during a private beta, subject to section 13.
18. Liability and third-party claims
To the extent permitted by applicable law and subject to any expressly agreed service-level commitments, the Services are provided on an “as available” basis. Blastup does not warrant that monitoring results, integrations or optional assistance will meet every particular requirement. You must assess their suitability for your operations.
To the extent permitted by applicable law, Blastup's aggregate liability for damages under or in connection with these Terms is limited to the total fees received from you for the Services. This limitation does not apply to wilful misconduct, intent or gross negligence, death or personal injury, infringement of intellectual property rights, or any liability that cannot lawfully be limited.
Subject to those exceptions and mandatory law, Blastup is not liable for indirect, incidental, special or consequential losses, including lost profits, goodwill or business opportunities. These provisions do not remove mandatory rights concerning defective services, data protection or other legally protected remedies.
To the extent permitted by law, you are responsible for third-party claims and reasonable related costs caused by your unlawful use, unauthorised monitoring, infringing materials or material breach of these Terms. This does not cover loss caused by Blastup's own breach or misconduct. We will notify you of a relevant claim and reasonably cooperate; neither party may agree a settlement imposing obligations on the other without consent.
19. Contract records and notices
The applicable legal documents, accepted offer and confirmation records identify what you agreed to. Where a paid-plan contract PDF is supplied, it records the relevant customer billing identity, Blastup issuer details and accepted commercial and legal terms. Delivery to your billing contact and a Blastup accounting contact supports contract administration; it is not a claim that you applied a handwritten or qualified electronic signature.
Later changes to a billing profile do not alter an earlier contract or issued accounting document. Replacement agreements or amendments must identify their own effective terms. Service notices are sent to the relevant account or billing contact and may also be displayed in the account. Send formal questions, disputes and termination requests to [email protected].
20. General provisions and governing law
These Terms and the applicable order and incorporated documents constitute the agreement for the Services. Neither party may assign its contractual rights or obligations without the other's written consent, except where mandatory law provides otherwise. A waiver of one breach is not a waiver of another. If a provision is invalid, the remaining provisions continue to apply to the extent lawful.
Greek law governs this agreement. Unless another venue is validly agreed, the courts of Athens, Greece have jurisdiction, subject to mandatory jurisdiction rules. If you are entitled to mandatory consumer protection in another jurisdiction, this choice does not deprive you of that protection or of a forum that mandatory law makes available.
Contact Blastup about these Terms at [email protected].