Privacy Policy

The Department of Artificial Intelligence & Data Science, SRM Valliammai Engineering College, S.R.M. Nagar, Kattankulathur – 603203, Chengalpattu District, Tamil Nadu, India, organises Altruixx 2K26 and decides how the information described here is used. Under India's Digital Personal Data Protection Act, 2023, the department is the Data Fiduciary and you are the Data Principal.

Every question, correction and deletion request on this page goes to contact@altruixx2k26.app.

To sign in: your email address. We send a six-digit code to it and never ask you for a password. That address is also where your confirmation goes.

About your team: the team name, your college, whether you are an internal or external team, and the events you enter. For INNOVIX, the abstract document you upload.

About every member: full name, phone number, register number, year of study and department. The team lead additionally provides an email address; we do not ask teammates for one.

If your team pays — external teams only: the screenshot of your transfer, the UTR or transaction reference on it, the amount, and the payee name and amount our software reads back out of that image.

Automatically: standard web request logs from our host, and a counter that limits how often sign-in codes can be requested. That counter stores a one-way hash of your email address and IP, never the address itself, and is cleared daily.

Names, register numbers, years and departments print your certificates, and are how the desk confirms on the day that the people in front of us are the team that registered. Register numbers also stop the same student being entered by two different teams.

Phone numbers and the lead's email are how coordinators reach a team about a venue change, a delayed round, or a problem with a submission.

The payment screenshot and its transaction reference are the only evidence available to us that a transfer happened — we have no access to the college bank account, so a person reads them. That same reference is what makes it impossible for one payment to be claimed by two teams.

We do not sell your information, we do not use it for advertising, and we do not share it with another college, a sponsor or any company.

In a Supabase project hosted in the ap-south-1 (Mumbai) region: a Postgres database plus two private file buckets, one for abstracts and one for payment screenshots. Neither bucket is public. Each time an organiser opens a file, a link is generated on the spot and stops working sixty seconds later.

The website runs on Vercel, which keeps ordinary request logs. Confirmation emails are delivered through Resend.

Payment screenshots are also sent, at the moment you upload one, to OCR.space — a text-recognition service outside India — which reads the amount, the payee and the transaction reference so that you do not have to type them. The image is transmitted for that one purpose. If you would rather your screenshot were not processed this way, tell a coordinator and we will verify your payment by hand instead.

Named student organisers and faculty coordinators of the department, each of whom has to be added to an access list by hand before their account can open the admin console. There is no shared login and no general 'admin' account.

No participant can read another participant's registration. That is enforced by the database itself, not by hiding pages in the interface — a signed-in participant who asks the database for every registration receives their own and nothing else.

Volunteers at the check-in desk see only the team in front of them: names, events, and whether payment is confirmed. They do not see payment screenshots.

Payment screenshots, and everything our software read out of them, are deleted within 30 days of the event — by 28 September 2026. They exist to verify one transfer and serve no purpose afterwards.

Registration and participant records are kept until the end of the current academic year, so that certificates, results and any dispute about them can be settled, and are then deleted.

An encrypted copy of the database is taken weekly as a safeguard against data loss. Each copy is destroyed after seven days, and none can be opened without a passphrase held by the organising team.

Abstracts submitted to INNOVIX are kept for the same period as registration records and are read only by that event's judges.

You may ask for a copy of everything we hold about you, ask us to correct anything that is wrong, and ask us to delete it. You may withdraw your consent at any time, though we cannot keep a registration active without the details above.

Write to contact@altruixx2k26.app from the address you registered with, or tell any coordinator. We will respond within 30 days. A deletion request made before the event will be treated as withdrawing your registration; one made afterwards will not remove your name from certificates already issued or results already published.

If a team lead registered on your behalf, you may make any of these requests yourself — you do not have to go through them.

Sign-in is by one-time code, so there is no password of yours for us to lose. Who may read which record is decided by the database rather than by the application. Uploaded files are checked by their contents rather than their name. Keys and credentials never reach your browser.

None of that makes a system unbreakable, and we would rather say so than imply otherwise. If you believe your information has been exposed, tell us at the address above; we will investigate and tell everyone affected.

One cookie, set when you sign in, which keeps you signed in and remembers nothing else. No advertising cookies, no analytics, no cross-site trackers anywhere on this site. Signing out removes it.

If what we collect or how long we keep it changes, this page changes on the same day and the date at the top moves with it.