Legal

Privacy Policy

Dokaai — Omnichannel Notification Platform

Effective Date: October 31, 2026Last Updated: October 31, 2026

1. Introduction and Scope

Nthgram Technologies Private Limited ("Dokaai", "we", "us", or "our") respects your privacy and is committed to handling personal information responsibly. Dokaai operates a cloud-based communications orchestration platform that enables businesses to manage notifications through connected services.

1.1 Privacy Policy Overview

This Privacy Policy explains how we collect, use, process, disclose, protect, and retain personal information in connection with our websites, applications, and services. It also describes the privacy rights and choices that may be available to individuals.

Where Dokaai handles account, billing, and service-administration information for its own purposes, it generally acts as a data controller or data fiduciary, as applicable. Where Customers use Dokaai to process Recipient information, those Customers generally determine the purposes of that processing, and Dokaai acts on their instructions.

1.2 Scope and Applicability

This Policy covers website visitors, Account Users, representatives of Customers, and Recipients whose information is processed through Dokaai on behalf of Customers. Our handling of information depends on our relationship with the individual and the nature of the relevant processing.

This Privacy Policy applies to Dokaai's Services. Where applicable, additional data processing terms may govern how we process Personal Information on behalf of Customers. Please also review our Terms and Conditions.

For questions about this Policy, please contact the Privacy and Grievance Contact listed in Section 20.2.

1.3 Definitions

  • "Personal Information" means information relating to an identified or identifiable individual and includes personal data or similar terms under applicable law.
  • "Services" means Dokaai's websites, applications, APIs, notification tools, and related services covered by this Privacy Policy.
  • "Customer" means the business or organization that subscribes to or uses the Services. Customer does not refer to the Customer's own customers or end users; those individuals are Recipients where the definition below applies.
  • "Account User" means an owner, administrator, employee, contractor, or other team member authorized by a Customer to access or use the Services on its behalf.
  • "Recipient" means a Customer's own customer, end user, subscriber, employee, or another individual to whom the Customer sends or intends to send a notification, or whose Personal Information is otherwise processed through the Services on the Customer's behalf.
  • "Controller" or "Data Fiduciary" means the person or organization that determines the purposes and means of processing Personal Information, as those terms apply under relevant law.
  • "Processor" means a person or organization that processes Personal Information on behalf of and under the instructions of a Controller or Data Fiduciary.

2. Our Role in Processing Personal Data

Dokaai processes different categories of personal information in different capacities.

2.1 Information Controlled by Dokaai

For information collected directly through our website, account registration, billing, customer support, security operations, and business communications, Dokaai generally determines the purposes and means of processing.

This includes:

  • Account-holder details.
  • Business contact information.
  • Subscription and billing information.
  • Account authentication and security records.
  • Customer support communications.
  • Website usage and analytics information.

For such information, Dokaai generally acts as a data controller or data fiduciary, as applicable under relevant data protection laws.

2.2 Information Processed on Behalf of Customers

When a Customer uses Dokaai to manage notifications, configure communication workflows, upload Recipient details, or process application events, the Customer generally determines:

  • What personal information is collected.
  • Which individuals receive notifications.
  • What content is communicated.
  • Which channels and providers are used.
  • What preferences, consent rules, and retention settings apply.
  • The purposes for which notifications are sent.

In these circumstances, Dokaai generally acts as a data processor or data-processing service provider acting on the Customer's instructions.

The Customer remains responsible for establishing the applicable legal basis for collecting and using the Recipient information and for providing necessary privacy notices.

The applicable role depends on the processing context. Dokaai acts as a Processor when it processes Recipient Personal Information on a Customer's documented instructions. Dokaai acts as a Controller or Data Fiduciary for Personal Information processed for its own account administration, billing, security, support, website, and business-communication purposes.

2.3 Information Received by Notification Recipients

If you receive an email, SMS, WhatsApp message, push notification, or other communication from an organization using Dokaai, that organization is generally responsible for deciding why the communication was sent.

Requests concerning the message content, marketing consent, Recipient records, or the organization's communication practices should ordinarily be directed to the sending organization.

Dokaai will assist its Customers in addressing valid privacy requests to the extent required by applicable law and contractual obligations.

3. Information We Collect

The categories of information we process depend on how the Services are used.

We collect Personal Information directly from individuals, automatically through our websites and Services, and from Customers when processing information on their behalf.

3.1 Account and Registration Information

When users register for Dokaai, we may collect:

  • Full name.
  • Business email address.
  • Organization or company name.
  • Account identifiers.
  • Login and authentication information.
  • Account settings and preferences.
  • Organization and project membership.
  • User roles and permissions.
  • Relevant security and login activity.

When users choose third-party authentication, we may receive certain account information from the authentication provider, depending on the permissions granted.

Dokaai supports account registration using email and password, and sign-in through Google and GitHub. For email registration, Dokaai processes the user's email address, first and last name, country code, optional contact number, and authentication credential. For Google sign-in, Dokaai may receive the user's email address, given name, family name, and profile image. For GitHub sign-in, Dokaai may receive the user's username, email address, and profile image. Passwords are stored only in securely hashed form.

We do not require users to provide more personal information than is reasonably necessary for the relevant account functionality.

3.2 Subscription and Payment Information

When Customers purchase a subscription or paid service, we may process:

  • Billing name and business information.
  • Billing email address.
  • Billing address, where required.
  • Tax identification details, where applicable.
  • Subscription plan and renewal information.
  • Transaction identifiers and payment status.
  • Invoices and payment or invoice history.

Dokaai uses Razorpay as its payment processing provider.

Payment transactions may involve the collection and processing of additional payment information directly by Razorpay under its applicable privacy and security practices.

Dokaai may retain billing information, invoices, transaction identifiers, payment status, payment-method type, and related accounting records.

Payment credentials are processed by Razorpay. Dokaai does not store full payment card numbers, card verification values, PINs, or other sensitive payment-authentication information.

3.3 Customer-Provided Recipient Information

Customers may provide information relating to Recipients, including their end users, subscribers, employees, or other intended notification Recipients.

Depending on the Customer's configuration, this may include:

  • Names.
  • Email addresses.
  • Telephone numbers.
  • WhatsApp contact identifiers.
  • Push notification tokens and device identifiers.
  • Recipient identifiers or external user IDs.
  • Language and timezone preferences.
  • Notification preferences and consent-related information.
  • Customer-defined attributes and metadata.
  • Recipient audience, cohort, or list membership.
  • Other attributes supplied through APIs, files, templates, or workflows.

Dokaai processes this information to provide the notification-related functionality requested by the Customer.

Customers should only provide information that is necessary, lawful, and appropriate for their intended communication purposes.

3.4 Notification Events, Payloads, and Workflow Information

When Customers use Dokaai, we process information necessary to arrange, execute, monitor, and troubleshoot their communications. This can include event and request identifiers, Recipient details, message attributes, routing and channel instructions, preference settings, scheduling information, and records of processing outcomes.

Such information may include:

  • Notification handler identifiers.
  • Event identifiers.
  • Event payloads and template attributes.
  • Recipient information.
  • Channel selection and routing instructions.
  • Customer-configured Recipient preferences and suppression settings.
  • Scheduled execution timestamps.
  • Workflow configurations and execution state.
  • Message metadata.
  • Correlation and request identifiers.
  • Provider responses and delivery-related events.
  • Processing errors and execution status information.

Notification payloads may contain Personal Information when supplied by the Customer.

We process this information to execute, schedule, route, monitor, troubleshoot, and manage Customer-requested notification operations.

3.5 Provider Integrations and Credentials

Customers may connect third-party communication providers to Dokaai.

Depending on the integration, we may process:

  • Provider names and integration identifiers.
  • API keys and authentication credentials.
  • Access tokens or authorization information.
  • Sender identities and provider configurations.
  • Provider account references.
  • Provider responses and delivery-status information.

Such information is used to establish and operate Customer-authorized integrations.

Connected-provider credentials are protected using encryption and access controls.

3.6 Website and Technical Usage Information

When users visit our website or interact with our platform, we may collect technical information such as:

  • IP address.
  • Browser and device type.
  • Operating system.
  • Pages accessed.
  • Date and time of visits.
  • Referring website.
  • Session-related information.
  • Application performance and diagnostic data.
  • API usage information.
  • Security events.

The information collected depends on the website technologies, application features, and security measures actually deployed.

Dokaai processes application logs through Google Cloud for operational monitoring, troubleshooting, and security.

3.7 Support and Business Communications

When individuals contact Dokaai, request assistance, join a pilot program, or submit a business inquiry, we may process:

  • Contact details.
  • Organization information.
  • Support messages.
  • Technical diagnostic information.
  • Screenshots or files voluntarily provided.
  • Relevant account and service information.

We use this information to respond to requests, resolve technical issues, provide support, and maintain appropriate business records.

Information submitted through Dokaai's contact, demo, waitlist, and support forms is processed through Dokaai's systems and service providers to respond to requests, administer related programs, and maintain appropriate business records.

4. How We Use Personal Information

Dokaai uses personal information for the specified purposes described below in accordance with applicable law.

The following table summarizes the principal categories of information, why they are processed, Dokaai's role, and the applicable basis or processing authority. The applicable basis depends on the processing context and applicable law. Where Dokaai acts on behalf of a Customer, the Customer determines the applicable legal basis and Dokaai processes the information under the Customer's instructions.

Summary of Dokaai's personal-information processing activities
Data categoryPurposeDokaai's roleApplicable basis or processing authority
Account and organization informationCreate and administer accounts, organizations, projects, roles, and permissions.Controller or data fiduciaryProviding and administering the requested Services under a basis permitted by applicable law.
Authentication and security informationAuthenticate users, prevent unauthorized access, detect abuse, and investigate security incidents.Controller or data fiduciaryProviding and securing the Services under a basis permitted by applicable law, including compliance with applicable obligations.
Subscription and billing informationManage subscriptions, invoices, payments, and related billing and payment history.Controller or data fiduciaryAdministering subscriptions, invoices, and payments; compliance with applicable accounting, tax, and legal obligations.
Support and business communicationsRespond to inquiries, provide support, troubleshoot issues, and maintain business records.Controller or data fiduciaryResponding to requests and providing support under a basis permitted by applicable law.
Customer-provided Recipient informationResolve Recipients, apply preferences, and deliver Customer-requested notifications.Processor or data processor acting for the CustomerCustomer instructions; the Customer determines the applicable legal basis.
Notification content, events, and workflow informationRender, schedule, route, monitor, troubleshoot, and report on notification operations.Processor or data processor acting for the CustomerCustomer instructions; the Customer determines the applicable legal basis.
Provider integration information and credentialsEstablish and operate Customer-authorized communication-provider integrations.Processor or service provider acting for the CustomerCustomer instructions; the Customer determines the applicable legal basis.
Website and technical usage informationMaintain security, measure performance, understand usage, and improve website and service functionality.Controller or data fiduciaryEssential website and service operation and security under a basis permitted by applicable law.

4.1 Providing the Services

We use the information described above to administer Customer accounts and deliver requested communications, including selecting Recipients, applying Customer-defined rules, coordinating provider integrations, and supplying operational reports. Examples of these activities include:

  • Creating and administering Customer accounts.
  • Managing organizations and projects.
  • Processing notification events.
  • Resolving Recipients and audience information.
  • Executing notification workflows.
  • Rendering personalized templates.
  • Managing schedules, delays, and digests.
  • Applying configured routing and preference rules.
  • Connecting Customer-authorized delivery providers.
  • Processing unsubscribe and suppression instructions.
  • Providing operational dashboards and analytics.

4.2 Maintaining Security and Reliability

  • Authenticating users.
  • Preventing unauthorized access.
  • Monitoring unusual activity.
  • Identifying potential misuse, fraud, or abuse.
  • Enforcing technical limits.
  • Troubleshooting service failures.
  • Protecting platform infrastructure.
  • Investigating security incidents.
  • Maintaining records required by applicable law.

Automated systems may be used to identify suspicious patterns, subject to applicable law and appropriate safeguards.

4.3 Billing and Account Administration

  • Managing subscriptions.
  • Measuring billable usage.
  • Preparing invoices.
  • Processing payments.
  • Handling billing discrepancies.
  • Maintaining payment and invoice history.
  • Maintaining accounting and tax records.

4.4 Improving the Services

We may use operational information, usage patterns, service metrics, and appropriately aggregated or de-identified information to:

  • Identify service performance issues.
  • Improve product reliability.
  • Plan infrastructure capacity.
  • Understand feature usage.
  • Improve the user experience.
  • Develop additional platform functionality.

We do not use Customer notification content or Recipient-level Personal Information for unrelated advertising purposes.

Any use of Customer content for training external artificial intelligence models must be separately disclosed and appropriately authorized before such processing occurs.

5. Notification Delivery and Third-Party Providers

Dokaai coordinates communications through Customer-selected delivery providers and is responsible for its own processing activities.

5.1 Customer-Configured Delivery Providers

Customers may configure third-party communication providers through their own integrations and credentials.

Third-party communication providers may process this information under their own contractual, technical, and legal arrangements.

Provider-side retention, delivery operations, and further processing may differ from Dokaai's practices.

5.2 Information Transmitted for Delivery

To perform the Customer's requested operation, Dokaai may transmit necessary information to those configured providers.

Such information may include:

  • Recipient contact details.
  • Message content.
  • Template attributes.
  • Channel-specific identifiers.
  • Sender information.
  • Delivery instructions and metadata.

5.3 Provider Responses and Delivery Records

Dokaai may receive delivery acknowledgments, failure reports, status updates, or related analytics from configured providers.

6. Customer Role in Processing Personal Data

When Customers determine why and how Recipient or notification information is processed, they generally act as the Controller or Data Fiduciary, and Dokaai processes that information on their instructions as a Processor.

6.1 Lawful Collection and Processing

For Customer-controlled information, the Customer determines the applicable lawful basis, required privacy notices, and information necessary for the requested communication. This includes determining whether:

  • They have a valid legal basis for processing Recipient information.
  • Required notices have been provided to individuals.
  • Personal information submitted to Dokaai is relevant and reasonably necessary.

7. Sensitive Information and Data Minimization

Dokaai is designed primarily for notification management and related operational data.

7.1 Sensitive Information

Dokaai is not intended for unnecessary highly sensitive information. Unless Dokaai has expressly agreed to support a particular category under appropriate contractual and technical safeguards, Customers should avoid including sensitive information in notification content, payloads, templates, metadata, or support requests. Detailed prohibited and restricted data rules are set out in the Terms of Use and other applicable service terms.

7.2 Data Minimization and Payload Handling

Files uploaded or generated for import, export, cohort-processing, and similar jobs may contain Customer or Recipient Personal Information. Dokaai processes these files to perform the operation requested by the Customer.

The files are retained for up to five days and are accessible only through authorized, time-limited signed links scoped to the relevant organization. After five days, they are deleted from active storage.

Dokaai also processes Recipient contact information, notification content, template attributes, and related event data as necessary to deliver and monitor notifications. Event history and backup copies follow the separate retention practices described in Section 11.

8. Data Storage and Infrastructure

8.1 Cloud Hosting and Infrastructure

Dokaai uses Google Cloud Platform (GCP) to host its infrastructure and store service-related information.

We take reasonable measures designed to prevent unauthorized access, disclosure, alteration, and loss of information.

8.2 Data Storage and Processing Locations

Our primary hosting and data-storage infrastructure is located in Google Cloud regions in India.

Some information may also be processed by authorized service providers or communication providers outside the primary hosting environment.

8.3 Operational Systems and Storage

Depending on the operation, Customer information may be processed through applications, databases, object storage, queues, caches, monitoring infrastructure, and related systems.

9. Data Isolation and Access Controls

Dokaai operates a multi-tenant platform in which Customers may create organizations, projects, and associated resources.

9.1 Organization-Level Isolation

Customer information belonging to one organization is intended to remain logically separated from information belonging to unrelated organizations.

Dokaai does not authorize Customers to access the private information of other organizations.

Organization-level access is governed by the platform's implemented authentication, authorization, and permission controls.

9.2 Sharing Within an Organization

Projects are logically separated. Information may be shared between projects within the same organization only through supported sharing features enabled by an authorized Account User, such as a shared Recipient or audience pool.

Such sharing is governed by the platform's implemented authentication, authorization, and project-sharing controls.

9.3 Access by Dokaai Personnel

Authorized Dokaai personnel may require limited access to account or operational information for legitimate purposes, including:

  • Technical support.
  • Incident investigation.
  • Security maintenance.
  • Billing assistance.
  • Service troubleshooting.
  • Compliance with applicable law.

Routine administrative access to Customer information occurs through authenticated product interfaces or APIs for authorized purposes rather than through direct database queries.

GCP administrative access is restricted to authorized DevOps personnel using non-shared accounts.

10. Information Sharing and Disclosure

Dokaai does not sell Customer-provided Recipient information for unrelated advertising purposes.

We may disclose personal information in the following circumstances.

10.1 Customer-Configured Communication Providers

Where necessary to execute communications requested by Customers, Dokaai may transmit data to the configured communication providers.

10.2 Infrastructure and Operational Service Providers

Dokaai uses third-party service providers to support cloud infrastructure, hosting, storage, databases, authentication, payment processing, monitoring, security, and business communications.

Depending on the service, these providers may process Account User information, billing information, Recipient information, communications, and technical or usage information as necessary to provide the relevant service.

Where a provider processes Personal Information on Dokaai's behalf, Dokaai requires it to comply with applicable confidentiality, security, legal, and contractual requirements.

10.3 Organization Administrators and Authorized Users

Information may be made available to organization owners, administrators, or other authorized users according to their roles and permissions.

10.5 Corporate Transactions

If Dokaai or its operating company undergoes a merger, acquisition, restructuring, investment transaction, or transfer of assets, relevant information may be transferred subject to applicable confidentiality, contractual, and data-protection obligations.

10.6 Aggregated or De-identified Information

We may disclose statistical, aggregated, or effectively de-identified information that does not identify Customers or individual Recipients and is not reasonably capable of being used to reconstruct their Personal Information.

11. Data Retention and Deletion

Dokaai retains information according to its nature, processing purpose, service requirements, applicable plan, legal obligations, and appropriate operational needs.

Different types of information may have different retention periods.

11.1 Temporary Job-Processing Files

Files uploaded temporarily for notification-job processing, including generated error files, are available through the Services for up to five (5) days.

File uploads and downloads use secure, time-limited links.

After the five-day availability period, temporary job-processing files are deleted from active GCP bucket storage and become unavailable through Customer-facing service interfaces. Copies may remain temporarily in rolling backups under the separate backup-retention rule.

The five-day period applies to temporary job-processing files. Related event history, security records, legally required records, suppression data, configuration records, and backup copies may be governed by separate retention rules.

11.2 Notification Event History

Dokaai may retain notification event and delivery history while the relevant account remains active to provide the Services, support operations, troubleshoot delivery, and provide analytics.

For communications delivered through external providers, Dokaai generally retains operational event and delivery history, while the selected providers process delivery-related information according to their own practices.

Dokaai stores content and related records required to provide in-app notifications. In-app notification records older than one year may be moved to archive storage.

Moving information to archive storage does not mean that it has been deleted.

11.3 Customer Profiles and Configurations

Customer profiles, Recipient records, templates, template images and attachments, notification handlers, organization settings, and integration configurations may be retained while the relevant account remains active and the information is necessary to provide the Services.

Customers may be able to remove or modify certain information through supported product functionality.

After an account has been inactive for 12 months, Dokaai may notify the Customer about possible deletion. Inactivity alone does not currently trigger automatic deletion. Account-termination retention is described in Section 11.9.

11.4 Analytics and Diagnostic Records

Application logs, diagnostic records, and error records are retained only for a limited period reasonably necessary for security, troubleshooting, service reliability, and legal compliance.

Dokaai limits logged information and masks or removes sensitive values where appropriate.

Aggregated or de-identified operational metrics may be retained for longer where they no longer identify an individual.

11.7 Billing and Financial Records

Dokaai may retain billing contact information, invoices, subscription details, transaction references, payment status, and payment or invoice history for as long as reasonably necessary for billing, accounting, tax, fraud-prevention, legal, and dispute-resolution purposes.

Dokaai does not store full payment-card numbers, CVV, PIN, or other sensitive payment credentials. Such information is processed by the applicable payment provider.

11.8 Backups

Information may remain in backup systems after deletion from active production systems.

Backups are managed according to their applicable retention and recovery schedules.

Where information remains in backups, it is subject to applicable access restrictions and will be removed as those backups expire or are replaced, unless further retention is legally required.

Production database backups are retained on a rolling basis for approximately seven days.

11.9 Account Termination and Data Deletion

Following account termination, Customer information that is not subject to separate legal, billing, security, or dispute-resolution retention requirements may be retained for up to three months while technical deletion processes are completed.

Information no longer required will be deleted or de-identified according to applicable retention procedures. Backup copies will expire according to the schedule described in Section 11.8.

12. Data Security

Dokaai recognizes the importance of protecting the information entrusted to its Services.

12.1 Technical and Organizational Safeguards

We maintain technical and organizational safeguards appropriate to the nature of the information processed and the risks involved.

Depending on the system, such safeguards include:

  • Authentication and authorization controls.
  • Restrictions on access to organization and project data.
  • Authenticated and authorized API access.
  • Rate limits and abuse prevention.
  • Encryption and restricted handling of provider credentials.
  • HTTPS/TLS transport security.
  • Storage encryption and access controls.
  • Application monitoring and logging.
  • Automated database backup procedures.

The specific safeguards that apply to each service component depend on its implemented configuration.

No internet-based service or electronic storage system can be guaranteed to be completely secure.

Dokaai cannot guarantee the prevention of every security incident. This does not limit any obligations imposed by applicable law or binding contractual commitments.

12.2 Security Incidents and Personal Data Breaches

If Dokaai becomes aware of a security incident affecting Personal Information, we will take reasonable steps to investigate and address the incident.

Where Dokaai processes Personal Information on behalf of a Customer, we will notify and assist the affected Customer as required by applicable law and relevant agreements.

Where Dokaai acts as a Controller or Data Fiduciary, we will provide notifications to affected individuals or authorities where required by applicable law.

13. Cookies and Similar Technologies

Our website and applications use first-party cookies and browser storage where necessary to provide, secure, and operate the Services.

13.1 Essential Cookies and Browser Storage

  • Maintaining authenticated sessions.
  • Supporting account registration and email verification.
  • Preserving Account User, organization, project, invitation, sign-in-provider, and interface context.
  • Protecting against unauthorized activity.

Under the current configuration, the primary authentication cookie remains available for approximately 9 hours and 36 minutes, and a temporary email-registration cookie remains available for up to 10 minutes.

Information stored in browser storage may remain until it is removed by the application, cleared during supported account or session actions, or deleted through browser controls. Clearing or disabling essential cookies or browser storage may sign an Account User out or affect application functionality.

13.2 Third-Party Technologies

Dokaai does not currently use Google Analytics, advertising pixels, or other non-essential analytics or advertising cookies on its websites or applications.

Our website may embed Google Maps on contact or location pages. When an embedded map loads, the visitor's browser connects directly to Google. Google may receive technical information such as the visitor's IP address, browser or device information, and referring page, and may use cookies or similar technologies according to its own privacy practices. For more information, please review the Google Privacy Policy.

14. International Data Transfers

14.1 Cross-Border Data Processing

Dokaai's primary cloud infrastructure is hosted in India.

However, some processing may involve service providers, Customer-configured communication providers, support operations, or other activities involving different countries.

Dokaai does not represent that every processing activity occurs exclusively within India unless this has been expressly agreed and technically verified.

14.2 International Transfer Safeguards

Dokaai primarily hosts its production infrastructure in India. However, certain service providers, integrations, authentication providers, payment processors, Customer-selected delivery providers, or support tools may process Personal Information in other countries.

Where an international transfer requires additional safeguards, Dokaai will use appropriate contractual, organizational, or legally recognized transfer mechanisms as required by applicable law.

Customer-selected providers may process information in locations determined by the Customer's configuration and the provider's own terms.

14.3 Customer-Selected Provider Transfers

Customers using third-party delivery providers are responsible for assessing the international processing arrangements relevant to their chosen providers.

15. Privacy Rights and Requests

Depending on applicable law, individuals may request access to, correction of, or deletion of their Personal Information, withdraw consent where applicable, and exercise other legally available privacy rights.

A deletion request may not result in the immediate deletion of every record. Dokaai may retain information where reasonably necessary for billing, tax, security, fraud prevention, dispute resolution, legal compliance, or backup and recovery purposes.

Where Dokaai processes Personal Information on behalf of a Customer, Dokaai may refer the request to that Customer and provide reasonable assistance as required by applicable law.

Account changes, organization administration, subscription cancellation, data export, and account termination are governed separately by the Terms of Use.

15.1 Requests from Dokaai Account Users

Account Users may contact us regarding Personal Information that Dokaai controls directly.

Requests may be submitted to the Privacy and Grievance Contact listed in Section 20.2.

We may request reasonable information to verify identity and prevent unauthorized disclosure or deletion.

We will respond within applicable legal deadlines.

15.2 Requests from Notification Recipients

If an individual receives a communication through Dokaai on behalf of a Customer, the Customer ordinarily determines the purposes of that communication and manages the relevant Recipient relationship.

Such individuals should generally contact the sending organization to exercise their rights relating to that organization's records.

If we receive a request relating to data processed on behalf of a Customer, we may refer the request to the Customer or assist the Customer in responding, consistent with applicable law and our contractual obligations.

15.3 Marketing Preferences and Opt-Outs

Dokaai may provide unsubscribe and communication-preference mechanisms for notifications sent on behalf of Customers.

Depending on the Customer's configuration, these mechanisms may allow a Recipient to manage preferences for an email address, communication group, topic, campaign, category, or broader marketing communications. Logged-in users may also be able to manage available preferences through the application.

An unsubscribe request for one organization or communication category does not necessarily unsubscribe the individual from unrelated organizations or categories.

Where a Customer controls the relevant Recipient relationship, Dokaai may refer the request to that Customer or apply the Customer-configured preference or suppression mechanism.

Dokaai may also send its own product information, marketing, or promotional communications. Dokaai marketing emails provide an unsubscribe link, and individuals may also request a marketing opt-out through the Privacy and Grievance Contact listed in Section 20.2.

A Dokaai marketing opt-out applies to marketing communications and does not prevent necessary account, billing, transactional, service, or security communications.

Dokaai may retain limited information necessary to respect valid opt-out instructions.

16. Children's Privacy

16.1 Direct Collection from Children

Dokaai is a business-oriented platform and does not intentionally market accounts to children.

If we discover that we have directly collected information from a child in circumstances prohibited by applicable law, we will take appropriate steps to address that information.

16.2 Customer Processing of Children's Data

Customers who use Dokaai to process personal information relating to children are responsible for complying with the applicable requirements concerning parental consent, authorization, notices, and restrictions on processing.

17. Third-Party Websites and Services

17.1 External Websites and Integrations

Our website or applications may contain links to third-party websites, software, integrations, or external services.

17.2 Independent Third-Party Privacy Practices

These third parties operate under their own terms, privacy notices, and security practices.

This Privacy Policy does not govern independent processing conducted by third parties outside Dokaai's control.

18. Automated Processing and Artificial Intelligence

18.1 Automated Operational Processing

Dokaai may use automated systems to operate notification workflows, apply configured routing and preference rules, identify technical failures, and detect potentially abusive or suspicious activity.

Such processing may include automated evaluation of operational metadata, configuration information, and platform activity.

18.2 AI Features and Customer Data

Dokaai is implementing optional, subscription-based AI-assisted features that Customers may enable and use to generate or improve notification and email content.

When enabled, these features may process prompts or queries, attribute names, template or email content, and selected knowledge-base content through Dokaai's agent and retrieval-augmented generation components. Dokaai does not intentionally add Recipient contact information to AI inputs, and Customers should avoid including unnecessary Personal Information.

Customers may connect their own AI-provider credentials through a bring-your-own-key configuration. Processing by a Customer-selected provider, including its retention and model-training practices, is governed by that provider's terms and the Customer's configuration.

Dokaai may collect relevance scores and limited feature feedback to evaluate and improve its AI-assisted experience. Relevance feedback does not authorize a Customer-selected provider to use Customer data for unrelated model training.

18.3 Automated Decision-Making Rights

Where applicable law provides rights relating to automated decision-making, Dokaai will respect those rights in accordance with its legal role and obligations.

19. Changes to This Privacy Policy

19.1 Policy Updates

We may update this Privacy Policy from time to time to reflect:

  • Changes to our Services.
  • New or modified features.
  • Changes in data-processing practices.
  • Changes to infrastructure or service providers.
  • Applicable legal or regulatory developments.
  • Security or operational requirements.

19.2 Notifications and Effective Dates

When this Policy is updated, we will publish the revised version and update the latest revision date.

If a change materially affects how we collect, use, share, retain, or otherwise process Personal Information, we will provide a prominent notice through our website or application.

Where required by applicable law, we will provide additional notice or obtain consent before the relevant change takes effect.

20. Contact Information and Grievances

20.1 Company and Contact Details

Nthgram Technologies Private Limited

Dokaai — Omnichannel Notification Platform

Website: https://dokaai.com

Registered Office: H.NO. 614/P-007 (KH-279), Raheem Nagar, Dudauli, Faizullaganj-IV, Lucknow 226021, Uttar Pradesh, India

Operated by Nthgram Technologies Private Limited.

20.2 Privacy Requests and Grievance Contact

For questions about this Privacy Policy, personal data processing, privacy rights, or complaints, contact:

Privacy and Grievance Contact: atuljoshi@dokaai.com

We will review privacy-related inquiries and respond according to applicable legal requirements.