Last updated: May 11, 2026
1. Information We Collect
Account & Identity: When you sign in with Google OAuth or create an email/password account, we receive your name, email address, and (for Google sign-in) your profile picture. This is used solely to authenticate your account and personalise your profile.
App-Created Events: Events you manually create or edit inside the app (title, date, time, description, event type, recurrence rules) are stored in our Supabase database linked to your user ID. Only events you explicitly save in the app are uploaded to our servers.
Device Calendar Events (optional): With your explicit permission, the app reads event data (titles, dates, recurrence) from calendars stored on your device (Google, iCloud, Samsung, or other local calendars). This data is displayed inside the app and stored only on your device using local storage. Device calendar events are never uploaded to our servers unless you manually edit the event inside the app and save it — at which point it becomes your own app-created event and is synced normally.
Contact Birthdays (optional): With your explicit permission, the app reads birthday dates from your device contacts. Only the contact name and birthday date are used. No phone numbers, email addresses, physical addresses, or any other contact fields are read or stored. Contact birthday events are stored locally on your device and are never uploaded to our servers.
Google Calendar Events (optional): If you choose to connect your Google Calendar account via the in-app import feature, the app requests read-only access (calendar.readonly scope) to your Google Calendar. Events are fetched and displayed locally in the app. Google Calendar event data is stored locally on your device and is never uploaded to our Supabase database. The Google OAuth access token is stored securely on your device using expo-secure-store and is used solely to read your calendar. We do not modify, delete, or write any Google Calendar data.
Preferences & Settings: App settings such as theme, notification preferences, calendar system (Shahenshahi/Kadmi/Fasli), selected city, and reminder timing are stored locally on your device. If you are signed in, some preferences are also synced to our servers so they are restored when you sign in on another device.
Location (optional): With your explicit permission, the app accesses your device's location solely to calculate Choghadiya (auspicious time) and Gah period timings. Your coordinates are used only for this calculation and are never transmitted to or stored on our servers. The calculated city name may be stored locally on your device for display purposes.
Push Notification Tokens: If you enable push notifications, your device's push token may be stored to deliver scheduled notifications. Notifications are scheduled and sent from your device; we do not use a third-party push messaging service that stores your token externally.
Usage & Diagnostics: Aggregate, anonymous crash reports may be collected to improve app stability. No personally identifiable usage data is sold or shared with third parties.
2. Device Permissions Explained
The app may request the following runtime permissions. Each permission is optional and can be revoked at any time in your device Settings:
None of the above permissions are used for advertising, profiling, or any purpose beyond the feature described.
3. What Stays on Your Device vs. What Goes to Our Servers
We follow an offline-first, local-only principle for sensitive device data:
| Data Type | Stored Locally Only | Synced to Server |
|---|---|---|
| Device calendar events (imported) | ✓ | ✗ |
| Contact birthday events (imported) | ✓ | ✗ |
| Google Calendar events (imported) | ✓ | ✗ |
| Your location / coordinates | ✓ | ✗ |
| Events you create / edit in the app | ✓ (also) | ✓ (if signed in) |
| User preferences / settings | ✓ (also) | ✓ (if signed in) |
| Account identity (name, email) | ✗ | ✓ (authentication) |
Promote-on-edit: If you edit a device calendar or contact birthday event within the app and save it, it transitions into an app-created event and is synced to our servers as your own event. The original device/contact record is not modified.
4. How We Use Your Information
We do not sell, rent, trade, or share your personal information with any third party for advertising or marketing purposes.
5. Third-Party Services
The following third-party services are used. Each receives only the minimum data necessary to perform its function:
Supabase — Backend database and authentication provider. Your app-created events, account identity, and preferences are stored on Supabase's servers (AWS infrastructure, US region). Supabase does not receive device calendar, contacts, or location data. See supabase.com/privacy.
Google Sign-In / Google OAuth — Used for account authentication. When you sign in with Google, Google provides us with your name, email, and profile picture. Separately, if you connect Google Calendar, we request only the calendar.readonly scope to read your events — we never write to your Google Calendar. The Google OAuth token is stored on your device using expo-secure-store and is not transmitted to our Supabase database. See Google Privacy Policy.
expo-secure-store — A React Native library that stores the Google Calendar OAuth token in your device's secure hardware-backed storage (Android Keystore / iOS Secure Enclave). This token never leaves your device except when communicating with Google's servers.
Web3Forms — Used to process contact and support form submissions from our website. When you submit a form, your name, email, and message are sent to Web3Forms' servers. See web3forms.com/privacy.
Expo / EAS (Expo Application Services) — Used for app distribution, builds, and over-the-air updates. EAS may collect device identifiers and tokens for update delivery. See expo.dev/privacy.
Solar / Choghadiya Calculations — Sunrise and sunset times are calculated entirely on your device using the NOAA Solar Calculator algorithm (Jean Meeus, Astronomical Algorithms, 1998). No external API is contacted and no location data leaves your device for this purpose.
Moon Phase Data — Moon phase information is bundled within the app as a static data file. No external service is contacted to retrieve moon data.
6. Data Retention
Your account data (events, preferences) is retained for as long as your account is active. If you delete your account via the app Settings or the Delete Account page, all associated data — including events, preferences, and profile information — is permanently deleted from our servers within 30 days.
Locally stored data (device calendar imports, contact birthday imports, location, Google Calendar cache) is stored on your device and is removed when you uninstall the app or clear app data. It is not retained by us.
Authentication records and tokens held by Google are subject to Google's own retention policies.
7. Security
8. Your Rights
Depending on your jurisdiction, you may have the right to:
To exercise any of these rights, contact us using the details below or use the in-app self-service deletion feature.
9. Children's Privacy
Parsi Calendar is not directed to children under the age of 13 (or the applicable age in your jurisdiction). We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal data without your consent, please contact us immediately using the details below and we will delete that information promptly.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date at the top of this page and, where appropriate, notify you through the app. Continued use of the app after changes are posted constitutes your acceptance of the updated policy.
11. Contact Us
For privacy-related questions, data access requests, or deletion requests, please contact us via our support form or at: