Privacy Policy
Effective date: 17 November 2026
This policy covers Mail Calendar Sync, the operator-managed calendar integration presented at calendar.da4nik-ai.ru.
Data accessed and collected
The integration accesses configured Exchange and Mail.ru calendar records and Google Calendar data. Calendar records may include titles, descriptions, locations, dates, time zones, recurrence rules, identifiers, status and other event fields present in the source. The deployed configuration omits attendee and organizer fields from imported events and skips all-day events.
Google OAuth access and refresh tokens, source account credentials, synchronization mappings, event identifiers, cached calendar records and operational logs are stored on the operator’s server. This public website does not collect Google passwords, offer a sign-in form, or use analytics or advertising cookies. The web server may record IP addresses, requested URLs, timestamps, user agents and response codes for operation and security.
Purpose and Google permissions
Data is used to connect authorized calendars, identify the destination, import events, apply changes and cancellations, prevent duplicate copies and diagnose failures. The authorization requests calendar, calendar.readonly and calendar.events scopes. Full Calendar permission can allow reading, editing, sharing and permanently deleting calendars accessible to the account; the integration’s intended operation is limited to the configured synchronization workflow.
Sharing and limited use
Source event data is sent to Google Calendar to provide the synchronization requested by the account owner. Hosting infrastructure processes stored data and server requests. Data is not sold, used for advertising, or used to train generalized AI or machine learning models. Human access is limited to authorized operation, troubleshooting, security and legal obligations.
Mail Calendar Sync’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Storage, security and retention
OAuth tokens and source credentials are held in restricted server files. This website uses HTTPS. Synchronization records, caches, logs and backups may remain on the server until removed by the operator; there is currently no fixed automatic deletion deadline. No storage or transfer method guarantees absolute security.
Revoke access and delete data
You can revoke access through Google Account connections. Revoking access stops future authorized Google API access but does not delete previously synchronized events or server copies. To stop source synchronization and request removal of credentials, tokens, cached records, logs and backups, contact the operator at strizhakovr@gmail.com. Events already copied to Google Calendar remain in that account until deleted there.
Changes and contact
The operator is the administrator of Mail Calendar Sync at da4nik-ai.ru. For support and privacy requests, including data deletion, contact strizhakovr@gmail.com. Changes to this policy will be published here with an updated effective date.