Document Control
| Document | Privacy Policy |
| Data Controller | Shayr Omnichannel Private Limited (operating as Adya) — for account data |
| Applies to | adya.ai, the Adya platform (Vanij, GTM Agent, RAS), APIs and related services, across cloud, dedicated and on-premise deployments |
| Key regimes | India DPDP Act 2023 & Rules 2025; EU/UK GDPR; California CCPA/CPRA |
| Related documents | Terms of Service; Data Processing Addendum; Sub-processor List; Security Policy; Record of Processing Activities; Retention Schedule |
Contents
- 1. Introduction
- 2. Our Privacy Programme at a Glance
- 3. The Two Roles Adya Plays — Please Read First
- 4. Personal Data We Collect (as Controller)
- 5. How We Use Personal Data (as Controller)
- 6. Why We Are Allowed to Use Your Data (Legal Bases)
- 7. Consent and Notice Management
- 8. When We Share Personal Data
- 9. AI, Profiling and Automated Decisions
- 10. Data Location and International Transfers
- 11. Records of Processing and Data Inventory
- 12. Data Retention and Deletion
- 13. Your Rights
- 14. Children’s Data
- 15. Cookies and Similar Technologies
- 16. Security, Certifications and Assurance
- 17. Data Breach Notification
- 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
| Area | Our commitment | Section |
|---|---|---|
| Role clarity | Controller / processor role mapped for every deployment model (cloud, dedicated, on-premise) and every product, with a DPA on every customer relationship | 3 |
| Consent & notice | Consent responsibilities set out in every customer contract, with an optional consent schedule; versioned notices; withdrawal as easy as giving consent | 7 |
| AI & automated decisions | No training on Customer Content; every AI/analytics use mapped to data source and lawful basis; no solely automated decisions with legal or similarly significant effects | 9 |
| Records of processing | Maintained Record of Processing Activities (RoPA) and data inventory, reviewed on a fixed cycle and on every material change | 11 |
| Retention & deletion | Category-level retention schedule, automated deletion, and a deletion log that evidences every erasure | 12 |
| Security & assurance | Layered technical and organisational controls; independent certification and audit status disclosed | 16 |
| Accountability | Named Grievance Officer / DPO, privacy review for new features and vendors, staff training | 18 |
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.
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).
| Adya as Controller | Adya as Processor | |
|---|---|---|
| What data | Account, billing, device, and usage data we collect about you | Customer Content you submit and the data your deployed agents handle |
| Who decides how it’s used | Adya | You (the customer) |
| Governing document | This Privacy Policy | The Data Processing Addendum (DPA) |
| Example | Your email address used to log you in | A prospect list your GTM Agent processes |
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:
| Deployment | Hosted by | Account data | Customer Content | Contract |
|---|---|---|---|---|
| Adya Cloud (default) | Adya on GCP | Controller | Processor | Terms + DPA |
| Dedicated / single-tenant cloud (on request) | Adya-managed, isolated environment in a customer-selected region | Controller | Processor | Terms + DPA + deployment schedule |
| On-premise / customer cloud (on request) | Customer, on its own infrastructure | Controller (licence and support contacts only) | Customer Content stays with the customer; Adya has no standing access. Adya is a Processor only for data the customer chooses to share for support, for that purpose only | Licence + support terms + DPA covering support access |
3.2 Role by product
| Product | Personal data involved | Adya’s role |
|---|---|---|
| Vanij builder platform | Data customers connect to the agents, apps and models they build and deploy | Processor for Customer Content; Controller for builder account data |
| GTM Agent | Prospect and contact data, outreach content and engagement data, on customer instructions | Processor — the customer is controller of its prospect lists and outreach. |
| RAS (Research and Analysis Suite) | Documents and research data supplied by the customer; publicly available information retrieved at the customer’s request | Processor |
| adya.ai website and marketing | Visitor, lead and newsletter data | Controller |
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:
- Provide, operate, maintain, and secure the Services and your account;
- Authenticate you and prevent fraud, abuse, and unauthorised access;
- Process payments and manage your subscription;
- Provide support and respond to your requests;
- Analyse usage to improve platform performance, reliability, and features;
- Send service and security notices (these are not optional while you hold an account);
- Send product updates and marketing only where permitted, and always with an easy way to opt out;
- Comply with legal obligations and enforce our Terms.
- We do not sell your personal data.
- We do not use Customer Content to train, fine-tune, or improve AI models.
- We do not share your data with third parties for their own marketing.
- We do not make solely automated decisions about you that have legal or similarly significant effects.
6. Why We Are Allowed to Use Your Data (Legal Bases)
Where the GDPR or similar laws apply, we rely on: contract (to provide the Services you signed up for); legitimate interests (to secure and improve the Services, balanced against your rights); consent (for optional marketing and non-essential cookies); and legal obligation (to meet our compliance duties). Under India’s DPDP Act, we process personal data on the basis of your consent or the legitimate uses permitted by Section 7 of the Act. The lawful basis for each activity is recorded in our Record of Processing Activities (section 11).
7. Consent and Notice Management
Consent is anchored in contract. Each customer agreement sets out who is responsible for notice and consent, and customers can choose to add a consent schedule that defines exactly how consent is handled for their data. For our own account-level data, we capture consent at sign-up and in the product, and you can withdraw it at any time.
7.1 Contract-based consent model (customer and third-party data)
Our customer agreements — Terms of Service, order form and DPA — allocate consent responsibilities for personal data brought onto the platform:
- Standard position: the customer, as controller, is responsible for giving notices to and obtaining consent (or another lawful basis) from its users, prospects, employees and other third parties, and warrants that it has done so. Adya processes that data only on the customer’s documented instructions.
- Optional consent schedule: customers may elect to add a consent schedule to their contract. It specifies the consent and lawful-basis fields agents must respect, suppression and do-not-contact lists (for example, for GTM Agent outreach), how withdrawals and deletion requests are propagated across agent workflows and connected systems, and the consent and processing logs Adya exports to support the customer’s audits.
- Record of terms: each executed agreement, DPA and any elected consent schedule is held in the customer contract and DPA register (section 3.3) for the term of the relationship.
7.2 Consents we collect (as Controller)
| Purpose | How it is captured | Default |
|---|---|---|
| Account creation and acknowledgement of Terms and this Policy | Click-through at sign-up or signed order form, with links to the current versions | Required to use the Services (contractual basis) |
| Marketing emails and product updates | Separate, unticked opt-in at sign-up or in account settings — never bundled with acceptance of the Terms | Off |
| Analytics cookies | Cookie banner with granular accept / reject choices | Off until accepted, where consent is required |
| Case studies, testimonials, research participation | Specific request, agreed in writing | Off |
7.3 How consent is evidenced
Acceptance of the Terms and this Policy is recorded against the account with the date and the version accepted, or by the executed contract for enterprise customers.
7.4 Notice versioning
Each version of this Policy and of our contractual privacy terms carries a version identifier and effective date. Prior versions are archived, so we can show which terms applied to any customer or user at any point in time (see the version history in section 19). For material changes we re-notify users and customers and seek fresh consent where the law requires. Notices are available in English and, on request, in any language listed in the Eighth Schedule to the Constitution of India, as required under the DPDP Act.
7.5 Withdrawing consent
You can withdraw consent at any time, through the same or an equally simple route:
- Marketing — unsubscribe link in every email, or account settings;
- Cookies — “Cookie preferences” link in the website footer, or browser settings;
- Any other consent — email or contact the Grievance Officer (section 18).
Withdrawal is actioned within 2 to 3 business days. Processing on that basis stops and relevant sub-processors are instructed accordingly. Withdrawal does not affect processing carried out before it. For third-party data, withdrawals are handled by the customer as controller; where the customer has elected the consent schedule, Adya propagates them across agent workflows as that schedule specifies. Where applicable, we will accept consent given or withdrawn through a Consent Manager registered with the Data Protection Board of India.
8. When We Share Personal Data
We share personal data only as needed and never for third-party marketing. Categories of recipients:
| Recipient | Why | Safeguard |
|---|---|---|
| Sub-processors / service providers | Hosting, infrastructure, analytics, payments, support tooling | Due diligence before onboarding; contractual data-protection terms; listed in our Sub-processor List with advance notice of changes |
| Connected Model providers | When an AI model is used — prompts go to the provider you (or, where applicable, the configuration) selected | Your own credentials: your agreement with the provider. Adya-provided access: provider is our sub-processor, bound by no-training terms (section 9.2) |
| Third-party Connectors | When you connect or send data to external systems (e.g., CRMs, email providers, data tools) | Governed by your agreement with the destination provider |
| Affiliates | To operate and support the Services | Bound by equivalent protections |
| Legal / authorities | Where required by valid legal process or to protect rights and safety | Limited to what is legally required; notice where lawful |
| Corporate transactions | Merger, acquisition, or asset sale | Successor bound by this policy; you are notified of material changes |
9. AI, Profiling and Automated Decisions
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:
| Activity | Data source | Lawful basis | Profiling | Automated decision? |
|---|---|---|---|---|
| Product analytics and reliability | Usage and device data collected by Adya | Legitimate interests; consent for analytics cookies | Aggregate trends only; no individual profiles | No |
| Security, fraud and abuse detection | Connection, device and usage logs | Legitimate interests; legal obligation | Account-level risk signals | No — signals are reviewed by a person before any account action |
| Marketing to Adya’s own customers and prospects | Account data and stated preferences | Consent, or legitimate interests where permitted | Basic segmentation (e.g., plan, role, region) | No |
| Service-improvement statistics | Aggregated, de-identified usage | Legitimate interests | None | No |
| Customer-configured agents (e.g., GTM lead prioritisation, RAS analysis) | Customer Content | Customer’s lawful basis (Adya as Processor) | As configured by the customer | Customer decides; platform provides human-approval checkpoints |
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
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:
| Field | What it captures |
|---|---|
| Activity and purpose | What we do with the data and why |
| Data subjects and categories | Whose data, and which types (e.g., contact, usage, billing) |
| Source | Collected from the individual, from the customer, or from a third party |
| Lawful basis | Contract, consent, legitimate interests, legal obligation, or DPDP legitimate use |
| Systems | Where the data is stored and processed |
| Recipients and transfers | Sub-processors, Connected Models, transfer mechanism and destination country |
| Retention | Retention period and deletion method, linked to the schedule in section 12 |
| Security measures and owner | Key controls, and the accountable owner within Adya |
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:
| Data category | Retention period | At end of period |
|---|---|---|
| Account data | While the account is active + 1 to 3 months after closure only if agreed prior contractually | Deleted or anonymised |
| Billing / tax records | As required by law — typically up to 8 years under Indian tax rules | Deleted |
| Consent and preference records | Life of the consent + 1 years, as evidence (Only if agreed contractually prior to the engagement) | Deleted |
| Marketing data | Until you opt out or withdraw consent | Deleted; a minimal suppression entry is kept so we continue to honour the opt-out |
| Support tickets and correspondence | 6 months after the ticket closes | Deleted |
| Customer Content (Adya Cloud / dedicated) | Until you delete it, or contract end + 30-day export window | Deleted from primary systems; confirmation provided on request |
| Backups | Rolling; expire within 35 days | Overwritten |
| Agent execution logs | Minimum 30 days (configurable by customer) | Deleted |
| Security / audit and processing logs | At least one year where required by the DPDP Rules 2025 (Upon contractual agreement) | Deleted |
| On-premise deployments | Determined and controlled by the customer | Customer-controlled |
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.
| Right | What it means |
|---|---|
| Access | Get a copy of the personal data we hold about you |
| Correction | Fix inaccurate or incomplete data |
| Erasure | Ask us to delete your data, subject to legal retention |
| Withdraw consent | Withdraw consent where we relied on it, without affecting prior processing (section 7.4) |
| Portability | Receive certain data in a portable format (where applicable) |
| Object / restrict | Object to or restrict certain processing (GDPR) |
| Automated decisions | Not to be subject to solely automated decisions with legal or similarly significant effects (GDPR) |
| Nominate (DPDP) | Nominate another person to exercise your rights in case of death or incapacity |
| Grievance redressal | Raise a complaint and have it addressed within statutory timelines |
| No sale / no sharing (CCPA) | We do not sell or “share” personal information as defined by California law |
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
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:
| Framework | Status | Scope |
|---|---|---|
| ISO/IEC 27001:2022 (information security) | Certified | [e.g., Adya platform, cloud infrastructure and Bengaluru operations] |
| SOC 2 Type II | Certified | Trust Services Criteria: [Security, Availability, Confidentiality] |
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
- Any updates to this Privacy Policy will be communicated through the Application.
- By continuing to use the platform after changes are posted, you agree to the revised terms.
Adya