Privacy Policy for ApplyLog

Last updated: September 16, 2026

ApplyLog ("the extension," "we," "our") is a Chrome extension that helps you track job and internship applications and sync them to a Google Sheet in your own Google Drive. This policy explains what data ApplyLog accesses, how it's used, and your choices.

Data We Access

Google Account Data (via OAuth)

When you click "Connect," ApplyLog uses Google's sign-in (chrome.identity) to request permission for a single scope:

• https://www.googleapis.com/auth/drive.file — a limited Drive scope that only lets ApplyLog see and manage the specific spreadsheet(s) it creates, or that you explicitly select yourself through Google's own file picker. It cannot browse, search, or access any other files in your Drive.

We do not request access to your email address, contacts, calendar, or any other Google data beyond what's listed above.

Job/Internship Data You Enter

Information you type into the "Add Job" form (job title, company, status, type, location, salary, deadline, link, notes) is written directly to your connected Google Sheet using the Sheets API. This data is stored in your own Google Drive — ApplyLog does not copy it to any external server we control.

Data Stored Locally (chrome.storage)

ApplyLog uses Chrome's built-in storage.local and storage.sync APIs to remember, on your device (and synced across your own Chrome profile, if enabled):

• The ID of your connected spreadsheet and its formatting state
• An in-progress "Add Job" form draft, so you don't lose unsaved entries if the popup closes

This data stays within your Chrome profile and Google's own sync infrastructure for Chrome — it is not sent to us.

Import Feature

If you use the "Import from an old spreadsheet" feature, you select the old spreadsheet yourself through Google's own file picker (opened in a new browser tab). That selection is what grants ApplyLog access to that one file — ApplyLog cannot browse your Drive to find it on its own. ApplyLog then reads that spreadsheet (via the Sheets API, using the same OAuth token) to detect and map its columns, and writes the matched rows into your ApplyLog sheet.

How We Use Your Data

We use the Google user data described above solely to provide and operate ApplyLog's core functionality. Specifically:

• We use the Sheets API to create your "ApplyLog - Job Applications" spreadsheet, apply its formatting (frozen header row, column widths, status colors, dropdown validation, filters), and keep it in sync as you add, edit, or import job entries.
• We use the data you enter in the "Add Job" form to write a corresponding row into your spreadsheet, so your applications stay organized without manual data entry.
• We use the Sheets API to read your existing rows back so ApplyLog can display them in the Applied, Saved, and In Progress tabs, power search/filtering, and calculate the stats shown in the popup.
• When you use the import feature, we use the data solely to detect column headers, map them to ApplyLog's schema, and write the resulting rows into your spreadsheet.

We do not use your Google user data for any other purpose. We do not use it for advertising, to build user profiles, to train generalized or non-personalized AI/ML models, or for any purpose unrelated to providing ApplyLog's job-tracking features to you.

What We Don't Do

• We do not sell, rent, or share your Google user data with third parties.
• We do not use your data for advertising or for training AI/ML models.
• We do not operate a backend server that stores your job data — everything lives in your own Google Sheet and your local Chrome storage.
• We do not access, read, or transmit any Google Drive files other than the spreadsheet(s) ApplyLog creates or that you explicitly connect.

How We Protect Your Data

ApplyLog is designed so that as little of your data as possible passes through anything other than your own Google account and your own device:

• All communication with Google's APIs (Sheets, Drive, and OAuth/identity) happens over HTTPS/TLS encryption.
• Your OAuth access token is obtained and held using Chrome's built-in chrome.identity API. ApplyLog never sees, stores, or transmits your Google password.
• ApplyLog does not operate a backend server, so your job/internship data is never transmitted to or stored on infrastructure we control — it lives only in your own Google Sheet and in Chrome's local/sync storage on your own device or Google account.
• Access is scoped as narrowly as Google's APIs allow: the drive.file scope limits ApplyLog to only the spreadsheet(s) it creates or that you explicitly open, not your wider Google Drive.
• You can revoke ApplyLog's access at any time — either by clicking Disconnect in the extension or from your Google Account permissions page — which immediately stops any further access to your data.

Data Retention and Deletion

Your job/internship data persists for as long as it exists in your Google Sheet — you control it directly and can edit or delete it at any time, either through ApplyLog or directly in Google Sheets.

Clicking Disconnect in the extension revokes ApplyLog's cached OAuth token and clears the locally stored spreadsheet reference. You can also revoke ApplyLog's access at any time from your Google Account permissions page. Revoking access does not delete the spreadsheet itself, since it lives in your own Drive.

Children's Privacy

ApplyLog is not directed at children under 13, and we do not knowingly collect data from children under 13.

Changes to This Policy

If we make material changes to this policy, we'll update the "Last updated" date above.

Contact Us

Questions about this policy or how ApplyLog handles your data? Email us at applylogsupport@gmail.com.