Privacy
Draft version 2026-10-23.ad-1 · updated 23 October 2026
Information collected
Account and role details, professional profile fields, employment preferences, consents, KYC evidence, applications, interviews, offers, messages and operational audit events are processed to provide the corresponding feature. Payment references and accounting records will be processed when real billing is enabled. Demo testing should use fictional information.
Purpose and permissions
Authentication, utility communications, optional marketing, profile visibility, profile photo, recruiter contact, recruiter chat, matching and document processing use separate purpose records where applicable. Optional marketing is not required. Profile visibility and contact/chat choices can be changed from the profile workspace.
Who can see your profile
Recruiters see only the information their membership, quota, applicant relationship and your current permissions allow. Unpaid previews remove names and contacts on the server. Anonymous photos are reduced and blurred before delivery. KYC documents are not placed in the public candidate directory. Internal team access uses role permissions and audit events.
Storage and security
Profile and KYC payloads, private documents and message bodies are encrypted at rest. Private documents and photos use authenticated, time-limited access. Access is checked again at retrieval. Session cookies, CSRF protection, rate limits and private-response caching rules protect application requests.
Providers and translation
WhatsApp/Meta authentication, real payment gateways and external message delivery are not active. English and Hindi product text is hosted locally. Other language choices provide Google translation of the public homepage or browser translation instructions; private profiles, documents and session links are not forwarded by JobIndia to Google. A third-party browser translation feature has its own provider terms.
Retention and deletion
Private demo account copies expire after 24 hours and the scheduled cleanup removes their dependent data; canonical fictional templates are retained for demonstrations. Real-account and document retention schedules, legal holds and deletion-review workflows must be approved before launch. Financial records may require retention under applicable law; a deletion request does not erase immutable accounting history automatically.
Your choices and requests
You can edit professional details, change visibility and availability, withdraw an application and change contact/chat or matching consent using the existing workspaces. Requests for access, correction, erasure and grievances will use the approved support process before public launch. Withdrawing consent can limit the related feature. Previously lawfully received copies may remain with a recruiter subject to their own legal obligations.
Cookies and changes
Essential session and security cookies support sign-in and forms. Language preference is stored in a cookie; theme preference uses browser local storage. External advertising trackers are not embedded. New providers, tracking or materially different data uses require an updated notice and applicable consent. This draft does not claim a completed privacy audit.
Social: additional information and purposes
Social processes professional/company identity, optional profile fields, named visibility and audience choices, posts/revisions, genuine relationship actions, approved encrypted chat, request decisions, receipts, reports and moderation/appeal records. Explicit current Social service acceptance is recorded separately from optional visibility decisions and historical hiring consent. Private company operator attribution is used for access control and audit, not displayed as the public company author. Social processing is not permission for unrelated AI training or advertising targeting.
Social: audiences and company operators
Supported audience choices will control social display. A voluntarily named Social profile is separate from an anonymous recruitment preview and cannot guarantee invisibility to every employer, secondary account or screenshot. Company operators may access company content and conversations only within their authority; their private login/audit identity is not the public company author. Profile visibility, a connection and private contact permission remain separate choices.
Private media conversion; proposed safety publication
Uploaded originals remain in private quarantine. Actual processed WebP bytes are encrypted into a separate database payload store with hashes and bounded chunks; feed metadata does not contain binary payloads. The uploader can privately inspect a processed preview. Required visual, OCR, QR and audio/video checks are unavailable, so current uploads are held and are not exposed to other members. Future publication must recheck exact content/revision and current audience, blocks, restrictions, deletion and expiry. Missing/failed checks do not create a safe verdict or automatic member penalty.
Social: presence and message confidentiality
Presence uses qualifying foreground heartbeats every 30 seconds with a 90-second online expiry, multiple-session/tab aggregation and current access checks. UTC activity is displayed in IST; coarse presence cache expires after at most 30 days without renewal. Peers see presence only under the approved-chat setting; hidden/unavailable is not proof of being offline. Delivered/read states require actual bounded recipient acknowledgements and respect read-receipt preferences; fetching alone does not mean read. Messages are encrypted at rest, not promised to be end-to-end encrypted. Staff receive only protected complaint evidence under narrow verified reviewer authority with audit; unrelated private conversations are not disclosed to a reporter.
Social: deletion, stories and copies
Stories are intended to stop being visible after the configured default 24-hour period even if cleanup is delayed. Visibility expiry is different from deletion from recovery copies or lawful moderation holds. Before activation, actual retention periods and removal jobs must be documented and provided to members. Removing a post or permission restricts future platform access but cannot recall screenshots or copies another person already legitimately received. Existing financial/legal retention obligations remain separate.
Social: preference changes and privacy requests
Social settings are intended to support current audience, presence/receipt, request, block and contact choices as those controls become available. Requests for access, correction, export or deletion require identity/authority checks and consideration of other members’ privacy. Optional permissions can be withdrawn without treating that as permission to delete another participant’s records or rewrite audit/financial history. Unavailable self-service options must not be presented as working.
Help and private support conversations
Help provides a private text conversation between the signed-in account and explicitly authorised verified support staff. It remains accessible when Social posting is restricted. Replies are genuine staff messages; an AI assistant is not connected and response times are not guaranteed. Peer approval rules do not prevent a member from contacting official support. Phone/contact sharing, attachments and government-ID uploads are prohibited in this chat; any requested appeal evidence belongs in its separate private process. Ordinary support conversations expire30days after the latest message; disposable demo conversations expire with the original24hour demo. Expiry is enforced on reads and scheduled deletion. Only authorised staff can use the separate support inbox; setup-only or simulated staff is not real authority.