Adal Privacy Policy

Adal is a webhook infrastructure service that helps users receive, inspect, store, forward, and replay webhook requests. This Privacy Policy explains how Adal collects, uses, stores, and protects personal data when you use our website, dashboard, API, webhook servers, command-line interface, and related services.

This Policy applies to data you provide directly to Adal, data generated through your use of the Service, and data received through webhook requests sent to your Adal servers.

Because Adal processes webhook requests on behalf of its users, webhook payloads, headers, query parameters, and other request data may contain personal data or other sensitive information depending on how you configure and use the Service. You are responsible for ensuring that you have the necessary rights, permissions, and legal basis to send such data to Adal.

By using Adal, you acknowledge that your data will be processed as described in this Privacy Policy.

For the purposes of this Privacy Policy:

• “Adal”, “we”, “us”, or “our” means the provider and operator of the Adal service.
• “Service” means the Adal website, dashboard, API, webhook servers, command-line interface, and any related services provided by Adal.
• “User”, “you”, or “your” means a person or organization that accesses or uses the Service.
• “Account Data” means data related to your Adal account, such as your email address, authentication data, account settings, plan information, and related administrative information.
• “Service Configuration Data” means data you configure in the Service, including servers, destination URLs, tokens, delivery settings, storage settings, region settings, and other technical configuration.
• “Webhook Content” means the content of webhook requests received by Adal on your behalf, including request bodies, payloads, headers, query parameters, path information, and any data included in those requests.
• “Request Metadata” means technical information about webhook requests, such as timestamps, HTTP method, request size, source IP address, processing status, delivery status, retry history, and related diagnostic information.
• “Destination” means a URL or local delivery target configured by you to receive webhook requests forwarded by Adal.
• “Region” means a geographic or infrastructure location where certain parts of the Service may process or store data.
• “Personal Data” means any information relating to an identified or identifiable natural person.
• “Processing” means any operation performed on data, including collection, receipt, storage, access, transmission, forwarding, deletion, and protection.

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

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

When Adal receives, stores, forwards, or replays webhook requests on behalf of a User, LLP “ADAL CLOUD” generally acts as a data processor or service provider. The User determines the content of the webhook requests and the purposes for which such data is processed.

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

This Privacy Policy applies to the Adal website, dashboard, API, webhook servers, command-line interface, and related services that link to or reference this Policy.

This Policy covers personal data that we collect directly from you, data generated through your use of the Service, and data received, stored, forwarded, or replayed through webhook requests sent to your Adal servers.

This Policy does not apply to third-party websites, services, applications, or integrations that are not operated by Adal, even if they send data to Adal or receive data from Adal. Such third-party services are governed by their own privacy policies and terms.

When you configure a Destination, you are responsible for the service, server, application, or local environment that receives forwarded webhook requests from Adal. Adal does not control how data is processed after it has been delivered to a Destination configured by you.

If you use Adal on behalf of an organization, customer, or another person, you are responsible for ensuring that you have the authority and legal basis to use the Service and to send data to Adal.

We collect different categories of data depending on how you use Adal.

Account Data

When you create and use an Adal account, we may collect and process data such as:

• your email address
• authentication information
• account settings
• language, theme, and interface preferences
• plan, limits, and usage-related information
• administrative information related to your account

We do not store your plain-text password. If password-based authentication is used, passwords are stored only in a hashed form.

Service Configuration Data

When you configure the Service, we may collect and process technical configuration data such as:

• server names and settings
• destination URLs
• delivery settings
• storage settings
• selected or assigned regions
• authentication tokens, access tokens, API keys, or other credentials provided by you
• retry, replay, and delivery behavior settings

You are responsible for ensuring that any credentials, URLs, or configuration values you provide to Adal are valid and appropriate for use with the Service.

Webhook Content

When webhook requests are sent to your Adal servers, we may receive and process data contained in those requests, including:

• request bodies and payloads
• HTTP headers
• query parameters
• path information
• HTTP method
• content type
• request size
• files or other data included in the request, if supported by the Service

Webhook Content is determined by you and by the third-party services, applications, or systems that send requests to your Adal servers. Adal does not control the content of webhook requests before they are received by the Service.

Depending on your server settings and plan, Webhook Content may be stored, partially stored, or not stored.

Request Metadata

We may collect and process technical metadata about webhook requests, including:

• timestamps
• source IP address
• request size
• server identifier
• processing status
• delivery status
• retry history
• replay history
• error messages
• diagnostic information related to request processing and delivery

Request Metadata is used to provide the Service, display request history, support delivery diagnostics, enforce limits, prevent abuse, and maintain reliability.

Delivery Data

When Adal forwards webhook requests to configured Destinations, we may collect and process delivery-related data such as:

• destination identifier
• delivery attempt timestamps
• delivery status
• HTTP response status code
• response time
• connection errors
• timeout errors
• retry attempts
• delivery logs
• limited response information, where applicable

This data helps you inspect delivery behavior, debug failed deliveries, and replay requests where supported.

Technical and Security Data

When you access or use the Service, we may collect technical and security-related data such as:

• IP address
• browser type and version
• device and operating system information
• user agent
• session information
• authentication events
• access logs
• API usage logs
• CLI connection logs
• security events
• error logs

We use this data to operate, secure, monitor, debug, and improve the Service.

Billing and Payment Data

If you subscribe to a paid plan or purchase credits, we may process billing-related data such as:

• selected plan
• subscription status
• usage counters
• billing email
• invoice information
• payment status
• payment provider customer or subscription identifiers

Payment card details and other sensitive payment information are processed by our payment provider. Adal does not intentionally store full payment card numbers.

Communications Data

If you contact us, subscribe to updates, or receive service-related messages, we may process communication data such as:

• your email address
• message content
• support requests
• feedback
• transactional emails
• product or service notifications

We use this data to respond to you, provide support, send important service-related information, and communicate about your account or use of the Service.

We use the data we collect to provide, operate, secure, and improve the Service.

In particular, we may use data for the following purposes:

Providing the Service

We use Account Data, Service Configuration Data, Webhook Content, Request Metadata, Delivery Data, and Technical Data to:

• create and manage your account
• authenticate you and maintain your sessions
• receive webhook requests sent to your Adal servers
• store webhook requests according to your server settings and plan
• display request history in the dashboard
• forward webhook requests to configured Destinations
• deliver webhook requests through Adal CLI where applicable
• support replay and retry functionality
• apply server configuration, delivery settings, storage settings, and region settings
• provide API access and CLI connectivity

Request Inspection, Delivery, and Debugging

We use Webhook Content, Request Metadata, and Delivery Data to help you inspect incoming webhook requests, understand delivery behavior, debug delivery failures, and verify that requests were received and processed as expected.

This may include showing request headers, payloads, query parameters, delivery attempts, response status codes, timing information, error messages, and retry or replay history in the dashboard.

Reliability, Abuse Prevention, and Security

We use Technical and Security Data, Request Metadata, Delivery Data, and usage-related information to:

• monitor Service availability and performance
• detect, prevent, and investigate abuse, fraud, spam, excessive traffic, unauthorized access, and security incidents
• enforce rate limits, usage limits, plan limits, and other technical restrictions
• protect the Service, our infrastructure, our users, and third parties
• maintain logs necessary for security, diagnostics, and incident response

Billing, Plans, and Usage Limits

We use Account Data, Billing Data, and usage-related information to:

• manage subscriptions, credits, invoices, and paid plans
• calculate usage
• enforce plan limits
• process payments through our payment provider
• provide billing-related support
• send billing and subscription-related notifications

Support and Communications

We use Account Data, Communications Data, Technical Data, Request Metadata, and other relevant information to:

• respond to support requests
• investigate technical issues reported by you
• send transactional and service-related messages
• notify you about important changes to the Service, your account, billing, security, or this Privacy Policy
• process feedback or inquiries you send to us

Service Improvement

We may use aggregated, statistical, or diagnostic information to understand how the Service is used, improve reliability, improve user experience, prioritize product development, and troubleshoot performance or usability issues.

Where possible, we use aggregated or de-identified data for analytics and product improvement. We do not use Webhook Content to train AI models.

Legal Compliance and Enforcement

We may use data where necessary to:

• comply with applicable laws, regulations, legal obligations, and lawful requests
• keep records required for tax, accounting, security, or compliance purposes
• enforce our Terms of Service
• protect our rights, users, infrastructure, and third parties
• resolve disputes or investigate violations

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

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

Performance of a Contract

We process personal data where it is necessary to provide the Service to you, manage your account, receive and process webhook requests, forward requests to configured Destinations, provide request history, support retries and replays, provide API and CLI access, enforce plan limits, and perform other actions requested by you.

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

Legitimate Interests

We may process personal data where it is necessary for our legitimate interests, provided that 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 the withdrawal.

Processing Webhook Content on Your Behalf

When Adal receives, stores, forwards, or replays Webhook Content on behalf of a User, the User determines the content of the webhook requests and the purposes for which such data is processed.

In such cases, Adal generally processes Webhook Content as a data processor or service provider on behalf of the User. The User is responsible for ensuring that there is an appropriate legal basis for sending Webhook Content to Adal and for configuring the Service in a way that complies with applicable laws.

Adal does not decide what personal data is included in webhook requests sent to your servers.

Adal is designed to receive, inspect, store, forward, retry, and replay webhook requests on behalf of its Users.

Webhook Content is determined by you and by the third-party services, applications, systems, or users that send requests to your Adal servers. Adal does not control the content of webhook requests before they are received by the Service.

Webhook Content may include personal data, confidential information, authentication data, business data, or other sensitive information, depending on how you configure and use the Service.

You are responsible for:

• deciding which systems are allowed to send webhook requests to your Adal servers
• ensuring that you have the necessary rights, permissions, and legal basis to send Webhook Content to Adal
• configuring servers, storage settings, regions, destinations, and delivery settings appropriately
• avoiding unnecessary collection or transmission of personal data or sensitive information
• ensuring that Webhook Content does not violate applicable laws, third-party rights, or contractual obligations
• protecting server URLs, tokens, credentials, and other access details
• deleting Webhook Content when it is no longer needed, where such deletion is available through the Service

You should not send highly sensitive data to Adal unless it is necessary for your use case and you have taken appropriate legal, technical, and organizational measures.

Adal may process Webhook Content only as necessary to provide the Service, including receiving requests, storing them according to your settings and plan, displaying them in the dashboard, forwarding them to configured Destinations, supporting retries and replays, debugging delivery issues, enforcing limits, preventing abuse, and maintaining security.

Adal does not use Webhook Content for advertising purposes and does not sell Webhook Content to third parties.

Adal does not use Webhook Content to train AI models.

When you configure a Destination, Adal forwards Webhook Content to the Destination according to your settings. You are responsible for the Destination and for any processing of Webhook Content that occurs after delivery to that Destination.

If Webhook Content contains personal data relating to your customers, users, employees, or other third parties, you are responsible for providing any required notices, obtaining any required consents, and ensuring that your use of Adal complies with applicable data protection laws.

Adal stores and retains data only for as long as necessary to provide the Service, comply with legal obligations, resolve disputes, enforce our agreements, maintain security, and support operational reliability.

Retention periods may depend on the type of data, your plan, your server settings, your storage settings, the selected or assigned Region, and applicable legal or technical requirements.

Webhook Storage Settings

Depending on your server configuration, plan, and available features, Adal may support different storage modes for webhook requests.

Full storage means that Adal may store request metadata, headers, query parameters, path information, and request body or payload.

Headers-only storage means that Adal may store request metadata, headers, query parameters, and path information, but not the request body or payload.

No payload storage means that Adal does not intentionally store the request body or payload, although limited operational metadata may still be processed and retained as necessary to provide the Service, maintain security, enforce limits, debug delivery, and record delivery status.

The exact data stored may depend on the server configuration and the technical features enabled for your account.

Webhook Content Retention

Webhook Content is retained according to your server settings, plan limits, storage mode, and applicable retention period.

Where the Service allows you to delete webhook requests, request history, server data, or stored payloads, deletion will remove that data from active systems within a reasonable period, unless retention is required for legal, security, abuse prevention, billing, backup, or operational reasons.

Deleted Webhook Content may remain for a limited period in backups, logs, or disaster recovery systems before being overwritten or removed according to our backup and retention procedures.

Request Metadata and Delivery Data

Adal may retain Request Metadata and Delivery Data for longer than Webhook Content where necessary to provide request history, delivery diagnostics, replay and retry functionality, abuse prevention, security monitoring, usage calculation, billing support, and operational reliability.

This may include timestamps, server identifiers, delivery status, retry history, replay history, response status codes, error messages, and diagnostic information.

Account and Configuration Data

We retain Account Data and Service Configuration Data for as long as your account remains active or as needed to provide the Service.

If you delete your account, we will delete or deactivate Account Data and Service Configuration Data within a reasonable period, except where we need to retain certain data for legal, tax, accounting, security, fraud prevention, dispute resolution, or compliance purposes.

Billing and Legal Records

Billing records, invoices, payment status information, tax records, and related administrative records may be retained for the period required by applicable law.

This data may be retained even after account deletion where necessary to comply with legal, tax, accounting, or regulatory obligations.

Logs and Security Records

Technical logs, access logs, authentication logs, API logs, CLI connection logs, security events, and abuse prevention records may be retained for a limited period to maintain security, investigate incidents, debug issues, prevent misuse, and protect the Service, users, infrastructure, and third parties.

Where possible, logs are limited to the information necessary for operational, diagnostic, and security purposes.

Backups

Data deleted from active systems may remain in encrypted or access-controlled backups for a limited period.

Backups are used for disaster recovery, business continuity, and security purposes. Backup data is not used for normal production access unless it is restored as part of a recovery process.

User-Controlled Deletion

Where the Service provides deletion controls, you may delete servers, destinations, stored webhook requests, request history, or other data through the dashboard, API, or other supported interfaces.

Deleting a server or request may remove associated Webhook Content from active systems, but some related metadata, logs, delivery records, billing records, or backup copies may be retained where necessary as described in this Policy.

Data Minimization

Adal aims to limit stored data to what is necessary for the configured Service behavior.

You can reduce the amount of Webhook Content stored by selecting an appropriate storage mode, avoiding unnecessary payload storage, limiting sensitive data sent to Adal, and deleting data that is no longer needed.

Adal may allow you to select or may assign a Region for certain parts of the Service, including the storage and processing of webhook request data.

Where regional storage is available and enabled, Adal aims to store Webhook Content and related request data in the selected or assigned Region according to your server settings, plan, and available infrastructure.

Regional storage may apply to data such as:

• Webhook Content
• Request Metadata
• Delivery Data
• server-specific request history
• stored payloads, where payload storage is enabled

Some data may be processed or stored outside the selected or assigned Region where necessary to provide, secure, operate, or support the Service. This may include Account Data, authentication data, billing data, usage data, support communications, system logs, security records, monitoring data, email delivery data, payment provider data, and data processed by third-party service providers.

Adal does not guarantee that all categories of data will remain exclusively within a selected Region unless this is expressly stated in a separate written agreement or specific Service documentation.

When you configure servers, storage settings, destinations, and regions, you are responsible for selecting the configuration appropriate for your legal, security, and compliance requirements.

If a Destination is located outside the selected or assigned Region, webhook requests may be transmitted to that Destination according to your configuration. Adal does not control the location, infrastructure, or data processing practices of Destinations configured by you.

Regional storage settings do not prevent data from being transmitted outside a Region where such transmission is required by your configuration, including delivery to Destinations, use of Adal CLI, API access, support requests, or other actions initiated by you.

Adal does not sell personal data, Account Data, or Webhook 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 may share data with trusted service providers that help us operate the Service. These providers may process data on our behalf and only for the purposes described in this Privacy Policy or in accordance with our instructions.

Such service providers may include:

• hosting and infrastructure providers
• database, storage, and backup providers
• email delivery providers
• payment and billing providers
• authentication and security providers
• monitoring, logging, and error tracking providers
• analytics providers, if used
• customer support and communication tools
• content delivery, DDoS protection, or network security providers

The categories of data shared depend on the provider and the purpose of processing. For example, a payment provider may process billing and payment-related data, while a hosting provider may process data stored or transmitted through the Service.

Payment Providers

If you purchase a paid plan, subscription, or credits, payment and billing data may be processed by our payment provider.

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

Destinations Configured by You

When you configure a Destination, Adal forwards webhook requests to that Destination according to your settings.

A Destination may be a third-party service, your own server, your application, your local environment, or another server controlled by you. 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 configured by you.

Third-Party Integrations

You may configure third-party services, applications, or systems to send webhook requests to your Adal servers or receive webhook requests from Adal.

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 it is necessary to:

• comply with applicable laws, regulations, legal processes, 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 possible, 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 business 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 provides 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 person.

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

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

Depending on your location, server settings, selected or assigned 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.

Where regional storage is available and enabled, Adal aims to store Webhook Content and related request data in the selected or assigned Region, as described in the “Regional Data Storage” section. However, certain categories of data may still be processed outside that Region where necessary to provide, operate, secure, support, or improve the Service.

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. These 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 configured by you.

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

These measures may include:

• encryption in transit using TLS
• access controls for accounts, dashboard, API, and internal systems
• authentication and authorization mechanisms
• hashed password storage, where password-based authentication is used
• token-based access for API, CLI, servers, or other Service features
• infrastructure monitoring and logging
• security and abuse prevention controls
• backup and disaster recovery procedures
• restricted access to production systems
• internal access based on operational need
• separation of user accounts, servers, and request data at the application level
• regular review of security-relevant events and errors

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 these 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, storage settings, regions, destinations, and access controls in a way that is 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 as soon as possible.

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.

Adal may use cookies and similar technologies to provide, secure, and improve the Service.

Cookies are small text files stored on your device by your browser. Similar technologies may include local storage, session storage, tokens, or other browser-based storage mechanisms.

Essential Cookies

We may use essential cookies and similar technologies that are necessary for the Service to function properly.

These may be used to:

• keep you signed in
• maintain your session
• authenticate requests
• protect against unauthorized access
• remember security-related state
• prevent abuse
• support dashboard and API functionality

Essential cookies are required for the Service to operate and cannot be disabled through the Service without affecting core functionality.

Preference Cookies

Where applicable, we may use cookies or browser storage to remember your preferences, such as:

• language preferences
• theme or appearance settings
• dashboard interface preferences
• other non-sensitive settings

These technologies help provide a consistent user experience.

Analytics Cookies

Adal does not currently use advertising cookies.

If we use analytics cookies or similar analytics technologies, we will use them to understand how the Service is used, monitor performance, improve usability, and prioritize product improvements.

Where required by law, we will request your consent before using non-essential analytics cookies.

Advertising Cookies

Adal does not use cookies to sell personal data or Webhook Content.

Adal does not use Webhook Content for advertising purposes.

Adal does not use advertising cookies unless this is clearly disclosed and, where required by law, based on your consent.

Managing Cookies

You can control or delete cookies through your browser settings. Most browsers allow you to block cookies, delete existing cookies, or receive a warning before cookies are stored.

If you block or delete essential cookies, some parts of the Service may not work correctly, including login, dashboard access, session management, API access, or security features.

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 the right to do so.

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 the 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 try to resolve your concern.

Requests Related to Webhook Content

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

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

If we receive a request from an individual relating to Webhook 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 it is 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.

You may request deletion of your Adal account or export of certain data associated with your account, where supported by the Service and required by applicable law.

Account Deletion

If you delete your account or request account deletion, Adal will delete or deactivate your account within a reasonable period, subject to applicable legal, security, billing, backup, and operational requirements.

Account deletion may include deletion or deactivation of:

• your Account Data
• servers created under your account
• destinations configured by you
• API keys, CLI tokens, and other access credentials
• stored webhook requests and request history
• stored Webhook Content, where applicable
• Service Configuration Data associated with your account

After account deletion, you may lose access to the dashboard, API, CLI connections, servers, request history, stored payloads, delivery history, replay functionality, billing information, and other Service features.

Data That May Be Retained

Some data may be retained after account deletion where necessary or permitted by law.

This may include:

• billing records
• invoices
• payment status information
• tax and accounting records
• security logs
• abuse prevention records
• legal and compliance records
• records necessary to resolve disputes or enforce our agreements
• data stored in backups for a limited period before deletion or overwriting

We will not retain deleted account data longer than necessary for the purposes described in this Privacy Policy.

Server and Request Deletion

Where the Service provides deletion controls, you may delete individual servers, destinations, webhook requests, request history, or stored payloads without deleting your entire account.

Deleting a server may disable its webhook URL and stop future processing of requests sent to that server. It may also delete or make unavailable associated request history, stored Webhook Content, delivery history, replay data, and related configuration, depending on the Service functionality available at the time.

Deleting a webhook request or stored payload may remove it from active systems within a reasonable period, subject to backup, logging, security, legal, and operational limitations described in this Privacy Policy.

Data Export

Where supported by the Service or required by applicable law, you may request an export of certain data associated with your account.

Exportable data may include:

• Account Data
• Service Configuration Data
• server settings
• destination settings
• request history
• Request Metadata
• Delivery Data
• stored Webhook Content, where available and permitted
• billing or usage-related information

The scope and format of exported data may depend on the type of data, your plan, technical feasibility, security requirements, and applicable law.

Webhook Content Controlled by Users

If Webhook Content contains personal data relating to your customers, users, employees, or other third parties, you are responsible for determining whether such data should be exported, deleted, retained, or otherwise processed.

Where Adal processes Webhook Content on your behalf, we may assist you with deletion or export requests where required by applicable law and technically feasible.

Requesting Deletion or Export

You may request account deletion or data export by using the available dashboard controls, API functionality, or by contacting us at: [email protected]

We may need to verify your identity before processing deletion or export requests. We may also need additional information to locate the relevant account, server, request, or data.

We will process deletion and export requests within the time required by applicable law.

Adal is not intended for use by children.

You must be at least 18 years old, 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, Webhook Content may contain personal data submitted by third-party systems, applications, or services. Users are responsible for ensuring that any Webhook 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 Webhook Content processed through Adal contains children’s personal data in violation of applicable law, please contact us at: [email protected]

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. This may include notice through the Service, dashboard notification, email notification, or another appropriate method.

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

Your continued use of the Service after the updated Privacy Policy becomes effective means that you acknowledge 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.

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

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

If your request relates to Webhook Content, please include enough 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:
LLP “ADAL CLOUD”
BIN: 260640039277
Republic of Kazakhstan
[email protected]