Effective September 9, 2026 · Updated September 9, 2026
This notice covers the SDM Residence Life Duty Portal, SDM Residence Life Budget Portal, and their public information website.
Bryce Nussbaum is the operator and institutional records custodian. For access, corrections, deletion inquiries, or privacy concerns, contact bryce.nussbaum.sdsmt@gmail.com. Send only a non-sensitive description; never send PINs, student narratives, medical details, identity documents, or financial records. A secure channel will be arranged when needed.
Duty processes staff identity, roles, buildings, availability, schedules, duty logs, rounds, and notification settings. Budget processes staff access, accounts, purchase and check requests, transactions, history, and reports. Free-text entries become part of these records.
Google Apps Script and Sheets provide processing and storage. The apps use the deploying account’s Google email identity for administration, Google mail services for operational notifications and PIN recovery, and Google’s spreadsheet export service for Budget workbooks. Staff use email and a portal PIN; signing in does not grant access to their personal Google files or inboxes.
Records are stored in Google Sheets; Apps Script also uses settings, caches, and logs. HTTPS and server-side role/account checks protect portal access. Authorized staff, approved notification recipients, report recipients, and Google’s service providers process information for these functions. Education-record disclosure requires consent or an applicable FERPA exception and legitimate educational need. The released duty calendar publicly shows dates, buildings, and assigned staff names—not private logs or budget records.
Google user data is used only for the described functions and permitted improvements, consistent with the Google API Services User Data Policy, including applicable Limited Use requirements. It is not sold or used for advertising, data brokering, credit/lending decisions, or training generalized AI/ML models. Transfers and human access must meet that policy’s consent and exception requirements.
Devices may retain email addresses, preferences, Duty sessions, and availability drafts. The portals do not save raw PINs in browser storage; browser password managers may save them. Use trusted devices. Spreadsheet sharing, exports, delivered emails, and provider backups have separate access and retention controls.
Institutional records follow the applicable SDBOR/South Dakota retention schedules and authorized disposition process. There is no blanket deletion period. Records are preserved while classification is unresolved or a legal, audit, litigation, or inspection hold applies. No automatic destruction schedule is enabled.
Duty blocks its legacy age-based purge. Budget retains prospective purchase correction/void history and archive/restore history for retained requests. Directors may purge an individual archived Budget request after documenting retention eligibility, disposition authorization, and hold review. The request and its internal archive history are removed from current app storage; a disposition receipt remains. Linked purchases and accounting history are unchanged. History and receipts remain in the shared workbook and are not immutable. Archiving alone does not authorize destruction. Controls do not cover every record, direct spreadsheet edit, Sheets version, email, export, or backup; separate copies require separate handling.
Requests are recorded, identity and authority are verified, and relevant records are preserved during review. Corrections remain traceable. Deletion requires satisfied retention/hold obligations and documented custodian authorization; a request does not guarantee erasure. Separate copies and provider recovery periods must also be addressed.
For education-record inspection or amendment, use the South Dakota Mines Registrar’s FERPA process, including its deadlines and hearing rights. Portal support does not replace that process.
This information site accepts no operational submissions, embeds no records, and has no added optional analytics. Google may process technical information under its Privacy Policy. Material changes to data use will be communicated, with consent when required; prior notices are retained. This notice does not replace institutional approval or certify legal compliance.