Privacy Policy

Last updated: April 26, 2026

This Privacy Policy explains how Nobalaa OTP, available through dashboard.gminx.net, collects, uses, stores, and protects information when businesses use our OTP messaging service.

1. Information We Collect

We may collect and process the following types of information:

• Client account information, including client name, email address, account status, and login information.
• Recipient phone numbers submitted through the OTP API.
• OTP request metadata, including request time, recipient, delivery status, purpose, and provider response.
• Technical logs, including IP address, request metadata, API usage logs, authentication events, and error logs.
• Messaging provider configuration required to deliver OTP messages.

2. How We Use Information

We use collected information to:

• Provide OTP delivery and messaging services.
• Authenticate API requests using bridge tokens.
• Send OTP messages through selected messaging providers.
• Monitor delivery status, troubleshoot failed requests, and maintain service reliability.
• Detect abuse, prevent unauthorized use, and protect platform security.
• Comply with applicable legal, regulatory, and operational requirements.

3. WhatsApp Cloud API and Meta

When WhatsApp Cloud API is selected as the delivery provider, message data such as recipient phone number, template name, language, OTP parameters, and delivery metadata may be sent to Meta Platforms, Inc. for the purpose of delivering WhatsApp messages.

Meta processes such data according to its own terms, policies, and WhatsApp Business Platform requirements.

4. Data Sharing

We do not sell personal information. We may share limited information only with:

• Messaging providers required to deliver OTP messages.
• Hosting, infrastructure, monitoring, and security service providers.
• Authorities or regulators when required by law.

5. Data Retention

We retain OTP request logs, delivery metadata, and technical logs for operational, security, debugging, fraud prevention, and compliance purposes. We may delete or anonymize information when it is no longer needed.

6. Security

We use reasonable technical and organizational safeguards to protect information, including encrypted connections, access controls, token-based authentication, restricted administrative access, and secure credential handling.

7. Customer Responsibilities

Clients using Nobalaa OTP are responsible for ensuring that they have a lawful basis to send OTP messages to recipients and that their use complies with applicable privacy, messaging, telecom, and data protection laws.

8. User Rights

Depending on your location, you may have rights to access, correct, delete, restrict, or object to the processing of your personal information. To submit a request, contact us using the details below.

9. Contact

For privacy questions or data requests, contact us at: support@nobalaa.com

10. Changes to This Policy

We may update this Privacy Policy from time to time. The latest version will always be available on this page.