Privacy, without the mystery.

1. What this covers

This policy applies to LogBook, a Syed Systems product, and to the information processed when you visit, sign in to, or use the service. In LogBook, students are typically records managed by an instructor; they do not need a separate LogBook account to appear in a course roster.

2. What you put in LogBook

• Account and workspace details - name, email address, institution, designation, course memberships, and settings.
• Academic records - course details, student roster fields, attendance, assessments, scores, grades, notes, reports, and export data you choose to create.
• Messages and recipients - email addresses, subjects, message content, and delivery status when you ask LogBook to send a grade report or another course message.
• Support information - anything you voluntarily include when you contact us for help.

3. Sign-in and technical information

If you sign in with Google, Microsoft, or GitHub, that provider shares the account identifier and basic profile details needed to authenticate you. We do not receive your provider password. LogBook and its infrastructure may also process IP address, browser or device information, timestamps, error reports, and security logs to keep the service working and protect accounts.

4. Why we use information

• To authenticate you and keep your account and workspace secure.
• To save, sync, calculate, search, export, and display your records.
• To send verification, password-reset, and service messages.
• To send course messages only when you direct LogBook to do so.
• To troubleshoot failures, prevent abuse, and improve reliability.
• To respond to support requests and comply with valid legal obligations.

We do not sell personal information. We do not use student records to serve advertising.

5. Security in practical terms

LogBook protects stored records with encryption and uses encrypted connections for data in transit. Access controls and tenant-scoped database policies are used to keep one professor's workspace separate from another's.

Some online operations-such as tabulation, search, report generation, and exports-require authorized LogBook services to temporarily process data in memory to complete the request. That processing is limited to the requested operation; encrypted storage is not a claim that no service can ever process readable data.

6. Services that help us operate

LogBook relies on specialized providers to deliver the product. Depending on the feature you use, these include Cloudflare for web hosting, Neon for database storage, Azure for backend hosting and encryption key management, Resend for authentication email, and ZeptoMail for instructor-directed course email. Our authentication service processes sign-in identifiers and session information. Google, Microsoft, and GitHub may also process information when you choose their sign-in or integration services. These providers operate under their own terms and privacy policies.

7. Google Classroom data

Connecting Google Classroom is optional. It is separate from signing in, and only an instructor can start it. When you connect, Google asks you to grant four read-only permissions. LogBook uses them only to import your own Classroom courses into your LogBook courses:

• Courses (read-only) - the names, sections, rooms, and IDs of active courses you teach, so you can choose which Classroom course to link to a LogBook course.
• Rosters (read-only) - the students enrolled in the linked course and their names, so you can match them to your LogBook roster.
• Student email addresses (read-only) - used only to suggest which Classroom student is which LogBook student. You review every suggestion before it is saved.
• Coursework and grades (read-only) - published assignment titles, topics, and maximum points, and the grades you have returned to students, so they can be imported into the grading scheme you approved.

LogBook never creates, changes, or deletes anything in Google Classroom. What it stores: your Google access and refresh tokens, the ID of the linked Classroom course, the Classroom ID of each student you confirm as a match, the published assignment details listed above, and the returned grades it imports as LogBook scores. All of these are encrypted before they are saved, using keys protected by Azure Key Vault. Classroom student email addresses are shown to you during matching and are not saved by LogBook.

When you disconnect a Google account, LogBook asks Google to revoke its access and deletes the stored tokens. Grades you already imported stay in your LogBook courses as part of your records, together with the encrypted course link, student matches, and assignment details that explain where they came from, until you delete the course or your account. You can also remove LogBook's access at any time from your Google Account permissions page.

LogBook's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google Classroom data for advertising, do not sell it, do not use it to train AI or machine learning models, and do not let people read it except with your permission, for security purposes, or to comply with law.

8. Retention and deletion

We keep account and workspace data while your account is active. When you request account deletion, we aim to remove the primary records within 30 days. Encrypted backups or deletion tombstones may remain for up to 90 days for recovery, security, and data-integrity purposes before expiring. Records may also be retained where a longer period is required by law or necessary to resolve a security or abuse matter.

9. Your controls

• Export your workspace and course records from LogBook.
• Update your account information and connected providers.
• Delete your account and request removal of associated records.
• Contact us to ask for access, correction, or clarification.

For a privacy request, email info@syedsystems.dev. Please use an address associated with your LogBook account so we can verify the request.

10. Changes to this policy

We may update this policy as LogBook changes. If an update materially changes how we use information, we will provide notice through the service or by email where appropriate. The date above shows when this version took effect.