rootwatch rootwatch Terms of Service
Version 1.6 · Last updated: 3 October 2026
These Terms govern the use of the rootwatch service. They are written to be read: if any part is unclear, write to us before subscribing.
1. Who we are and who these Terms apply to
1.1 Provider. rootwatch is a service provided by Código Luminoso, Unipessoal Lda, a single-member private limited company incorporated under Portuguese law, with tax ID (NIPC) 516 097 121, registered at the Commercial Registry under the same number, with a share capital of €500, and registered office at CAIS – Espaço Empresarial, Largo José da Cruz, n.º 3, 2260-369 Vila Nova da Barquinha, Portugal. Contact: geral@terraroot.pt · +351 249 248 178. rootwatch and terraroot are brands of Código Luminoso, Unipessoal Lda. In these Terms, "we" and "us" mean Código Luminoso, Unipessoal Lda.
1.2 Customer. "You" or "Customer" means the natural or legal person who creates a rootwatch account. If you create the account on behalf of a company or another organisation, you represent that you have authority to bind it to these Terms.
1.3 For professionals only. rootwatch is intended exclusively for professionals: companies and other organisations, and natural persons who carry on a professional activity on their own account (for example, registered self-employed workers and freelancers), who take it out for that activity. We do not contract with consumers, that is, with anyone who intends to use the service for purposes outside their trade, business, craft or profession. The declaration of professional status you make when creating the account and when subscribing, and its consequences, are set out in clause 8.
1.4 Payment processed by a third party. Purchases are processed by Sold through Link, LLC, an affiliate of Stripe, acting as merchant of record. Sold through Link, LLC collects the price, issues the receipts and invoices for the purchase, handles refunds and payment disputes and is responsible for taxes on the sale in the countries where Stripe provides that coverage; elsewhere, the invoice is issued in our name and taxes are our responsibility. Payment support is provided at support.link.com. The contract for the rootwatch service itself is concluded with us. The purchase is also subject to Stripe's Sold through Link terms. See clause 6.
1.5 Acceptance. You accept these Terms when you create the account and again when you subscribe. The contract is concluded when you complete the order at checkout; before that you can review and correct the data entered. We archive the version of the Terms accepted, the date and the consent given, and email them to you. The Terms exist in Portuguese and English (clause 16.2). You can read, download and print these Terms at any time at rootwatch.terraroot.pt/terms.
2. What rootwatch does and does not do
2.1 The service. rootwatch monitors completion confirmations of scheduled automations. For each automation you configure a unique address to which the automation sends an HTTP request (a "ping") at the end of each run, and you define when the confirmation is expected. If the confirmation does not arrive within the deadline, rootwatch opens an incident and sends an alert to the destinations you configured (email and/or webhook to Slack, Discord or Google Chat). When the confirmation arrives again, it notifies you of the recovery. The dashboard shows the state of each automation, organised by end client.
2.2 What a signal means. A success ping confirms what your integration reported; it does not verify that the business outcome of the automation was correct. A failure ping reports what the integration reported. The absence of a ping does not mean the automation did not run: it may result from a run that never started, a failure before the last step, a delay, or a problem sending the request. rootwatch tells you that the expected confirmation did not arrive and where to look; it does not guess the cause.
2.3 What rootwatch does not do. It does not run, retry, pause, fix or alter your automations. It does not access the platforms they run on. It does not receive or store the content that the automations process; it receives only operational metadata (state, run and event identifiers, time of sending). It is not intended for systems whose failure may endanger life, health or safety, and it does not replace the control mechanisms of your own systems.
2.4 Honest states. rootwatch only asserts what it can observe. If rootwatch itself is unavailable or its detector is no longer up to date, the dashboard shows the state as "stale" or "unavailable", never as "all good". See clause 12.
2.5 Compatibility. rootwatch works with any platform able to send an HTTP request. At launch, the step-by-step guide is tested for n8n; for other platforms we provide the HTTP contract and a generic example.
3. Account and security
3.1 Creation. The account is created with an email address and a password. You must verify the email before subscribing: that is the address to which we send alerts and account notices.
3.2 Age. You must be at least 18 years old to create an account.
3.3 Credentials. You are responsible for keeping your password and the ingestion token of each automation secret. Tokens are credentials: whoever has them can send pings on behalf of your automation. Do not place them on public pages, screenshots or repositories. If you suspect a leak, generate a new token in the dashboard; the old one stops working immediately. Tell us if you suspect unauthorised access to the account.
3.4 Isolation. Each account only accesses its own clients, automations and events. Do not attempt to access other accounts' resources.
3.5 One account owner. Each account has an owner, identified by the registration email, who is our contact for everything concerning the contract.
4. Plan, limits and acceptable use
4.1 Single plan. There is one plan: €49 per month, per account, plus applicable taxes, renewing monthly. It includes up to 50 monitored automations, an unlimited number of end clients (organisational groupings), email and webhook alerts (Slack, Discord or Google Chat) with recovery notice, a dashboard and per-client status pages, and email support.
4.2 Automation limit. The limit of 50 is a hard limit: the 51st automation cannot be created. Paused automations count towards the limit; deleting one frees the slot immediately and invalidates its token. The dashboard always shows how many automations you have ("37 of 50"), warns from 40 onwards and sends an email when you reach 45 and 50. If you need more than 50, write to us.
4.3 Frequency, ping quota and retention. The minimum supported interval between pings of the same automation, the monthly ping quota per account (agency) and the history retention period are stated in the pricing section of the website (rootwatch.terraroot.pt/#preco) and in the documentation in force on the subscription date, and form part of these Terms. The quota counts the pings of all automations in the account. If the account exceeds the quota, pings beyond the limit are still accepted but may be summarised; we warn you in the dashboard.
4.4 Acceptable use. You may not: (a) use the service for unlawful activity or to monitor systems on which people's safety depends; (b) attempt to access third parties' accounts or resources; (c) deliberately overload the service, test its security without written authorisation, or circumvent limits; (d) send personal data, credentials or business content in pings (the input schema is restricted and unknown fields are rejected); (e) resell the service as your own without a written agreement with us. You may, of course, use rootwatch to provide services to your own clients.
5. Your obligations
5.1 Non-blocking integration. Configure the call to rootwatch so that a failure on our side never blocks, retries or alters your automation's work: use short timeouts and do not make business actions depend on rootwatch's response. A failed ping request is a monitoring failure, not a reason to re-run payments, messages or other operations.
5.2 Data you enter. The names of your end clients, the names of automations, and the email addresses and URLs used as alert destinations are chosen by you. You are responsible for having a lawful basis to entrust those data to us and for informing the individuals concerned, where they are natural persons. We process those data on your behalf under Annex I (Data Processing Agreement).
5.3 Your clients and users. You are responsible for what your end clients and staff do with the access you give them (for example, links to shared status pages) and for their compliance with these Terms.
5.4 Accurate information. Keep your contact email, your billing details and the details given in your declaration of professional status (clause 8.1) up to date. Notices sent to the account email are deemed received on the business day after sending, unless proven otherwise.
6. Price, billing and payment
6.1 Price. €49 per month, per account, excluding taxes. VAT or equivalent tax is added, if applicable; applicable taxes (or the reverse-charge mention, where you provide a valid VAT number and the law so provides) are calculated and shown at checkout before you confirm the purchase. We do not personalise prices on the basis of automated decisions. The price may be shown in your local currency, at the exchange rate stated at checkout by Sold through Link, LLC.
6.2 Who charges you. Payment is made by card or another method available at checkout to Sold through Link, LLC, acting as merchant of record for the transaction. Your statement shows LINK.COM* rootwatch. Receipts and invoices for the purchase are issued and sent by Sold through Link, LLC (Link). Sold through Link, LLC charges the monthly renewals until you cancel.
6.3 Automatic renewal. The subscription renews automatically every month, on the same date, at the price in force, until cancelled. You receive an email notice at least 30 days before any price change; if you do not accept it, you may cancel before it takes effect.
6.4 Failed payment. If a renewal charge fails: (a) Sold through Link, LLC retries several times over 14 days; (b) during those 14 days the service works in full and we notify you by email and in the dashboard, stating the exact date on which monitoring will be suspended; (c) after 14 days without payment, monitoring is suspended: the dashboard becomes read-only, the detector stops evaluating deadlines and sending alerts, pings continue to be received and stored, and each automation's state shows "monitoring inactive since [date]"; (d) paying the open invoice reactivates the service from the next deadline onwards, with no retroactive alerts; (e) 30 days after suspension (day 44 after the failure), the subscription is cancelled and clause 10 applies.
6.5 Sold through Link terms. When you purchase, you also accept Stripe's Sold through Link terms, available at link.com/terms, which govern the payment transaction, refunds processed by Link and payment support. In case of conflict concerning the payment transaction, those terms prevail; in everything concerning the service, these Terms prevail.
7. Term and cancellation
7.1 Term. The contract lasts one month and renews monthly (clause 6.3).
7.2 Cancelling. You may cancel at any time, without a call and without giving a reason, in the dashboard ("Account → Subscription → Cancel"), in the subscription management portal or in your Link account. Cancelling ends the renewal; monitoring continues until the end of the period already paid, with the end date visible in the dashboard. There is no refund for the current period, except as provided in 7.3, 10.3 and 17.3.
7.3 Refunds processed by Link. Regardless of the above, Sold through Link, LLC may process refunds in the cases set out in its policy (for example, a service not provided or substantially different from its description) within 60 days of each charge. Where that policy is more favourable to you than these Terms, it prevails.
8. Customer's professional status
8.1 Declaration. When creating the account, you declare that you are taking out rootwatch for your trade, business, craft or profession, and not as a consumer, and you provide the name of your company or business, your country and your tax identification number or VAT number. If you also use the service for personal purposes, you declare that the professional purpose is the predominant one. You confirm that declaration when subscribing, in the dashboard, before payment.
8.2 Basis of these terms. We conclude the contract, set the price and define these terms on the basis of that declaration. For that reason, these Terms do not include the rights that the law reserves exclusively for consumers.
8.3 Accuracy and verification. You are responsible for the truth and accuracy of the declaration and of the details provided. We may ask you, proportionately, for evidence confirming them. If the declaration proves to be false or inaccurate, or if you do not confirm it when we ask you to, we may terminate the contract under clause 10.2, and you are liable for the damage that the false or inaccurate declaration causes us, under the general rules of law. This clause does not set aside any mandatory legal rules that apply.
9. Changes to the service and to these Terms
9.1 To the service. We may change the service for valid reasons: security, legal compliance, technical evolution, changes in the suppliers we depend on, or improvement of functionality. Changes that materially reduce what the service does are communicated by email at least 30 days in advance. If you do not accept them, you may cancel free of charge.
9.2 To these Terms. We may change these Terms for the same reasons. We notify you by email at least 30 days in advance, stating what changes. The new version applies from the date stated in the notice; if you disagree, you may cancel before that date free of charge. Changes required by law or correcting clerical errors may take effect immediately.
10. Termination, data and export
10.1 By you. You may cancel the subscription (7.2) and, separately, delete the account in the dashboard.
10.2 By us. We may suspend or terminate the account if you breach these Terms seriously or repeatedly (in particular 4.4), if your declaration of professional status is false or inaccurate or is not confirmed when we ask (8.3), if the law requires it, or for non-payment. In the first three cases, except in security emergencies or where required by law, we notify you by email at least 15 days in advance and give you the opportunity to remedy the situation. For non-payment, suspension and cancellation follow the time limits and notices in clause 6.4.
10.3 Discontinuation of the service. If we decide to stop providing rootwatch, we give at least 60 days' notice, charge no renewals from the notice onwards, and refund the proportionate part of any period already paid that will not be provided.
10.4 Export and deletion. Before and after termination you may request an export of your data (clients, automations, history of events, run windows, incidents and monthly figures) by email to geral@terraroot.pt (the request only needs to identify the account), and we deliver it in full, through a single-use download link, valid for 7 days, sent to the account email (the file is never sent as an attachment, and is deleted from our servers after the download or when the link expires), with no limit on quantity, in a structured, commonly used, machine-readable format: a ZIP file with JSON and NDJSON, described at rootwatch.terraroot.pt/export-format. After the subscription ends we keep the account in read-only mode for 12 months, to allow reactivation and export; we then delete the data, with notice by email at least 30 days in advance. If you delete the account, we delete the data within 30 days. We keep only what the law requires us to keep (for example, accounting records, for 10 years), evidence of your acceptance of these Terms and of the consents given, for 5 years after the contract ends, and backups, which expire on 30-day cycles.
10.5 Switching to another provider. rootwatch is a data processing service within the meaning of Regulation (EU) 2023/2854 (the Data Act), Articles 23 to 31 of which apply to this contract:
(a) Request. You may at any time tell us by email to geral@terraroot.pt that you wish to switch to another provider or to your own on-premises ICT infrastructure, or to erase your exportable data. There is no notice period: the process starts on the day we receive the request.
(b) Transition period. From the request, a transition period of up to 30 consecutive days runs, during which the contract remains in force on its normal terms and the service continues at the normal price. The subscription is cancelled at the end of the transition and does not renew again: if the paid period ends earlier, it renews once, at the normal price, and the service continues until the end of that new period. During that period we give reasonable assistance to you and to third parties you authorise, keep providing the service with due care, inform you of known risks to its continuity and maintain the security of the data. You may extend the transition period once, for the period you consider appropriate. If 30 days is technically unfeasible, we tell you within 14 working days of the request, with the justification and an alternative period of no more than seven months, during which the service continues.
(c) Exportable data. The data you entered or that use of the service generated in your account: account and professional declaration data, clients, automations and their schedules, events, run windows and the result of each, incidents, monthly figures, the log of alerts sent, share links and the log of administrative actions, in the format described at rootwatch.terraroot.pt/export-format. For security reasons, the password, the ingestion and share tokens (stored only as hashes) and the webhook addresses, which are credentials the Customer already holds, are excluded.
(d) Retrieval and end. After the transition period, the data remain available for export for at least 30 days; in practice, for the period in clause 10.4. The contract ends when the switch is complete or, if you asked for erasure, when erasure is done, and we notify you by email. Exportable data are fully erased at the end of the retrieval period, under clause 10.4, or earlier if you ask.
(e) No switching charges. We charge nothing for switching, and exporting your data is never charged for. During the transition period only the normal service price is due.
11. Intellectual property
The software, brand, name, documentation and design of rootwatch belong to us or our licensors. We grant you a non-exclusive, non-transferable licence to use the service for the duration of the contract, under these Terms; the licence ends with the contract. The data you enter and the events generated by your automations are yours; you grant us only the rights needed to provide the service. Suggestions you send us may be used freely, without obligation to compensate.
12. Availability, support and absence of a guaranteed service level
12.1 No SLA. rootwatch is provided without a minimum availability commitment and without service credits. We do what is reasonable to keep it available and, where possible, give notice of planned maintenance.
12.2 rootwatch unavailability. When rootwatch is unavailable or its detector is not up to date, it cannot detect missing confirmations or send alerts; during those periods the dashboard shows the state as "stale" or "unavailable". We do not guarantee detection or delivery of alerts during those periods. We recommend that you keep your own safeguards for critical automations.
12.3 Alert delivery. Alerts are sent by email and by webhook (Slack, Discord or Google Chat) through third parties; we do not control their final delivery (spam filters, outages of those platforms, wrong addresses). Verify your destinations with the test alert available in the dashboard.
12.4 Support. Support is provided by email (geral@terraroot.pt), on Portuguese business days, with a first reply within 2 business days. Questions about payments, receipts and invoices may also be handled with Link (support.link.com). Do not send us personal data about your end clients by email: support does not need it, and instructions about that data are given in the dashboard (Annex I.8). Alerts are sent from an address that does not receive replies.
12.5 Separate confirmation. Clauses 12.1 and 12.2 describe characteristics that differ from what you might expect from a monitoring service. They are presented to you in the dashboard, at the "Subscribe" step, before you are redirected to checkout, and we ask you to confirm them at that point, separately and expressly. Without that confirmation the subscription cannot be completed.
13. Liability
13.1 General rule. We are liable, without limit, for damage we cause intentionally or through gross negligence, and for personal injury. Nothing in this clause excludes liability that the law does not allow to be excluded.
13.2 Cap. Except for intent or gross negligence, our total contractual liability to you, for all damage arising from non-performance, delay or defective performance of this contract, is limited to the amount paid for your rootwatch subscription (including what you paid to Sold through Link, LLC) in the 12 months preceding the event giving rise to it. In the same cases, we are not liable for loss of profit, loss of business, reputational damage or other indirect damage, including damage resulting from an automation whose failure was not detected or alerted. This cap does not apply to non-contractual liability, nor to the cases in clause 13.1.
13.3 Third parties. We are not liable for the acts or omissions of the platforms on which your automations run, of the alert recipients' email services or of messaging platforms (Slack, Discord, Google Chat), or of Sold through Link, LLC in the payment transaction, except to the extent the law attributes that liability to us. We are liable for our sub-processors (the list referred to in clause 14) as for our own acts, under the general rules of law, subject to the cap in clause 13.2, which does not apply in case of intent or gross negligence.
14. Personal data
We process personal data in accordance with the Privacy Policy, which forms part of these Terms. For the data you enter on behalf of your end clients, we act as processor and the Data Processing Agreement in Annex I applies. The current list of sub-processors is published at rootwatch.terraroot.pt/subprocessors; we give 30 days' notice by email before changing it, and you may object by cancelling the service.
15. Complaints and complaints book
15.1 Complaints. Write to geral@terraroot.pt or to the address in clause 1.1. We reply within 15 business days at most.
15.2 Electronic complaints book (Portugal). You may file a complaint through the official Portuguese platform at www.livroreclamacoes.pt. The competent supervisory authority is ASAE — Autoridade de Segurança Alimentar e Económica (www.asae.gov.pt).
16. Governing law, jurisdiction and language
16.1 These Terms are governed by Portuguese law. For disputes arising out of or in connection with this contract: (a) if the Customer is established outside Portugal, the courts of the judicial district of Santarém, Portugal, have exclusive jurisdiction; (b) if the Customer is established in Portugal, the court of the judicial district of Santarém has jurisdiction in the matters in which procedural law allows the parties to agree on the venue and, in all other matters, the court determined by law. In any case, mandatory rules providing otherwise are reserved.
16.2 These Terms exist in Portuguese and in English. For customers resident in Portugal the Portuguese version prevails; for all others, the English version prevails.
17. Final provisions
17.1 These Terms, the Privacy Policy, Annex I and the published price and limit conditions constitute the entire agreement between us concerning the service. 17.2 If any clause is held invalid, the others remain in force, and the default rules of law apply to the affected part. 17.3 We do not assign our position under this contract without your agreement. If the rootwatch business is transferred to another company, we will ask for that agreement by email at least 30 days in advance, identifying the acquirer. If you do not give it by the transfer date, the contract ends on that date, free of charge to you and with a refund of the proportionate part of any period already paid and not provided. 17.4 We do not waive any right by not exercising it immediately. 17.5 Notices to you: to the account email. Notices to us: geral@terraroot.pt.
Annex I — Data Processing Agreement (Article 28 GDPR)
I.1 Parties and subject matter. This Annex applies whenever we process, on your behalf, personal data that you enter into rootwatch or that your automations send us ("Customer Data"): names and identifiers of your end clients, automation names, email addresses and URLs used as alert destinations, and run metadata (identifiers, states, timestamps). For those processing operations, you are the controller and we are the processor. The data of your own account (email, password, billing, security logs) are processed by us as controller, as described in the Privacy Policy.
I.2 Nature, purpose and duration. Storage, organisation, retrieval and transmission of Customer Data for the sole purpose of providing the service described in the Terms (recording events, detecting missing confirmations, sending alerts, displaying the dashboard and status pages), for the duration of the contract and until deletion under clause 10.4. Categories of data subjects: your end clients and staff, and the alert recipients you designate. We do not process special categories of data; you have undertaken not to enter them (clause 4.4-d).
I.3 Instructions. We process Customer Data only on your documented instructions, which are: these Terms, the configuration you make in the dashboard, the export request in clause 10.4, and the transfer authorisation in I.7. If an instruction appears to us to infringe data protection law, we inform you immediately. We process the data for our own purposes only to the extent required by law, informing you unless the law prohibits it.
I.4 Confidentiality. The persons we authorise to process Customer Data are bound by a duty of confidentiality and access only what is strictly necessary.
I.5 Security. We apply the technical and organisational measures required by Article 32 GDPR, appropriate to the risk, including: encrypted communications in transit; ingestion tokens stored only as hashes; logical isolation between accounts, with every query filtered by the authenticated account; a restricted input schema that rejects unknown fields; no logging of full request bodies; access control and logging of administrative operations; encrypted backups with 30-day rotation; regular security updates.
I.6 Sub-processors. You give us general authorisation to use the sub-processors published at rootwatch.terraroot.pt/subprocessors. As at this version they are: Hetzner Online GmbH (hosting of the API, database and backups), Scaleway SAS (email delivery) and Vercel Inc. (hosting of the website and dashboard). We impose on them, by written contract, the same data protection obligations as those in this Annex, in particular sufficient guarantees of appropriate technical and organisational measures, and we remain fully liable to you for their performance. We notify you by email 30 days before adding or replacing a sub-processor; if you object on reasonable data protection grounds and we cannot find a reasonable alternative, you may terminate the contract free of charge.
I.7 International transfers. We transfer Customer Data outside the European Economic Area only with a valid basis: an adequacy decision (including the EU-US Data Privacy Framework for certified entities) or the European Commission's standard contractual clauses, with any supplementary measures that are warranted. The basis applicable to each sub-processor is stated in the list referred to in I.6.
I.8 Assistance. Taking into account the nature of the processing, we assist you as far as possible in responding to data subject requests (the dashboard lets you view, correct and delete Customer Data; export is requested by email, in a request that only identifies the account, and the file is delivered through a download link, under clause 10.4) and in meeting the obligations in Articles 32 to 36 GDPR: security, notification and communication of breaches, impact assessments and prior consultation. If a data subject contacts us directly about Customer Data, we tell them to contact you and we let you know there was a request, without replying on the merits, without forwarding the content and without keeping the message, unless the law requires us to. Your instructions about Customer Data are given through the dashboard (creating, changing, pausing and deleting clients and automations, alert destinations, shares, account deletion). Support email is not for giving instructions about your end clients' data or for sending us that data; if we receive it anyway, we delete it without using it.
I.9 Personal data breaches. We notify you without undue delay, and at the latest 48 hours after becoming aware, of any personal data breach affecting Customer Data, with the available information on the nature of the breach, the data and data subjects affected, the likely consequences and the measures taken.
I.10 Deletion and return. At the end of the provision of the service, at your choice we return Customer Data to you (by export) or delete it, including copies, unless a legal obligation requires retention. You may choose at any time: request an export by email, or delete the account in the dashboard, which deletes the data immediately (backups expire in the next cycle, within 30 days). If you do not choose, the instruction is that of clause 10.4: the account is kept read-only for 12 months after the subscription ends, for reactivation and export, and deleted at the end of that period.
I.11 Audit. We make available the information necessary to demonstrate compliance with this Annex and with Article 28 GDPR and, at most once a year, after a data breach or when a supervisory authority requires it, we allow for and contribute to audits, including inspections, by you or an independent auditor mandated by you, with 30 days' notice, during business hours, without affecting other customers' security, at your expense unless the audit reveals a material breach.
I.12 Liability. Between the parties, liability arising from this Annex follows clause 13. This does not limit the rights of data subjects against either party under Article 82 GDPR.
I.13 Precedence. In case of conflict between this Annex and the rest of the Terms, this Annex prevails with respect to the processing of personal data.