ESENet

Legal

Privacy Policy

Working draft — not yet reviewed or approved by ESEN.

Sections marked Needs review describe something ESEN or legal counsel needs to decide, not something this platform has already settled. Everything else describes what ESENet actually does today, as built — not aspirational or invented policy.

What data ESENet collects

Depending on your account type, ESENet stores:

  • Everyone: your name, email address, and account role (student, company, or admin).
  • Students: profile photo and banner, headline, bio, skills, availability, LinkedIn URL, education, work experience, projects, certifications, and your CV file.
  • Companies: company name, website, description, logo and banner, and the profile of anyone your company invites or who is approved to join it as a team member.
  • Activity: opportunities you post or apply to, applications and their status history, posts, comments, likes, and any content report you file.

Why it's collected

Each of the above exists to run a specific part of the platform: your profile so companies and other students can find and evaluate you, your CV so a company you apply to can review it, applications and their status so both sides can track a hiring process, and posts/comments/reports to run the community feed and its moderation.

Needs review The exact legal basis for each category (consent, legitimate interest, contract, etc.) under whichever data protection framework applies to ESEN.

Who can see your data

  • Student and company profiles (name, headline, bio, skills, education, experience, projects, certifications, company info) are publicly readable — visible to anyone visiting ESENet, signed in or not. This is a real, current characteristic of the platform, not a hypothetical.
  • Your CV file is private: only you and a company you’ve actually applied to can access it, via a time-limited signed link — never a public URL.
  • An application’s message and status are visible to you and to the company you applied to, not to other students or other companies.
  • Feed posts, comments, and likes are visible the same way the rest of the feed is — publicly, unless a post or comment has been removed by its author or by an admin.

Needs review Whether student profiles being visible to fully anonymous, logged-out visitors (not just other ESEN community members) is the intended scope, or should be restricted to signed-in users only.

Data retention

Needs review How long each category of data is kept after it’s created, and how long after an account is deleted or goes inactive.

Account deletion

Students and company team members can delete their own account from their profile page. Doing so removes your CV, education, experience, projects, certifications, and profile photos, and signs you out immediately. Your posts, comments, and applications are not deleted outright — deleting them would also destroy other people’s legitimate records that reference them (a comment thread someone else is part of, a company’s own record of your application) — instead your name on them changes to “Deleted user”.

A company account that currently owns a company can’t self- delete yet — ownership transfer isn’t built, so an owner needs to contact ESEN directly to transfer or close their company first.

Needs review Whether posts/comments/applications should eventually be eligible for full removal on request (not just anonymization), and after how long.

Cookies

See the Cookie Policy for what ESENet actually sets today.

Third-party services

ESENet is built on Supabase, which provides the database, authentication, and file storage this platform runs on — every category of data described above is stored there. No other third-party service currently processes ESENet data (no analytics, no advertising, no separate email provider yet).

Your rights

Needs review What rights ESENet commits to (access, correction, deletion, export) and how someone actually exercises them, under whichever legal framework applies.

Contact

Needs review A real contact address or person at ESEN responsible for privacy questions.