Privacy Policy

Planify 1.2 privacy notice for people 16 or older in supported regions.

Prepared November 10, 2026Planify 1.2 · minimum 16 in supported regions

Applies to Planify 1.2 when you use that version. Planify 1.1 retains its earlier notice and 18+ minimum. Availability and required approvals can vary by region.

Planify is provided by Peak Development LLC. Support and privacy requests can use Planify Support or hockeycam21@gmail.com, the currently published contact fallback. This mailbox is monitored; response times can vary. The service terms, privacy notice and separate consumer-health notice describe different parts of the service.

This notice applies when you use Planify 1.2, including TestFlight, and covers its widget, share extension and related website and support services. The separate Planify 1.0 privacy notice remains available for that version. Planify does not sell personal information, run third-party advertising or use your plan to build advertising profiles. Device permissions, Account Sync, optional analytics and AI sharing have separate controls.

Your plan, accounts and connections

Your device holds a protected local plan. Optional Account Sync stores supported tasks, schedules, to-dos, routines, projects, Focus notes/history, planning notes, preferences and referenced task/list photos in per-account Cloudflare storage. Sync does not itself send the workspace to OpenAI. Active timers, connection credentials, device permissions and chat history stay on the device. Sharing text or a link to Planify stores a local review draft only after the app’s eligibility check is current; it does not itself send a cloud/AI request. If eligibility is missing, expired or restricted, open Planify to check it before sharing. Pending shared drafts are preserved rather than automatically erased by a restriction. Drafts saved by older versions may remain in the original device inbox and are not retroactively assigned to a particular account by this update. Pausing sync keeps existing copies. Offline devices and older private CloudKit copies may retain information until separately updated or removed.

With permission, selected calendar and task-list content can be read and locally cached. Apple Calendar permits supported writes. Direct Google Calendar and Outlook/Canvas/Notion/subscription-calendar views are read-only here; supported Apple Reminders and Microsoft To Do connections can send user-approved changes back to writable lists. Google Tasks is Coming Soon in this release: new setup, synchronization, list changes and AI access are unavailable. Existing cached data is preserved until you remove it, and existing access can be disconnected or cleaned up. Google sign-in and Google Calendar remain separate available features. Credentials are held in Keychain or the provider SDK's secure storage. Notion OAuth proofs pass through our server for exchange; connection tokens return to the device. Disconnecting removes local credentials/cache, not the original provider records or every task already planned in Planify.

Planify's use and transfer of Google Workspace API information adheres to the Google API Services User Data Policy and Google Workspace API User Data and Developer Policy, including Limited Use. Google Workspace data is not used to create, train or improve foundational or generalized AI models. With explicit AI-sharing permission, relevant selected connection information may be processed to answer your planning request.

Firebase Authentication supports Apple, Google and email/password sign-in. Firebase stores account email, provider identifiers and password hashes for email/password accounts. Signup passwords transit the Planify server to Firebase and are not retained or logged by Planify. Apple and Google passwords are not supplied to Planify. We store keyed account/provider identifiers, hashed sessions, protected authentication records, eligibility and service counts; Apple authorization tokens are encrypted for validation/revocation. Matching email addresses alone do not merge accounts. An initial signup response does not itself establish that an account was created or eligibility was approved; restriction details and account access remain subject to the appropriate verified sign-in/recovery checks. Google sign-in is separate from Calendar access; The included Google Sign-In SDK declares collection of profile/contact information, including phone-number information, identifiers, approximate network location and operational usage information. Planify does not offer phone sign-in or request a phone-number scope.

Apple handles purchases without providing us payment-card details. Server verification uses transaction and entitlement data and opaque account ownership links. Signed app proof may be checked for older restoration without retaining the proof. Limited purchase ownership links survive account deletion to prevent cross-account reuse and support the appropriate restoration path. Account deletion does not cancel Apple subscriptions.

Optional media, health and personal sources

Apple Speech processes selected voice capture subject to device/language/service availability. Camera and selected photos support planning capture and task/list images; Apple Vision can recognize text locally. Plany can send selected photos to OpenAI. Selected PDF-page text, filenames, page numbers and metadata can be sent; the PDF file stays on the device. Follow-ups can reuse selected context. Saved chat-photo sources expire within seven days and a 50MB archive, may expire sooner when full, and are excluded from device backups/iCloud. Cleanup runs when storage is accessed; removal or sign-out clears saved source copies. A subsequent message sends retained images only when you choose Send.

With separate Apple Health permissions, Planify can read permitted sleep/step information for local features and write chosen mood check-ins. It does not read Health mood history or write reflection text to Apple Health. Apple Health records remain independently manageable in Health/iOS Settings after Planify account deletion. Local weather can use device location through Apple Weather. In the 1.2 release scope, Plany does not automatically collect or include HealthKit sleep/step, Apple Weather or device-location context, including through old stored sharing flags. Optional Planify mood/reflection excerpts need a separate source choice in addition to AI permission. Selected calendar/task-list content, including user-entered event locations, and messages/attachments may still reveal health or location information; this is not a promise of no health processing. A selected calendar event can include an exact venue or address, and that location field can be included in retained AI planning context; automatic device-location enrichment remains unavailable. See the separate consumer-health notice.

Optional AI and background delivery

Eligible users can choose Agree to Use Plany. For a person 16–17, this also requires current parent/guardian permission and an available supported method and region; the teen must make their own affirmative sharing choice. Continue without Plany leaves AI sharing off. This does not itself send a chat. Sending may include the message, up to twelve relevant conversation messages, the draft, bounded planning context, selected attachments and relevant connected events/tasks. Up to eight short facts quoted from adult messages can be saved with on-device chat history for follow-up. A new chat starts new memory. Explicit approval applies drafts or changes; AI can be wrong.

Cloudflare and OpenAI process this content to provide planning. Planify requests that OpenAI turn off Responses application-state storage for these requests. OpenAI’s published API default excludes submitted content from model training unless the customer opts in. Provider abuse-monitoring records may generally remain up to thirty days, with applicable safety and legal exceptions. Your withdrawal cannot recall an issued request or erase independently retained provider records immediately.

Accepted background requests use encrypted service storage for the request, selected context/attachments and reply. Unprocessed requests expire within 24 hours. Processed requests are scheduled for removal. Replies expire within thirty days, and device acknowledgment schedules earlier removal. Opaque job metadata expires on its thirty-day schedule. Failed deletion and hosting backups may persist longer. Reply retrieval and later provider steps recheck current age, account access and AI-sharing permission. An earlier accepted check does not itself authorize a later step after a fresh denial; a request already sent to a provider cannot be recalled. Chat history and unfinished chats stay on the sending device. Optional completion notifications use generic completion information and open the matching chat. An encrypted hashed-session reference permits a fresh eligibility check before a pending alert; an expired session can prevent notification, while fresh eligible sign-in can still retrieve an unexpired reply.

AI requires a US network-country signal supplied by Cloudflare; this is not verified residence or GPS tracking. Unknown or other countries cannot use AI, including while travelling. A US admission marker stays with background job metadata for up to thirty days; work without the marker cannot execute or return content.

Separate optional Dynamic Island background updates are off by default. If you enable them, Planify can send generic source icons, counts, times, appearance and an activity push token to our service and Apple for the original activity window of up to eight hours. This transport excludes titles, notes, provider/event identifiers, user URLs, credentials and AI content. Tokens/authorization/payloads are encrypted; operational metadata is opaque. End/cancel/expiry schedules removal, with retries on failure. An offline withdrawal may not reach the service immediately.

Age eligibility and permission records

The first-open Terms acknowledgment is recorded on this device as an agreement version and acceptance time. It is separate from Apple’s age result, account access, guardian permission and AI sharing. It does not itself send a chat or grant analytics, Health, calendar, notification or purchase permission.

Where a parent/guardian permission method is offered, the service handles the request’s contact/identity information, linked account, permission choices, notice/policy versions and decision times to provide and enforce that method. An email link establishes mailbox access plus the stated declarations; it does not independently prove adulthood or guardianship. Requesting permission or opening a link does not itself enable the teen’s AI sharing. The guardian-email method remains unavailable until its reviewed method and market configuration is enabled. Current permission evidence and bounded history follow the retention and rights provisions below; email-provider mailbox copies have separate handling.

Planify 1.2 has a minimum age of 16 in supported regions. Independent access for people 16–17 requires an enabled reviewed-market policy; a country being listed in the App Store is not evidence that this teen policy is active. Parent permission does not override the minimum age or a saved restriction. Initial admission requires Apple’s suitable shared age range and applicable Apple/account checks to succeed. Required Apple approvals remain separate from Planify’s choices. A manual age selection is not an admission alternative. Declined, unavailable or unclear initial sharing leaves ordinary app and AI access unavailable; Settings, retry and account/privacy/billing help remain available. Planify does not request your exact birthday or an identity-document upload in ordinary setup. Apple range information may be user-declared, guardian-declared or confirmed according to Apple's process; this is not universal independent identity verification. Required significant-update, denial/revocation and account-age correction controls remain separate from your AI-sharing choice.

After a genuine completed Apple age check meeting the current minimum and same-account admission, a protected device-only record can remember that result for the same installation, account and policy. Ordinary reopens can show your saved planner without repeating a blocking age screen. It is cached access information rather than a newly returned Apple answer, and does not grant server access or AI consent by itself. Regulatory checks and bounded range rechecks can run without replacing the admitted planner. An explicit recheck, owner change, definite refusal/restriction or new required control can invalidate it.

For server admission, Apple App Attest binds an age-access report to a genuine instance of the app and a short-lived server challenge. The service checks the report, request/key binding and replay counter before saving verified access evidence. Apple App Attest establishes app integrity, not independent proof of a person's legal identity or birthday. The limited report can contain age bounds, Apple declaration/check status, policy/account context and timestamps. The service also handles a public app/device-key identifier, public verification key, integrity proof and counter. A private signing key stays on the device. An opaque Apple receipt may also be retained for bounded abuse-prevention handling; we do not treat it as an independently verified fraud metric or age/identity proof. Challenges and single-use admissions expire after two minutes. A trusted-app age report remains valid for thirty days; routine resumption can sign a new challenge against that stored report without sending a fresh age report. Public keys, device bindings, counters and the limited opaque receipt are kept until ninety days of inactivity and are removed only when no active report still references the key. Expired challenges/admissions are cleaned during new challenge issuance and hourly service cleanup; expired reports/session references and unreferenced inactive keys are cleaned during hourly service cleanup. Physical removal can follow expiry and may require retries. Final account deletion removes that account's keys, receipts, reports, challenges/admissions and session references; separate protective minor/revocation denial records and hosting backups retain their stated limits.

Pre-release accounts retain their saved-data and rights routes. If an existing account is below the applicable minimum, has an unresolved earlier minor restriction or lacks a required permission, it can be restricted while support, data-rights, billing-management and deletion help remain available. Restriction alone does not silently erase plans. Recorded minor restrictions are not removed merely by choosing adult or reinstalling. The service preserves protective restrictions for recognized verified identities after account deletion; using a different identity is not an authorized way to bypass the age rule. Historical guardian choices, notice versions, keyed recipient/guardian identifiers and bounded permission history may remain until deletion/expiry; these do not by themselves enable ordinary teen access or Plany. For email/password sign-in, the service can associate an account with a purpose-specific keyed value derived from the email verified by Firebase, after server identity/session checks. If that recognized account has a protective minor restriction or its required app permission is revoked, a limited protective record keeps the keyed value, denial reason and time to prevent access through a newly created Firebase account using the same verified mailbox. It does not store the raw email in that protective record, merge workspaces or grant adult status. The active account association is removed on deletion; the protective denial currently has no automatic expiry. Contact support about an incorrect restriction, including a shared or reassigned address. Addresses not previously observed cannot be identified retroactively by this mechanism. Current permission evidence remains while the account exists and up to 100 recent decision records are retained for one year. Contact support for a disputed age record or suspected underage use; do not supply another person's identity to bypass a restriction.

Diagnostics, feedback and retention

Optional app analytics are off by default. Opted-in action names, timing, app version and redacted counts use a random installation ID; an opaque purchase-account token can associate outcomes. Planner/calendar/Health content is not attached. Optional analytics expire after ninety days. Turning them off or requesting deletion may queue an offline retry. Apple MetricKit can provide bounded diagnostics. Necessary authentication, abuse prevention, allowances and costs use separate operational records.

Individual operational request details expire after thirty days; current-month allowances and aggregate counts/costs remain to enforce limits. Purchase status and monthly reporting may remain up to one year. Feedback contains only the chosen message/category, optional reply contact and optional app/device details; Plany ratings/notes do not automatically include chats. In-app feedback is scheduled to expire after 365 days. We keep support email and any attachments you send for as long as needed to handle your request, maintain relevant records, or meet legal and security obligations.

Cloudflare hosts the website and processes network/request information for delivery and protection. Where enabled, its Web Analytics records website traffic/performance separately from the app analytics choice. Support messages and chosen attachments sent through branded support/privacy aliases may be processed by Cloudflare Email Routing, Gmail and Resend. Direct mail to the published Gmail fallback is received by Gmail. Resend may also process historical and, where an approved email method is enabled, current parent-permission mail; mailbox copies and in-app feedback have separate deletion/retention handling. Apple, Google/Firebase, connected providers, Cloudflare, OpenAI and relevant email providers process information for the purposes described here and under their own applicable terms. We may disclose information where legally required or necessary for applicable security/legal purposes.

Security

Planify uses operating-system data protection, secure device credential storage, authenticated account access and encrypted HTTPS connections. Stored background AI content and selected server credentials are encrypted. Account Sync is protected service storage and is not end-to-end encryption against the service operator. No method of storage or transmission can be guaranteed completely secure.

Your choices and rights

You can decline/revoke device permissions, disconnect sources, pause sync, withdraw AI, remove saved photos/history, export supported planning data and request account deletion. These have different effects. AI withdrawal stops new sharing on this device immediately; offline server withdrawal retries when connected. Other devices/jobs follow the last saved server choice until it arrives. The server then rejects subsequent AI steps/results and attempts cancellation; an issued provider call may finish.

Account deletion requires fresh same-account sign-in and confirmation. It removes active account access, server workspace, relevant permission records and this device's plan. Interrupted provider cleanup can retain an encrypted deletion target/journal until retry succeeds. Opaque deletion markers prevent stale workspace upload. Original provider tasks/events, Apple Health records, Apple subscriptions, disconnected devices and older iCloud copies require separate handling. Limited purchase/allowance, app-withdrawal and anti-downgrade denial identifiers can survive deletion for restoration, security and protective access purposes. Limited legacy-denial identifiers have no automatic expiry in the current implementation. Hosting backups follow provider retention; restoring a backup must not restore active access to a deleted account.

For access, correction, export, deletion, withdrawal or an applicable appeal, contact Planify privacy help or hockeycam21@gmail.com. We may request proportionate information to protect the account and locate records; do not send passwords, identity documents or unrelated medical records through ordinary support. We handle applicable rights within governing deadlines. If we decline a privacy request and you want us to review the decision, reply to that decision or email hockeycam21@gmail.com with the subject Privacy appeal and the request reference. We will explain the outcome and any applicable complaint route within the time required by applicable law. You do not need to create a new account to contact us about a privacy request. Independent providers may require a separate request. Lock-screen widgets, notifications and Live Activities can expose information according to your settings; review visibility and title-hiding controls.