Saical Privacy Policy
Effective: July 17, 2026 / Last updated: July 23, 2026
Service: Saical (https://saical.jp)
Operator: Independent developer
Contact: Contact form
This policy explains what information Saical (the “Service”) handles and how it is used.
1. Our core principle: we do not store your period history
The Service writes cycle predictions to your Google Calendar. By design, our server does not store:
- Your period history or an accumulated log of past entries
- Symptoms, physical condition, or other health information
- The contents of calendar events not created by the Service
Your period records remain in your own Google Calendar. Our server retains only the minimum information listed below.
2. Information we collect and store
| Information | Purpose |
|---|---|
| Google account identifier and email address | Sign-in, account identification, and reconnection notices |
| Google Calendar access tokens | Create and update events; tokens are encrypted at rest with AES-256-GCM |
| Cycle settings | Calculate predictions and generate calendar events |
| Your latest period start date only | Prediction anchor; each new entry overwrites the previous value and no history is accumulated |
| IDs of events created by the Service | Update those events together. Future prediction dates are calculated when needed and are not stored on our server |
| LINE user ID, only if you connect LINE | Associate LINE input with your account |
| Time zone and language preference | Date calculation and service messages |
| Usage events, such as screen and action types | Improve the Service. Dates and cycle values are excluded; record and notification events are stored without a user ID. Retention is 30 days |
| Stripe customer and subscription identifiers, if you support the Service | Manage optional payments and subscriptions; card details are handled by Stripe and are not stored by us |
We use only cookies required to maintain your signed-in session. We do not use advertising cookies, tracking cookies, Google Analytics, or a similar third-party analytics service.
3. Google API data
Our use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.
- We request only permission to view and edit accessible Google Calendar events
- We do not use Google user data for advertising
- No human reads this data except with your consent, for security purposes, or where required by law
4. LINE integration
LINE integration is optional and intended for Japanese-language use. Messages you send through LINE remain in your LINE chat history and are governed by LY Corporation's privacy policy. The Service receives only the record command and your LINE user ID.
5. Sharing with third parties
We do not sell or provide stored information to third parties or advertising companies. This does not prevent disclosure when required by law. Google, LY Corporation, Stripe, Resend, Web Push delivery providers, and our hosting provider process data only as needed to operate sign-in, calendar, LINE, payment, email, notification, and hosting functions.
6. Deleting your data
- Disconnect Google: revoke access at Google Account permissions.
- Calendar events: delete them directly from your Google Calendar at any time.
- Server data: use “Delete account” in Settings. Associated tokens, settings, event IDs, LINE connection data, and billing customer record are deleted immediately from the live database. Copies in disaster-recovery backups expire automatically within 14 days and are not used for normal service operations. Contact us if you cannot access Settings.
7. Security
Google Calendar tokens are encrypted at rest using AES-256-GCM. All network communication uses HTTPS.
8. Governing law and changes
This policy is governed by Japanese law. Changes will be posted on this page, and material changes will also be announced within the Service. The English version is currently intended for users in the United States, Canada, Australia, and New Zealand.