Privacy Policy
SCalendar / sCalendar - Seamless Calendar, developed and provided by iLeaf.
Last updated: October 27, 2026
This policy explains how SCalendar accesses, uses, stores, and shares information when you use its calendar, reminder, widget, template, and optional account connection features.
Calendar and reminder information
With your permission, SCalendar accesses calendars and reminders available through Apple's calendar and reminder services to display, search, create, edit, and manage your events and tasks. Information can include titles, dates, time zones, notes, locations, event URLs, reminders, and organizer or participant details. Synchronization with your calendar providers is subject to your device and account settings.
Optional Google Calendar connection
You can choose to connect a Google account to copy events with invitees and create events from participant templates. This connection is optional. Google handles sign-in; SCalendar does not receive your Google password.
- Calendar list (calendar.calendarlist.readonly): reads calendar identifiers, names, access roles, and related metadata to find source events and let you select a destination calendar.
- Events (calendar.events): reads source event details, including organizer and participant names, email addresses, and participation information, to prepare a copy. It creates a new event with the details and invitees you select. Although this permission also permits editing and deletion, the participant-copy feature does not modify or delete the original Google event.
When you choose Save and Invite, SCalendar sends the new event and selected participant details to Google Calendar. Google stores the event and may send invitations or notifications to those participants, who can see information included in the invitation. Saving a template alone does not send invitations.
Who receives Google user data
SCalendar shares, transfers, or discloses Google user data to the following recipients for the purposes described below:
- Google LLC (Google Calendar and Google authorization services): SCalendar sends authorization requests and tokens to Google to establish and maintain the connection. When you choose Save and Invite, it sends the event details and selected participant names and email addresses to Google Calendar to create the event and request invitation notifications. Calendar API requests go directly from your device to Google.
- The invitees you select and people with access to the destination calendar: Google Calendar can disclose the new event's title, dates, location, notes, URL, organizer information, and participant information to these people through invitations, notifications, or calendar access, according to the event and calendar sharing settings. Review the destination calendar, event details, and invitees before saving. Saving a template alone does not send invitations.
- Apple, when you use Apple's calendar synchronization or device backup services: Event information can be downloaded to Apple's calendar database on your device through the Google account configured in iOS. Locally stored app data, such as participant templates containing Google event details and email addresses, may be transferred to Apple for iCloud Backup if you enable that service. These transfers depend on your device and Apple account settings.
- Recipients or services you choose through sharing or export: If you explicitly share or export calendar information using SCalendar or iOS sharing controls, the information you select is provided to the recipient, app, or service you choose.
- iLeaf support, only if you choose to include information in a support request: We receive the Google event details or participant information that you voluntarily send us and use that information to investigate and respond to your request. Do not send passwords or OAuth tokens.
The Google Calendar integration does not send Google calendar content, participant details, or OAuth tokens to an iLeaf-operated backend, advertising networks (including Google AdMob), or analytics services (including Firebase Analytics). We do not sell or rent Google user data, disclose it to data brokers, or share it for advertising or general-purpose AI or machine learning training. We do not transfer or disclose Google user data to other third parties for purposes unrelated to the user-facing features described in this policy.
Storage, retention, and security
Google Calendar requests go directly from your device to Google's services over HTTPS. The Google Calendar integration does not upload event content, participant details, or OAuth tokens to an iLeaf-operated server. Google access and refresh tokens are stored in the device's Keychain with protection that makes them available only while the device is unlocked and prevents their migration to another device.
Event drafts and retrieved Google data are processed on your device. If you save a participant template, its event details, participant addresses, and destination calendar information are stored in the app's local settings until you delete the template. Other features may retain local templates or event history. Local app data may be included in device backups according to your Apple settings. Events stored with Google, Apple, or another calendar provider remain subject to that provider's retention and account settings. No security measure can guarantee absolute protection.
Disconnecting, revoking access, and deleting data
- Use Disconnect in SCalendar's Google connection controls to remove the locally stored Google tokens and stop that connection.
- To revoke the permission at Google, remove SCalendar from your Google account's third-party connections. Disconnecting in the app does not itself revoke Google's authorization.
- Delete saved templates and history using the app's corresponding controls. Removing the app removes its local app data, but Keychain credentials can persist after uninstalling, so disconnect and revoke access first. Manage any retained device backups through Apple.
- Disconnecting, revoking access, deleting a template, or uninstalling SCalendar does not delete events already created in your calendar or invitations already sent. Manage those events in your calendar service.
Google data use and sharing limits
Google Calendar data is used only to provide the calendar features described above. We do not sell Google user data, use it for advertising or advertising profiles, send calendar content to analytics services, or use it to train general-purpose AI or machine learning models. The Google integration does not provide iLeaf with routine access to read your calendar content. If you contact support, share only the information needed to investigate your request.
Our handling and transfer of information obtained through Google APIs follow the Google API Services User Data Policy, including its Limited Use requirements.
Advertising and usage analytics
SCalendar uses Google AdMob for advertising and Firebase Analytics for usage analysis. These services may process device and app information, identifiers, IP addresses, ad interactions, and usage information under their own policies and the applicable consent and device settings. Calendar content and participant email addresses are not supplied to these services by the Google Calendar integration.
You can control tracking in iOS settings, manage advertising privacy choices when available in the app, and change the app's usage analytics preference. Learn more from Google's Privacy Policy and Firebase privacy information.
Support and policy updates
If you email support, we receive the address and information you send and use it to respond and resolve your request. Do not send passwords or access tokens. For privacy questions or assistance with deletion, contact studio.ileaf@gmail.com.
Changes to this policy will be published on this page with an updated date. If we change how Google user data is used, we will provide notice and obtain additional consent where required before using it in the new way.