Adal Cloud Adal Cloud
Product
Incoming webhooks Outgoing HTTP requests
Documentation Guides Pricing
Open dashboard ↗
Webhooks and outgoing HTTP requests Navigation
Incoming webhooks → Outgoing HTTP requests → Documentation → Guides → Pricing →
Open dashboard ↗
Privacy and data

Adal Cloud Privacy Policy

How Adal Cloud processes account data, HTTP requests and responses, traffic purchases, retention and deletion.

Last updated on November 4, 2026

Introduction

Adal Cloud provides incoming webhook delivery and asynchronous outgoing HTTP requests through an API. This Privacy Policy explains how Adal processes personal data when you use the website, dashboard, API, webhook Servers, Adal CLI and related services (the “Service”).

The Policy covers data you provide, data received from webhook senders, outgoing requests you submit, responses returned by your designated recipients, and technical and payment records generated by use of the Service.

HTTP request and response content, URLs, headers, query parameters and credentials may contain personal or sensitive data. You are responsible for having the rights, permissions and legal basis necessary to submit that data and instruct its delivery. By using Adal, you acknowledge the processing described here.

Definitions

  • “Adal Cloud”, “Adal”, “we”, “us” or “our” means “ADAL CLOUD” LLP, registered in the Republic of Kazakhstan, the provider and operator of the Service.

  • “User”, “you” or “your” means a person or organization using the Service.

  • “Account Data” means your email, authentication data, settings and related administrative information.

  • “Service Configuration Data” means Servers, Channels, Endpoints, recipient URLs, tokens, delivery and response-saving options, Region selections and other configuration.

  • “HTTP Content” means incoming webhook content, outgoing HTTP request content and any stored response content, including methods, URLs, paths, query parameters, headers and bodies.

  • “Request Metadata” means identifiers, ownership and Region references, timestamps, sizes, processing states, delivery outcomes and related technical records. Source IP information may be processed for incoming requests where applicable.

  • “Delivery Data” means attempt records, outcomes, timing and execution diagnostics associated with incoming or outgoing requests.

  • “Destination” means a recipient designated through a Channel/Endpoint or an outgoing request URL, including a local application reached through CLI.

  • “Traffic Package” means a one-time purchase of traffic volume, not a subscription or a permanent account tier.

  • “Region” means the location selected for processing a Server's incoming requests or an outgoing submission.

  • “Personal Data” means information relating to an identified or identifiable natural person.

  • “Processing” includes collection, receipt, storage, access, transmission, execution, deletion and protection of data.

Who We Are

Adal is operated by “ADAL CLOUD” LLP, a limited liability partnership registered in the Republic of Kazakhstan.

For purposes of applicable data protection laws, “ADAL CLOUD” LLP is the provider and operator of the Service and may act as a data controller when processing Account Data, billing information, security data, communications, and information relating to use of the Service.

When processing HTTP Content and delivering incoming or outgoing requests on your instructions, “ADAL CLOUD” LLP generally acts as a data processor or service provider. You determine the content, recipients, response-saving choice and purposes of that processing.

If you have questions about this Privacy Policy or how personal data is processed, contact us at [email protected].

Scope of This Policy

This Policy applies to the Adal website, dashboard, API, webhook Servers, CLI and related services that reference it. It covers incoming webhooks, independent outgoing HTTP submissions, optional saved responses and associated operational data.

Third-party senders and recipients have their own privacy practices. You select the recipient of a delivery and may instruct delivery outside your selected Region. Adal does not control data once it reaches your application, local computer or another designated service. Likewise, regional expiry does not remove copies in those environments.

If you use Adal on behalf of an organization, customer or another person, you are responsible for having authority and a lawful basis for those instructions.

Data We Collect

Account Data

We process your email address, authentication and session information, account settings, interface preferences and administrative records. Passwords are stored as hashes rather than readable passwords. API-token and CLI Channel secrets are shown when issued and stored as hashes for verification.

If you sign in with Google or GitHub or connect one of those accounts, we process the provider name, your account identifier with that provider and the verified email address used for the connection. We use this information to identify you, create or link your Adal account and manage the connection. Provider tokens used to complete sign-in are not retained for ongoing access to your Google or GitHub account.

Service Configuration Data

Configuration can include Server settings, Channels and Endpoints, recipient URLs and credentials, selected Regions, delivery options and whether outgoing response bodies are saved. Treat the complete recipient URL, headers and other configuration as sensitive, even if a field is not labelled as a secret.

HTTP Request and Response Content

Incoming HTTP Content is supplied by the sender and your integration. Outgoing HTTP Content is supplied through the API on your instructions. It can include methods, URLs, paths, query parameters, headers and request bodies, including files or personal data contained in them.

Adal processes HTTP responses to determine execution outcomes. Outgoing response-body storage is disabled by default. If enabled for a submission, saved response bodies can include content from successful, unsuccessful or incomplete attempts. Status codes, timing and technical diagnostics may still be recorded when response bodies are not saved. Enabling the option later does not recover a response body that was not saved.

Request Metadata and Delivery Data

We process identifiers, owner and Region references, Server or recipient references where applicable, timestamps, request sizes, states, attempt outcomes, response status codes, errors, durations and usage counters. We also process outgoing idempotency keys to recognize repeated submissions.

These records support your request history, delivery diagnostics, traffic accounting and secure access. Detailed HTTP diagnostics can contain URLs, headers and other sensitive information even when response bodies are not saved. Their retention differs from the minimal history and accounting records described below.

Technical and Security Data

We process IP addresses, browser and device information, session and authentication events, connection information, errors and security records needed to operate and protect the Service. Operational logs are designed to exclude HTTP bodies, headers and recipient credentials. Content and diagnostics available in your account are retained service data.

The public website also collects visit statistics, including the time of a visit, page path, language, browser, operating system and device type. We use visit statistics to understand website use and improve the Service.

Billing and Payment Data

For one-time Traffic Package purchases we process the package code, purchased volume, price, currency, tax treatment, purchase and payment identifiers, payment status, usage and balance records, checkout information, and refund or dispute records where applicable. Free grants and renewal dates also form part of traffic accounting. There is no subscription renewal or subscription-status lifecycle for these purchases.

Payment details are processed by the payment provider, currently Dodo Payments. Adal does not intentionally store full payment card numbers. Payment providers process the payment information required under their own terms and privacy notices.

Communications Data

If you contact us or receive service-related messages, we process your email address, message content, support requests, feedback and related delivery records. Account emails are sent through Postmark, which processes the recipient address and email content to deliver the message. Open and link-click tracking is disabled for these account emails. Do not include unnecessary HTTP Content, API secrets or recipient credentials in support communications.

Local CLI Data

Adal CLI saves delivery data on the computer where it runs so it can resume interrupted work. This can include request bodies, recipient URLs and credentials, and delivery progress. CLI output can contain recipient paths and query strings. You control access, backups and deletion of those local files and logs; service retention does not automatically delete them.

How We Use Data

Providing the Service

We use Account Data, configuration, HTTP Content and technical records to authenticate users, receive incoming webhooks, execute outgoing HTTP jobs, deliver requests to designated recipients, display retained content and history, process retries, and recover execution state.

For outgoing requests, the API's acceptance response confirms a job, not a completed recipient operation. Request and attempt records allow you to follow the later outcome. An API token authorizes submissions and reads; it is separate from a browser session or a recipient's credentials.

Request Inspection, Delivery, and Debugging

We display available content and diagnostics to authorized users through the dashboard and API. This can include HTTP headers, bodies, optional saved outgoing responses, attempt timestamps, outcomes and error categories. HTTP Content remains service data and is not treated as ordinary observability output.

Reliability, Abuse Prevention, and Security

We process technical records to maintain availability, diagnose failures, prevent abuse and unauthorized access, enforce traffic and technical limits, and protect users and third parties. Service-side logs, traces, metrics and alerts are designed to avoid recording customer payloads or sensitive recipient configuration.

Traffic Purchases and Accounting

We record one-time purchases, Free grants and renewals, incoming and outgoing usage, refunds, payment status and the resulting balance. Free bytes are spent first; paid bytes add together without time-based expiry. We process payment and tax information with the payment provider and send purchase-related notices. Traffic overage can reduce the paid balance below zero but does not itself cause an automatic monetary charge.

For independent outgoing requests, the decoded request body counts once when the first attempt starts. If response-body saving is enabled, the saved response bytes from each attempt count additionally. These accounting records may need to remain after the associated HTTP Content has expired.

Support and Communications

We use relevant account, technical and communications data to answer your requests and send account, billing, security and policy notices. Share only information needed for your request and avoid sending HTTP bodies or credentials in support messages. For information about protecting your account and request data, see the Security page.

Service Improvement

We use appropriate aggregated, statistical or diagnostic information to improve reliability and usability. HTTP Content and recipient credentials are not used for advertising, profiling, data enrichment or AI-model training. Processing by infrastructure providers is limited to operating the Service on our behalf.

Legal Compliance and Enforcement

We retain and process necessary records to meet applicable legal, tax and accounting obligations, resolve disputes, investigate abuse, protect rights and enforce agreements. This does not make ordinary operational logs a repository for customer request or response bodies.

Legal Bases for Processing

Where the GDPR or similar data protection laws apply, we process personal data only where we have a legal basis to do so.

Depending on the category of data and the purpose of processing, we rely on the following legal bases.

Performance of a Contract

We process personal data where necessary to provide the Service to you, manage your account, receive incoming webhooks, execute outgoing HTTP requests, deliver to designated Destinations, provide history and retries, provide API and CLI access, and enforce applicable usage and technical limits, and perform other actions you request.

This includes processing Account Data, Service Configuration Data, HTTP Content, Request Metadata, Delivery Data, Technical and Security Data, and Billing and Payment Data where necessary to provide the Service.

Legitimate Interests

We may process personal data where necessary for our legitimate interests, provided those interests are not overridden by your rights and interests.

Our legitimate interests include:

  • operating, maintaining, and improving the Service

  • monitoring reliability and performance

  • debugging errors and delivery failures

  • preventing abuse, spam, fraud, unauthorized access, and security incidents

  • protecting the Service, our infrastructure, our users, and third parties

  • enforcing technical limits and preventing misuse

  • maintaining diagnostic, security, and audit logs

  • communicating with you about important service-related matters

Legal Obligations

We may process and retain certain data where necessary to comply with legal, tax, accounting, regulatory, or compliance obligations.

This may include billing records, invoices, payment status information, security records, and records required to respond to lawful requests or protect our legal rights.

Consent

Where required by law, we may process personal data based on your consent.

This may apply, for example, to optional marketing communications, non-essential cookies, or other optional features that require consent.

You may withdraw your consent at any time where processing is based on consent. Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.

Processing HTTP Content on Your Behalf

When Adal processes HTTP Content on your behalf, you determine the content, recipient, response-saving choice and purposes of processing.

In those circumstances, Adal generally acts as a data processor or service provider. You must have an appropriate legal basis for submitting HTTP Content and instructing its delivery and storage.

Adal does not determine which personal data you or your senders include in requests, or which personal data your chosen recipients return in responses.

HTTP Content and User Responsibility

You and the systems you connect determine HTTP Content. Incoming senders, outgoing API callers and recipients may include personal data, confidential information and credentials in URLs, headers, bodies or responses.

You are responsible for having a lawful basis, providing required notices and obtaining necessary permissions; choosing authorized recipients and Regions; limiting unnecessary sensitive data; protecting tokens and URLs; deciding whether outgoing response bodies should be saved; and handling data subject requests for the content you control.

Adal processes that content as needed for the instructed delivery, storage, diagnostics and retries, and to secure and operate the Service. We do not sell HTTP Content, use it for advertising or train AI models on it.

Delivery to a recipient or CLI computer creates a copy outside regional storage. You are responsible for the privacy and retention practices of systems you control and for reviewing the practices of third parties you choose. Deleting a Server or letting regional content expire does not remove those copies.

Storage, Retention and Deletion

Data categories have different purposes and lifecycles. Buying a larger Traffic Package does not extend content retention or select a different storage mode. HTTP Content is retained under the scheduled regional lifecycle described below.

HTTP Content Retention

Incoming and outgoing requests receive a scheduled deletion date 90 days after acceptance. The schedule applies to regional HTTP Content and outgoing saved response bodies and detailed HTTP diagnostics. Retries, purchases and Free renewal do not extend it.

After expiry, HTTP Content is no longer available through the Service. Removal takes place in the background rather than at the exact expiry second. This does not extend the retention period or make expired content available again.

Request Metadata and Delivery Data

HTTP-content expiry does not automatically remove all journal entries. Minimal request identifiers, ownership and Region references, timestamps, statuses, attempt outcomes and accounting or recovery records can remain after the body is unavailable. Detailed HTTP diagnostics are distinct from these minimal records.

These records currently do not have one fixed automatic deletion schedule. We retain them as needed for history, service operation, usage accounting, security, dispute resolution and legal obligations. A visible status record does not mean the original payload or response is still stored or recoverable.

Server and Recipient Deletion

Before deleting a Server, remove its links from all Routers, including disabled Routers. Deletion stops new intake once the change takes effect. Accepted requests retain their existing scheduled deletion dates; Server deletion does not itself immediately erase their HTTP Content, metadata or history. The deleted ingest address remains reserved and is not assigned to another user.

Changes to Channels, Endpoints and credentials do not change deliveries already accepted with the previous settings or automatically cancel work in progress. Revoking an API token stops its further authorized use but does not erase or cancel jobs already accepted with it. A Server, recipient or token deletion is not an account-wide erasure request.

Local CLI and Recipient Copies

The CLI may keep local copies of request content and recipient settings to complete interrupted deliveries. A client can finish work already saved on your computer even after the content expires in Adal. Service retention cannot erase local files, logs, backups or content already delivered to an application or third party. You determine retention and deletion in the systems you control.

Account and Configuration Data

We retain Account Data and configuration while needed to provide and secure your account. You can request account deletion in Settings → Danger zone → Delete account, as described under Account Deletion and Data Export. You can also contact [email protected] for assistance, deletion or export requests. We verify such requests and process them within applicable legal time limits, considering their scope and necessary retention exceptions.

Billing and Legal Records

Purchase, payment, refund, invoice, tax and related records may remain after content expiry or account closure where required for accounting, legal obligations, fraud prevention, disputes or integrity of traffic accounting. These records currently do not have one fixed automatic deletion schedule. We retain them only as needed for the stated purposes and applicable legal requirements.

Support Communications

Support communications have a separate lifecycle and currently no fixed automatic deletion schedule. They are retained as needed to handle the request, preserve relevant correspondence and meet applicable obligations. Do not send unnecessary payloads, tokens or recipient credentials to support.

Logs and Security Records

Operational and security records are retained according to their diagnostic, security and legal purposes. This Policy does not promise one fixed retention period for all logs. Service-side operational logs are designed to exclude HTTP request and response bodies and sensitive recipient configuration. Local CLI output and user-controlled logging are separate.

Backups

Where backup or recovery copies exist, removing data from active systems does not necessarily erase every backup copy immediately. Such copies are protected and limited to recovery, security and necessary operational purposes, and expire or are removed under the applicable backup lifecycle. Backup frequency and expiry follow the applicable recovery arrangements; backup copies are not a user archive. Restoring a copy does not renew the original scheduled HTTP-content retention period.

User-Controlled Deletion

Use supported controls for configuration changes and Settings → Danger zone → Delete account for account deletion. Contact us for assistance or other data subject requests. The scope of a control is specific: removing a Server or token is not a command to purge all request history or cancel all accepted jobs. Necessary legal, billing and security records may remain under the exceptions described here.

Data Minimization

Limit sensitive data sent to Adal and its recipients, save outgoing response bodies only when needed, protect local journals and logs, and manage copies in your own systems. You cannot assume that a paid package, Free renewal or configuration deletion changes a request's content-retention schedule.

Regional Data Storage

Incoming HTTP Content is processed and stored in the Server's selected Region. Outgoing requests are executed and their HTTP Content is stored in the Region selected for the submission. Choosing a Region determines the location used for that storage and execution; it does not mean that every transfer or related processing step takes place only there.

Account, sign-in, billing, usage, support and security information, as well as request status and history, may be processed separately from HTTP Content and outside the selected Region.

Delivery sends HTTP Content to your chosen recipient, which may be outside the selected Region. CLI execution creates local copies on its computer, and dashboard or API reads transmit content to the requesting client. You are responsible for these choices and for any data-transfer obligations that apply to your integration.

We do not promise that all Account Data or every transient processing step remains inside one Region, nor do we control the recipient's infrastructure and onward processing.

Sharing with Third Parties

Adal does not sell personal data, Account Data, or HTTP Content to third parties.

We may share data with third parties only where necessary to provide, operate, secure, support, or improve the Service, comply with legal obligations, process payments, or protect our rights, users, infrastructure, and third parties.

Service Providers

We use service providers to operate the Service. They process the data needed for their role, including:

  • Dodo Payments for checkout and payment processing, including payment, billing and refund information.

  • Postmark for account emails, including recipient email addresses, message content and delivery status.

  • Google and GitHub, when you choose to sign in with or connect those accounts, for authentication and the associated account identity and email information.

  • Hosting, storage and network providers for the data stored or transmitted through the Service.

Providers process data for the purposes described here and under the terms applicable to their services. Signing in through Google or GitHub and using a payment provider also involves those providers' own privacy notices.

Payment Providers

If you purchase a Traffic Package, payment and billing data may be processed by our payment provider, currently Dodo Payments. Purchase, payment and refund references are retained for the purposes described above; these are not subscription records.

Adal does not intentionally store full payment card numbers. Payment card details and other sensitive payment information are processed by the payment provider under its own terms and privacy policy.

Destinations Configured by You

When you configure an incoming recipient or specify an outgoing request URL, Adal transmits the request to that Destination on your instructions. Responses are processed for execution and, when enabled for outgoing requests, response bodies are retained.

A Destination may be a third-party service, your own server, your application, your local environment, or another server you control. You are responsible for the Destination and for any processing of data that occurs after Adal delivers data to that Destination.

Adal does not control the privacy, security, infrastructure, or data-processing practices of Destinations you configure.

Third-Party Integrations

You may configure third-party systems to send webhooks to your Servers or instruct incoming and outgoing HTTP delivery to third-party recipients. Those recipients may return data that Adal processes as an HTTP response.

Your use of such third-party integrations is governed by the terms and privacy policies of those third parties. Adal is not responsible for how third-party integrations collect, use, transmit, store, or protect data before sending it to Adal or after receiving it from Adal.

Legal Requirements and Protection

We may disclose data where we believe disclosure is necessary to:

  • comply with applicable laws, regulations, legal process, or lawful requests

  • respond to court orders, subpoenas, or government requests

  • enforce our Terms of Service or other agreements

  • investigate, prevent, or address fraud, abuse, security incidents, or technical issues

  • protect the rights, property, safety, infrastructure, or security of Adal, our users, or third parties

Where legally permitted and reasonably practicable, we may notify affected users of legal requests for their data.

Business Transfers

If Adal is involved in a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar transaction, data may be transferred as part of that transaction.

In such cases, we will take reasonable steps to ensure that personal data remains protected and is processed in accordance with this Privacy Policy or a policy that affords materially similar protections.

Aggregated or De-Identified Data

We may share aggregated, anonymized, or de-identified information that does not identify you or any individual.

Such information may be used for analytics, reporting, product improvement, service statistics, or public communication about the Service.

International Data Transfers

Adal may process and store data in countries other than the country where you are located.

Depending on your location, Server or outgoing-request settings, selected Region, Service configuration, and the third-party service providers we use, your data may be transferred to, stored in, or processed in countries outside your country, the European Economic Area, the United Kingdom, or Switzerland.

HTTP Content is stored in the selected Region as described above. Delivery to your recipients, access from your devices, and account, billing and operational processing may cross regional or national boundaries.

This may include Account Data, authentication data, billing data, usage data, support communications, technical logs, monitoring data, email delivery data, payment-provider data, security records, and data processed by third-party service providers.

Where we transfer personal data internationally, we take steps designed to protect that data in accordance with applicable data protection laws. Those steps may include relying on:

  • adequacy decisions adopted by competent authorities

  • Standard Contractual Clauses or similar contractual safeguards

  • data processing agreements with service providers

  • technical and organizational security measures

  • transfer risk assessments, where required

  • other lawful transfer mechanisms available under applicable law

If you are located in the European Economic Area, the United Kingdom, or Switzerland, and your personal data is transferred to a country that has not been recognized as providing an adequate level of protection, we will use appropriate safeguards where required by applicable law.

International transfers may also occur when you configure a Destination outside your selected or assigned Region, when you use Adal CLI from another country or region, when you access the dashboard or API from another location, or when you instruct Adal to transmit data to a third-party service.

You are responsible for ensuring that your configuration of Servers, Destinations, CLI connections, Regions, and third-party integrations complies with the data-transfer requirements applicable to your use case.

Adal does not control the location, infrastructure, or data-processing practices of Destinations you configure.

Security

Adal implements reasonable technical and organizational measures designed to protect data against unauthorized access, loss, misuse, alteration, disclosure, or destruction.

Access to account settings, request content and history requires authentication and is restricted to the account that owns the data. Passwords are stored as hashes. API tokens and CLI Channel secrets authorize access on behalf of their owner and must be kept private.

The public website uses HTTPS, and CLI connections to the platform use WSS. Delivery to a recipient uses the URL you configure; use HTTPS for public recipients. Adal needs access to the original HTTP Content to execute the deliveries you request. Connection encryption does not prevent designated recipients or your CLI client from receiving that content.

Operational logs are designed to exclude customer HTTP bodies, headers and recipient credentials. Detailed request diagnostics available in your account are retained service data and can contain sensitive information. More information is available on the Security page.

Adal uses security measures appropriate to the nature of the Service and the data being processed. However, no method of transmission over the Internet, no method of electronic storage, and no online service can be guaranteed to be completely secure.

You are responsible for keeping your account credentials, API keys, Server URLs, CLI tokens, Destination credentials, and other access details secure. You should not share those credentials with unauthorized persons or expose them in public repositories, client-side code, logs, screenshots, or other public locations.

You are also responsible for configuring your Servers, response-saving options, Regions, Destinations, and access controls in a manner appropriate for your security and compliance requirements.

If you believe that your account, Server URL, API key, token, Destination, or any other access detail has been compromised, you should rotate or revoke the affected credentials where possible and contact us promptly.

Adal may suspend, restrict, or disable access to the Service, an account, Server, token, Destination, or other feature where we reasonably believe it is necessary to protect the Service, our users, infrastructure, third parties, or data.

Cookies

Adal uses cookies and browser storage to keep you signed in, protect account access and remember preferences.

Essential Cookies

Sign-in cookies maintain your browser session. Browser storage also supports sign-in, connections to Google or GitHub and keeping sign-in and sign-out state consistent across open tabs.

For password sign-in, the remember-me option controls whether sign-in is saved on your device. Google and GitHub sign-in is saved on the device. Closing a tab does not sign you out; sign out explicitly on shared devices.

Preference Cookies

The public website uses a language-preference cookie that lasts up to one year. The dashboard also uses browser storage for interface preferences such as appearance.

Analytics Cookies

The website collects the visit statistics described under Technical and Security Data without setting analytics cookies. These statistics are separate from cookies used for sign-in and preferences.

Advertising Cookies

Adal does not currently use advertising cookies or use HTTP Content for advertising.

Managing Cookies

You can block or delete cookies and browser storage through your browser settings. Blocking essential cookies can prevent browser sign-in and dashboard access. Clearing preference storage can reset your language or appearance choices. API-token authentication is separate from browser sign-in.

Your Rights

Depending on your location and applicable data protection laws, you may have certain rights in relation to your personal data.

These rights may include:

Right of Access

You may request confirmation of whether we process personal data about you and request access to that personal data.

Where applicable, you may also request information about the purposes of processing, categories of personal data processed, categories of recipients, retention periods, and other information required by applicable law.

Right to Rectification

You may request that we correct inaccurate or incomplete personal data about you.

You may also be able to update certain Account Data directly through the dashboard or account settings.

Right to Erasure

You may request that we delete personal data about you where applicable law gives you that right.

This right may be subject to limitations. For example, we may need to retain certain data for legal, tax, accounting, billing, security, fraud-prevention, dispute-resolution, backup, or compliance purposes.

Right to Restriction of Processing

You may request that we restrict the processing of your personal data in certain circumstances, for example while we verify the accuracy of the data or assess an objection to processing.

Right to Data Portability

Where applicable, you may request a copy of personal data that you provided to us in a structured, commonly used, and machine-readable format.

Where technically feasible and required by law, you may also request that we transmit such data to another controller.

Right to Object

You may object to certain processing of your personal data where we rely on legitimate interests as the legal basis for processing.

You may also object to processing for direct marketing purposes, if such processing is used.

Right to Withdraw Consent

Where we process personal data based on your consent, you may withdraw that consent at any time.

Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.

Right to Lodge a Complaint

If you believe that we process your personal data in violation of applicable data protection laws, you may have the right to lodge a complaint with a competent data protection authority.

We encourage you to contact us first so that we can attempt to resolve your concern.

Requests Related to HTTP Content

HTTP Content may contain personal data relating to your customers, users, employees, or other third parties.

Where Adal processes HTTP Content on behalf of a User, the User is generally responsible for handling data subject requests relating to that HTTP Content.

If we receive a request from an individual relating to HTTP Content controlled by one of our Users, we may direct that individual to the relevant User or assist the User in responding to the request, where required by applicable law and technically feasible.

How to Exercise Your Rights

You may exercise your rights by contacting us at: [email protected]

We may need to verify your identity before responding to your request. We may also ask for additional information if necessary to locate the relevant data or process your request.

We will respond to requests within the time required by applicable law.

In some cases, we may decline or limit a request where permitted by law — for example, if the request is manifestly unfounded or excessive, if we cannot verify your identity, if we are required to retain the data, or if fulfilling the request would adversely affect the rights and freedoms of others.

Account Deletion and Data Export

Account Deletion

Use Settings → Danger zone → Delete account to request deletion. First remove all Routers, Servers and Channels, including disabled resources, and revoke active API tokens. The interface checks these conditions and displays the scheduled UTC date before confirmation. You can also contact [email protected] for assistance or a separate deletion request; we verify identity and authority and handle its scope and required exceptions within applicable legal time limits.

Confirmation schedules deletion for the first midnight UTC at least 30 days later. All refresh sessions are revoked immediately and you are signed out; already issued access tokens remain valid until expiry. Successfully signing in with your password, Google or GitHub before cleanup begins cancels the request. A password reset or refresh of an existing session does not cancel it. Once cleanup begins, the account cannot be restored through this recovery flow.

Deletion removes account data, configuration and service-side HTTP Content. Resources created after confirmation are included without a further notice. The entire unused traffic balance, including paid traffic, is forfeited at deletion. Minimal anonymized status and usage records and the necessary records described below may remain. Copies already held on your computer or by recipients are outside service-side deletion.

The scheduled date starts cleanup; completion can be delayed by temporary processing unavailability. The completion email is sent after service-side cleanup. Account deletion is separate from deleting an individual Server, recipient or token.

Data That May Be Retained

Necessary purchase, payment, refund, tax, accounting, dispute, security and legal records may remain under the purposes and retention criteria described in this Policy. Where backup copies exist, their removal follows the applicable backup lifecycle. We do not retain data longer than necessary for those purposes and applicable legal requirements.

Server and Request Deletion

Deleting a Server stops future intake once the deletion reaches the receiving Region, but leaves previously accepted requests on their original content-retention schedule. Minimal status and accounting records may remain after that content expires. The ingest address is not reassigned to another user.

Changes to Servers, Channels, Endpoints or tokens do not automatically cancel accepted work or erase copies saved by your CLI. Contact us for erasure requests that go beyond the scope of an available configuration control.

Data Export

Where supported or required by law, you may request available Account Data, configuration, request metadata, delivery records, usage and purchase information, and retained HTTP Content. Expired content and response bodies that were never saved cannot be reconstructed through an export.

The available scope and format depend on the data involved, technical feasibility, security and applicable law. Exports may include sensitive information; secure any copies you receive.

HTTP Content Controlled by Users

You are responsible for data subject requests relating to HTTP Content you control. Adal may assist as required by law and technically feasible. We do not control copies held by your senders, recipients, CLI devices or third-party systems.

Requesting Deletion or Export

Contact [email protected] with enough information to locate the relevant account or request, without sending unnecessary payloads or credentials. We may verify identity and authority and ask for clarification before disclosure, deletion or export. Requests are processed within the time required by applicable law.

Children’s Privacy

Adal is not intended for use by children.

You must be at least 18 years of age, or the age of legal majority in your jurisdiction, to create an Adal account and use the Service.

We do not knowingly collect personal data directly from children. If we become aware that we have collected personal data directly from a child without appropriate authorization, we will take reasonable steps to delete that data.

Because Adal processes webhook requests on behalf of Users, HTTP Content may contain personal data submitted by third-party systems, applications, or services. Users are responsible for ensuring that any HTTP Content sent to Adal complies with applicable laws relating to children’s data and privacy.

If you believe that a child has provided personal data to Adal directly, or that HTTP Content processed through Adal contains children’s personal data in violation of applicable law, please contact us at: [email protected]

Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in the Service, legal requirements, technical infrastructure, data-processing practices, or other operational reasons.

When we update this Privacy Policy, we will revise the “Last updated” date at the top of the Policy.

If we make material changes that significantly affect your privacy rights or how we process personal data, we will take reasonable steps to notify you. Notice may be provided through the Service, a dashboard notification, email, or another appropriate method.

Unless otherwise stated, changes to this Privacy Policy become effective when posted.

Your continued use of the Service after the updated Privacy Policy becomes effective constitutes acknowledgment of the updated Policy.

If you do not agree with the updated Privacy Policy, you should stop using the Service and may request deletion of your account as described in this Policy.

Contact

If you have questions about this Privacy Policy, how Adal processes personal data, or how to exercise your privacy rights, contact us at: [email protected]

You may also contact us to request access, correction, deletion, restriction, export, or other actions relating to your personal data, where applicable under data protection laws.

If your request relates to HTTP Content, please include sufficient information to help us identify the relevant account, Server, request, or time period. For security reasons, we may ask you to verify your identity and authority before disclosing, deleting, exporting, or modifying any data.

If you use Adal on behalf of an organization, we may direct certain privacy or data-protection requests to the account owner, administrator, or other authorized representative of that organization.

For legal and privacy matters, please contact:

“ADAL CLOUD” LLP BIN: 260640039277 Republic of Kazakhstan [email protected]

Adal Cloud Adal Cloud

Receive webhooks and send HTTP requests through the API, with queues, retries and delivery history.

Product

  • Incoming webhooks
  • Outgoing HTTP requests
  • Documentation
  • Guides
  • Pricing
  • Blog

Company

  • About
  • Changelog
  • Contact

Legal

  • Security
  • Privacy Policy
  • Terms of Service
© 2026 “ADAL CLOUD” LLP. All rights reserved.