Privacy Policy
Research Control Room · Effective 3 October 2026
Operator and scope
Research Control Room is a personal research-planning application operated by Lorenzo Gorini. This policy covers its Google Calendar integration, related application data, and this public information site. Contact: lore.gorini@gmail.com.
Information accessed and stored
- Google Calendar list information, including calendar identifiers, names, display colors, selection state, and access roles.
- Event identifiers, titles, locations, status, and start dates or times from calendars displayed by the application.
- OAuth access and refresh tokens, granted permissions, token expiry times, and connection timestamps. The application does not receive your Google password.
- Research tasks, plans, focus-session records, and identifiers linking application-created focus blocks to Google Calendar events.
Purpose and permissions
Calendar information is used to display the day’s schedule and support research planning. OAuth tokens allow the server to retrieve authorized Calendar data without repeated sign-in. When requested by the user, task titles, focus-block times, and task/session identifiers are sent to Google to create events in the designated Research Control Room calendar.
The application requests read access to the calendar list and events, plus permission to manage events on calendars the account owns. Although the Google permission is broader, the current application limits writes to creating focus blocks in the designated calendar. It does not use this access to modify external invitations.
Storage, access, and retention
Application records and OAuth tokens are stored in the operator’s private server database. Database backups may also contain them. Access is restricted through server permissions and private-network access. Google API requests use HTTPS. Calendar listings are retrieved on demand for display; the application does not intentionally maintain a permanent copy of these listings in its database.
Stored application records and connection credentials remain until the operator deletes them or they are no longer needed. There is currently no automatic retention or backup-expiry schedule. Revoking Google access stops future authorized API access but does not automatically delete existing local records or backup copies.
Sharing and use restrictions
Google data is used only to provide the described planning and Calendar features. It is not sold, used for advertising, or used to train general-purpose AI or machine-learning models. Calendar contents and OAuth credentials are not published on this website or in its public GitHub repository. Data is exchanged with Google as needed for the integration and may be accessed by the operator for maintenance, troubleshooting, or deletion requests.
Research Control Room’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Your controls and deletion
You can revoke the connection through your Google Account’s third-party connections settings. To request deletion of locally stored credentials, associated records, or backup copies, contact the operator at the email above. Existing focus blocks in Google Calendar remain until deleted in Google Calendar; disconnecting does not delete them.
This public website
These informational pages are hosted by GitHub Pages. They do not contain analytics scripts, advertising, sign-in forms, or Google Calendar data. GitHub may process technical request information, including IP addresses, under its Privacy Statement.
Changes
This policy will be updated when the application’s data practices change. The effective date above identifies the current version.