1. Who we are
ODS (Open Design School) is an online design school and studio platform at nidihub.org, run by the ODS team at the Industrial Design Centre (IDC School of Design), IIT Bombay. In this policy, “we” means that team, and “the platform” means the website and the tools you reach from it with the same sign-in.
This policy explains what personal data the platform keeps, why, where, for how long, and what you can ask us to do with it. It follows India’s Digital Personal Data Protection Act, 2023.
2. What this policy covers
One account opens all of these, and this policy covers all of them:
- The school: courses, lessons, your progress and the student dashboard.
- The community: profiles, groups, the activity feed, forums and private messages.
- The tools: GIDhub (code and project repositories), Design (Penpot), Sketch (Excalidraw), the AI assistant, and Ask, the course AI assistants in GID Studio and on lesson pages.
- The sign-in that connects them.
3. What we collect
When you get an account
Your username, your name, your email address and a password. Your password is stored only as a secure one-way code (a “hash”); nobody at the platform can read it. We also note which groups you belong to (for example, students of a course), because that decides what you can open.
When you learn
The courses you are enrolled in, the lessons you complete and when, and your progress.
When you choose display settings
If you tick “Save to my account”, we keep your display and reading settings (such as text size, spacing, focus mode, read-aloud and lesson language) with your account so they follow you to other devices. They describe how you like pages shown, not any condition. Teachers cannot see them. Untick the box to delete them; otherwise they stay in your browser only.
When you take part
What you choose to post or upload: your profile details, posts in the activity feed and forums, private messages, and the files you keep in the tools, such as repositories in GIDhub, designs in Penpot and drawings in Sketch.
If you offer a brief (Bring a brief, no account needed): your name, your e-mail address, your organisation if you give one, whose problem it is, and the problem in your own words. Only the Platform lead and the faculty read it, to decide whether it can become a studio brief; it is not published, shared or reused without your written agreement. To ask us to remove it, write to office@nidihub.org. To keep automated sending out, the form keeps a scrambled form of your network address for one hour, never the address itself.
If you are invited as a juror or an alumni reviewer: that you accepted the reviewer compact, when, and the conflicts you declared are kept with your role in that course; the course’s teachers see them. Where a teacher chooses a first reading with names hidden, the people judging see a hand-in without its makers’ names until they have written their own notes.
When you use the AI assistant
What you type and the answers you get, kept in your own chat history until you delete them.
When you use Ask
Ask sends only what you choose: your question and the conversation so far in that panel, the lesson you are on (with the minute of the lecture) unless you take it off, and a picture only if you add one. We do not keep your questions or the answers. The conversation stays in your GID Studio window or your browser tab, and is gone when you close it or start a new conversation. Our servers record that a question was asked, when, and how long the answer took, without your name and never what you wrote. To keep Ask fair and its cost limited, each person can ask up to 20 questions in 10 minutes and 200 a day; to count this, the server remembers when you asked (not what), in its memory only, until the end of the day. Ask is optional and off until you turn it on; every course can be followed without it.
When you work in the studio (GID Studio)
Your studio work is kept in your own private project on GIDhub, which you can open, download and delete. What goes there, and who else sees it:
- Your sketchbook and Easel drawings, with any voice notes you record inside them (the microphone listens only while you hold the button). You can choose to keep the sketchbook on your computer only.
- Pin-ups. When you pin a piece, it goes to your project and your course’s instructors can see it, with your name. Their marks and notes are saved beside it. Only what you pin is shown; nothing else in your project is.
- The class wall. A pin goes on the class wall only if you tick it (work handed in for a charrette always goes on the wall). Classmates and instructors then see the picture and your name, never the instructors’ marks. You can take it off the wall at any time; an instructor can hide it. Earlier versions stay in your project’s history.
- Saved Ask conversations, only if you choose “Save to my project”: one file per conversation, in your project alone.
- Precedents you collect, and pictures you bring from your phone with a scan code or the field kit. Phone links work once and for a short time (10 minutes for a scan, 3 hours for the field kit); what you send waits on our server only until your app collects it, then it is removed from there.
- Photos of people (field kit). A photo with people in it is accepted only with their faces blurred on the phone, or with a record of their consent (who agreed, how and when, and their spoken “yes” if you record it). The photos stay private in your project.
Teams. When an instructor forms a team, the team gets its own private project. Each member’s sketchbook is copied into it, and members see each other’s latest drawing. If a team is ended, its project is kept and members can still read it.
Who is in the studio. Off unless you choose “Count me” or “Show my name”. It is held only in our server’s memory for two minutes after you were last there, shown only to students of the course (not to instructors), and never written down.
Charrettes and extra time. A charrette’s brief and times are kept with the course. If you choose “more time” in your display settings, your own end time is later; only you see it. Extra time arranged by the institute is kept with your account without any reason, seen only by administrators, and you see it in your copy of your data.
Mentors. Mentors are invited and checked by the platform. You choose what to send a mentor; they see only that, and their replies are kept in your project.
Portfolio. Private until you share it. Sharing makes a link anyone with it can open (search engines are asked not to list it), showing your name, the course and the pieces you chose. You can replace the link or stop sharing. A picture you take out of your portfolio is deleted with its files. A certificate shows only facts (your name, the course, the dates) and can be checked only while you show it.
Adapting a course. A course’s instructors can let others adapt it. If you adapt one, your copy is in your own GIDhub account, and the course’s instructors can see that you adapted it.
On your own computer. GID Studio keeps your sign-in in Windows Credential Manager, and keeps your drawings, Desk pictures and a few recent pages so it works offline. “Sign out everywhere” removes your sign-in, the Desk pictures and the app’s browsing data; drawings kept on the computer stay there until you delete them. On a computer marked “Shared” in its settings, every sign-in asks for the password and everyone is signed out when GID Studio closes. Now and then the app asks our server whether a newer version exists; nothing about you is sent with that question, and a new version is installed only when you choose it.
When you ask for help, or ask your teacher
Help on a lesson is built into the page and sends nothing: opening it is not recorded, and nobody is told you looked. If you choose “Ask your teacher”, you write a private message to the course’s teacher in the course site’s messages. If you choose “Ask the class”, you post in the course’s forum, which the class and its teachers can read.
What your teacher sees. On their Teaching page, a course’s instructors see how many unread messages they have from students of that course, how many questions in the course forum have no reply, and the list of the course’s students by name and team. They never see the text of a message there (only in their own inbox), and nothing there shows how anyone works or ranks anyone.
Notices, briefs, hand-ins and juries
Each course keeps its notices, briefs, juries, lab jobs, hand-ins, feedback and jury notes, each with who made it and when. Each one reaches only the people it concerns, in their inbox (in GID Studio and at nidihub.org/inbox/):
- Notices and briefs go to the class: its teachers, teaching assistants, students and invited guests. Briefs and juries also go to the course’s invited jurors.
- A hand-in is the files you hand in and an optional note. It is kept privately on our server and can be opened only by you (or your team, for a team hand-in), the course’s teachers and teaching assistants, and its invited jurors. Each hand-in gets a receipt with the time, the file names and a fingerprint (SHA-256) of each file; an earlier hand-in is kept when you hand in again.
- Feedback and jury notes on a hand-in go to you (or your team) and the course’s teachers.
- Lab jobs go to you (or your team), the course’s teachers and teaching assistants, and the course’s invited lab staff; a cost the lab asks the teachers to approve goes to them and to you.
- “Seen” is kept for you alone, so that what you have opened is cleared on every device. Nobody, teachers included, is shown what you have read.
Assessment. Marks are kept in the department’s own records, not on the platform. A course’s teachers can note their own level for each criterion of a brief’s rubric, and a note, for their own reference; only the course’s teachers see it, never students. If a teacher asks for it, the AI gives its own reading of a hand-in against the rubric, with reasons. For that, the brief, its rubric, your note, the text files of the hand-in and up to four of its pictures are sent to OpenRouter (section 6); nothing is kept there. The reading is labelled as the AI’s, is kept beside the teacher’s notes and seen only by the course’s teachers, never by students, and never changes the teacher’s own levels.
When you are invited into a course
A course’s teacher can invite someone by e-mail to take part as a teaching assistant, juror, lab staff or guest, until a date they choose. We keep the e-mail address, the name and note the teacher gives, the role and the end date. The invitation link works once, for 14 days; we keep only a fingerprint of it. When you accept, the role is linked to your account, and it ends on its date by itself. If you have no account, you can make one (a username, your name, your e-mail address and a password); we send a link to confirm the e-mail address first. An account made this way reaches only its inbox and the courses it was invited to.
When we ask for your consent
We ask when it matters, about one thing at a time, in English or Hindi. On joining, you agree once that you have read how ODS uses your data and agree to the terms of use. Everything else is a separate choice: Ask asks once, the first time you use it, because your question goes to an AI service outside India; in each course, you choose whether your teachers may ask the AI to read your hand-ins; and a teacher may ask to show a piece of your work, or to use a crit as an example (only if everyone in that crit agrees). Saying no never changes your course or your grade, and the person who asked sees only your answer, never a reason. We keep a record of each answer: what it was about, your answer, the exact words you were shown (and in which language), and when. A change of mind is added as a new entry; nothing is rewritten. You see the whole record, and can withdraw any yes in one click, on the My consents page (nidihub.org/you/consents/, or Settings, You, My consents in GID Studio). The record is part of “Download a copy of my data”. For field trials of prototypes, consent is given on paper and kept by the institute; we keep only that the forms exist and where.
If you test ODS in its beta, or report a bug
Until 31 December 2026, ODS is in beta: a small group of invited testers tries it. If you join through a tester invitation, we keep that you are a tester, whether you try ODS as a student or as a teacher, and when you joined. The platform’s administrators see this list; it says nothing about what you do. Student testers are enrolled in a demo course and teacher testers become its teachers, so the people in that course see their names. Anyone who is signed in can report a bug: what happened, what you expected, where, and, when sent from GID Studio, its version. A report is kept with your name and seen only by you and the administrators; you see its state and any note the team adds. Please leave passwords and private details out of a report. Tester accounts and bug reports are kept until the end of the beta; then the team closes the tester accounts and deletes the reports. Before that, you can download a copy of your data.
E-mail from the platform
We send e-mail from office@nidihub.org for password resets, to confirm the e-mail address of a new account, for course invitations, for course e-mails from the course site, and a daily digest: once a day, from 6 pm India time, only if something new has reached your inbox. Our e-mails are plain text, with no pictures and no links that record whether you opened or clicked them. You can switch the digest off on your inbox page; everything in it stays in your inbox.
Automatically
A record of sign-ins, and technical logs (including your IP address) that the servers keep to run and protect the platform. For actions that change something (for example “pinned a piece”, “handed in”, “sent to a lab”, “adapted a course”), the records name the person and the time, never the content; requests to the AI are recorded without a name. The records and logs are kept for one year and then erased (section 7). We do not use analytics or tracking tools.
4. What we do not do
- We do not sell or rent your data.
- We do not show advertising, and we do not use advertising or analytics trackers.
- We do not use your data to build a marketing profile of you.
5. Why we use it
- To give you your account and one sign-in for every tool.
- To run your courses: enrol you, show your progress, and let your instructors see how you are doing in their course.
- To let you take part in groups, forums and messages.
- To keep the platform secure and working: preventing abuse, fixing faults, and restoring from backups when needed.
- To contact you about your account or your courses (for example, a password-reset link).
- To answer your questions with the course AI assistants (Ask). Their answers are marked as AI and can be wrong. No decision about you is made by AI: grades and assessment are always by people.
6. Who else can see it
Inside the platform
Other signed-in members can see your profile, your public group and forum posts, and your name next to them. Private messages are seen only by the people in the conversation. Instructors can see enrolment and progress in the courses they teach, and the hand-ins, lab jobs and replies of their courses as section 3 describes. People invited into a course see only what their role needs there. A small number of administrators can see account data when that is needed to run the platform.
Community and course pages are for signed-in members only; the course catalogue and course descriptions are public.
Services that help run the platform
| Service | What it receives | Where |
|---|---|---|
| Hostinger (hosting) | Everything on the platform, stored on the server we rent | Mumbai, India |
| YouTube, by Google (lesson videos) | Videos are embedded in YouTube’s privacy-enhanced mode: nothing is stored on your device when a page loads. When you play a video, YouTube receives your IP address and may store information on your device | Google’s servers |
| OpenRouter (AI answers for Ask, and readings of hand-ins a teacher asks for) | What Ask sends (see section 3), plus the passages from the course lectures found for your question, to produce an answer; and, only when a teacher asks for an AI reading of a hand-in, what section 3 lists for that | Outside India. OpenRouter, a US company, passes each request to one of the AI providers it works with, which may be in the USA or elsewhere. We allow only providers that keep nothing (zero data retention) and do not train on what they receive, and OpenRouter itself does not store prompts. |
| Hostinger Mail (email, sent from office@nidihub.org) | Your email address and the message, to deliver it: password resets, sign-up confirmations, course invitations, the daily digest and course e-mails | Hostinger’s mail servers. Hostinger is a company in Lithuania; its mail servers may be outside India. |
We share data with authorities only when the law requires it.
7. Where it is kept, and for how long
- Where: on the platform’s server in Mumbai, India, and in backup copies on IIT Bombay’s own equipment. The exceptions: Ask, where your question is processed outside India by OpenRouter’s providers to produce an answer and is not kept there or by us; an AI reading of a hand-in that a teacher asks for, processed the same way; and e-mail, delivered through Hostinger’s mail servers (section 6).
- Your account and what you created: for as long as your account exists. When an account is closed, its data is removed, except where we must keep something by law.
- Tester accounts and bug reports: until the end of the beta (31 December 2026), then removed.
- Backups: a full copy is made every night. The server keeps the last 7 and IIT Bombay keeps the last 14, so a deleted item disappears from all backups within about two weeks.
- Records and technical logs: kept for one year from when they are made, as India’s data protection rules require for security and accountability (DPDP Rules 2025, rules 6 and 8), readable only by the platform’s administrators, and then erased.
8. Cookies
The platform uses only the cookies it needs to work: to keep you signed in, to remember that you are signed in across the tools, and to protect forms against abuse; and, if you change display settings, one that carries them to GID Projects. There are no advertising or analytics cookies. Lesson videos use YouTube’s privacy-enhanced mode, so YouTube stores nothing on your device unless you play a video; if you do, it may (see section 6). Profile pictures are drawn by the platform itself; no picture is fetched from outside services such as Gravatar.
9. How we protect it
- All connections use encryption (HTTPS).
- One sign-in with strong password rules, and access to accounts only by invitation.
- Administrator access is limited to a few people.
- Nightly backups, copied off the server and test-restored every week.
No system is perfectly secure. If a breach affects your personal data, we will tell you and the Data Protection Board of India as the law requires.
10. Your rights
You can ask us to:
- tell you what personal data we hold about you and how we use it;
- correct or update it;
- erase it, including closing your account;
- withdraw consent for anything that relies on it (on the My consents page, in one click; this may mean you can no longer use part of the platform);
- nominate someone to act for you if you cannot.
A copy of your data: in GID Studio, Settings, You, “Download a copy of my data”. It gives your account details, your courses and progress, your posts, your saved settings and your GIDhub projects as files on your computer.
Erasure: when you ask us to erase your data or close your account, we remove your account and what you created from all of the platform’s tools within 30 days, and tell you when it is done. What stays, and why: records and logs, for the one year the law requires (section 7); and what you made together with others, such as replies in a forum discussion or work in a team project, stays for them, with your account removed and your name replaced by “former member” where the tool allows. Backups lose it within about two weeks.
You can change much of it yourself in your profile and account settings. For anything else, or to raise a concern, write to office@nidihub.org. We will reply within 30 days. If you are not satisfied with our answer, you can complain to the Data Protection Board of India.
11. Children
The platform is for people aged 18 or older, and everyone signing up confirms that they are. A student under 18 (for example a first-year student who is 17) can join only through their institute: the institute first obtains the verifiable consent of a parent or guardian, as India’s Digital Personal Data Protection Act and Rules require, and then makes the account. We do not track or monitor the behaviour of children, or show them advertising; we do neither for anyone.
12. Changes to this policy
When the platform changes in a way that affects your data (for example, connecting a new service), we will update this page and change the date below. For significant changes, we will also tell you when you next sign in.
13. Contact
Grievance officer: The Grievance Officer of ODS (a role), nidihub.org
Email: office@nidihub.org
Address: Industrial Design Centre, IIT Bombay, Powai, Mumbai 400076
Last updated: 12 October 2026