YOUR INFORMATION, EXPLAINED

Privacy policy

NextDue helps you capture deadlines, plan schedules, and receive reminders in Chrome. This policy explains the information the extension handles and the choices you have. The session-storage protections below apply to version 0.1.4 and later. Earlier versions kept imported Calendar details in persistent local extension storage; updating migrates those records into session storage and removes the old active local records. Browser or device backups may retain older copies.

Information stored on your device

NextDue stores the following in this Chrome profile:

• Items you enter: titles, notes, due dates, schedule start and end times, all-day status, repeat rules, reminder choices, completion and archive status, and related timestamps.
• Capture information you explicitly request through Chrome's context menu: selected text, the source page address, and its title when available. This information becomes a draft for you to review. Source information and selected text may also be included in the item's notes.
• Unfinished popup and dashboard drafts, settings, snooze and reminder-delivery state, the last delete or archive action available for undo, and temporary reminder-chip preferences.

Quick Add interprets text on your device. NextDue does not send that text to a parsing or translation service. Local items and settings do not use Chrome Sync and are not backed up to a NextDue server.

Optional Google Calendar connection

Google Calendar is disconnected by default. If you connect it, NextDue uses Google's authorization service and Calendar API to:

• Read and cache in memory a catalogue of readable calendars, including calendar identifiers, names, colors, access roles, time zones and default reminders, so you can choose calendars to display and a writable destination for new events. This catalogue can include calendars hidden in Google Calendar. Your display selection and creation destination are stored locally and do not change Google's calendar visibility or sharing settings.
• Import upcoming events only from calendars selected for NextDue, within your chosen range of 14, 30, 60, or 90 days. Before you customize the selection, NextDue follows the visible primary calendar and other visible calendars selected in Google Calendar. Your NextDue selection is stored locally and does not change Google Calendar settings.
• Display and cache in memory event titles, descriptions, attachment links, dates and times, locations, meeting links, reminder settings, your response status, and calendar identifiers, names, and colors. Event responses can include attendee information; NextDue uses response information to determine your own participation and whether to show an event.
• Display the email address available from your Chrome profile and local connection/sync status.
• Create a Google Calendar event whenever you add a new item through Quick Add, its exact-details form, a captured or restored draft, or the address bar while connected. The event is created in the writable calendar you choose under Settings → Calendar, initially your primary calendar, using the title, notes, dates and times, repeat rule, and reminder setting. This includes date-only entries, which are all-day events unless you enable a Quick Add default time. Timed entries without an explicit range or duration last 30 minutes. Notes can include source information you captured from a page. This can be an owned calendar or a calendar shared with you with write access. Existing local items stay local when edited. If the Calendar write fails, the new item remains local with an explanation.
• Create an event directly from the Month or Week Calendar view when you choose to save in its event editor. That editor sends the title, description, location, dates and times, all-day choice, repeat pattern and reminder to the writable calendar selected in the editor. Its unsaved draft stays in the open dashboard's memory; it is not automatically saved as a local task on failure. A draft identifier and a one-way content marker are included in the Google event to help confirm retries without creating duplicates.

Calendar synchronization runs periodically while connected and can also be requested from Settings. Google stores events created there according to your Google account and calendar settings. People with access to the chosen destination calendar may be able to see them under those settings. Existing Calendar events are managed in Google Calendar; completing or hiding a mirrored item in NextDue does not delete the Google event. Hiding a calendar in NextDue removes its active local mirrors and their NextDue reminders without deleting its Google events. Choosing which calendars appear in NextDue is separate from choosing where a new event is saved. New connected entries still save to the chosen destination when that calendar is hidden in NextDue.

Authorization tokens are managed by Chrome's Identity API and used to make requests directly to Google. NextDue does not ask for your Google password or write access tokens into its item or draft storage. Google requests use HTTPS. Google's handling is described in the Google Privacy Policy.

Data protection and security

NextDue uses the following technical measures to protect Google user data, including calendar details, profile information and authorization tokens:

• Encryption in transit: Calendar API requests are sent directly from the extension to Google over HTTPS using TLS. Authorization tokens are sent in the Authorization header, not in page URLs. These connections encrypt data while it travels over the network.
• Google-managed authorization: NextDue uses Chrome’s Identity API and Google’s OAuth consent flow. It does not collect your Google password. The extension uses access tokens in memory for API requests and does not write them into its items, settings or draft storage. Chrome manages the authorization cache.
• Memory-only Calendar cache: Imported event content, the calendar catalogue and the displayed profile email are held in Chrome’s in-memory extension session storage. NextDue does not persist that cache through browser restarts. Chrome clears it when the browser restarts or the extension is disabled, reloaded or updated. NextDue refreshes it from Google when connected; imported events and their reminders may be unavailable until that refresh succeeds.
• Storage access restrictions: Local and session extension storage are restricted to trusted extension contexts. The reminder chip cannot directly read those storage areas; it receives the reminder information needed for its feature through validated messages to the extension’s background worker. Ordinary webpages cannot directly access extension storage. NextDue fails rather than falling back to a persistent Calendar cache if the required storage protections are unavailable.
• Minimal persistent state: Local items you create, unfinished form drafts and preferences remain on your device. Preferences include the identifiers of calendars you choose to display and write into; a calendar identifier can contain an email address. NextDue also retains connection status, the last sync time, a hashed account identifier, and up to 4,000 hashed event-state records containing completion, archive, snooze and reminder-delivery state. These records preserve your choices after a restart without retaining imported titles, descriptions, locations or meeting links. Hashing is not encryption. Text you deliberately copy from a Calendar event into a local item or form draft is retained as that local content.
• Device protections and limits: The publisher does not operate a server that receives or stores your items or Calendar data. NextDue does not add its own encryption at rest to persistent local items, drafts or preferences, and relies on Chrome and your device’s access controls for that data. Someone with access to your unlocked device or Chrome profile may be able to access it. Memory-only storage does not protect against a compromised device or operating-system memory capture.
• Restricted extension actions: The extension validates the sender identity and origin of internal messages and limits the actions available to its reminder chip. The chip requires both an enabled setting and the optional website permission. Event text is treated as data rather than executable code, and executable scripts are bundled with the extension.
• Access removal and cleanup: You can disconnect Google Calendar in Settings or revoke NextDue’s access in your Google Account. Disconnecting clears Chrome’s cached authorization for the extension and removes mirrored Calendar events and account-specific cached details from NextDue. Local items you entered and events already saved in Google Calendar remain, as explained below.

No storage or transmission method can guarantee absolute security. Keep Chrome and your operating system updated and protect access to your device and Chrome profile.

Reminders and links

Reminder titles and scheduling information may appear in Chrome reminder windows and your operating system's notification banners. You can enable or disable each channel in Settings. Your operating system controls whether its notifications appear on a lock screen or in notification history.

The reminder chip on Google Search, Gmail, and Google Calendar pages is off by default. Chrome requests access to these websites only when you enable the chip in Settings. Enabling it displays your NextDue reminders on those pages and lets you act on them. Disabling it removes that website access and the chip from open tabs. The chip does not read your searches, inbox, or page contents. Page or selection capture occurs only when you choose the corresponding NextDue context-menu action.

When you choose a meeting, source, attachment, Calendar, or location link, Chrome opens that destination. Opening a location without a web address sends the location text to Google Maps as a search. The destination's privacy practices apply to that visit.

Sharing and use

NextDue has no developer-operated backend, advertising, or analytics service. The extension does not transmit your items or Calendar data to the publisher. Information is sent to Google for the Calendar features you enable and to link destinations you choose as described above. Chrome and your operating system provide local storage, authorization, and notification services.

NextDue does not sell user data, use it for advertising, or use it for creditworthiness or lending decisions. It uses the information described here only to provide its deadline, schedule, capture, and reminder features. If you separately contact the publisher, provide only the information you want the publisher to receive; the extension does not automatically attach your items or Calendar data.

Limited Use: NextDue's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. NextDue's use of user data also complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Retention and your controls

• Items: edit or delete local items in NextDue. Completed and archived items remain in local storage until removed. Deleting an item retains a copy for the last-action undo feature; that undo record is held in memory until replaced by a later delete/archive action, used to restore the item, or cleared when Chrome restarts or the extension is disabled, reloaded or updated.
• Drafts: unfinished Quick Add and exact-details form drafts in the popup and dashboard are cleared when submitted or reset. Drafts more than seven days old are discarded when that surface next attempts to restore them; this is not an automatic background deletion timer. Pending context-menu captures are held in memory until opened, replaced, or cleared with the browser session. Unfinished Quick Add/exact-details drafts remain in local browser storage as described above. The separate Calendar-view event editor holds its draft in the open dashboard's memory until saved or closed; closing or reloading the page discards it. A save with an uncertain result retains that draft in the open page for checking or retrying.
• Calendar: disconnect under Settings → Calendar to stop synchronization, clear cached authorization state, remove mirrored Calendar items and Calendar entries in undo storage, and clear the displayed account email, calendar catalogue, saved display selection and creation destination, and hashed Calendar state records. The last sync timestamp is retained. Manual items and any drafts or copies you created remain local. A request already sent to Google can still finish after disconnecting.
• Google account access and events: disconnecting NextDue does not delete events from Google Calendar. Manage those events in Google Calendar. You can also remove NextDue's account access through Google Account connections.
• All local extension data: uninstalling NextDue removes its extension storage from that Chrome profile. Data already stored by Google or retained separately by your operating system is managed through those services.

Imported Calendar content uses session storage in version 0.1.4 and later. Persistent local data uses Chrome extension storage and local browser storage. Protecting access to your device and Chrome profile remains necessary. Removing a record from extension storage is not a guarantee of forensic erasure from device backups or other operating-system records.

This website and Cloudflare

This informational website is hosted on Cloudflare Pages. It does not include advertising, analytics scripts, a login, or a contact form. Cloudflare processes technical request information, such as IP addresses and browser information, to deliver and protect the website. Cloudflare’s handling of this data is described in the Cloudflare Privacy Policy. Visiting this website does not give it access to your NextDue items or Google Calendar data.

If you contact the publisher by email, your email address, message, and any information you choose to include will be handled to respond to your request. Only include the information needed for support.

Changes and contact

This policy will be updated if NextDue's data practices change. The last-updated date above identifies the current version. Material changes requiring a new disclosure or consent will be presented before the new handling begins.

For questions about this policy, contact [email protected].