Privacy Policy

What FenriX is

FenriX is a non-commercial community project built by students and academics. It is not a company, has no legal entity, sells nothing, and charges no fees. This policy explains, in plain terms, what data the project handles and why. Questions: hello@fenrix-ai.com.

The short version

The public site runs without analytics, ad trackers, or marketing cookies. Cohort games use team accounts, and running a fair competition means we keep an operations log: who signed in, who downloaded which dataset, and who submitted what, including network addresses. Everything we collect is listed below. We sell nothing and we share nothing for marketing.

What we collect

Site visits. This site is hosted on Vercel. Like most hosting providers, Vercel processes technical request data (such as IP address, browser type, and requested pages) in short-lived server logs to deliver the site and protect it from abuse. We do not use this data to identify visitors.

Contact and applications. If you write to us or submit a form, we receive what you send and use it only to respond.

Team accounts. Cohort games require a team account created with an instructor-issued key. We store the team name, the email address given at registration, a display name, a hashed password, and a record of the terms the team accepted at sign-up. Passwords are never stored in plain text. One account is shared by the whole team by design.

Competition operations log. When a signed-in team uses a cohort game we record the event, the timestamp, the IP address, and the browser identifier for: sign-ins, dataset downloads (including which file version), and submissions (including file name, size, and checksum). This log exists to keep the competition fair, to secure the platform, and to resolve disputes about who submitted what and when.

Submissions. Files and links a team submits for evaluation are stored so the instructor can evaluate them and keep a record of the cohort.

Cookies. Signed-in teams get one strictly necessary session cookie plus a marker that only switches the header label. No analytics cookies, no advertising cookies, no cross-site tracking.

Cohorts run by a course or school

A cohort is usually run by an instructor, course, or school. That instructor or school sets the participation rules and can see the cohort’s records: team accounts, submissions, scores, timestamps, and activity logs. The project uses cohort data only to run the game and keep it fair, and follows the instructor’s reasonable instructions. If your school treats participation as part of an education record, your school’s own policies govern that.

Why we handle it

We handle personal data to: run the site and cohort games; create and authenticate accounts; run competitions and evaluations; make datasets and submissions available; keep audit trails for fairness, security, and dispute resolution; answer messages; and prevent abuse. For users in the EU, EEA, UK, and Switzerland, this rests on your consent when you register and on the project’s legitimate interest in running a fair, secure educational game.

AI, evaluation, and automated processing

FenriX games may use software, algorithms, or AI-assisted tools to score submissions, compare outputs against evaluation data, detect duplicate or anomalous submissions, generate cohort analytics, and help instructors review results. These tools support educational evaluation and competition integrity. We do not use submitted files, strategies, or cohort records to train third-party foundation models. Where an automated score matters to a participant, the instructor makes the final call.

Where it runs

We use Vercel for hosting, Neon for the database, and Cloudflare for file storage. These providers process data mainly in the United States. If you are outside the United States, taking part means your data may be handled in the United States by these providers. We add no other providers without updating this page.

Retention

Operations logs are kept for 12 months, then deleted, unless a longer period is needed to handle a security issue or a dispute. Team accounts, grants, scores, and submissions are removed or de-identified about 6 months after the cohort ends, unless the instructor asks us to remove them earlier. Backups cycle out on our normal backup schedule. We may keep aggregated or de-identified data that no longer identifies a person or team.

Your rights

You can ask us to access, correct, delete, or export the personal data we hold about you, and to withdraw consent. Users in the EU, EEA, UK, and Switzerland have these rights under the GDPR and the Swiss FADP, including the right to complain to a data-protection authority.

How to ask. Write to hello@fenrix-ai.com. We may ask for enough information to find the right account. If your cohort is run by a course or school, we may pass the request to them or act on their instructions. We answer within the time the law allows.

Security and incidents

We use reasonable safeguards to protect data, including encryption in transit, salted password hashing, access controls, rate limiting, and limited internal access. No system is perfectly secure. If we learn of a security incident affecting personal data, we will look into it and tell affected people or schools where the law requires it.

What we do not do

We do not sell personal data. We do not share it for marketing. We do not profile visitors. We do not embed social media trackers or analytics.

Children and minors

FenriX is not directed to children under 13 and does not knowingly let children under 13 create accounts or submit personal data. Cohort games are meant for university-level education, professional training, or other instructor-led settings. Users under 18 may take part only with permission from a parent, guardian, school, or instructor. If we learn we collected data from a child under 13 without the required permission, we will delete it.

Changes

If our data practices change, this page changes first and the date above moves.