NEXUS · November 2, 2026

Privacy Policy

Editable draft for owner and qualified legal review. Data practices and retention periods must be verified before publication. This document is not a compliance guarantee.

1. Operator and contact

Controller/operator: [OWNER LEGAL NAME AND ADDRESS]. Privacy contact: [VERIFIED PRIVACY CONTACT]. Supply verified details before launch.

2. Information currently used

NEXUS account creation uses a name, username, email address and a password hash. Profiles may contain a biography, skills, interests, goals and collaboration preferences. The service also processes connections, projects, collaboration requests, posts, comments, reactions, saved items, opportunity listings and applications, private messages, notifications, preferences and user reports. Session tokens are issued in an HTTP-only cookie; only a hash of the session token is stored in the database. Never put a password or session token in profile content.

3. Purpose and sharing

Information is used to authenticate members, display profile information according to selected visibility, operate collaboration features and protect the service. Private messages are intended for their participants. The owner must document any processors, hosting and cross-border data transfers after reviewing the actual deployment.

4. Retention and deletion

Members can request account deletion in Profile & settings by confirming the current password and entering DELETE MY ACCOUNT. This removes credentials, sessions, identifying profile data, authored posts/comments/messages, connections, sent applications and saved items. Projects they own are archived so current team members retain shared work; their opportunity listings are closed. Notifications sent to other members are anonymized. Some de-identified project and audit associations may remain to preserve collaboration history. The owner must set retention periods and review this behavior before launch.

5. Security and children

NEXUS uses password hashing and server-side access checks, but no online service can promise absolute security. The operator must set age eligibility, child-safety controls and breach-response procedures before launch.

6. Rights and legal review

Applicable access, correction, withdrawal, grievance and other data rights depend on jurisdiction. Obtain review under applicable Indian privacy and data-protection laws and other operating jurisdictions. Update this draft to match actual vendors, tracking, storage, retention and operational practices.

Last updated: November 2, 2026. Owner review required.

Back to NEXUS