Privacy policy
TagBook is device inventory and checkout software for school districts, operated by SC Networks LLC ("SC Networks", "we"). This policy explains what information TagBook handles, why, and how it is protected. It covers the TagBook service at tagbook.net and its district sites (such as yourdistrict.tagbook.net).
Whose data it is
Each school district that uses TagBook gets its own TagBook site and its own separate database — no district's data is stored with another's. The district decides what information goes into TagBook and who can see it, and the data belongs to the district. We process it on the district's behalf, under its direction, only to provide TagBook to that district, and a district can make that a contract by signing a student data privacy agreement with us (in Wisconsin, the Wisconsin Student Data Privacy Agreement; elsewhere, the National Data Privacy Agreement). Questions about information a school holds about you or your child — including requests to see or correct it — should go to the school district, and we help the district answer them.
What information TagBook handles
- When staff sign in with Microsoft or Google: the name and email address on the account, the Microsoft organization or Google Workspace domain it belongs to, and whether Microsoft or Google has verified the email address. We never see passwords, and TagBook does not ask for access to anyone's mail, files, calendar or contacts.
- People the district adds: names, email addresses, and the role, school and grade the district assigns (for example, staff or student).
- Devices: asset tags, serial numbers, makes and models, status, location, purchase details and notes.
- Checkouts: who has which device, when it was checked out and returned, due dates, and notes staff record.
- Signed forms: when a district uses TagBook for device agreements, the signer's name (including a parent or guardian's), the handwritten signature or a photo of a paper form, the document version signed, when, and the device, browser and network (IP) address used.
- Information from the district's own systems, if the district connects them (such as Google Admin, Microsoft Intune, Jamf or Meraki): device details like operating system version, last check-in, network addresses and (for Chromebooks) daily active times; a device's recent and assigned users, which some systems record with an email address or phone number; and the district's user directory. TagBook reads these with access the district grants and controls.
- Files the district uploads, such as agreement documents and the district's logo.
How it is used
Only to provide TagBook to the district: tracking devices and checkouts, collecting signatures, producing the district's reports, keeping its records in sync with its own systems, and support the district asks for. We do not sell information, use it for advertising, build profiles of students or staff, or use it for any purpose other than serving the district it belongs to.
Information received from Google sign-in is used only to identify the person signing in and decide what they may access. TagBook's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Who else is involved
- Microsoft Azure hosts TagBook and its backups, in the United States.
- Microsoft and Google handle sign-in for the account a person chooses to sign in with.
- Dell receives device serial numbers — nothing else — when a district turns on warranty lookups.
We may disclose information when the law requires it, and will tell the district first where the law allows.
How it is protected
- Every connection to TagBook uses HTTPS. Backups are encrypted at rest by Azure Storage. Each district's backups sit in their own storage container, and that district's site is the only service granted access to it; the storage accepts no shared keys.
- Only people a district's administrators name can sign in, each with the access level the district assigns, and access is checked again on every request — removing someone takes effect at once.
- SC Networks staff do not have accounts in a district's TagBook. When a district asks for help, its own administrator acts, or we use that district's emergency account for the purpose and then change its password. Its sessions last at most a working day, and every use is logged.
If we learn of a security incident affecting a district's information, we will notify the district promptly, within any time our agreement with the district sets, and as the law requires.
Cookies
TagBook uses only the cookies it needs to work: one that keeps you signed in, a short-lived one used during sign-in, one that keeps a district's signing device paired, and on login.tagbook.net one that remembers which district you chose. There are no advertising or analytics cookies and no third-party trackers.
Students
TagBook is a tool for school staff. Students do not create accounts or sign in. Student information enters TagBook only from the district, and a student or guardian may sign a device agreement on a school device, which is recorded for the district.
Keeping and deleting information
Information stays as long as the district uses TagBook. District administrators can permanently remove a person's identifying information: their name and email are replaced and their handwritten signatures and photos deleted, while device history stays without saying who. When a district stops using TagBook, we give it its entire database as a single file and then delete its site, database and backups after the retention period in our agreement with the district.
Changes
If this policy changes, we will post the new version here with a new effective date and tell districts about material changes before they take effect.
Contact
SC Networks LLC, 114223 Quincy Lane, Marshfield, WI 54449
info@scnetworks.io