Security
Identity and permissions
CalendarGuardian uses provider-native authorization. The Microsoft server connector requests delegated User.Read and Calendars.ReadWrite plus standard OpenID Connect/offline-access scopes. The Google server connector uses Google OAuth/OpenID Connect and the Google Calendar events scope needed to read and modify events. Apple-native clients request calendar access through EventKit, and Android-native clients use Android runtime Calendar permissions. CalendarGuardian does not require users to provide their Microsoft, Google, or Apple Account password.
Credential protection
Server-side OAuth token material is designed to be encrypted using AES-256-GCM at the application layer. Production client secrets and encryption keys are maintained outside source code in protected hosting configuration. Native platform permissions are mediated by the device operating system. HTTPS is required for production server endpoints and webhook callbacks.
Provider notification validation
CalendarGuardian validates provider notification identifiers or secret state before acting on calendar-change webhooks. Microsoft Graph subscriptions use protected client-state values. Google Calendar notification channels use per-channel tokens and identifiers. Subscription/channel renewal is handled by the service and stale provider subscriptions are removed where supported.
Data minimization
The core detection engine is rules-based and does not require transmitting calendar content to a third-party generative-AI model provider. Calendar content is retrieved or locally read as necessary to evaluate events. Full event snapshots are intended to be retained server-side only for events requiring review, reported events, or removed events, subject to retention and deletion controls. Native clients can perform risk scoring locally.
Operational safeguards
Production design includes least-privilege provider access, protected webhook validation state, origin checks on browser state-changing requests, security headers, encrypted token storage, production-secret validation, retention cleanup, provider-subscription renewal controls, dependency management, backup/recovery appropriate to stored data, and monitored hosting. Automatic risk-based removal is off by default.
Platform-specific limitations
Calendar providers and operating systems control synchronization, permissions, API semantics, and attendee notifications. CalendarGuardian cannot guarantee that every deletion is silent or that every provider exposes equivalent reporting, restore, or background-processing capabilities. Provider-specific behavior is acceptance-tested before a capability is represented as supported.
No implied certification
CalendarGuardian does not claim SOC 2, ISO 27001, FedRAMP, HIPAA certification, or another independent security certification unless DealDoctor expressly publishes that the certification has been obtained and identifies its scope.
Responsible disclosure
Send suspected vulnerabilities to support@dealdoctor.pro with the subject SECURITY - CalendarGuardian. Please provide enough information to reproduce the issue without accessing or exposing data that you are not authorized to access.