Privacy Policy
Project N Assignment Management System ("Project N", "we") helps supervisors, students and university leadership run projects phase by phase. This policy explains what we collect, why, where it is kept and the choices you have.
Who is responsible for your data
In an institution workspace, your university decides how Project N is used and is responsible for the people and project data in it. We process that data on its behalf. In a supervision workspace (independent supervisors), the workspace owner plays that role. Either way, we are responsible for running the service securely.
What we collect
- Account details: your name, email address, and a securely hashed password. We never store your password in plain text.
- Workspace and role details: the workspaces you belong to, your roles (for example Supervisor, Student, Head or Dean) and your faculty or department.
- Project data: phases, deadlines, submissions and their versions, reviews, comments, weekly updates and logged hours.
- The Activity Log: a dated record of actions on projects (who did what, in which role, and why).
- Security records: sign-ins, password resets, session changes and similar events, kept so we can protect accounts.
- AI usage: how much AI processing each workspace uses, so we can apply budgets.
Files stay in Google Drive
Submission files are stored in the Lead supervisor's own Google Drive, not on our servers. We use Google's limited drive.file permission, which only lets Project N see files and folders it created. It cannot read the rest of your Drive. We keep only file details such as name, type, size and a link. The access token for Drive is stored encrypted and is never sent to your browser.
If you sign in with Google, we only ask for your name, email address and profile picture.
AI feedback
When AI is turned on for a workspace and project, submitted files are sent to Google's Gemini API to produce feedback for students and a summary for supervisors. Files are held in memory only for that request and are not written to our disk or database; we store the feedback that comes back. We use Gemini's paid service, under which Google does not use the content to train its models. A workspace or project can turn AI off at any time.
Who can see what
Access follows your role. Students see their own group's project. Supervisors see the projects they supervise. Heads and Deans see projects in their department or faculty. Institution Admins manage structure and people but cannot open project content, and our platform administrators see workspace details and usage only, never project content.
Services we rely on
- Render runs our application server.
- Neon hosts our database, in the Singapore region.
- Google provides Drive storage, Google sign-in and Gemini AI.
- Resend sends our emails (verification, invites, reminders and review notifications).
- Encrypted backup storage keeps nightly database backups.
- Google Fonts serves the fonts on this website, so Google receives your IP address when the page loads.
We do not sell your data or use it for advertising.
Cookies
We use one essential cookie to keep you signed in. It is httpOnly (scripts cannot read it), only sent to our sign-in endpoints, and expires after 30 days without use. We do not use advertising or tracking cookies.
How long we keep data
We keep account and project data while your workspace is active. If your account or workspace is closed, we delete the data or anonymize it, apart from what we must keep for security or legal reasons. Backups roll off on their normal schedule. Activity Log entries cannot be edited by anyone, so that project history stays trustworthy.
Your choices and rights
You can update your profile in Settings. You can also ask to see, correct, export or delete your personal data. In an institution workspace, start with your workspace admin, since your university manages your account. You can always reach us through the Help Center in the dashboard.
Security
Connections use HTTPS. Every workspace's data is kept separate at the database level, sessions are short-lived, and sensitive tokens are encrypted. No system is perfectly secure, so please use a strong, unique password.
Children
Project N is built for universities and their staff and students. It is not intended for children.
Changes
If we change this policy in a meaningful way, we will update the date above and let workspace owners know.