Privacy Policy

1. Who We Are and What ReadSlot Does

ReadSlot ("the extension") is a Chrome extension that saves articles, videos, PDFs, documentation, and repositories, estimates their reading time, and suggests suitable blocks in Google Calendar. It is published by Archiom ("we", "us", "our").

ReadSlot stores your reading queue on your device and connects directly to Google Calendar only when you choose to enable Calendar features. This policy explains how ReadSlot handles your information.

2. Reading Data Stored Locally

ReadSlot stores saved URLs, page titles, notes, tags, collections, reading-time estimates, scheduling preferences, session history, and extension settings in your browser. This data is not uploaded to a ReadSlot server because ReadSlot does not operate a backend.

3. Google User Data ReadSlot Accesses

If you connect Google Calendar, ReadSlot accesses:

• calendar names, identifiers, and access roles so you can select calendars;
• free/busy time intervals so ReadSlot can suggest available reading periods; and
• event information needed to create, update, reconcile, or detect deletion of ReadSlot reading events that you explicitly confirm.

ReadSlot does not use Calendar data to build advertising profiles, determine credit or eligibility, or train generalized artificial-intelligence or machine-learning models.

4. How Google User Data Is Used

ReadSlot uses Google Calendar data only to provide these user-facing features:

• show calendars available for scheduling;
• find open periods without retrieving event titles through the FreeBusy API;
• suggest reading blocks according to your settings;
• create a Calendar event only after your explicit confirmation; and
• keep the corresponding local reading session consistent with that event.

A saved URL is included in a Google Calendar event only when you review and confirm an event whose description contains that URL.

5. Storage and Retention

Google access tokens are cached and managed by Chrome Identity. ReadSlot does not write access tokens to IndexedDB, extension settings, logs, or a remote server. Selected calendar identifiers and identifiers for confirmed ReadSlot events may be stored locally for as long as the extension data remains on your device so that scheduling and reconciliation work.

Your reading data remains locally until you delete it, clear the extension's data, uninstall the extension, or your browser removes it. Items moved to ReadSlot's trash are scheduled for permanent deletion after 30 days unless you restore or permanently delete them sooner.

6. Sharing and Disclosure

ReadSlot does not sell, rent, or share Google user data with advertisers, data brokers, or other third parties. Calendar requests are sent directly from the extension to Google APIs. Information is disclosed only when you instruct ReadSlot to create or update a Calendar event, when required by applicable law, or when necessary to protect users and the service.

7. Security

ReadSlot minimizes requested permissions, uses Chrome's OAuth token management, prohibits remote executable code, validates external data, and requires explicit confirmation before Calendar creation. No system can guarantee absolute security, but ReadSlot is designed to keep reading data on-device and reduce unnecessary access.

8. Your Choices and Controls

• You can use the reading queue without connecting Google Calendar.
• You can disconnect Google Calendar and revoke ReadSlot's authorization from ReadSlot settings.
• If in-product revocation cannot reach Google, you can remove ReadSlot from your Google Account permissions page.
• You can export or permanently delete local ReadSlot data.
• You can uninstall ReadSlot to remove its locally stored extension data.

Revoking ReadSlot's authorization does not automatically delete Calendar events you previously chose to create. You can delete those events directly in Google Calendar.

9. Google API Services User Data Policy

ReadSlot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

10. Children's Privacy

ReadSlot is not directed to children under 13, and ReadSlot does not knowingly collect children's personal information through a ReadSlot-operated service.

11. Policy Changes

Material changes will be reflected on this page with a revised effective date. If a change materially affects Google user-data handling, ReadSlot will provide an appropriate notice before the new practice takes effect.

12. Contact and Support

For privacy questions or support, use the ReadSlot issue tracker at github.com/archiom-io/readslot/issues, or email [email protected]. Do not include OAuth tokens, private Calendar data, or sensitive saved URLs in a public report.