Document Control

Contents

  1. 1. Introduction
  2. 2. Our Privacy Programme at a Glance
  3. 3. The Two Roles Adya Plays — Please Read First
  4. 4. Personal Data We Collect (as Controller)
  5. 5. How We Use Personal Data (as Controller)
  6. 6. Why We Are Allowed to Use Your Data (Legal Bases)
  7. 7. Consent and Notice Management
  8. 8. When We Share Personal Data
  9. 9. AI, Profiling and Automated Decisions
  10. 10. Data Location and International Transfers
  11. 11. Records of Processing and Data Inventory
  12. 12. Data Retention and Deletion
  13. 13. Your Rights
  14. 14. Children’s Data
  15. 15. Cookies and Similar Technologies
  16. 16. Security, Certifications and Assurance
  17. 17. Data Breach Notification
  18. Amendments to This Policy

1. Introduction

This Privacy Policy explains how Shayr Omnichannel Private Limited, operating as Adya (“Adya”, “we”, “us”), handles personal data in connection with the Adya platform and services, including the Vanij builder platform, GTM Agent and the Research and Analysis Suite (RAS) (together, the “Services”).

Privacy at Adya is run as an operating programme, not a document: every processing activity is recorded, every consent we rely on is logged against the notice that was shown, every AI use of personal data is mapped to a source and a lawful basis, and every deletion leaves an auditable trail. This policy describes that programme.

2. Our Privacy Programme at a Glance

3. The Two Roles Adya Plays — Please Read First

Adya is an AI orchestration platform. We handle data in two distinct roles, and which role applies depends on the data, the product and how the Services are deployed.

Plain-language summary

As a Controller — for account-level data we collect directly from you (your name, login, billing, how you use the platform). This policy mainly governs that data.

As a Processor — for the content you put into the platform (prompts, files, datasets, and the data your agents handle). You are in control and we act only on your documented instructions under our Data Processing Addendum (DPA).

3.1 Role by deployment model

Adya is cloud-hosted by default. On customer request we deploy in a dedicated environment or on the customer’s own infrastructure (on-premise or customer cloud). The deployment model determines our role:

3.2 Role by product

3.3 DPA coverage and client register

Every customer relationship is covered by a DPA: our standard DPA is incorporated into the Terms of Service, and enterprise customers may execute a negotiated DPA. We maintain a customer DPA register recording, for each customer: products used, deployment model, Adya’s role, DPA version and execution date, approved sub-processors, data-residency region, and any customer-specific instructions.

The rest of this policy focuses on data for which we are the Controller, unless stated otherwise.

4. Personal Data We Collect (as Controller)

4.1 Registration and account data

Name, work email, phone number, organisation, role, country/region, and account preferences you provide when registering.

4.2 Billing data

Plan, billing contact, billing address, transaction history, and tax identifiers. Payments are processed by third-party payment processors; we do not store full card or bank-account numbers. We receive only tokens and limited details (such as the last four digits and card type) needed for billing and fraud prevention.

4.3 Device and connection data

IP address, browser type, operating system, device identifiers, and session information, collected automatically when you use the Services.

4.4 Usage data

How you interact with the platform — features used, actions taken, agents created, and diagnostic and performance logs. We use this to operate, secure, and improve the Services.

4.5 Support, communications and consent records

Records of your communications with us, including support requests and correspondence, and records of the consents and preferences you give or withdraw (see section 7).

4.6 Customer Content (processor role)

Prompts, files, datasets, and instructions you submit, and the data your agents process, may contain personal data about third parties. We handle this on your behalf as a Processor under the DPA — not for our own purposes. We do not use Customer Content to train AI models (see section 9).

5. How We Use Personal Data (as Controller)

We use account-level personal data to:

What we do not do

8. When We Share Personal Data

We share personal data only as needed and never for third-party marketing. Categories of recipients:

9. AI, Profiling and Automated Decisions

Plain-language summary

Adya doesn’t train AI models on your data. Every AI or analytics use of personal data is mapped to where the data came from and why we are allowed to use it. We don’t make solely automated decisions with legal or similarly significant effects on anyone, and we give customers the controls to keep a human in the loop.

9.1 No training on your data

Adya does not use Customer Content, prompts, or outputs to train, fine-tune, or develop foundation or general-purpose AI models, for ourselves or any third party.

9.2 Connected Models

When you use a Connected Model (such as Anthropic Claude or OpenAI models), your inputs are transmitted to that provider to deliver the Service you requested. If you connect your own model credentials, the provider is your vendor and its handling of your data is governed by your agreement with it; we recommend disabling training where offered. If you use model access provided by Adya, the provider acts as Adya’s sub-processor, is listed in our Sub-processor List, and is contractually prohibited from training on your data.

9.3 Connectors and other Third-Party Services

When you use a Connector to send data to or receive data from an external system (such as a CRM, email or messaging provider, data warehouse, or productivity tool), Adya transmits the data as you have configured. How that external system stores, uses, and shares the data is governed by your agreement with that provider — not by this Privacy Policy.

9.4 Adya’s role

For data flowing through Connected Models and Connectors, Adya’s role is limited to routing and orchestration; the destination provider remains responsible for what happens on its systems. See the Terms of Service and DPA for further detail.

9.5 Inventory of AI, profiling and analytics uses

Every use of personal data in AI/ML, profiling or analytics is recorded in our RoPA. The current inventory:

9.6 Automated decision-making

As Controller, Adya does not make decisions based solely on automated processing that produce legal or similarly significant effects on individuals (GDPR Article 22). Customers who deploy agents to make or support decisions about individuals are responsible for meeting the applicable rules; to support them, the platform provides configurable human-approval steps, logs of agent actions and the inputs used, and the ability to explain and contest outcomes.

9.7 Model and vendor governance

Before a model provider or AI vendor is enabled by Adya, we review its data-use, retention, security and transfer terms. New AI features that involve personal data go through a privacy review and, where processing is likely to be high-risk, a Data Protection Impact Assessment.

9.8 Service improvement

We may use aggregated and de-identified usage statistics (which do not identify you or reconstruct Customer Content) to improve platform performance and reliability.

10. Data Location and International Transfers

10.1 Region selection

Where the Services offer region selection, you may choose the region(s) in which your Customer Content is primarily stored. We honour the configuration you select.

10.2 Cross-border transfers

Account-level data and some operational data may be processed in other countries where we or our sub-processors operate. Where we transfer personal data internationally, we use lawful transfer mechanisms, including the EU/UK Standard Contractual Clauses and equivalent safeguards, and we comply with applicable cross-border transfer rules under the DPDP Act. Transfers are recorded in the RoPA.

10.3 On-premise and customer-cloud deployments

Customer Content remains in the customer’s environment and jurisdiction. Adya has no standing access; any support access is time-bound, approved by the customer, and logged.

11. Records of Processing and Data Inventory

Plain-language summary

We keep a living record of what personal data we hold, where it sits, why we have it, who it goes to, and when it is deleted.

11.1 Record of Processing Activities (RoPA)

Consistent with GDPR Article 30 and the accountability obligations of the DPDP Act, we maintain a RoPA in two parts: a Controller register (activities where Adya decides the purpose) and a Processor register (processing performed for each customer). Each entry records:

11.2 Data inventory

The RoPA is backed by a data inventory mapping personal data across our systems — [e.g., production database, object storage, data warehouse, logging and monitoring, CRM, billing, support desk, email].

11.3 Review cycle

The RoPA and inventory are reviewed every six months and whenever we launch a new product or feature, onboard a new sub-processor, or change how data is used. The RoPA is available to supervisory authorities on request, and the relevant processor entries are available to customers under the DPA.

12. Data Retention and Deletion

We keep personal data only as long as needed for the purposes in this policy, then delete or anonymise it. Our retention schedule:

12.1 How deletion works

Retention periods are enforced by scheduled deletion jobs aligned to the schedule above; data is removed from primary stores and ages out of backups on the rolling cycle. Individual erasure requests are logged as tickets, verified, and completed within statutory timelines. Where DPDP erasure timelines or category-specific deletion rules apply, we meet them, including advance notice to Data Principals where required.

12.2 Evidence of deletion

We keep a deletion log — request or trigger, data category, systems covered, date completed and who executed it — without retaining the deleted data itself. On contract termination we provide customers with written confirmation of deletion on request. Deletion jobs are monitored and their completion verified quarterly.

13. Your Rights

Depending on where you live, you have rights over your personal data. We honour these regardless of region, subject to verification and legal limits.

Requests are logged, tracked and answered within the timelines required by applicable law. Where we are a Processor, we pass the request to the relevant customer and assist them in responding.

14. Children’s Data

Plain-language summary

Adya is a business platform and is not for children. We don’t knowingly collect data from anyone under 18.

The Services are intended for businesses and professionals and are not directed to children. We do not knowingly collect personal data from individuals under 18. Consistent with the DPDP Act and its 2025 Rules, we do not knowingly process children’s personal data without verifiable parental consent, and we do not undertake tracking, behavioural monitoring, or targeted advertising directed at children.

15. Cookies and Similar Technologies

We use strictly necessary cookies to run the Services and — with your consent where required — analytics cookies to understand usage and improve the platform. Cookie choices are logged as consent events (section 7). We do not use cookies to build advertising profiles. You can manage non-essential cookies through our cookie banner, the “Cookie preferences” link, or your browser settings.

16. Security, Certifications and Assurance

16.1 Security controls

We apply technical and organisational measures including encryption in transit and at rest; least-privilege access control with multi-factor authentication for administrative access; tenant isolation; network protections; logging and monitoring; vulnerability management and annual independent penetration testing; secure handling of Model Credentials; vendor due diligence; and confidentiality obligations and privacy and security training for all staff. Details are in our Security Policy. No system is perfectly secure, but we work continuously to protect your data.

16.2 Certifications and independent assurance

Current status:

Where a certification is in progress, the controls it requires are already operating. Certificates, scope statements, the Statement of Applicability and audit reports are available to customers and prospective partners under NDA.

17. Data Breach Notification

If a personal-data breach occurs, we follow a defined and tested incident response process. Where we act as Controller, we notify the Data Protection Board of India and affected individuals within the timelines in the DPDP Rules 2025 and, where the GDPR applies, the competent authority without undue delay and where feasible within 72 hours. Where we act as Processor, we notify the affected customer without undue delay so it can meet its own obligations, and we support its response.

Amendments to This Policy