Privacy Policy
SnapCal ("the app," "we," "us") is an iOS app that reads the schedule details out of a screenshot and adds them to your calendar. This policy explains what we collect, how we use it, and the choices you have.
The short version
- To read an event, your screenshot is compressed and sent to our AI processing service. We do not keep the screenshot after recognition, and we never sell your data.
- On-device OCR is used only for the preview and is never uploaded. Recognition is used once, then discarded, and never used to train models.
- Calendar authorization tokens are stored securely on your device and only ever used to create events you've confirmed.
1. Information we process
Screenshots and images you choose
When you pick a screenshot or send an image through the system "Share" menu or Shortcuts, the app reads it to find the schedule details inside. To read an event, the screenshot is compressed and sent to our AI processing service (a third-party AI model), which identifies the date, time, location and title. On-device OCR is used only for the preview and is never uploaded.
This content is used only for that one recognition. We do not keep the screenshot after recognition: our server does not write the image to disk or to a database. To avoid calling the model repeatedly for the same screenshot, the server briefly holds the recognition result in memory (the event's title, date, location and similar text, not the image); it expires after 10 minutes and is cleared whenever the service restarts. This content is never used to train AI models.
Calendar access
When you write an event to the iPhone calendar, we request calendar permission through the system calendar (EventKit); when you choose to sync to Feishu, we request authorization from Feishu. Either way we only create events you've confirmed, and the Feishu authorization token is stored securely on your device. We never read, change, or delete your existing events, and we never upload your calendar contents to our servers.
Account information (optional)
You can try the recognition features without signing in. If you choose to sign in (for example, Sign in with Apple), we receive the basic information used to identify your account (such as email and display name). Sign in with Apple lets you hide your real email address.
Usage and subscription status
Your free-quota usage count, subscription status, and similar details are kept in local storage on your device to power the "10 free recognitions a month" logic. Subscription transactions are handled by the Apple App Store; we never touch your payment information.
Device permissions
- Photos / Images: so you can pick the screenshot you want to recognize.
- Calendar: so we can write the events you confirm into your local calendar.
Anonymous usage analytics (you can turn this off)
The app records anonymous product-interaction events (e.g. app opens, core feature usage, subscription funnel steps) to understand feature usage and improve the product. These events are tied to a random identifier stored only on your device (no name, email, or other personal information), and never include your screenshot content, recognition results, or calendar note text. You can turn this off anytime in Settings → Share & Feedback → Anonymous usage analytics; once off, we stop collecting these events. If you choose to participate in the "Share & Get Membership" campaign, your application record additionally uses this device identifier and any email you voluntarily provide, to match your submission and issue rewards — see "Third-party services" below.
2. Third-party services
To deliver its core features, the app interacts with the third parties below. Each one's own privacy policy applies to the data it processes:
- AI processing service: receives the compressed screenshot, identifies the date, time, location and title, and parses them into a structured event.
- System calendar (EventKit): writes events to the calendar you choose through the system calendar (EventKit), including calendars under iCloud, Google, Exchange and other accounts you have signed in to in iOS.
- Feishu (Lark) Open Platform: creates events after you authorize it.
- Apple App Store: handles downloads and subscriptions.
- PostHog: receives the anonymous usage-analytics events described above, for product analytics; never receives your screenshot content or recognition results.
Limited Use of Google API services
The app's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We use Google Calendar access only to create events at your request — never for advertising, never to sell the data, and never to train general-purpose AI models.
3. What we don't do
- We don't sell your personal data.
- We don't use your screenshots or calendar contents to serve ads.
- We don't read your photos or calendar unless you take an action.
- We don't use the content you recognize to train AI models.
4. Data retention and security
Recognition is temporary: the screenshot sent for recognition is discarded after processing and not stored, and the recognition result is held in server memory only briefly, expiring after 10 minutes. Subscription status, usage counts, calendar authorization tokens, and similar data are stored locally on your device. Deleting the app clears this local data. We take reasonable technical and organizational measures to protect data in transit and in processing.
5. Children's privacy
The app is not intended for children under 13, and we don't knowingly collect personal information from children.
6. Your rights and choices
- Revoke the app's Photos or Calendar permission anytime in your system settings.
- Revoke the app's access in the security settings of your Feishu account (and the Google account you use to sign in).
- Delete the app to clear the local data on your device.
- For further data access or deletion requests, reach us at the email below.
7. Policy updates
We may update this policy from time to time. Significant changes will be reflected by updating the "Last updated" date on this page. We recommend checking back periodically.
Contact us
Questions about this privacy policy? Reach us at [email protected]