← App Studio
Privacy

Privacy Policies.

Effective August 4, 2026. Choose an app below for its specific policy.

DaybreakIn

DaybreakIn does not include third-party advertising, cross-app tracking, or third-party behavioral analytics. It does not sell Calendar, Reminder, Health, Screen Time, planning, reflection, or story information.

Local data

Task Focus items, intentions, mood logs, stories, generated illustrations, Pause reflections, and related daily information are primarily stored locally on your device.

Optional iCloud synchronization

Daily timeline data may sync through your private iCloud container when you enable iCloud synchronization. This optional synchronization is subject to Apple’s iCloud privacy practices. DaybreakIn does not store Health information or Screen Time usage history in iCloud.

Calendar and Reminders

With your permission, DaybreakIn can read Apple Calendar events and Apple Reminders to display them in your timeline. This information is not sold, used for advertising, or sent to an external analytics service. You can hide either source in DaybreakIn or revoke permission through system settings.

Focus Shield and Screen Time

Focus Shield is a free feature that uses Apple’s Family Controls and Managed Settings frameworks to temporarily restrict the apps and categories you select while a Task Focus timer runs. DaybreakIn does not read or display daily or weekly Screen Time usage history, upload Screen Time history, retain Screen Time reports, monitor which apps you open, or measure how long you use them. It stores only Apple-provided private selection tokens locally and removes active restrictions when the focus session ends.

Apple Health

Optional Apple Watch Pause cues read only Apple Health high-heart-rate alert events. DaybreakIn does not read raw heart-rate history. It does not write or modify Health data. It does not upload Health data to iCloud or use Health data for advertising or profiling. The event is processed on device and used only to offer a gentle Pause notification. DaybreakIn is not a medical device and does not diagnose stress, illness, or any medical condition. This feature is free and optional.

Microphone and speech

Microphone access is requested only when you choose voice input. Speech transcription is configured to require Apple’s on-device speech recognition. DaybreakIn does not send recordings to an external AI service.

On-device intelligence

Foundation Models and Image Playground features run through Apple’s on-device frameworks on compatible devices. Generated illustrations are saved locally only after you choose or accept an image. On unsupported devices or when an Apple model is unavailable, DaybreakIn uses local fallback behavior where available and does not promise that AI features will be available.

Notifications

Notifications are optional and may include morning intention check-ins, evening feeling check-ins, reminders, focus timer or Live Activity updates, and optional Apple Watch high-heart-rate Pause cues. Notifications are not advertising and can be disabled through DaybreakIn or system settings.

Analytics and tracking

DaybreakIn does not include third-party advertising, cross-app tracking, or third-party behavioral analytics. Apple may provide the developer with aggregated App Store analytics under Apple’s own policies.

Data deletion and export

You can delete DaybreakIn data through Insights → Settings gear → Delete All My Data. Deletion removes local DaybreakIn data and requests deletion of the app’s private iCloud record. You can export supported data as JSON. Storybook PDF export requires DaybreakIn Pro.

Retention

Local data remains until you delete it or remove the app, subject to device backups and Apple’s platform behavior. Private iCloud data remains until you delete it through DaybreakIn or manage it through Apple’s iCloud controls.

Contact

For privacy questions, contact thecalicocat.coco@gmail.com.

KitchenPeer

KitchenPeer is local-first. It does not sell recipes, pantry data, meal plans, shopping lists, cooking activity, purchase details, or personal data. It does not include third-party advertising SDKs or use cross-app tracking.

Data KitchenPeer processes

KitchenPeer may process recipes, ingredients, pantry items, quantities and units, purchase and expiry dates, freshness estimates, meal plans, shopping-list items, cooking steps, timers, notes, recipe photos or documents you choose, receipt scans you choose, app settings, and Pro entitlement state. This information supports the features you request, including stock updates you confirm after cooking.

Recipe import and scanning

You can create and edit recipes manually or import pasted text. Pro users can also import from links, photos, PDFs, and receipt scans. Camera access is used only when you choose to photograph a printed recipe or receipt. Images and documents are accessed only through the system picker after you choose them. KitchenPeer does not send recipes, pantry items, scans, or cooking activity to an external generative-AI service.

Link import

When you choose to import a recipe from a link, KitchenPeer must fetch that public page. The website may receive ordinary request information, such as your IP address, under its own privacy practices. KitchenPeer uses the page to perform the import you requested.

Local storage and private cross-device sync

KitchenPeer stores data on your device by default. When Pro is active and iCloud is available and configured, recipes, pantry information, meal plans, shopping lists, and cooking-related records can sync through your private iCloud account. Apple controls iCloud authentication, encryption, and account access. If iCloud is unavailable or Pro is inactive, KitchenPeer continues using local storage.

Purchases

Apple handles KitchenPeer Pro purchases through StoreKit and App Store Connect. KitchenPeer receives only the entitlement status needed to determine whether Pro is active and does not receive your full payment card details.

Optional permissions

Permissions are requested only when you use the related feature. Camera is used for recipe or receipt photos you take in the app. Microphone and Speech Recognition are used for hands-free cooking commands. Notifications are optional and used for cooking timers and pantry expiry reminders. You can disable granted permissions at any time in iOS Settings.

Apple platform features

Widgets, Live Activities, App Intents, and the share extension use only the information needed to show or run the KitchenPeer experience you request. Shared app-group storage gives the related extensions access to relevant local KitchenPeer data. The embedded Apple Watch companion receives a compact copy of up to 25 current recipes from the paired iPhone through Apple WatchConnectivity and stores the last received copy on the watch for offline cooking. Pantry, meal-plan, shopping-list, and active iPhone timer state are not sent to the watch.

Analytics and tracking

KitchenPeer does not include third-party advertising SDKs, use cross-app tracking, or sell personal data. Apple may provide the developer with aggregate App Store Connect analytics, crash information, proceeds, and subscription reporting under Apple’s policies.

Food-safety notice

Freshness dates, expiry suggestions, pantry matching, and cooking suggestions are estimates for planning convenience. Rely on product labels, allergy information, appliance instructions, food-safety guidance, and your own judgment before cooking or consuming food. KitchenPeer is not medical, nutrition, allergy, or professional food-safety advice.

Your choices and deletion

You can edit or delete KitchenPeer content in the app and disable optional permissions in iOS Settings. Deleting the app removes local app data from that device, subject to device backups and Apple’s platform behavior. Data synced through your private iCloud account is governed by your Apple ID and iCloud settings.

Contact

For privacy questions, contact thecalicocat.coco@gmail.com.

GPASync

GPASync stores academic records locally on your device using Apple frameworks. No account is required, and GPASync does not sell personal data.

Academic information

GPASync processes the courses, grades, credits, semester progress, graduation plans, academic goals, scholarship information, and GPA forecast inputs you enter to provide personal academic planning and deterministic calculations.

Local storage and services

Academic records remain on your device. GPASync does not use Firebase, external AI providers, or a custom backend for academic records.

On-device explanations

When available, Apple Foundation Models run on device only to explain deterministic academic calculations. They do not replace the underlying calculations or send academic records to an external AI provider.

Widgets and notifications

Widgets use local App Group data to show GPA and credit summaries. Notifications are optional and are used only when you enable reminder toggles. You can disable reminders or notification permission at any time.

Purchases

Apple handles App Store purchases through StoreKit. GPASync receives the purchase entitlement needed to unlock optional Pro features. Apple purchase history remains managed by Apple.

Delete your data

You can delete app data inside GPASync through Settings → Data → Delete All App Data. This removes GPASync academic records stored by the app on your device. Apple purchase history is not deleted because Apple manages it.

Contact

For GPASync privacy questions, contact ddhyuliani@infinitelearning.id.

Energy Valley

Health data is used only to power your in-app village and wellness progress. It is never sold, used for advertising, or shared with data brokers.

HealthKit information

With your permission, Energy Valley reads relevant activity and workout information from Apple Health to calculate energy and game progress. The app requests only the HealthKit data types needed for these features and does not write or access health data without authorization.

Storage

Village state, progression, and preferences are stored on your device and may be shared with the app’s widget through Apple’s app-group storage. Apple controls HealthKit authorization.

Your choices

You can change Health access at any time in the Health app or iOS Settings. The game remains subject to the data available under the permissions you choose.

Trainwell

Trainwell does not sell your workout, readiness, hydration, recovery, or training-history information.

Information used

The app processes workout links you choose to import, generated routines, completed sessions, and wellness information you enter to provide planning, guidance, and history features.

Storage and permissions

Training data is stored on your device and may use Apple platform storage or iCloud when enabled. Any Health, notification, or link-import permission is optional and used only for the corresponding feature.

Your choices

You can edit or delete routines and training history and manage permissions through iOS Settings.

GrowthFest

GrowthFest is an internal event companion for GrowthFest ’26. It uses event information only to operate participant schedules, booth registration, check-in, Growth Passport progress, reflections, and mentor event-management features.

Event information

GrowthFest may process participant names, participant or mentor roles, mentor booth assignments, booth details and schedules, registrations and registration times, participation type, optional sharing topics, check-in status, passport stamps, and learning reflections. The participant directory is searchable inside the app so attendees can select their event identity. Mentor access is protected by a PIN.

Apple CloudKit storage

Event roster, booth, and registration records are stored in the app’s shared Apple CloudKit public database. This is event data shared through the GrowthFest app, not data stored in each participant’s private iCloud account. Apple operates the CloudKit infrastructure. GrowthFest has no third-party software dependencies and does not send this event data to an external advertising or generative-AI service.

On-device storage

The app stores the selected participant record identifier in UserDefaults so it can restore the selected identity. It may also cache the participant directory, including participant names, roles, and booth assignments, on the device to improve loading. Choosing another participant or signing out clears the saved participant identifier.

Who can see information

Attendees can view their own registrations, schedule, and passport progress. Mentors can view registrations for booths they manage, including participant names, check-in or stamp status, participation type, and sharing topics where provided. Event organizers with CloudKit access may administer the roster, booths, and event records.

Permissions

The current app does not request Camera, Photos, Microphone, Contacts, Health, or location permission. A booth’s written location describes an event venue and does not use device location services.

Your choices and deletion

You can unregister from an optional booth inside the app, which deletes that registration record. You can clear the selected identity on your device by choosing another participant or signing out. For roster corrections or deletion requests involving shared event records, contact the event organizer or thecalicocat.coco@gmail.com.

Flourish

Flourish is a private mentoring observation and feedback system for an approved program roster. It does not sell mentoring records or use them for advertising.

Information Flourish processes

Flourish may process mentor names and roles, device pairing status and device label, observation dates and context, observed and observing mentors, mentoring-stage answers, notes, summaries, Growth Activity details, feedback, reflections, archive status, and related program records. Administrators can manage the roster and review program observations.

Cloudflare storage and network information

Flourish sends authorized program data to a Cloudflare Worker and stores it in a Cloudflare D1 database. Network requests necessarily provide Cloudflare with ordinary connection information such as an IP address. During failed pairing attempts, Flourish stores a one-way hash derived from the client address and uses recent attempts to enforce a 15-minute lockout window that reduces PIN guessing.

Pairing and authentication

Participants pair an approved identity using a one-time PIN or QR code. The raw pairing PIN and raw device session token are not stored in the D1 database; only SHA-256 hashes are stored there. On Apple devices, the revocable session token and paired mentor identity are stored in Keychain. Pairing attempts are rate-limited, and administrators can reset pairing or revoke device sessions.

Camera and local data

Camera permission is optional and used only when you choose to scan a one-time mentor pairing QR code. If the web version is used, an unfinished observation or pending submission may be stored temporarily in that browser’s local storage so work can be restored or submitted when connectivity returns.

Access controls

Mentors can read feedback addressed to them and observations they submitted. Only the observed mentor can write the corresponding reflection. Journey access is limited to the relevant mentor unless an administrator is authorized. Administrators can manage roster members, devices, observations, archives, and exports.

Retention and deletion

Program records remain in Flourish until they are archived or permanently deleted by an authorized administrator. Unpairing removes the local identity and revokes active sessions, but it does not automatically delete mentoring observations. Administrators can permanently delete an observation and its associated Growth Activity details and reflection. For access, correction, or deletion requests, contact the program administrator or thecalicocat.coco@gmail.com.

Security and purpose

Flourish uses the information only for pairing, mentoring observations, feedback, reflection, growth journeys, program administration, and authorized exports. No system can guarantee absolute security, but Flourish uses role-based authorization, hashed credentials, revocable sessions, rate limiting, and restricted administrative routes to protect program data.