PRIVACY & GOVERNANCE POLICY

We collect explicit information provided directly by users when submitting application forms, including email address, GitHub profile URL, and technical area of interest.

All submitted forms undergo strict automated structural validation. Submissions lacking valid email formatting or normalized GitHub handle structures are automatically rejected before processing.

To prevent spam and data duplication, each applicant is restricted to a single submission. Duplicate email addresses and duplicate GitHub account handles are rejected automatically by server-side verification.

GREVIX strictly refrains from requesting or collecting government identifiers, financial details, passwords, or personal physical addresses during open application rounds.

For privacy protection, client browser inputs are automatically cleared from the local form DOM immediately following successful transmission to prevent unauthorized shoulder surfing.

Application data is stored exclusively in a secure, local structured file format (details.xlsx) located on local system hardware under administrator access.

Local spreadsheets are strictly registered in repository ignore rules (.gitignore). Confidential files are never tracked, committed, or pushed to public GitHub repositories.

Client-side browser inspect tools and web scripts cannot view stored applicant details. All storage logic is handled server-side, preventing exposure to external visitors or network sniffers.

GREVIX does not sell, rent, license, or trade candidate application records to commercial advertisers, marketing aggregators, or third-party data brokers.

Access to local candidate records is strictly confined to verified GREVIX core team members responsible for recruitment, interviewing, and project placement.

Submitted emails and technical interest descriptions are processed solely to evaluate suitability for open-source engineering tracks, hackathons, and technical workshops.

Email addresses are utilized to send interview invitations, onboarding instructions, and community project updates within a 14-day evaluation timeline.

GitHub profiles are reviewed to assess public commit activity, open-source repositories, and technical stack familiarity prior to team allocation.

Each valid record is appended with a precise timestamp and numerical identifier to maintain organized, auditable community rosters.

Server logs record operational transaction events to detect automated bot submissions, denial of service attempts, or abuse of recruitment endpoints.

Applicants retain the right to request verification of their recorded application data by contacting the core team via official community email.

If an applicant updates their email or GitHub handle, they may request manual amendment of their entry in the local application roster.

Applicants may request total removal of their information at any time. Upon verified request, all corresponding entry rows are permanently deleted from local spreadsheets.

Candidates may withdraw from community consideration without penalty, terminating all active communication and record retention.

Candidate records are retained for a maximum duration of 180 days, after which inactive application data is systematically archived or purged.

GREVIX operates without persistent tracking cookies, cross-site behavioral retargeting scripts, or commercial analytics pixels.

Static web assets, typography, and SVG icons are served cleanly without background user profiling or location tracking cookies.

Client browser local storage is strictly limited to non-sensitive session states such as UI view preferences and theme configuration toggles.

External links to Discord, GitHub, or social channels redirect users to third-party platforms governed by their respective independent privacy terms.

We do not employ canvas fingerprinting, audio context profiling, or device hardware telemetry to identify website visitors.

All network data exchanged between user clients and production endpoints is encrypted in transit using standard TLS 1.3 cryptographic protocols.

Backend services run under strict principal-of-least-privilege process controls with automatic input sanitization to prevent injection vulnerabilities.

In the event of an infrastructure security anomaly, system administrators will isolate affected endpoints and notify impacted applicants promptly.

GREVIX reserves the right to update this Privacy & Governance Policy to reflect evolving technical architecture or community governance requirements.

For privacy inquiries, erasure requests, or security reports, contact the core team directly via email at teamgrevixorg@gmail.com.