The short version
Planify does not sell personal information, run advertising, or use third-party advertising trackers. Planning information is stored on your device. If you enable cloud AI, the content and planning context sent for your request are processed through Cloudflare and OpenAI. Optional iCloud, calendar, sign-in, and support features also involve the providers described below.
1. Scope
This policy applies to Planify 1.0 for iPhone, its widgets and share extension, and the Planify website and support channels. Features labeled as in development for a future update are separate from this version. Apple, Google, and other services you choose to connect operate under their own privacy policies.
2. Information Planify handles
Planning information
Planify stores tasks, to-dos, projects, routines, daily plans, focus notes and history, completion insights, saved Plany conversations, preferences, and related organization details. This information is stored on your device in protected app storage.
Private iCloud sync
If iCloud Sync is enabled, Planify stores a copy of your workspace in the private CloudKit database associated with your Apple Account. Planify does not place this workspace in a developer-accessible public database.
Calendars
If you grant Calendar access, Planify reads the calendars you select so commitments can appear beside your plan. You can connect Apple Calendar through iOS. You can also connect Google Calendar directly in Planify Settings and choose which calendars and events to display. Google Calendar credentials are kept in the device Keychain. A protected on-device cache retains recently viewed Google events and synchronization tokens to reconcile changes; it is excluded from iCloud sync. Calendar titles, event times, and other relevant event details may be included in planning context sent through Cloudflare to OpenAI when you use cloud AI. Google sign-in for cloud AI is separate from Google Calendar authorization. With your permission, Planify can edit or delete Apple Calendar events where the calendar allows changes. Google Calendar access is read-only; edit and delete actions open Google Calendar so you can make changes there.
Google Workspace data and Limited Use
Planify’s use and transfer of information received from Google Workspace APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. Planify does not use or transfer Google Workspace user data, including raw or derived data, to create, train, or improve foundational or generalized AI or machine learning models.
When you explicitly enable cloud AI, relevant calendar information may be processed through Planify’s Cloudflare-hosted service and the OpenAI API solely to generate personalized planning assistance. This processing requires your consent. Planify does not enable sharing of this API content for model training. The provider retention practices described below still apply.
Voice, photos, and documents
If you use voice capture, audio is provided to Apple’s Speech framework for transcription. Processing availability can depend on the device, language, and Apple’s services. Images and scanned documents are processed with Apple’s Vision technologies to extract planning context. When you send photos in Plany chat, processed copies are kept in protected local storage for up to seven days, subject to a storage limit and earlier deletion. Those photo copies are excluded from iCloud sync and device backups. If you use cloud AI, selected photos and extracted context are sent through Cloudflare to OpenAI. For PDF and document requests, extracted text from the pages you select, page references, and document metadata are included in the request. Follow-up messages can include the document context retained for that conversation.
Cloud AI and account sign-in
Cloud AI is optional and requires your consent. Your submitted text, selected images, selected document-page text, relevant conversation history, and planning context included by the app pass through Planify’s Cloudflare-hosted service to OpenAI to generate a response. Planify 1.0 uses synchronous requests; the service does not store chat text, photos, or AI replies in its account database. Saved Plany conversations remain in protected storage on your device and are not included in iCloud workspace sync.
Planify requests that OpenAI not store responses as API application state. This does not mean zero retention: OpenAI may retain content for abuse monitoring, ordinarily for up to 30 days, subject to its exceptions and applicable requirements. OpenAI states that API content is not used to train its models by default. See OpenAI’s API data controls.
To operate the service and enforce usage limits, the developer can review pseudonymous account request counts, request type (text, image, or file), time, image/page counts, token usage, and estimated AI cost. These reports do not include chat text, responses, images, file contents, or filenames. Individual request records expire after 30 days; aggregate usage and cost records remain with the budget ledger to enforce limits, including after account deletion. Earlier private-testing records may retain invitation associations for abuse prevention.
Planify uses Firebase Authentication for Apple, Google and email/password accounts. Google account sign-in requests basic identity only and is separate from Google Calendar access. Firebase stores the account email, provider identifiers, and a secure password hash for email/password accounts, and sends verification and password-reset emails. Apple and Google verify their own provider credentials; Planify does not receive your Apple or Google password. Account information is used for authentication and account management, not model training or promotional email. The cloud service stores a pseudonymous account identifier, sign-in provider, hashed sessions, usage and security records. Earlier private-test accounts may also have invitation associations. For Apple accounts, it also stores an encrypted refresh token to validate and revoke the connection. It does not store Google ID or refresh tokens in its server database. During account deletion, the service retains an encrypted Firebase account identifier and a pseudonymous deletion record to retry interrupted cleanup, even after sign-in expires. These deletion records are removed when cleanup completes; unresolved requests remain pending until cleanup can be confirmed. Device credentials are kept in the iOS Keychain or the provider SDK’s secure storage. Accounts are not combined merely because their email addresses match.
Planify check-ins
Mood check-ins and written reflections in Planify 1.0 are saved within Planify. This version does not connect to Apple Health, read Health data, or save moods or reflections to HealthKit. Optional iCloud sync and cloud AI are described separately on this page; enabling one does not connect Planify to Apple Health.
Purchases
Apple processes App Store payments. Planify uses StoreKit to request product information and determine whether your Apple Account has an active Planify Pro subscription or lifetime entitlement. Planify does not receive your full payment-card details.
For cloud Pro, Planify verifies Apple transaction identifiers and purchase status on its server and links the purchase to your signed-in Planify account. When you explicitly restore an older purchase without an account token, the app may send Apple-signed app transaction proof containing the app purchase identifier and verification metadata. The server checks this proof without storing it. Opaque account and purchase ownership links are retained after account deletion to prevent reuse across accounts and allow restoration to the same account. An already linked purchase is not automatically transferred to a different Planify account.
Diagnostics
On supported devices, Apple may make crash, hang, and responsiveness diagnostics available through MetricKit. Planify 1.0 keeps a small, redacted diagnostic history locally for troubleshooting.
Support requests
When you email support, we receive the email address, message, attachments, and app details you choose to send. Support email is handled through Gmail and your email provider. TestFlight feedback and diagnostic attachments are handled through Apple. The public website does not submit or store support-form entries. Please avoid sending passwords or unnecessary private planning information.
3. How information is used
- Provide, personalize, and preserve your plan.
- Sync information when you enable iCloud.
- Complete calendar, notification, sharing, voice, and purchase actions you request.
- Restore purchases and enforce Planify Pro access.
- Respond to support requests and diagnose reliability problems.
- Protect the app and support service from misuse.
Planify does not use your plans to build advertising profiles, sell personal information, or deliver third-party targeted advertising.
4. When information is shared
Information is shared only when needed for a feature you choose or when legally required. Depending on your choices, recipients may include Apple through iCloud, StoreKit, Speech, Calendar, notifications, and diagnostics; Google through sign-in and direct Calendar access; Cloudflare for the cloud service and its security processing; OpenAI for cloud AI requests; and your email provider and our support mailbox provider when you contact support.
Planify does not currently include third-party advertising SDKs or cross-app tracking SDKs.
5. Retention and deletion
- On-device data: remains until you remove it, delete your Planify account, or uninstall the app. Account deletion removes this iPhone’s Planify plans, but does not remove events from your connected calendars.
- iCloud data: remains in your private iCloud database when sync is paused. Account deletion also removes the Planify workspace in your connected iCloud account. Offline devices and disconnected iCloud accounts may retain copies. You can manage app data through your Apple Account’s iCloud settings or contact support for instructions.
- Calendar: revoke Apple Calendar access in iOS Settings. Disconnect Google Calendar in Planify to remove its local credentials and cached Google events, or revoke authorization in your Google Account. Disconnecting does not delete events in your Google Calendar account.
- Planify account: after you confirm your sign-in and type DELETE, deleting the account removes this iPhone’s plans and the workspace in the connected iCloud account, removes its Firebase authentication record and active Planify credentials and sessions, and requests provider disconnection. Limited pseudonymous invitation, allowance, spending and purchase-ownership records can remain to prevent abuse and duplicate use. Calendar events and App Store subscriptions remain; manage or cancel subscriptions through your Apple Account. Signing out or uninstalling does not by itself delete the server account. Deleting the account does not remove content independently retained by a provider under its policies.
- Support requests: are retained only as long as reasonably needed to resolve the request, ordinarily no longer than 12 months, unless law or an active security issue requires longer retention.
To ask a privacy question or request help deleting information, use the Support page.
6. Your choices
You can decline or revoke Calendar, microphone, speech-recognition, motion, notification, camera, and photo permissions in iOS Settings. You can pause iCloud Sync in Planify, export supported planning data, delete your Planify account and its connected workspace, and manage or cancel subscriptions through your Apple Account.
7. Security
Planify uses iOS data protection for local planner files, keeps sign-in credentials in secure device storage, uses Apple’s private CloudKit database for optional sync, and uses encrypted HTTPS connections for supported external services. No storage or transmission method can be guaranteed completely secure.
8. Children
Planify does not knowingly collect personal information from a child under 13 through the website. A parent or guardian who believes a child submitted information can contact support for deletion assistance.
9. Changes to this policy
This page will be updated when Planify’s data practices materially change. The update date and app-version scope at the top identify the policy that applies.
10. Contact
Questions, deletion requests, and privacy concerns can be submitted through Planify Support.
Email: Support