Privacy Policy

1. Who we are

Rezint Tech operates Rezint Clinic Queue, a SaaS product for QR-based clinic check-in and live OPD queues. Rezint Clinic Queue is the product name. Rezint Tech is the legal/business identity.

2. What information we collect

Website information

When you browse public pages we may process standard technical data such as IP address, browser type, and approximate location via our hosting and analytics providers (for example Vercel Analytics / Speed Insights where enabled). This is used to keep the site working and to understand aggregate usage — not to build a patient file from the marketing pages.

Customer / clinic information

Clinic onboarding and contact forms collect name, clinic name, mobile, email, city, optional notes, and optional referral codes. Clinic profiles may include name, branding, hours, fees, doctor names, and similar operational details entered by the clinic.

Patient information processed by Rezint Clinic Queue

When a patient checks in at a clinic, the product may process name, mobile number, visit type, optional symptom or disease tags, queue status, and visit history the clinic keeps for follow-up. That information is collected inside the product for that clinic’s operations — not as a public company-website form for health records.

3. Purpose of processing

We process information to provide the queue product, onboard clinics, support accounts, prevent abuse, improve reliability, and communicate about the service. We do not sell patient data.

4. Data minimization

Patients and clinics should enter only what is needed for the visit or for running the queue. Optional fields can be left blank. Do not paste unrelated medical files into contact forms.

5. Data storage

Application data is stored in Firebase / Google Cloud services configured for this product. Public website hosting may be on Vercel or similar. Storage location follows those providers’ regions as configured for the project.

6. Data retention

Queue and history records are kept as needed for clinic operations and product features (including follow-up / past care where the clinic uses them). Contact leads are kept for onboarding follow-up. We do not currently promise an automatic timed wipe of all visit history.

7. Access control

Visit data is visible to authorized staff of that clinic and to Super Admin for support and platform operations. Role permissions limit what staff can change. See the Security page.

8. Security

We use HTTPS in production, Firebase authentication, and role-based Firestore rules. No method of transmission over the internet is completely secure.

9. Third-party service providers

Hosting, database, authentication, file storage, analytics, and email/phone networks process data only to run the service. We may disclose information if required by law.

10. Data deletion / request process

Clinics can update or remove staff accounts they control from the dashboard. Patients should first ask the treating clinic about their visit record. For a deletion or access request to Rezint Tech, email us with enough detail to identify the clinic and the request (we may need to verify you are authorized). We will not silently delete another clinic’s records on an unverified email.

11. Consent

Patients who check in provide the details needed to join that clinic’s queue. Clinics are responsible for telling patients how the clinic uses visit information. Product consent screens for ABDM health-information exchange are not claimed as live until that integration is actually shipped.

12. Healthcare / ABDM integration

Rezint Clinic Queue has been submitted for ABDM Sandbox integration and is undergoing integration/testing. We do not claim ABDM certification or production health-lockers/HIE as live features today. See ABDM Integration.

13. Health-information sharing

Today, sharing is within the clinic’s authorized users and infrastructure providers. Cross-facility ABDM exchange will follow official consent and API rules if and when that integration reaches production. We will not describe it as available before it is.

14. Children

Guardians may book tokens for minors. Do not enter unnecessary sensitive details beyond what the clinic needs for the visit.

15. Policy updates

We may update this policy. The “Last updated” date at the top will change when we do.