WallCal is a personal wall-calendar display that shows your Google Calendar events and Google Tasks reminders on a screen. This policy explains what data the application accesses, how it is used, and where it is stored.
WallCal is operated by Alex Bisson as a personal, non-commercial project. Contact: alex.bisson@gmail.com.
When you connect your Google account through the in-app settings, WallCal requests the following read-only OAuth scopes:
https://www.googleapis.com/auth/calendar.readonly — to read your calendar list and events so they can be displayed in the calendar grid.https://www.googleapis.com/auth/tasks.readonly — to read your Google Tasks lists and tasks so reminders can optionally be displayed in the calendar grid and side panel.WallCal never requests or uses write access to your Google account. It cannot create, modify, or delete any calendar event, task, or other item on your behalf.
Information retrieved from Google APIs is used solely to render the calendar and reminders interface in your browser. Specifically:
Your Google data is not used for advertising, analytics, profiling, training machine-learning models, or any purpose other than displaying the calendar interface to you.
WallCal has no backend server. All data processing happens entirely within your web browser. The following items are stored locally in your browser's localStorage on the device you use:
Your calendar events and tasks themselves are fetched from Google APIs each time the calendar refreshes and are held only in memory for rendering. They are not written to localStorage or any other persistent storage.
WallCal does not transmit your Google data to any third party. The only network destinations contacted by the application are:
oauth2.googleapis.com, www.googleapis.com) — to authenticate you and fetch your calendar and tasks data.api.open-meteo.com) — to fetch weather forecasts for the city you optionally select. No identifying information is sent; only the latitude and longitude of the chosen city.cdn.jsdelivr.net) — to load the Twemoji emoji rendering library.No analytics, tracking pixels, advertising networks, or third-party data brokers are integrated into WallCal.
WallCal's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
All communication with Google APIs uses HTTPS. OAuth authorization uses the Authorization Code flow with PKCE (Proof Key for Code Exchange) to protect the authorization process. Tokens are stored in your browser's localStorage and are accessible only to the WallCal origin (https://wallcal.alexbisson.com). Because storage is local to your browser, anyone with physical access to your device may be able to view the stored tokens; treat the device hosting WallCal accordingly.
You may revoke WallCal's access to your Google account at any time by visiting myaccount.google.com/permissions and removing WallCal from the list of connected applications. You may also clear all locally stored data by clearing site data for wallcal.alexbisson.com in your browser settings.
Tokens and preferences remain in your browser's localStorage until you clear them or until the browser evicts them. WallCal itself does not retain any of your data on a server because no server-side storage exists.
WallCal is not directed at children under 13 and does not knowingly collect any information from them.
If this policy changes, the updated version will be published at this URL and the "Last updated" date at the top will be revised.
For questions about this policy or about WallCal, contact alex.bisson@gmail.com.