Privacy, without the fine-print fog.

Time Pebbles is a Chrome extension that helps you create reusable time blocks and deliberately place them as events in Google Calendar. This policy explains the data the extension handles and why.

What is handled

Data Time Pebbles handles

Time Pebbles handles only the information needed to provide its visible features:

• Pebble library data: Pebble names, durations, selected colors, list title, order, archive state, and the delete-warning preference.
• Calendar placement data: The event title, selected date and time, duration, time zone, and color for an event you deliberately place. Time Pebbles also keeps the Google event ID, event link, status, and private Time Pebbles identifiers for up to 20 recent placements so it can verify the event and prevent duplicates.
• Calendar metadata: The primary calendar’s event-label IDs, names, and colors, used to show the same color choices in Time Pebbles.
• Visible Calendar layout: The dates and time-grid geometry visible in Google Calendar Week view, used locally to translate a click, drag, or drop into the chosen date and time.
• Authentication information: A Google OAuth access token obtained and managed through Chrome Identity after you choose Connect Google Calendar. Time Pebbles does not request or receive your Google password and does not save the OAuth token in its own storage.

Time Pebbles does not collect health, financial, precise-location, browsing history, or advertising-profile data. It does not include advertising or analytics.

Plain purpose

How the data is used

The extension uses this data only to:

• create, display, edit, reorder, archive, restore, and delete Pebbles;
• translate an explicit placement gesture in Google Calendar Week view into a date and time;
• create and verify the Calendar event you deliberately placed;
• use the primary calendar’s real event-label palette;
• show placement progress and prevent duplicate Calendar events; and
• recover the Calendar connection after a normal extension reload.

On your device

Storage and retention

Pebble library data and recent placement records are stored locally in chrome.storage.local on your device. Time Pebbles does not operate a developer server and does not copy this data to one.

Local data remains until you delete it, clear the extension’s storage, or uninstall the extension. The recent-placement record is limited to 20 items. Google Calendar events remain in your Google Calendar until you delete them there. Deleting a Pebble from Time Pebbles does not delete Calendar events that were already created.

Where data goes

Data sharing and transmission

Time Pebbles sends Calendar requests only to Google Calendar API endpoints over HTTPS to perform the action you requested. Google receives and stores the event data because the event is created in your Google Calendar. Chrome and Google manage OAuth authorization under their own privacy terms.

The interface may request font resources from Google Fonts. Google may receive standard network information associated with that request, such as the IP address and browser user agent, under Google’s privacy policy.

Time Pebbles does not sell user data, share it with advertisers or data brokers, use it for credit decisions, or use it for personalized advertising. The publisher does not permit humans to read user data except with your specific consent for support, when required for security or by law, or after it has been aggregated and anonymized for permitted internal operations. Time Pebbles currently has no developer-side copy of user data to inspect.

Safeguards

Security

All Calendar API traffic uses HTTPS. The extension requests narrowly scoped permissions, keeps executable code inside the installed package, and does not load remote JavaScript or WebAssembly.

You stay in control

User choices and deletion

You can edit, archive, restore, or delete Pebbles in the extension. You can remove all local Time Pebbles data by uninstalling the extension or clearing its stored data in Chrome. You can revoke Google Calendar authorization from your Google Account’s third-party access settings. Revoking access stops future Calendar API calls but does not delete existing Pebbles or Calendar events.

Google API data

Limited Use disclosure

Time Pebbles’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve the user-facing time-block placement features described above. It is not used or transferred for personalized advertising, unrelated profiling, or other prohibited purposes.

Questions and updates

Changes and contact

This policy will be updated if Time Pebbles’ data practices change. Questions or privacy requests can be submitted through the support page.