LockIn is run by Affaan Ahmad, an individual based in Pakistan. It is not a company. Questions about your data go to contact@lockinapp.tech.

LockIn asks Google for read-only access to four things, and nothing else. It cannot post, submit, grade, edit or delete anything in Classroom, because it never requests permission to.

• Your course list, including course names and the section label the teacher set.
• Coursework in the courses you choose to track: titles, descriptions, due dates and links.
• Course topics, used to group work.
• Your own submission state, so work you have already turned in stops appearing as outstanding.

The submission data Google returns also contains your grades. LockIn discards them on arrival and has no column to store them in. No part of the product reads or shows a grade.

• Your email address and Google account identifier, to identify your account.
• Your section, programme code, batch and any alternative spellings you add, which is what the section matching runs on.
• Your time zone, which decides when a deadline counts as due today.
• Course names, sections and state for the courses Google shows you.
• Coursework titles, descriptions, due dates and links for the courses you track.
• Whether each piece of work is turned in, and whether it was late.
• What LockIn decided about each assignment, the section evidence it found, and how confident it was.
• Your own decisions: which courses to track, which assignments are yours, and what you have hidden.
• Your Google access and refresh tokens, encrypted.
• A history of sync attempts and any errors, used to tell you how current your data is.

When LockIn decides an assignment is not for your section, it stores the reason: which section labels it found in the post and how it read them. That record exists so the decision can be explained to you and corrected, rather than being an unaccountable judgement about your coursework. It is also what makes the “Review” screen able to show you why it was unsure.

Nobody buys it, and it is not used for advertising, profiling or training any model. Three providers necessarily process it in order for the product to run:

• Google, which is the source of the coursework and handles sign-in.
• Supabase, which hosts the database and the authentication service.
• The hosting provider that serves the application and its request logs.

Your data is never shared with your teachers, your university, or other students. LockIn reads Classroom as you, and shows the result only to you.

Settings has two separate controls. Disconnecting Google revokes LockIn’s access and deletes the stored tokens, while leaving the coursework already imported in place, so nothing updates but nothing disappears. Deleting your account removes the profile, courses, coursework, submission records, classifications and every decision you have made, and revokes the Google grant.

Account deletion is immediate and cannot be undone. It is not a request queue and there is no recovery window.

Settings has a link that downloads everything LockIn holds about you as a single JSON file: your profile, your courses, every assignment it has read, and the decision it made about each one along with the section evidence behind that decision.

Your Google tokens are deliberately not included. They are credentials rather than information about you, and putting a live key to your Classroom account in your downloads folder would be a worse outcome than omitting it.

Coursework and your decisions are kept until you delete your account or stop tracking the course.

Sync history is kept for 90 days and then deleted, except for the most recent attempt and the most recent successful sync, which are retained so LockIn can still tell you how current your data is.

Google tokens are encrypted before they are stored, and the table holding them is unreadable through the public API by any client, including your own. Every other table is protected by database-level row security, so one student’s query cannot return another student’s rows even if the application asks for them.

No system is secure in an absolute sense and this page does not claim that. To report something, write to contact@lockinapp.tech.

LockIn is built for university students and is not directed at children. If you believe a child has created an account, write to contact@lockinapp.tech and it will be deleted.

This page changes when the product does. Because it is written from the database schema, a change to what is stored is a change here.