Privacy Policy | Presynce Attendance Tracker

Summary

Presynce is local-first. The extension reads the participant list in a Google Meet session you choose to track and sends it to your own browser. Records are stored in your browser by default. We do not sell your data, show ads, or use it for profiling.

Data reaches our cloud database (Firebase) only if you sign in with Google and turn on backup. Even then, it is stored under your account and is not shared with other users.

Who we are

Presynce ("Presynce", "we", "us") is an attendance management system made of two parts: a Chrome extension that captures attendance in Google Meet, and a web dashboard where you organize, review, and export records. It is developed and maintained by an individual developer in the Philippines as an academic capstone project.

This policy covers the Presynce extension and the Presynce web dashboard (together, the "Service"). It does not cover Google Meet, Google Workspace, or any other service run by a third party.

Information we handle

The Service handles only what it needs to build an attendance record. The table below lists each category, why it is needed, and where it goes.

Information	Source	Purpose
Participant display names	The Google Meet participants list, only while you are tracking attendance	Building the attendance list and applying the "Last Name, First Name M." format
Join time and total time present	Measured by the extension during tracking	Attendance duration, first-seen time, Present / Late / Absent rules
Profile picture web address (URL)	Google Meet participant tiles	Showing avatars in record and absentee tables. The image itself is not copied; your browser loads it from Google
Meeting code, meeting title, date, start and stop time	The Google Meet page address and page	Labeling and sorting records
Groups, group names, teacher/handler names, and group settings you enter	You	Organizing records and generating longitudinal (matrix) reports
Google account name, email address, profile photo, and account ID	Google Sign-In (only if you choose to sign in on the web dashboard)	Identifying your account for cloud backup and showing your account details
App preferences (for example, Auto Backup on/off, matrix display mode, last backup time)	You	Remembering your settings

What we do not collect. The Service does not record audio, video, screen content, or chat messages. It does not read the contents of your Google Drive, Gmail, or Calendar. It does not collect passwords, payment information, precise location, or government IDs. It does not verify the identity of participants; it only records the display names they enter in Google Meet.

Usage analytics. The Service does not currently include advertising or analytics trackers. The extension keeps some technical health counters in memory to detect when Google Meet changes its layout (for example, whether a page element could be found). These are not sent to us by the Service as it currently works. If that changes, this policy will be updated before it does.

How we use it

To capture attendance for meetings you choose to track and to produce standardized, alphabetized attendance records.
To consolidate records into groups and generate summaries, absentee lists, and exports (Excel and PDF).
To back up and restore your records and groups when you sign in and enable backup.
To keep the Service secure and working, and to respond to support or feedback you send us.

We do not use your data for advertising, we do not sell it, and we do not use it to build profiles or to make automated decisions about participants.

Where your data lives

Scope note. The Chrome Extension itself only reads the Google Meet participant list while you are actively tracking a session — it does not perform sign-in, does not store your Google account credentials, and does not connect to Firebase or any cloud service directly. Sign-in, cloud backup, and restore are features of the separate web dashboard described below, not of the extension.

In your browser (default)

Attendance records, groups, and settings are stored in your browser's local storage on the dashboard's website. This data stays on your device and is not uploaded unless you turn on cloud backup. Because it lives in your browser, clearing site data, switching browsers or devices, or using private windows can remove or hide it.

In the extension

While you track attendance, the extension holds the session in memory. About every few seconds it saves a temporary recovery copy to the Google Meet page's local storage so that an interrupted session can be recovered. This copy is removed after the dashboard confirms the record was saved. The extension does not have its own permanent storage separate from this temporary recovery copy.

Between the extension and the dashboard

When you stop tracking, the extension opens the Presynce dashboard in a new tab. The dashboard asks the Meet tab for the record using the browser's built-in messaging, and each side accepts messages only from the expected website address. The record goes from your Meet tab directly to your dashboard tab; it does not pass through a Presynce server.

Sign-in and cloud backup

Sign-in and cloud backup are optional, and are only available on the web dashboard — not inside the Chrome Extension. If you sign in with Google, we use Firebase Authentication to verify your account and receive your name, email address, profile photo, and account ID.

If you turn on Auto Backup or run a manual backup, your attendance records (including participant names, times, and avatar URLs) and groups are copied to Cloud Firestore, saved under your account. Backups are intended to be readable and writable only by the signed-in owner of that account. You can restore a backup to a device, and you can choose whether to merge it with the records already on that device. If Auto Backup is on, changes you make (for example, adding or deleting a record) are copied to the cloud automatically.

Signing out does not delete your cloud backup. See Retention and deletion for how to remove it.

We do not sell, rent, or trade your information, and we do not transfer it to advertisers or data brokers. We share information only in these situations:

Service providers. Google (Firebase Authentication and Cloud Firestore) processes account and backup data on our behalf. Vercel hosts the dashboard and may keep standard server logs such as IP address and browser type.
Content loaded from other sites. The dashboard loads fonts and icons from Google Fonts, Firebase scripts from Google, and helper libraries from jsDelivr and cdnjs (used for Excel/PDF export). Your browser contacts those providers directly when a page loads, which may reveal your IP address to them. Participant avatars load from Google's image servers.
Legal reasons. If required by law, court order, or to protect rights and safety, we may disclose information to the extent the law requires.
Exports you create. Files you export (Excel, PDF) are created on your device. What you do with them is up to you.

Google user data

Presynce's use and transfer of information received from Google APIs and from the Google Meet page will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

Information read from Google Meet and from your Google account is used only to provide and improve the user-facing attendance features described in this policy.
It is not sold, and it is not transferred to third parties except as needed to provide those features, to comply with law, or as part of a merger or sale with notice to you.
It is not used for advertising, including personalized or retargeted ads.
It is not read by humans unless you ask us to (for example, to fix a bug you report), it is needed for security, or the law requires it.
The extension reads only the minimum needed: participant names, times, avatar URLs, and meeting details — all visible on the Google Meet page itself, and only while you are actively tracking.

Presynce is an independent project and is not affiliated with, endorsed by, or sponsored by Google LLC. Google, Google Meet, Chrome, and Firebase are trademarks of Google LLC.

Retention and deletion

On your device. Records and groups stay until you delete them or clear your browser data. The dashboard keeps up to the 500 most recent records; older ones are removed automatically when the limit is exceeded. Deleting a record in the dashboard permanently removes it from that browser.
In the cloud. Backups stay until they are replaced by a newer backup or you ask us to delete them. Turning off Auto Backup stops new backups but does not remove earlier ones.
Deleting your cloud data. Email keytlingeyl@gmail.com from the Google account you used to sign in and ask for your backup and account data to be deleted. We will confirm and complete the deletion within a reasonable period, and no later than 30 days.
Temporary recovery copy. The recovery copy in the Meet tab is removed once the dashboard confirms the record was saved.

Security

We take reasonable technical steps to protect your information: data is transmitted over HTTPS, extension and dashboard messaging is limited to expected origins, cloud data is tied to your signed-in account and protected with Firebase security rules, and the extension collects only the minimum data needed. No method of storage or transmission is completely secure, and browser-stored data is only as safe as your device and browser profile. Use a screen lock, keep your browser updated, and avoid shared computers for attendance records.

If we learn of a breach that affects personal information, we will notify affected users and, where required, the appropriate authority, as the law provides.

Your rights

Depending on where you live, you may have the right to:

be informed about how your personal data is processed;
access the personal data we hold about you;
correct inaccurate data;
ask for deletion or blocking of your data;
object to or restrict certain processing, and withdraw consent at any time;
receive your data in a portable format (PDF and Excel exports serve this purpose); and
complain to your data protection authority.

These rights are recognized under the Philippine Data Privacy Act of 2012 (Republic Act No. 10173), which we follow, and under laws such as the European Union's General Data Protection Regulation (GDPR) for people in the EU/EEA. In the Philippines, you may contact the National Privacy Commission (privacy.gov.ph). To use any of these rights with us, email keytlingeyl@gmail.com. Because most data stays on your own device, you can also exercise much of this control directly: view, edit, export, or delete records in the dashboard.

Meeting organizers and participants

Presynce is a tool used by meeting hosts, teachers, and coordinators ("organizers"). When an organizer tracks a meeting, the names and times of the other participants are recorded. For that participant data, the organizer (or their school or organization) decides why and how it is used, and is responsible for having a lawful basis to record attendance, for telling participants that attendance is being recorded, and for following their institution's privacy rules. We act only as the tool provider and do not receive participant data unless the organizer backs it up to the cloud.

If you are a participant and want your name corrected or removed from a record, please ask the organizer who ran the meeting. If you cannot reach them, email keytlingeyl@gmail.com and we will help where we are able.

Children and minors

The Service is designed for teachers, coordinators, and professionals. It is not directed to children under 13, and we do not knowingly collect personal information directly from them. We do not collect ages and cannot tell whether a participant in a meeting is a minor. If you track a class that includes students under 13 or under the age of consent where you live, you are responsible for getting any permissions your school, local law, or laws such as the U.S. Children's Online Privacy Protection Act (COPPA) require. Do not sign in to Presynce if you are under 13. If you believe a child's information was backed up to the cloud, contact us and we will remove it.

Regional notices

Presynce is available worldwide through the Chrome Web Store, so here is how this policy applies in some regions.

Philippines. We follow the Data Privacy Act of 2012 (RA 10173). You may complain to the National Privacy Commission.
European Economic Area, United Kingdom, and Switzerland. Where GDPR or UK GDPR applies, our legal bases are your consent (for example, when you sign in and turn on cloud backup) and our legitimate interest in running and securing the Service. You may complain to your local data protection authority.
United States (including California and other states with privacy laws). We do not sell or share personal information for advertising, and we do not use it for profiling. You may ask to access, correct, or delete your information, and we will not treat you differently for doing so. Requests go to keytlingeyl@gmail.com; we may need to confirm you own the account before acting.
Canada. You may withdraw consent and ask to access or correct your information at any time, by emailing keytlingeyl@gmail.com.
Do Not Track. There is no common standard for Do Not Track signals. The Service does not run advertising or cross-site tracking, so it behaves the same whether or not the signal is on.

International use

Presynce is developed in the Philippines. Cloud backup data is processed by Google's Firebase infrastructure and may be stored in data centers outside your country. By enabling cloud backup, you agree to this transfer. We rely on the safeguards provided by Google's data processing terms for such transfers.

Research evaluation

Presynce is part of an academic thesis. If you take part in the evaluation survey, participation is voluntary, you may stop at any time, and the survey is designed not to collect personally identifiable information. Results are reported only in aggregated form. Attendance records you create while testing are not read or collected for the research unless you choose to share them.

Changes to this policy

We may update this policy as the Service changes, for example when new features are added. We will change the "Last updated" date above and, for significant changes, show a notice in the dashboard or on the extension's store page. Continuing to use the Service after a change means you accept the updated policy.

Contact us

Questions, requests, or concerns about privacy? Email keytlingeyl@gmail.com.