Last updated 18 November 2026
Your events.
Your account.
Who operates Calendar Drawer
Calendar Drawer is operated by FOTOSCASA UNIPESSOAL LDA (NIF 519031369), with registered office at Rua Dom Nuno Álvares Pereira, 13, 7570-239 Grândola, Portugal. For privacy questions or requests, contact mailserhumano@gmail.com. This policy covers the extension, this website and its Google authentication service.
Information used and why
The extension uses your Google account email and identifier, calendar list, time zone and event information to identify, display, park, organize, copy from templates and reschedule events. It reads the Google Calendar page to identify dragged events and their destination. It does not read your browsing history.
Google authorization is required to access your calendars. You choose whether to grant it. Calendar data is used only to provide event organization, synchronization and recovery, not advertising, profiling or training AI models.
Organization, templates and Trash
Drawer creates a secondary storage calendar in your Google account. While parked, events do not block availability and have reminders disabled. Drawer tries to hide its storage calendar from the normal time grid; if it remains visible, uncheck “Drawer · eventos em espera” in Google Calendar without deleting that calendar. Their original calendar, schedule, duration, reminders and supported settings are recorded as private event properties so they can be restored. Category identifiers, urgency, template status and Trash status are also stored on those events. Local categories, preferences and recovery records are not automatically synchronized between browsers.
An urgent item is another view of the same stored event. A reusable template remains in the storage calendar while each drop creates a new event in its original calendar. Moving an item to Drawer Trash is reversible. After confirmation, Empty Trash requests deletion from Google and removes matching local recovery records. Google may retain deleted data under its own retention and recovery rules. Copies previously created from a template are separate events and are not deleted when the template is trashed.
Where data is stored
Events remain on Google servers in your authorized account. Categories, preferences, identifiers and recovery records are stored locally in the extension. Pending operations remain until resolved. Completed recovery history is limited to 60 operations and approximately 1.5 MB, except for a larger individual record.
Access tokens are kept in the browser session. Your account email and identifier can be retained locally to reconnect the same account. The authentication service temporarily exchanges a single-use Google code and PKCE proof for an access token. It has no event endpoints or database and does not deliberately retain codes or tokens. It never receives your Google password.
How we protect Google user data
We use the following technical safeguards to protect the confidentiality and integrity of sensitive Google user data, including calendar events, account identifiers and authorization credentials:
- Encryption in transit. Communications between the extension, Google APIs and our authentication service use HTTPS with TLS encryption. The authentication service also exchanges authorization codes with Google over HTTPS. Calendar event data travels directly between your extension and Google, rather than through our server.
- Protected sign-in and credentials. Google OAuth uses a single-use authorization code, PKCE with SHA-256, and a random state value. The extension validates the state and expected redirect before exchanging a code. Access tokens are short-lived and kept in Chrome session storage; they are not saved to persistent local storage by Drawer and are removed when you disconnect. The server returns no refresh token. The OAuth client secret is held in a protected Cloudflare Worker Secret, never in the extension or public website.
- Restricted access. Chrome local and session storage access is restricted to trusted extension contexts. The extension validates message senders and checks that the Calendar account matches the connected account before calendar operations. The authentication endpoint restricts accepted extension origins and request formats and validates the code-exchange inputs; Google validates PKCE. We request only the Google permissions used by the app.
- Data minimization and logging safeguards. Our authentication service has no event database and does not receive calendar event content. Codes and tokens are processed temporarily for sign-in; application code does not write them or request bodies to logs. Authentication responses use Cache-Control: no-store to prevent caching.
- Device storage and recovery files. Events remain in your Google account, subject to Google's security controls. Local categories, pending operations and recovery records are stored in your Chrome profile. Drawer does not add its own encryption layer to local extension storage or exported backup files. Their protection therefore also depends on your device, operating-system account and browser-profile security. Keep your device locked and updated and store exported backups securely, since they may contain sensitive event information.
Service providers and technical logs
Google provides authentication and calendar storage. Cloudflare hosts this website and authentication service and processes technical connection information, which may include IP address, request URL, time and response status. Application code does not log authorization codes, access tokens or request bodies. Enabled Cloudflare Workers invocation logs on the current free plan have a three-day retention period. Cloudflare may process additional infrastructure and security data under its own policies.
These providers may process data internationally. See Google Privacy Policy and Cloudflare Privacy Policy. Calendar data is not sold, shared for advertising, or sent to the authentication service. Drawer has no advertising or marketing analytics.
Google API data
Calendar Drawer's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Your choices and deletion
You can disconnect in Settings or revoke permission through Google account connections. Uninstalling removes local extension data, but does not delete or restore events parked in the Drawer storage calendar. Return events to their original calendars before uninstalling. Disconnecting removes the current session token and account hint, but does not clear local categories or recovery records, or delete events in Google. Revoking access stops future authorized API access; it does not delete existing data. Exported recovery backups are files you control and may contain private event details; delete them yourself when no longer needed.
You may contact us to request access, correction or deletion of personal data we hold, or to exercise other applicable privacy rights. We cannot directly access events stored in your account. Support messages are used to respond to your request; avoid sending passwords, tokens or unnecessary event details.
Changes
Changes to this policy will be posted here with an updated date. Material changes to data use will be communicated before they take effect.
Free edition
The current edition is free to use. It does not require a payment card, trial activation or license key, and does not send license-validation requests.