PlanRight Privacy Policy

Information We Process

After you grant calendar access, the app reads existing calendar data only on your device to list writable calendars and detect duplicate events or time conflicts; it does not continuously scan your calendar in the background. Titles, times, locations, and notes from existing calendar events are not uploaded to ZEALX or sent to any third-party AI service or server. The app adds, updates, or deletes only events you explicitly confirm. Parsed event draft fields may be stored locally on your device for up to 30 days so you can continue later; original screenshots and original input text are not stored as part of a draft. You can delete drafts and recognition history in the app. If a history record is linked to a system calendar event, that system event is deleted only after your explicit confirmation.

Only after you explicitly consent under the new v2 authorization notice, the app corrects the orientation of the selected image, removes metadata, and compresses it on your device. The compressed copy, on-device OCR text or text you entered, plus language, reference date, and time zone, are sent through ZEALX to a third-party AI service for real-time schedule extraction. Your contacts and existing calendar contents are not sent.

The app uses calendar permission on your device only for events you confirm; contacts and existing calendar contents are not uploaded or sent.

To add events to the system calendar, the app uses calendar permission on your device. We do not upload your existing calendar contents or sync your full calendar database to our servers.

To prevent abuse and protect the service, the backend processes App Attest verification data, request time, request status, IP address, and similar basic server logs.

If you purchase a subscription, purchase and subscription status are handled by Apple App Store and StoreKit. We do not receive your full payment card information.

When you voluntarily submit feedback, we process the feedback, your optional contact email, app version, system version, device type, and language. This information is delivered through Alibaba Cloud Enterprise Mail, used only to reply, troubleshoot, and improve the product, and retained in the support mailbox only as long as needed for support, troubleshooting, and legal obligations.

How We Collect and Use Information

Information is collected only when you actively type, paste, or share text, choose an image, run the screenshot shortcut, and start recognition. The app does not continuously scan your photos, text, or calendar in the background.

Only after you explicitly consent under the new v2 authorization notice, the app corrects the orientation of the selected image, removes metadata, and compresses it on your device. The compressed copy, on-device OCR text or text you entered, plus language, reference date, and time zone, are sent through ZEALX to a third-party AI service for real-time schedule extraction. Your contacts and existing calendar contents are not sent.

Parsed results are used to create editable schedule cards and, after your confirmation, add events to the system calendar.

Server logs and App Attest data are used to verify request origin, troubleshoot issues, prevent abuse, and maintain service stability.

Calendar content translation is off by default, so parsed titles and notes remain in their original language. Only if you separately give explicit consent for translation and choose a target language are the parsed title and non-empty notes sent through ZEALX to a third-party AI service for real-time translation. Locations or addresses, contacts, and existing calendar contents are not uploaded for translation. If translation is unavailable or fails validation, the original text is kept. The ZEALX backend does not log or persist either the original or translated text after completing the response.

Storage and Retention

To detect duplicate events after the app restarts or translation is turned off, the app stores only non-reversible title fingerprints protected by a random, device-only HMAC key that is not synced, together with the minimal EventKit identity and time/calendar structure needed to bind one event unambiguously. The index does not include notes or locations and is never uploaded or logged. It is deleted when you delete the associated history in the app. If a system-calendar identifier becomes unavailable or a match is ambiguous, the app fails open and does not mark that candidate as a duplicate.

For performance monitoring, troubleshooting, and service stability, basic server logs may also record each request’s processing duration in milliseconds; this data is periodically cleared under the security-log rules described above.

When purchasing a subscription, the App generates a pseudonymous UUID for that installation and provides it to Apple as a StoreKit appAccountToken. Apple returns this identifier in transaction data; the backend associates it with subscription transactions and App Attest device records and retains it with the corresponding subscription or transaction record.

Recognition history and created schedule records are stored locally on your device. You can delete history in the app and manage created events in the system calendar.

The ZEALX backend does not write user input, OCR text, or AI output to application logs or create a persistent record of that content. The ZEALX backend does not retain that content after completing the response. The third-party AI service processes requests under its service terms and privacy notice.

Basic security logs may include a request identifier, time, status, IP address, and App Attest identifier, but not the recognition text. They are retained only as needed for security, abuse prevention, troubleshooting, and compliance, and are periodically cleared.

The backend persistently stores pseudonymous App Attest public keys and counters, daily usage records, StoreKit product and transaction identifiers and expiration or revocation status, and recent device associations. These records are used for service security, quota enforcement, paid access, purchase restoration, and device limits. By default, inactive App Attest keys and usage records, and expired or revoked transaction records, are deleted after 730 days; recent device associations are retained for 90 days. These periods are configurable. Active subscriptions and transaction records are retained while they remain valid.

ZEALX does not write the selected image or its compressed copy, recognition content, or AI model output to application persistent storage or logs; ZEALX does not retain that content after completing the response.

Sharing and Third-Party Services

The ZEALX backend does not retain recognition text after returning the response. Alibaba Cloud may store and process request data according to its service terms, privacy notice, and the rules for the selected service region; any such retention is governed by those terms rather than the ZEALX backend’s post-response non-retention practice.

Only after you explicitly consent under the new v2 authorization notice, the app corrects the orientation of the selected image, removes metadata, and compresses it on your device. The compressed copy, on-device OCR text or text you entered, plus language, reference date, and time zone, are sent through ZEALX to Alibaba Cloud Model Studio for real-time schedule extraction. Your contacts and existing calendar contents are not sent.

Alibaba Cloud states that Model Studio input is not used to train models and provides safeguards for transmission and service processing. We require every service provider to process data only for the purposes described above and to provide the same or equivalent privacy protection described in this Policy. Alibaba Cloud Model Studio Privacy Notice: https://www.alibabacloud.com/help/en/model-studio/privacy-notice

We also use Apple App Store and StoreKit to process subscriptions and payments. Apple processes transaction data under its privacy policy.

We do not sell your personal information and do not use your data for cross-app or cross-website advertising tracking.

Your Choices

The App still uses the pseudonymous technical identifiers described above for subscription and security functionality.

You can choose Not Now, in which case neither a compressed image copy nor any recognition or entered text is sent to the third-party AI service. You can also withdraw permission at any time in Settings > AI Data Sharing. After withdrawal, AI recognition stops until you explicitly allow it again.

You can avoid entering sensitive information, or edit AI-recognized schedule details on the confirmation page before adding them to Calendar.

You can manage calendar, camera, photo, and other permissions in iOS Settings.

You can delete recognition history in the app and delete created events in the system calendar. To make a privacy or data deletion request, contact support@zealx.net.

PlanRight has no sign-in account or user profile containing directly identifying details; a support email address alone still cannot be reliably matched to these pseudonymous backend records. You may ask support@zealx.net to delete support-mailbox messages that match feedback you submitted. You delete recognition history locally in the app and calendar events in the system Calendar. Targeted deletion of backend App Attest, usage, or transaction records would require a future in-app endpoint protected by a fresh App Attest assertion and is not currently available; until then, the automatic retention rules above continue to apply.

Security

We use HTTPS, App Attest, access controls, and data minimization to protect the service. No internet transmission or storage method can be guaranteed to be absolutely secure, but we continue to improve our safeguards.

Children's Privacy

PlanRight is not directed to children. We do not knowingly collect personal information from children.

Changes

If our data practices materially change, we will update this page and, where appropriate, notify users through the app or App Store page.

Contact Us

If you have questions about this Privacy Policy or data processing, contact us at support@zealx.net.