Skip to main content

Aivry – Al agents for real business conversations

Aivry AI Product Use & Safety Addendum

 

Effective Date: 28 August 2026
Last Updated: 28 August 2026

This AI Product Use & Safety Addendum (“Addendum”) establishes additional requirements governing the use of certain artificial intelligence products provided by Adzura Media (OPC) Private Limited, operating under the brand name Aivry (“Aivry”, “we”, “us”, or “our”).

This Addendum currently applies to:

  • Halo, AI-assisted recruitment intelligence
  • Milo, AI-powered patient experience and healthcare communication
  • Atithi, AI-powered hospitality and guest experience

These products operate in environments where AI-generated outputs, automated communication or workflow actions may affect individuals. They therefore require additional safeguards beyond Aivry’s general Terms & Conditions and Acceptable Use Policy.

1. Purpose

Aivry develops artificial intelligence to assist organizations and their teams.

Our products are not intended to remove human accountability from decisions that materially affect individuals.

The core principle governing this Addendum is:

AI assists. Humans remain accountable.

The appropriate level of human oversight depends on the nature and potential impact of the AI-supported activity.

2. Customer Responsibility

Customers using products covered by this Addendum remain responsible for:

  • Their use of AI
  • Decisions made using AI-generated information
  • Information supplied to the AI system
  • Accuracy of customer-controlled knowledge sources
  • Appropriate human oversight
  • Staff training
  • Access controls
  • Required consent
  • Privacy compliance
  • Industry-specific regulatory requirements
  • Appropriate escalation procedures

Deployment of an Aivry system does not transfer the customer’s professional, operational or legal responsibilities to Aivry.

3. AI Output Limitations

Customers acknowledge that artificial intelligence systems are probabilistic.

Outputs may occasionally be:

  • Incorrect
  • Incomplete
  • Outdated
  • Inconsistent
  • Biased
  • Misclassified
  • Contextually inappropriate
  • Hallucinated

AI-generated output must therefore be treated as decision-support or workflow-assistance information, where appropriate, rather than unquestionable fact.

Higher-impact outputs require greater human oversight.

4. Human Oversight

Customers must maintain meaningful human oversight where AI output could materially affect an individual.

A human escalation mechanism should be available where:

  • A user requests human assistance
  • The AI cannot confidently respond
  • Information is contradictory
  • The request falls outside the approved scope
  • Professional judgment is required
  • A complaint or dispute develops
  • Safety may be affected
  • The AI identifies an exceptional or sensitive situation

Customers must not deliberately remove human oversight from workflows where applicable law or reasonable safety practices require it.

PART I: HALO

5. Halo Purpose

Halo is an AI-assisted recruitment intelligence and workflow system.

Halo may assist with:

  • Resume parsing
  • Candidate organization
  • Candidate analysis
  • Skills matching
  • Candidate scoring
  • Candidate ranking
  • Recruitment communication
  • Interview assistance
  • Recruitment workflow management

Halo is designed to support recruiters and hiring teams.

It is not designed to replace them.

6. Recruitment Decision-Making

Halo must not be treated as the sole authority for employment decisions.

Customers must not use Halo to autonomously:

  • Make final hiring decisions
  • Make final rejection decisions
  • Determine promotions
  • Determine termination
  • Determine compensation
  • Make other material employment decisions

without appropriate human review.

AI-generated candidate scores, classifications, rankings and recommendations are advisory.

Final decisions remain the responsibility of the employer or recruitment organization.

7. Recruitment Fairness

Customers must not intentionally configure Halo to unlawfully discriminate based on protected characteristics.

Recruitment decisions should not unlawfully discriminate based on characteristics such as:

  • Race
  • Ethnicity
  • Religion
  • Gender
  • Disability
  • Age
  • Sexual orientation
  • Other legally protected characteristics

Customers are responsible for ensuring that their hiring criteria are lawful, relevant and appropriate.

8. Candidate Scoring

Halo may produce AI-assisted candidate scores or rankings.

These scores:

  • Are not objective facts
  • May contain errors
  • May reflect incomplete candidate information
  • May reflect limitations in customer-defined criteria
  • May reflect limitations or bias within underlying AI models

Customers should review the underlying candidate information before making material decisions.

A candidate should not be automatically rejected solely because an AI-generated score falls below a particular threshold unless the customer has independently determined that the workflow is lawful and appropriate.

9. Candidate Data

Customers using Halo are responsible for ensuring they have appropriate authority to process candidate information.

Candidate information should only be used for legitimate recruitment purposes.

Customers must not use Halo to unlawfully:

  • Profile candidates
  • Infer protected characteristics
  • Collect unnecessary sensitive information
  • Share candidate information without authority
  • Retain candidate information beyond appropriate periods

PART II: MILO

10. Milo Purpose

Milo is an AI-powered patient experience and healthcare communication system.

Milo may assist healthcare providers with:

  • Appointment booking
  • Appointment confirmations
  • Calendar coordination
  • Patient reminders
  • Pre-appointment instructions
  • Follow-up communication
  • Patient enquiries
  • CRM updates
  • Administrative coordination
  • Patient communication workflows

Milo is intended primarily to support administrative and communication workflows.

11. No Autonomous Medical Decisions

Milo is not a doctor, medical practitioner or emergency medical service.

Unless expressly designed, validated and contractually approved for a particular regulated use, Milo must not autonomously:

  • Diagnose medical conditions
  • Prescribe medication
  • Recommend treatment as a substitute for a clinician
  • Alter treatment plans
  • Determine clinical eligibility
  • Interpret medical results as a replacement for a qualified professional
  • Override medical instructions
  • Make autonomous clinical decisions

Medical decisions remain the responsibility of qualified healthcare professionals.

12. Medical Information

Where Milo communicates healthcare-related information, such information should be derived from sources approved by the healthcare customer.

Healthcare customers are responsible for maintaining the accuracy of:

  • Doctor information
  • Procedure information
  • Appointment information
  • Pre-appointment instructions
  • Follow-up instructions
  • Clinic policies
  • Patient communication templates
  • Other healthcare information supplied to Milo

Aivry cannot guarantee the accuracy of information where the underlying customer-provided source is inaccurate, incomplete or outdated.

13. Emergency and Urgent Situations

Milo must not be relied upon as the sole mechanism for handling medical emergencies.

Healthcare customers should establish escalation mechanisms for situations involving:

  • Emergency symptoms
  • Serious medical concerns
  • Immediate safety risks
  • Requests for urgent medical advice
  • Requests for a doctor
  • Situations outside Milo’s approved scope

Where appropriate, Milo should direct users toward qualified healthcare personnel or relevant emergency services rather than attempting to resolve the situation autonomously.

14. Patient Data

Healthcare customers remain responsible for ensuring that patient information is lawfully collected and processed.

Customers should apply data-minimisation principles.

Milo should not be intentionally configured to collect sensitive patient or medical information that is unnecessary for the intended workflow.

Access to patient information should be appropriately restricted.

15. Human Handover

Patients should be able to reach appropriate human staff where necessary.

Human escalation should be available for situations involving:

  • Medical questions
  • Complaints
  • Conflicting instructions
  • Sensitive patient matters
  • Billing disputes
  • Appointment problems requiring judgment
  • Requests outside approved AI capabilities

PART III: ATITHI

16. Atithi Purpose

Atithi is an AI-powered hospitality and guest-experience system.

Atithi may assist with:

  • Guest enquiries
  • Concierge communication
  • Reservation-related assistance
  • Food and beverage requests
  • Housekeeping requests
  • Maintenance requests
  • Service coordination
  • Request routing
  • Request tracking
  • Guest follow-ups
  • Internal operational communication

Atithi is designed to improve communication and coordination.

The hospitality customer remains responsible for delivering the physical guest experience.

17. Operational Information

Atithi may rely on information obtained from:

  • Property-management systems
  • Booking engines
  • CRM systems
  • POS systems
  • Customer databases
  • Internal documents
  • Hotel staff
  • Customer-provided knowledge bases

Customers are responsible for maintaining accurate operational information.

Atithi should not intentionally represent information as confirmed where the relevant source system has not confirmed it.

18. Reservations and Availability

Unless confirmed by an authoritative connected system, Atithi should not independently guarantee:

  • Room availability
  • Reservation confirmation
  • Room upgrades
  • Rates
  • Offers
  • Restaurant availability
  • Service availability
  • Late checkout
  • Early check-in
  • Other inventory-dependent requests

Where integrations fail or information cannot be verified, the request should be escalated or communicated as pending confirmation.

19. Physical Service Fulfilment

An AI workflow action does not itself prove that a physical service has been completed.

Atithi should not represent a service as completed solely because:

  • A ticket was generated
  • A message was sent
  • A request was assigned
  • A workflow was triggered

where actual completion has not been confirmed.

This may apply to:

  • Housekeeping
  • Maintenance
  • Food delivery
  • Luggage assistance
  • Transportation
  • Room service
  • Guest amenities
  • Other physical services

20. Guest Safety

Atithi must not be treated as a replacement for hotel security, emergency personnel or trained hospitality staff.

Appropriate escalation should be established for:

  • Medical emergencies
  • Fire or safety incidents
  • Security concerns
  • Threats
  • Lost children
  • Serious guest complaints
  • Violence
  • Criminal activity
  • Other urgent situations

21. Guest Data

Hospitality customers remain responsible for ensuring that guest information is collected and processed lawfully.

Customers should avoid unnecessary collection of:

  • Identity documents
  • Financial information
  • Sensitive personal information
  • Authentication credentials

through general AI conversations unless specifically required and appropriately secured.

PART IV: COMMON SAFEGUARDS

22. No Deceptive AI Impersonation

Products covered by this Addendum must not be intentionally configured to deceptively impersonate identifiable real individuals.

Where reasonably appropriate, users should understand that they are interacting with an automated or AI-assisted system.

AI-generated voices must not be used to falsely represent themselves as a specific real person without appropriate authorization.

23. Sensitive Information

Customers should apply additional safeguards where AI systems process:

  • Candidate information
  • Patient information
  • Medical information
  • Guest information
  • Financial information
  • Identity information
  • Other sensitive personal information

Safeguards may include:

  • Access controls
  • Data minimisation
  • Logging
  • Retention controls
  • Encryption
  • Staff permissions
  • Human review

depending on the deployment.

24. Knowledge Accuracy

Customers remain responsible for maintaining accurate and current information supplied to Aivry products.

AI systems may rely on:

  • Customer documents
  • FAQs
  • Policies
  • CRM records
  • Databases
  • Websites
  • Uploaded files
  • Integrated software

Incorrect source information can result in incorrect AI output.

25. Automation Safeguards

Where Halo, Milo or Atithi triggers automated actions, customers should consider safeguards including:

  • Confirmation steps
  • Human approval
  • Input validation
  • Access controls
  • Rate limits
  • Logging
  • Error handling
  • Escalation
  • Rollback mechanisms

Higher-impact actions should have stronger safeguards.

26. Third-Party Integrations

These products may rely on third-party:

  • AI providers
  • Communication platforms
  • Cloud infrastructure
  • APIs
  • CRM systems
  • ATS platforms
  • Healthcare systems
  • Property-management systems
  • Booking platforms
  • Other software

Third-party services may experience outages, errors or changes.

Customers should maintain appropriate operational procedures for situations where connected systems are unavailable.

27. Monitoring

Customers should periodically review their deployed AI systems for:

  • Incorrect responses
  • Hallucinations
  • Bias
  • Failed escalations
  • Automation errors
  • Knowledge problems
  • User complaints
  • Integration failures
  • Unexpected AI behaviour

Aivry systems should not be treated as permanently self-correcting or maintenance-free.

28. Prohibited Uses

Products covered by this Addendum must not be used for:

  • Fraud
  • Phishing
  • Illegal discrimination
  • Harassment
  • Deceptive impersonation
  • Unlawful surveillance
  • Unauthorized data collection
  • Manipulation of vulnerable individuals
  • Illegal automated decision-making
  • Circumvention of professional oversight
  • Other activity prohibited under Aivry’s Acceptable Use Policy

29. Incident Reporting

Customers should promptly notify Aivry of material incidents involving:

  • Serious AI errors
  • Patient-safety concerns
  • Significant discriminatory output
  • Major privacy incidents
  • Unauthorized access
  • Significant automation failures
  • Serious guest-safety incidents involving AI interaction

Reports may be submitted to:

grievance@getaivry.com

30. Enforcement

Violation of this Addendum may result in:

  • Required corrective action
  • Restrictions on functionality
  • Suspension of integrations
  • Temporary suspension
  • Termination of services

Immediate restrictions may be applied where continued operation creates a material risk to:

  • Individuals
  • Patient safety
  • Privacy
  • Security
  • Aivry infrastructure
  • Third-party systems

31. Relationship With Other Policies

This Addendum forms part of Aivry’s broader governance framework and should be read together with:

  • Terms & Conditions
  • Privacy Policy
  • Responsible AI Policy
  • Acceptable Use Policy
  • Cookie Policy
  • Applicable Data Processing Agreements
  • Customer-specific agreements
  • Statements of Work

Where a customer-specific agreement establishes stricter requirements, those requirements will apply to that customer.

32. New Aivry Products

Aivry may introduce additional AI products over time.

Where a new product operates in an industry or workflow involving material individual impact, Aivry may:

  • Add that product to this Addendum
  • Introduce additional safeguards
  • Create industry-specific requirements
  • Establish separate contractual requirements where necessary

The introduction of a new product does not reduce the obligations applicable to existing products.

33. Changes to This Addendum

Aivry may update this Addendum to reflect:

  • New products
  • New AI capabilities
  • Regulatory developments
  • Industry requirements
  • New safety practices
  • Changes to existing products
  • Changes to underlying technology

The current version will be published on Aivry’s website with an updated Last Updated date.

34. Contact

Questions concerning this Addendum may be directed to:

Adzura Media (OPC) Private Limited
Operating under the brand name
Aivry

Flat No. 402, Pandit Rao Nilayam
East Marredpally
Secunderabad, Telangana – 500026
India

Email: grievance@getaivry.com