Skip to content
KeepAlive
PricingSign inStart free
Menu
PricingSign inStart free

Data processing agreement

Last updated: 15 November 2026

This agreement is the GDPR Article 28 contract between the customer (“Controller”) and Raja Vemula, trading as RaDe Digital (“Processor”) for personal data the Controller sends to KeepAlive. It forms part of the terms of service when the Controller creates an account. A countersigned copy is available on request from support@radedigital.ie. It is not a substitute for advice from the Controller’s own lawyer.

1. Parties and roles

The Processor is Raja Vemula, trading as RaDe Digital, 7 Tandy's Rise, Tandy's Lane, Adamstown, Lucan, Co. Dublin, K78 E6P6, Ireland, support@radedigital.ie. RaDe Digital is a trading name. The Controller is the customer named on the KeepAlive account. For account data about the Controller’s own login, the Processor is an independent controller, as described in the privacy policy. This agreement covers personal data the Controller’s systems include in pings, check names and alert destinations.

2. Subject matter, duration, nature and purpose

  • Subject matter. Receiving HTTP pings, storing run history, deciding whether a job is late or down, and sending alerts to destinations the Controller configures.
  • Duration. For as long as the Controller has an account, and afterwards until deletion under section 10.
  • Nature and purpose. Hosting the monitoring configuration and the run history, and delivering alerts, only so the Controller can use KeepAlive.

3. Personal data and data subjects

  • IP addresses and user-agent strings of systems that send pings.
  • Any personal data in ping bodies. Only the first 10 kB of a POST body is stored.
  • Alert destinations: e-mail addresses, phone numbers and webhook URLs the Controller enters.
  • Names of checks, projects and tags, where they contain personal data.
  • E-mail addresses of team members the Controller adds.

Data subjects are the Controller’s staff and contractors, and anyone whose data the Controller’s jobs include in a ping. The Controller will not send special-category data (GDPR Article 9).

4. Instructions

The Processor processes this personal data only on the Controller’s documented instructions: these terms, this agreement, and the Controller’s use of the product (creating checks, choosing schedules, choosing alert channels, exporting or deleting data). If a law requires processing beyond those instructions, the Processor will tell the Controller first, unless the law forbids it.

5. Confidentiality and security

People authorised to process the data are bound by confidentiality. The Processor applies the measures in section 12, appropriate to the risk, as required by Article 32.

6. Sub-processors

The Controller gives general authorisation for the sub-processors listed at /privacy/subprocessors. The Processor will announce an addition or replacement at least 30 days in advance by updating that page and, for customers who have asked for e-mail notice, by e-mail. The Controller may object on reasonable data-protection grounds. If the objection cannot be resolved, the Controller may stop using the affected part of the service and delete the account. The Processor imposes terms on each sub-processor that are no less protective than this agreement and remains liable for their performance.

7. International transfers

The application and queue run in the EEA (UpCloud, Frankfurt). The database is hosted in an EU region. Where a sub-processor is established outside the EEA, or may access the data from outside it, the transfer is covered by that provider’s data processing addendum and the EU Standard Contractual Clauses (Commission Decision 2021/914). The provider, the region and the transfer tool are named on the sub-processors page. Alert destinations the Controller chooses may be outside the EEA; those services act for the Controller.

8. Assistance and data subject rights

The product lets the Controller export and delete its data. The Processor will forward any request it receives from a data subject to the Controller without undue delay and will not answer it, unless the law requires an answer. The Processor will assist with Articles 32 to 36, taking into account the nature of the processing and the information available to it.

9. Personal data breaches

The Processor will notify the Controller without undue delay after becoming aware of a personal data breach affecting the Controller’s data, and will include the information the Controller needs to meet its own duties. A fixed number of hours is not promised here. The Controller can ask for one in a countersigned copy.

10. Deletion and return

When the Controller deletes the account, or this agreement ends, the Processor deletes the personal data from live systems immediately. The Controller can export a copy first. Database backups are kept by our database host and then overwritten. The exact number of days is not published here yet. Email us and we will tell you. The Processor may keep what Union or Irish law requires it to keep, including invoices held by the payment provider.

11. Audits

The Processor will, on request and no more than once a year unless a supervisory authority requires more, provide a written description of the security measures and answer a reasonable security questionnaire. An on-site audit is available where a supervisory authority requires one, with reasonable notice, during business hours, and at the Controller’s cost unless the audit finds a material breach of this agreement.

12. Technical and organisational measures

  • TLS for public endpoints and for database and queue connections.
  • Alert destinations encrypted with AES-256-GCM. The key is not stored in the database.
  • The application database role cannot change the schema or rewrite the audit log.
  • Ping bodies capped at the first 10 kB. IP addresses shortened after 30 days. History deleted on the plan’s retention.
  • Application logs do not contain alert destinations or ping bodies.
  • Production access is limited to the operator. Queries for customer data are scoped by project membership. Ping ids are 128-bit random values.
  • Webhook deliveries are restricted to public HTTPS addresses.

13. Liability and governing law

Liability is governed by the terms of service, and nothing there limits liability that cannot be limited under Irish or EU law, including liability under Article 82 GDPR as it applies to a processor. This agreement is governed by the laws of Ireland. If this agreement and the terms conflict on a data-protection point, this agreement prevails.

© 2026 KeepAlive, powered by RaDe Digital. All Rights Reserved.

PrivacyTermsDPACookiesSub-processorsContact