Legal
Effective Date: September 01, 2026 • Version: 2.0 — rewritten, children’s privacy, and device-permission disclosures for Play & App Store compliance.
Last Updated: September 01, 2026 Version: 2.0 (rewritten for Apple, Google Play, and DPDP Act alignment) Previous version: 1.0 — June 21, 2026. If we make material changes, the Last Updated date and version will change and we will notify you as described in §17.
This is version 2.0 from Sep 01, 2026. Big changes get a new date, version, and a notice.
Caresy is built and operated by Caresy Care Services Private Limited (“Caresy”, “we”, “us”, “our”) — a hospital companion service for families who cannot be physically present during a hospital visit. This Privacy Policy explains what personal information we collect, how we use it, how we share it, how long we keep it, and how you control it when you use caresy.co.in, our booking widgets, and our iOS and Android apps (collectively, the “Service”). Last Updated: September 01, 2026 • Version: 2.0 Company: Caresy Care Services Private Limited Website/App: caresy.co.in and Caresy (iOS bundle in.co.caresy.app / Android package in.co.caresy.app)
We are Caresy Care Services Pvt Ltd. This policy covers our website and apps and explains what we do with your data in plain language.
This policy applies to: • caresy.co.in, including booking, quick-help, and support pages • Caresy iOS and Android apps (including push notifications and live trip sharing) • Companion dispatch and support communications that run the Service It does not cover: • Hospital information systems, doctor notes, or pharmacy systems operated by hospitals — hospitals are independent controllers. • External links you tap outside Caresy. We are governed by Indian law, including the Information Technology Act, 2000 and the Digital Personal Data Protection Act, 2023 (“DPDP Act”). Where you are outside India, local law may also apply, but our primary processing is in India (§16).
Covers our site and apps. Doesn’t cover hospitals’ own systems or links you click outside Caresy. Indian law governs.
We collect only what we need to arrange and run a safe companion visit. We group it so a reviewer can map app behavior to this policy without guessing. — Information You Provide • Account details: full name, email (from Google/Apple sign-in or you type it), primary mobile number, address, and emergency contact you enter. • Patient & family details: patient full name, age, gender, language preferences, mobility needs (e.g., wheelchair), cognitive/language needs, and any health context you choose to share (symptoms, conditions, past reports you describe in text). • Service details: hospital name/branch, doctor name, department, ward/room, diagnostic appointments, pharmacy pick-ups, and time slots. • Health-related uploads (voluntary): photos of prescriptions, discharge summaries, reports, or other documents you choose to attach to a booking — including text visible inside those images. • Support messages: what you send to support via WhatsApp, call, email, or in-app chat, and any attachments. • Payment context: UPI handle or card reference passed to our PCI-DSS compliant processor — we do not store full card numbers or UPI PINs. — Automatically Collected Information • Device & log: IP address, browser type, device type, OS and app version, language, timestamps, pages/screens viewed, booking actions, error and crash reports. • Performance & analytics: anonymized performance data via Vercel Speed Insights (see §8) to improve load speed — not cross-app tracking. • Approximate & precise location: only if you select “At home” as the meeting point (we store latitude/longitude you confirm), and — during an active visit only — live trip coordinates shared on channel trip:<id> to your booking circle. We never collect ACCESS_BACKGROUND_LOCATION. • Cookies identifiers (§9): only on the website, to keep sessions and remember form progress. — Information from Third Parties • Authentication providers: profile name and verified email from Google or Apple when you sign in with them. • Verification partners: for companions, verification result (not raw document images in our long-term store) from UIDAI (Aadhaar) and AuthBridge (police clearance) — used once to approve activation. • Communications providers: delivery status for SMS/WhatsApp (via MSG91 and WhatsApp gateway) and push (via Firebase Cloud Messaging) — not your message content. • Hosting & platform: infrastructure logs from Supabase (database/auth/storage) and Vercel (hosting/edge) — see §7–8.
You give us booking details and any health notes/reports you choose to share. Your phone auto-shares basic device logs and — only if you pick “At home” — location for pickup + live trip. Sign-in and verification partners send us only what’s needed.
We use information only for these direct purposes: • Create and manage your account and sign-in (including Google/Apple OAuth). • Provide core features: match a patient to a suitable companion by language/needs, dispatch, coordinate with the hospital front desk, and share live milestone updates (arrival, registration, consultation, pharmacy, return). • Generate support responses and, if you use an AI-assisted feature (§6), generate helpful draft information. • Personalize logistics (preferred language, mobility needs) — not ads. • Process payments, handle refunds, and manage late-cancellation fees via secure processors. • Send booking confirmations, assignment alerts, live-trip updates, and essential service notices (notification permission, §10). • Provide support and troubleshoot issues you report. • Detect fraud, abuse, or misuse of the Service. • Comply with law and enforce our Terms. We do not sell personal data. We do not use health content for advertising or cross-app tracking.
We use your data to run bookings, dispatch companions, send live updates, handle payments, and keep the service safe — never to sell or advertise.
Read this before you type, paste, or upload anything sensitive. What may go into AI: • Anything you type or upload that you route into an AI-assisted feature: free-text symptom descriptions, care questions, notes you add for the companion, and text extracted from photos/reports you attach. If you do not use an AI feature, that content is handled as normal booking information only. Who processes it: • Caresy itself processes booking/health content to run the Service. If an AI-assisted feature is enabled, that content may be sent to a third-party AI provider to generate a response. Provider: TBD — will be named here before any generative-AI feature is made generally available (current companion dispatch does not rely on a third-party generative model for clinical diagnosis). Training: • We do not use your prompts, uploads, or booking content to train or improve foundation models. If we use an API-based AI provider, we will contractually require that provider not use Caresy API data for model training unless you explicitly opt in, consistent with that provider’s API data-use terms. We will update this clause if that changes and will not imply otherwise. Storage & deletion: • Conversation history from an AI-assisted feature, if stored, is tied to your account and is deleted when you delete your chats or your account (§14). Account deletion cascades to AI chat history. Do not paste government IDs (Aadhaar number, etc.) into AI chat — use the dedicated verification flow for companions instead. Safeguards: • Access is limited to authorized operations/support staff on a need-to-know basis (role-based access, logging). Data in transit is TLS-encrypted; at rest it inherits Supabase/Vercel provider controls (§11). We review AI prompts/logs for abuse and safety only. Limitations: • AI output is supportive information only — not a medical diagnosis, treatment plan, nursing judgment, or emergency advice. Always consult a qualified healthcare professional. If a response looks wrong or risky, tell the companion and contact support; do not act on AI content alone.
Anything you send into an AI helper (text or photos you choose) may be processed to generate a reply. We don’t use it to train models and we don’t let our AI provider train on it. AI replies are help, not medical diagnosis — always check with a doctor.
We share only as needed to run the Service. We do not sell data to ad networks or brokers. • Assigned companion: name, hospital/room, language/mobility preference, emergency phone — only logistics needed to perform the visit. • Cloud hosting & database: Supabase (Postgres, Auth, Storage) and Vercel (website/edge hosting, Speed Insights) — they host and deliver the Service and see only what is stored/sent to them. • AI provider (if you use AI features): the prompt/upload you submit and the generated reply, to return an answer — no other personal data by default. Provider: TBD (named in §8 when live). • Communications: MSG91 (SMS OTP), WhatsApp gateway, and Firebase Cloud Messaging (FCM) for push — they receive phone numbers/device tokens and message delivery metadata. • Identity verification (companions only): AuthBridge (+ UIDAI/DigiLocker path where used) — companion documents/photos for one-time approval. • Payment processor: PCI-DSS compliant UPI/card provider (TBD — named in §8; processor handles raw payment data, not Caresy). • Platform providers: Apple and Google to verify Sign in with Apple/Google and to deliver app updates via App Store / Play. • Legal & safety: when required by law, court order, or to protect rights, safety, or prevent fraud. • Business transfer: if Caresy is sold or merged, personal data may move with the business, subject to this policy and notice under §17. Sharing beyond this list does not happen without your clear consent.
We share only with the companion and the vendors that actually run the service: hosting (Supabase/Vercel), messaging (MSG91/WhatsApp/FCM), verification (AuthBridge/UIDAI), and payments — never sold.
What each external service does, what it receives, why we use it, and whether you can opt out. • Supabase (Postgres/Auth/Storage/Realtime) What: database, auth, file storage, and live trip channel (trip:<id>) Receives: account, patient, booking, trip coordinates you provide; device tokens for push Why: to store and run your bookings securely Opt out: no — core service cannot run without storage. • Vercel (Hosting + Speed Insights) What: hosts caresy.co.in and measures anonymized web performance Receives: IP, browser, pages, performance timings Why: fast, reliable website + performance improvement Opt out: you can block analytics cookies (§9) — core site still works. • Google & Apple (Sign-in) What: OAuth sign-in Receives: name/email you authorize with Google/Apple Why: secure sign-in without passwords Opt out: use phone OTP or email instead where offered. • Firebase Cloud Messaging (FCM) What: push notifications via Expo Notifications (POST_NOTIFICATIONS) Receives: device push token, title/body you expect to receive Why: booking/live-trip alerts Opt out: deny notification permission (§10) — other features keep working. • MSG91 + WhatsApp gateway What: SMS OTP and WhatsApp milestone updates Receives: phone number, message content you expect via SMS/WhatsApp Why: verify you and keep family updated Opt out: you can use email support, but booking updates will be slower. • AuthBridge / UIDAI / DigiLocker (companions only) What: Aadhaar + police verification before a companion is activated Receives: companion’s verification data/images you (as companion) submit Why: safety of patients Opt out: companions cannot be activated without this check. • Payment processor — TBD What: UPI/card processing (PCI-DSS, tokenized) Receives: payment reference your bank/UPI app shares (not full card number stored by us) Why: refunds/cancellation billing Opt out: TBD — cash/UPI-offline options where available. • AI provider — TBD (see §6) Opt out: do not use AI chat features; normal booking works without AI. If a stack item is “TBD” above, we have marked it so we do not invent a name. The table will be completed before the feature/processor is made live and the policy version will be bumped.
Each vendor is listed with what it gets and whether you can say no. TBD means we haven’t named the final provider yet — we won’t fake it.
Website (caresy.co.in) uses cookies; the mobile app does not. What we use: • Essential (required): session cookies to keep you signed in, remember booking form progress, and protect against fraud/CSRF. • Functional/performance (optional): remember preferences and, via Vercel Speed Insights, measure anonymized page load performance. What we do not do: no cross-app tracking, no advertising cookies, no selling of cookie data. Control: • You can block optional cookies in your browser settings and in our Cookie Banner (where shown). Blocking essential cookies may break sign-in and booking. You can also clear cookies anytime in browser settings. • App: uses device storage (Expo SecureStore, UserDefaults, FileTimestamp/SystemBootTime reasons disclosed in iOS PrivacyInfo.xcprivacy) — not cookies. More: see “CookieBanner” in the website footer and your browser’s Help page.
Website cookies keep you signed in and remember your booking draft. You can block optional ones in your browser; essential ones are needed to book.
We only ask for a sensitive permission when you use a feature that needs it. Every permission is optional — deny and Caresy still works, you just type instead — and you can revoke it anytime in system Settings. We show an in-app explanation before the system dialog. • Location — ACCESS_COARSE_LOCATION + ACCESS_FINE_LOCATION (Android); NSLocationWhenInUseUsageDescription + NSLocationAlwaysAndWhenInUseUsageDescription (iOS) Why: to set pickup coordinates if you choose “At home” as meeting point, and — during an active visit only — to share live trip on channel trip:<id> with your booking circle (family + assigned companion + dispatch). When: at booking creation if you pick At home, and while a live trip you started is active. Required?: No. Type an address instead. If denied: you manually enter address; no pickup geocode and no live map. Background: we explicitly do NOT use ACCESS_BACKGROUND_LOCATION — blocked via app.json blockedPermissions. No continuous background tracking. • Photos & Media — READ_EXTERNAL_STORAGE (Android, pre-Android 13); NSPhotoLibraryUsageDescription (iOS) Why: to attach a prescription/report from your library to a booking. When: only when you tap “Attach photo/report”. Required?: No. If denied: upload disabled; booking otherwise normal. • Camera — NSCameraUsageDescription (iOS); blocked on Android (cameraPermission: false in expo-image-picker) Why: on iOS only, to capture a new photo of a prescription/report. When: only when you choose “Take photo”. Required?: No. If denied: pick from library or skip. Note: policy text now accurately matches app.json — Android does not request CAMERA. • Notifications — POST_NOTIFICATIONS (Android); NSUserNotificationUsageDescription (iOS) Why: booking confirmations, companion assignment, milestone and live-trip alerts. When: after you grant permission and have an active booking. Required?: No. If denied: you still get in-app and WhatsApp/SMS updates where available. Revocation: Settings → Privacy → Location/Photos/Camera/Notifications → Caresy → toggle off. Denial only disables that one feature.
Location for home pickup + live trip (no background), photos/camera for reports (iOS camera only), notifications for updates — all optional, change anytime in Settings.
What we actually do — no perfect-security promises: • In transit: TLS/HTTPS for website, app sync, and API calls (Supabase TLS, Firebase TLS). • At rest: data stored in Supabase managed Postgres/Storage with provider-managed encryption; backups inherit the same controls. • Access control: role-based access — only authorized operations/support staff can see booking data; least-privilege and session checks for every API call. • Isolation: companion verification data is handled in a separate approval queue; companions see only logistics for their assigned visit, not your whole history. • Monitoring: infrastructure and auth logs, rate limits, and abuse detection. • Third-party processors: we choose PCI-DSS compliant payment and verified-identity vendors and require them to handle data securely. • Incident response: if we learn of a security incident affecting your personal data, we will investigate, contain, and notify you/and regulators where legally required. What this does not mean: no system is 100% secure. You also help by using device biometrics/passcode and not sharing OTPs.
Encrypted in transit and at rest, limited staff access, role-based controls, and vetted vendors — but no service can promise perfect security.
How long we keep things, and what happens after: • Active account & bookings: while your account is active and for 12 months after your last booking to help with rebooking and support. • Patient records & care logs: until you delete them or your account — see §14. If you keep the account, you can delete a single patient or report at any time. • Trip/live location: precise coordinates for the trip are kept for 30 days after drop-off to resolve disputes, then deleted or anonymized. Logs of milestone timestamps may be kept 12 months. • AI chat history (if you use AI features): until you delete the chat or your account — then permanently removed per §14. • Analytics/performance logs: aggregated/anonymized within 90 days; raw IP-logs rotated per provider default (TBD exact window). • Support tickets: 24 months for quality/audit, then deleted or anonymized. • Billing/tax invoices: anonymized statutory records retained up to 8 years under Indian law, then purged — this is the only personal-data exception after account deletion (§14). After deletion: personal data is removed from live databases and backups on the provider’s rolling purge cycle (typically within 30–60 days). Anonymized or aggregated data that cannot identify you may be kept for research/service improvement.
We keep bookings ~12 months, live location 30 days, support 24 months, invoices up to 8 years for law — everything else deleted when you delete your account.
Under the DPDP Act and applicable law, you can: • Access: ask what personal data we hold about you. • Correction: fix name, phone, address, patient details, or report attachments. • Deletion: delete a patient, report, chat, or your whole account (§14). • Withdraw consent: toggle off optional processing with the same ease as you gave it — turn off location/photos/notifications in Settings (§10) or withdraw marketing consent in the Cookie Banner/profile. • Export/copy (where offered): request a copy of your account/booking data in a common format. • Object/restrict: ask us to pause certain processing where legally available. • Complain: contact our Grievance Officer or email support@caresy.co.in — and you can approach the Data Protection Board of India where your rights under DPDP are concerned. How to exercise: • In product: Profile (correct phone/name), booking detail (correct booking), app/device Settings (permissions), and Cookie Banner (cookies). • By email: support@caresy.co.in from your registered email — we verify ownership and respond within 30 days (DPDP-style). Identity is checked via your signed-in account — we never use an ID in the request body. Withdrawing consent may mean we cannot fulfill an active booking that needs that data (e.g., no location after you denied it). We will explain at the time.
Access, correct, delete, withdraw consent, export where available, and complain — via the app/website or support@caresy.co.in within 30 days.
This is the dedicated, always-available way to erase your data — required by Google Play and Apple Guideline 5.1.1(v). No need to contact support. How to delete: • Web (recommended, works for Play/App Store reviewers): visit https://caresy.co.in/account/delete while signed in (Google or Apple), type DELETE, tap “Permanently delete my account”. Direct API: POST https://caresy.co.in/api/account/delete (authenticated — you can only delete your own account). • In the mobile app: Profile → Danger zone → Delete account → Continue → type DELETE → confirm (calls the same endpoint with your session token). • By email (if you cannot sign in): email support@caresy.co.in from your registered email with subject “Delete my data” + your registered phone number — verified via account email. What gets deleted: • Deleting auth.users permanently cascades to profile, patient records, saved locations, bookings, trips/live-tracking data, care logs, AI chat history, push tokens, and notifications. Companion assignments on past bookings become anonymized (companion_user_id → null) — companions’ own accounts are untouched. What may remain: • Only anonymized billing/tax invoices retained up to 8 years by law (§12). Nothing else is kept. Is it reversible? • No. After you confirm, you are signed out and personal data is not recoverable. If you sign up again, it is a new account. Timeline: • Web/app: immediate, typically within minutes, with on-screen + email confirmation. Email requests: within 7 days. Backups: purged on provider cycle within 30–60 days (§12). If deletion fails, contact the Grievance Officer (§18) — we will fix it within 7 days.
Delete instantly at caresy.co.in/account/delete or in the app (Profile → Delete → type DELETE). Everything erased immediately except anonymized invoices kept for law. No undo.
Caresy is not for children. The Service is for adults (family members) booking companion assistance, typically for elderly patients. • Minimum age: you must be 18 or older to create an account. We require Google or Apple sign-in via an adult account holder — children cannot create accounts alone. • When a patient is a minor (e.g., a young family member): by adding that patient you confirm you are the parent or legal guardian and that you consent to us processing that minor’s information only to provide the booked visit (name, age, hospital logistics as in §4). We collect the minimum necessary, use it only for dispatch/matching/live updates (§5–7), and never for marketing, profiling, or ads. • If we learn a child’s data was provided without proper guardian consent, we delete it promptly after notice to support@caresy.co.in. • Target audience declaration for stores: Adults/Families — not children. No child-directed design or content. If you are under 18, please use Caresy only with a parent or guardian.
18+ to create an account. If a patient is under 18, their parent/guardian must book and consent; otherwise we delete the data.
Primary processing is in India (Supabase — region TBD, expected ap-south-1 Mumbai; Vercel global edge may route requests via the nearest edge, which can be outside India for performance). Ancillary processors (e.g., Firebase Cloud Messaging, Google/Apple auth) may process limited data (device token, email/name you authorized) outside India/ your country. Where a transfer outside India is needed to run the Service (e.g., edge caching, push delivery), we rely on the DPDP Act’s conditions for cross-border processing and on our vendors’ contractual safeguards (encryption in transit/at rest and access controls, §11). Exact hosting region will be confirmed from Supabase/Vercel project settings and this clause will be updated from TBD to a concrete region — we will not guess. If you are outside India, your information may be processed in India and in the vendor locations described in §7–8.
Main storage is in India; website edge and push/auth may touch systems outside India to deliver the service. We protect transfers with encryption and contracts.
We will not hide changes. • For non-material updates (typos, clarifications, new TBD filled in): we update Last Updated/Version (§1) and publish at https://caresy.co.in/privacy. • For material changes (new data type, new sharing, new retention rule, new AI behavior): we also notify in-app and/or by email to your registered address at least 7 days before the change takes effect, so you can review and withdraw consent or delete your account if you disagree. • We never reduce your rights without your clear, affirmative consent consistent with DPDP notice/consent expectations. • The current version is always at https://caresy.co.in/privacy — older versions available on request to support@caresy.co.in.
Small fixes update the date. Big changes get 7 days’ in-app/email notice before they start.
Questions, requests, complaints, or deletion help — contact us in your preferred way. Company: Caresy Care Services Private Limited Support & Privacy: support@caresy.co.in — for rights, deletion, DPDP requests, and general support — replies within 24 hours Grievance Officer: Caresy Grievance Officer, Caresy Care Services Private Limited Postal: The Skyboat Affection, Paramount Emotions, Sector 1, Bisrakh Jalalpur, Uttar Pradesh 201318 Website: https://caresy.co.in • In-app: Profile → Help & support → Chat on WhatsApp / Call / Email Phone: +91 97175 00225 (also WhatsApp: https://wa.me/919717500225) We aim to acknowledge privacy/rights requests within 48 hours and resolve within 30 days. If you are in India and remain unresolved, you can approach the Data Protection Board of India.
Email support@caresy.co.in, call +91 97175 00225, or write to the Grievance Officer in Bisrakh Jalalpur.