JobShield is operated by Gryvora Technologies Private Limited (“Gryvora”, “we”, “us”), with company website gryvora.com. This Privacy Policy explains how we process personal data when you use the JobShield product. Product/API hosting may use jobshield.co.in domains; the contracting entity is Gryvora.
We process personal data in India under the Digital Personal Data Protection Act, 2023 (DPDP Act) and, as applicable when rules are notified, the DPDP Rules. Electronic records and certain online activities may also engage the Information Technology Act, 2000. Insurance cover, when issued, is subject to the insurer’s terms and IRDAI-related disclosures from that insurer — Gryvora is not the underwriter and does not claim an IRDAI registration number in this app.
Depending on your journey: mobile number and account credentials; KYC identifiers and related records (e.g. PAN, address, name, UAN/EPFO employment history via our KYC provider); employer confirmation; payslip images and extracted salary/employer fields; work-email verification status; bank account details for claim payouts; nominee details; policy, premium, and payment metadata; support tickets; device/session data needed for security; and consent records (type, version, timestamp).
To create and secure your account; verify identity and employment; calculate premium and cover; process premiums and fees; handle claims and payouts; record consent; send service notifications; prevent fraud; improve reliability; and meet legal, tax, audit, and partner requirements. Purpose-specific consents (KYC, payslip, bank, claim, nominee, etc.) are collected in-app where required.
Where we rely on consent, we ask for clear, purpose-specific consent and record it with a policy version (currently shown in-app). You may withdraw consent by contacting us; withdrawal may limit or end features that depend on that processing (for example KYC or payouts). Other processing may be necessary to provide the service you request or to meet legal obligations — we describe this honestly and do not claim blanket “DPDP certification.”
We share data only as needed to run JobShield: KYC / identity and employment verification providers (e.g. Tartan and related EPFO/PAN services); payslip OCR/verification (e.g. Tartan); work-email verification providers; Razorpay (or successor PSP) for payments; insurer / insurance partners when cover is issued or for claim coordination; cloud hosting and security vendors; and authorities when legally required. Partners process data under their own terms and applicable law.
We keep account, consent, policy, payment, and claim-related records for as long as needed to provide the service and for insurance, tax, dispute, and audit purposes. Exact periods may vary by record type and legal requirements; we do not keep data longer than reasonably necessary for those purposes.
We use TLS (HTTPS) in transit, access controls, and encryption at rest on our cloud infrastructure for server-side data. Sensitive tokens on your device use platform secure storage. No method is perfectly secure; please protect your OTP and password.
You may request access to or correction of personal data we hold about you by emailing info@gryvora.com (or via in-app Support). Withdrawal of consent and deletion requests are handled case-by-case; we may need to retain certain records for insurance, tax, fraud prevention, or legal holds, and we do not yet offer full self-serve data-download or one-click erasure in the app.
For privacy questions, access/correction requests, or grievances about Gryvora’s processing of personal data in JobShield, contact: info@gryvora.com. You may also raise a ticket in-app Help & support. We aim to respond within a reasonable period. (Formal DPDP “Data Principal” grievance timelines and a named Grievance Officer designation should be confirmed with legal counsel before public marketing.)
JobShield is intended for adults eligible for the product (salaried members meeting our eligibility rules). It is not directed at children.
We may update this Privacy Policy. Material changes are tied to the consent/policy version in-app; re-acceptance may be required when that version changes.