Privacy
Notice Decoder, a SETU 2026 project by team Nova Nexus. Last updated 26 October 2026.
Your notices are read on your device
The text, PDF, Word file or photo you give Notice Decoder is read by code running in your own browser (or in the Chrome extension and Android app). Photos, PDFs and Word files are read on the device too; the first time, the reader files (about 10 MB) are downloaded to your browser and then work offline. The one exception is the AI check below.
AI check (optional, on by default, only when the rules are unsure)
When the rules cannot name an event well (for example they only found the word "Practical"), or the text came from a photo, the app sends the notice text and the events the rules found (title, type, date, time, venue) to our class server, which asks Anthropic's Claude Haiku model to suggest better names and types. Nothing else is sent: not your name, not your calendar, not your Google account. A notice the rules read cleanly is never sent. The answer can only rename an event or point at one the rules missed; dates and times always come from the rules, and every AI change is marked and can be undone. Our server caches the AI's answer (which quotes a few words of the notice) for up to 7 days, keyed by a fingerprint of the notice, so the same notice is not sent twice; the notice itself is not saved. Anthropic processes the text under its commercial terms (by default, API inputs are not used to train its models). Turn it off any time with the "AI check" switch under the notice box.
Google Calendar (optional)
If you press Add all to Google Calendar, Google asks you to sign in and allow Notice Decoder to
create a calendar called "Notice Decoder" and manage events in it (the calendar.app.created permission).
We use it only to add, update or undo the events you reviewed in that calendar, and nothing else: we cannot see your
other calendars or events, and we do not read your email. The
access token is kept in your browser for up to one hour (session storage) and is never sent to us. You can remove the
permission any time at myaccount.google.com/permissions.
Notice Decoder's use of information received from Google APIs adheres to the
Google API Services User Data Policy,
including its Limited Use requirements.
What is stored in your browser
- Settings such as "Add automatically" and "AI check", and the class you opened (so it is one tap next time).
- For a class representative: the class id and key for publishing.
- The events you added to a calendar from this browser (title, date, time, venue), so a new notice can be checked against them for clashes. Past events are dropped; "Clear them" under Clashes removes the rest.
- A short queue of reviewed events that could not be added while you were offline (the last 10), removed once they are added.
Clearing the site's data in your browser removes all of it.
Class calendar (optional)
If a class representative publishes events to a class calendar, those reviewed events (title, date, time, venue, link) are stored on our calendar service (Cloudflare) so classmates can subscribe, together with a short list of what changed and a few counters for the class console (how many publishes, revisions and cancellations, and which clashes were reported). The representative sees a preview and nothing is published until they press Publish. The class key lives only in the representative's browser; the server keeps a one-way hash of it. Anyone with the class link can see the class calendar, so do not publish anything private.
No ads, no tracking
There are no ads, no analytics and no tracking scripts in the app.
Contact
Questions or a request to remove a published class calendar: ankit25679@gmail.com.