This overview distinguishes the public demonstration website from a production healthcare deployment. Ask for evidence and agreed controls for your specific service before transferring patient information.
1. The public website
The public site serves pages, local typefaces, images and a prerecorded audio demonstration. It has no patient accounts, live microphone capture, payment form, embedded calendar or public medical-record upload. Its scripts do not include advertising or analytics trackers.
The sample interfaces contain illustrative workflow data. They are not live patient records or a production control panel. Business contact links open your email application. Please keep those enquiries free of health information and credentials.
2. Evidence to request for a deployment
A healthcare team should review the exact system it proposes to use, including hosting, telephony, speech processing, AI providers, integrations and staff access. Ask for the data flow, responsible contacts, processing countries and current subprocessor information in a form your organisation can assess.
Confirm which features are available, which controls are configurable, and which depend on a third party. This page does not assert ISO 27001 certification, SOC 2 attestation, DPDP certification, India-only hosting or an independently verified security audit. Any such representation must be supported by current evidence and its actual scope.
3. Access and data protection
Agree how staff identities are verified, how accounts are granted and removed, whether multi-factor authentication is supported, and who can view or export recordings. Restrict permissions to the information needed for the assigned role, and determine how actions are logged and reviewed.
Obtain details of encryption during transmission and storage, key management, backup protection and separation between customer environments. These are assessment areas, not unverified promises about a particular production environment. Customer systems connected to the service also need appropriate protections.
4. Retention, resilience and incidents
Set separate retention rules for audio, transcripts, summaries, operational logs and backups. Establish deletion and export processes, including what happens at contract termination and how a clinic handles a patient request.
Document service hours, outage handling, call fallback, backup and recovery arrangements, and a human owner when an automated step fails. The written agreement should specify incident reporting contacts, notification responsibilities and response expectations under applicable Indian requirements. A public demo is not a service-level commitment.
5. AI and workflow safeguards
Use clinic-approved administrative content, test language comprehension, and review failed or uncertain conversations. Clinical decisions remain with qualified professionals. Confirm that scheduling acknowledgements reflect an actual accepted booking and that a failed write-back creates a staff follow-up task.
Agree provider restrictions on model training and secondary use of patient information. Avoid sending unnecessary health details to calendars, general chat tools or shared messaging channels. Each destination needs its own suitability review.
6. Reporting a security concern
Email sales@swarelic.com with “Security report” in the subject. Include the affected public page, a short description, approximate time in IST, and safe steps to reproduce the issue. Start with a non-sensitive description if you need a secure exchange.
Do not include patient data, passwords, access tokens or another person’s information. Do not disrupt services, access accounts without permission or carry out intrusive testing. This reporting route does not grant authorisation to test systems or promise a bounty.
7. Related documents
The Healthcare Data Notice explains patient-workflow responsibilities. The Privacy Policy explains business enquiries and website information. For a proposed deployment, request the relevant contractual and technical documentation through the published business contact.