This policy applies to the native Sai app, version 2.0, provided by 하일 (CHAYIL). It explains what information stays on your device, what is synchronized with your account, what is used for AI briefings you request, and the choices available to you.
1. Accounts, Calendars, and AI
- Your Sai account stores and synchronizes relationship records. New events are saved to a connected calendar. Device calendar permission is separate from signing in to Sai.
- After reviewing and agreeing to the AI data-use notice, you can request a briefing using relevant relationship records, event information, and your question. Opening a screen alone does not send information to AI.
- Contact import reads only the names and duplicate-detection identifiers of contacts you explicitly select. Those identifiers remain on your device. Unselected contacts are neither stored nor uploaded.
Sai does not collect advertising identifiers, use behavioral analytics SDKs, collect your device's current location or location-tracking data, or collect remote push tokens. Event reminders are scheduled using local notifications on your device.
2. Information Stored on Your Device
App-specific storage holds onboarding status, notification and calendar display settings, people and relationship names, saved context, ongoing conversation topics, follow-up tasks, event links, contact duplicate-detection identifiers, and pending synchronization state. With your permission, the app also reads and locally stores calendar event titles, times, locations, status, original notes, and source identifiers to provide calendar features.
Login sessions and external calendar credentials use storage protected by iOS Keychain or Android Keystore.
3. Information Synchronized with Your Account
When you sign in to Sai, the following information may be sent to provide app features and synchronization across devices. Relationship records left only on a device by an earlier app version are added to the account only if you choose to import them.
- Account identifier, email address, and profile name
- People's names, relationship labels, and summaries you create, and the display names of contacts you select
- Event titles, times, locations, status, and calendar source information
- Saved context, ongoing conversation topics, follow-up tasks, and links between people and events
- Change identifiers, ordering, versions, time zones, and conflict state required for synchronization
Original calendar notes and contact duplicate-detection identifiers stay on your device and are not sent to Sai's account servers. Unselected contacts, contact phone numbers, email addresses and photos, and calendar attendees are neither stored in the app's own storage nor sent to Sai's account servers.
4. AI Briefings You Request
After you review and agree to the AI data-use notice and request generation, the names, relationship labels and summaries of people linked to the meeting, saved relationship context, conversation topics and hints, follow-up tasks, relevant event information, and your question are sent to OpenAI. Older records may also be used to find evidence relevant to the current meeting or question.
Original calendar notes and contact phone numbers, email addresses and photos are not added to this input. Sai's servers process account-level generation usage and request identifiers to enforce usage limits and prevent duplicate charges. AI suggestions are not automatically saved as factual relationship records without your review.
5. External Calendar Connections
On iOS, choosing to connect Google Calendar or NAVER Calendar communicates with that provider's authentication and calendar APIs. Connection credentials are stored securely on your device and deleted when you disconnect. Device calendar access takes place only with operating-system permission.
If you edit an original event note, the change may be sent to its calendar provider, such as Apple, Google, or NAVER. Disconnecting Sai or deleting a Sai account does not arbitrarily delete events held by the original calendar provider.
Information received from Google APIs is used in accordance with the Google API Services User Data Policy, including its Limited Use requirements. Google Calendar data is used for visible calendar, synchronization, relationship-record, and requested briefing features, and not for advertising, retargeting, credit scoring, or data sale.
6. Purposes and Service Providers
Information is used for authentication, on-device features, account synchronization, calendar connections, AI briefings you request, usage-limit management, reminder scheduling, conflict recovery, and data deletion. It is not used for advertising, third-party marketing, or tracking users across services.
- Supabase: Sai account authentication, relationship-data synchronization, briefing-result caching and usage processing, and account deletion requests
- OpenAI: relationship briefings and answers to follow-up questions that you request
- Apple and Google: the account sign-in option you choose
- Apple Calendar, Google Calendar, and NAVER Calendar: reading, writing, and synchronizing calendars you permit or directly connect
Each provider processes information under its own terms and privacy policy. Sai does not own data that already exists in your external calendars.
7. Retention and Deletion
Device data: Records in the app's own storage are retained until you delete them in the app's privacy and data screen or remove the app. Credentials can remain in iOS Keychain after app removal. When Sai detects a reinstall, it removes login and external calendar credentials from the previous installation before opening screens, widgets, or notifications. If verification or removal cannot finish, the app keeps the data closed and offers a retry. Deleting this device's data removes relationship records and pending synchronization records while preserving original calendars on the device or with external providers.
Account and server data: Synchronized information is retained while the account is maintained. Completing account and server data deletion removes the server account and synchronized data and clears that account's local copy, session, scheduled reminders, and widget display data on this device. If a network error prevents confirmation of the server result, the app retains a retry state and does not report deletion as complete.
AI briefings and evidence: Briefings and selected evidence may be cached per account to redisplay results and prevent duplicate generation or charges. Previous results are not reused when their underlying relationship records change or are deleted. Account deletion also removes the associated server cache. OpenAI calls disable storage for later response retrieval. This does not mean that all of the provider's operational or security logs are immediately deleted; the provider's data-processing policy applies separately.
Legal retention: If applicable law requires specific information to be retained for a defined period, it may be stored separately only for that purpose and period.
8. Permissions and Choices
- Contact, calendar, and notification permissions are optional and can be withdrawn in operating-system settings.
- Google and NAVER calendar connections can be removed in the app's calendar connection screen.
- You can view saved relationship records without requesting an AI briefing. You may choose not to import records left on a device by an earlier app version.
- The app's privacy and data screen provides separate actions for deleting device data and deleting account and server data.
9. Policy Changes
Material changes are announced in the app or on this page before they take effect. For wording corrections that do not affect users' rights, we update the effective date on this page.
10. Privacy Questions and Deletion Support
If the app cannot resolve a request to access, correct, or delete personal information, or if you need help deleting an account, contact us by email.
Privacy contact: 하일 (CHAYIL)
Email: vibe.wassup@gmail.com