Effective Date: April 12, 2026
Last Updated: May 6, 2026
This Vowlet Privacy Policy (hereinafter referred to as “this Policy”) is established by LittleBoris (hereinafter referred to as “we” or “us”) and applies to the Vowlet iOS application and its related features, pages, synchronization capabilities, notification capabilities, sharing capabilities, and support services.
This Policy is intended to explain: what information we process when you use Vowlet, why we process such information, how such information is stored and shared, and how you may manage your privacy and permissions.
If you do not agree with all or part of this Policy, you should discontinue use of the relevant features; however, please note that certain core functionalities may not operate properly without the necessary permissions or data.
This Policy applies to:
This Policy does not apply to:
For services provided by Apple, Apple may process relevant data independently in accordance with its own privacy policy and terms of service.
We process information in accordance with the principles of “necessary for feature functionality” and “minimal necessity.” Based on the code implementation of the current version as of May 6, 2026, Vowlet may process the following information:
Personal Profile Information Including your nickname, avatar Emoji, Memoji/avatar image, and avatar background color that you set or generate using system capabilities, as well as name information that may be synchronized from Apple CloudKit identity information in team sharing scenarios.
Vow and Plan Content Including vow titles, descriptions, categories, priority levels, goals, start dates, end dates, participant roles, invitation statuses, node tasks, check-in tasks, witness messages, completion notes, archived images, and vow locations.
Team Sharing and Partner Relationship Information Including CloudKit user record identifiers of friends, nicknames, avatar display information, last collaboration time, time added, and invitation and member status information used to establish and maintain sharing relationships.
Witness Messages In team-shared vows, you may send witness messages to other participants. Witness messages include message text and sending time, and are synchronized among all participants via CloudKit.
feedback@littleboris.com or contact us through other means, we may receive your email address, email content, and any attachments or issue descriptions you voluntarily provide.This information is used solely for exercise/sleep check-in verification, chart display, statistical display, and automatic completion determination. The current version does not upload raw HealthKit data to our own servers for advertising, marketing, or data brokerage purposes.
Location Information When you use the location-based check-in feature and grant location permissions, Vowlet reads your device’s location for that session to verify whether you have arrived at the designated location. If you complete a location-based check-in, the relevant check-in coordinates are saved as part of the check-in record within the application data, and may be synchronized across your devices via Apple’s iCloud / CloudKit mechanism.
Map and Location Search Information When you use features such as location search, location selection, or map display, your search keywords, location results, and map-related requests may be processed through Apple MapKit services.
Notification and Reminder Related Information Including notification authorization status, reminder preferences, reminder times, do-not-disturb periods, notification type preferences, and minimal necessary parameters used for notification navigation (e.g., vow identifier, notification type, target page).
Technical and Synchronization Related Information To implement iCloud / CloudKit synchronization, sharing relationship establishment, shared database subscriptions, and background silent refresh, Apple and system frameworks may process necessary technical information, including device and system environment, CloudKit record identifiers, sharing metadata, push event information, and necessary service status information.
As of May 6, 2026, the current version has not identified the following capabilities being used for core business processing:
Should future versions introduce any of the aforementioned capabilities or other new data processing activities, we will update this Policy and, where required by applicable laws, separately obtain your authorization or provide additional explanations to you.
We primarily collect information through the following methods:
Information You Directly Provide For example, when you fill in your nickname, create a vow, set tasks, send witness messages, submit text/image check-ins, or send feedback emails.
Information Generated When You Voluntarily Trigger System Capabilities For example, when you tap location-based check-in, select photos, enable notifications, authorize HealthKit, search for locations, or use team sharing.
Information Returned by Apple Systems and Cloud Services For example, identifying sharing relationships through CloudKit sharing invitations, refreshing profile information through CloudKit public databases, prompting for shared status changes through silent push notifications, and returning purchase transaction information through Apple’s in-app purchase mechanism.
Information Automatically Generated on the Local Device For example, notification preferences, read status, certain feature toggles, reminder deduplication markers, local cache status, and subscription entitlement information.
We process your information primarily for the following purposes:
Providing Core Functionality For creating, editing, displaying, and managing vows, tasks, nodes, statistics, and check-in records.
Verifying and Displaying Check-in Results For example, generating or displaying check-in status based on the text you enter, images you submit, your current location, and HealthKit reading results.
Providing Synchronization, Backup, and Multi-Device Experience When Apple iCloud / CloudKit is available, for synchronizing necessary application data across your devices and maintaining profile records required for sharing relationships.
Establishing and Maintaining Team Sharing Relationships For creating invitations, identifying the identities of both parties to an invitation, maintaining partner lists, synchronizing profile information, and processing shared status changes.
Sending Reminders and Messages For scheduling local reminders, displaying real-time notifications, and triggering appropriate prompts or page navigation after shared status changes.
Providing Support, Troubleshooting Issues, and Maintaining Service Security When you report issues or when we perform necessary processing to ensure functionality stability, integrity, and security, we may use the minimum necessary information.
Processing In-App Purchases and Subscriptions For verifying purchase status, managing subscription entitlements, and providing purchase restoration functionality.
Fulfilling Legal Obligations or Responding to Legitimate Requests Under applicable laws, regulatory requirements, judicial orders, or legitimate governmental requests, we may process or disclose necessary information.
The current version processes certain persistent data based on Apple’s SwiftData and CloudKit mechanisms. This means:
To support partner identification and profile refresh, the current version may write the following profile information to the corresponding records in Apple CloudKit:
Some of this information is used for:
Please do not set highly sensitive, confidential, or information you do not wish to display in sharing relationships as your nickname or profile information. In particular, the current version may synchronize the real name field in team sharing scenarios; therefore, you should carefully evaluate whether to enable the relevant sharing capabilities.
As of May 6, 2026, in the current code implementation, data directly related to establishing relationships with other users is primarily focused on:
Shared Data Visibility:
Should future versions introduce broader multi-party collaboration, cross-user vow sharing, cross-user check-in, or community interaction capabilities, we will update this Policy separately based on the new functionality.
After you authorize Vowlet to access HealthKit, we read exercise and sleep information related to functionality for the following purposes:
Regarding HealthKit data, we specifically note:
You may revoke the relevant authorization at any time through the Health app or system settings on your iPhone. Upon revocation, the relevant functionality may be degraded, rendered inoperable, or unable to continue automatic determination.
When you use location-related features:
Location Setting You may voluntarily select location names, coordinates, and radius ranges for vows or check-in tasks.
Location Verification When you initiate a location-based check-in, the application reads your device’s actual location for that session and determines whether you are within the target radius.
Record Storage The current version saves the actual check-in coordinates of location-based check-ins as part of the check-in record. This record may be saved locally along with application data and may be synchronized via Apple’s iCloud / CloudKit mechanism.
Apple Map Services If you use location search, map display, or map feature parsing functionality, the relevant requests may be processed by Apple MapKit.
If you do not agree with our processing of location information as described above, please do not enable the location-based check-in feature or disable location permissions in system settings.
The current version allows you to:
These media contents are voluntarily selected and submitted by you. Except for local display, persistence, and Apple cloud synchronization necessary to implement functionality, we do not use them for advertising analytics or sell them to third parties in the current version.
The images you select are compressed before saving to optimize storage and transfer efficiency. Compressed images may be synchronized across your devices via Apple cloud services. Images in your original photo album are not directly accessed or uploaded by the application.
Please do not upload images containing other individuals’ private information, sensitive documents, financial information, medical records, or other content you are not authorized to share.
Vowlet uses notification capabilities to provide:
The current version simultaneously uses:
Notification Related Data:
Notification content may include vow titles or functional text and may be displayed on the lock screen, notification center, or banners in accordance with your system settings. You may disable notification permissions at any time in system settings, or adjust reminder preferences and do-not-disturb periods within the application.
Except in the following circumstances, we do not sell your personal information to third parties, nor do we use your personal information for third-party advertising targeting:
Disclosure to Apple-Provided Infrastructure To implement Apple platform capabilities such as iCloud / CloudKit, HealthKit, MapKit, photo selection, and push notifications, necessary information may be processed by Apple as an independent service provider.
Disclosure to Other Users When You Voluntarily Use Sharing Features When you use team sharing or partner invitation features, certain profile information and sharing relationship information may be visible to other users who have established a relationship with you.
Reporting and Security Protection Vowlet provides a reporting feature that allows users to report inappropriate content or behavior. When you submit a report, the relevant information is used solely by the developer for security review and processing.
Legal Requirements or Rights Protection When we have reasonable grounds to believe that disclosure is necessary to comply with legal obligations, enforce agreements, protect user safety, investigate fraud, or respond to legitimate requests, we may disclose necessary information as required by law.
Business Reorganization or Asset Transfer In the event of a future merger, acquisition, reorganization, asset transfer, or similar transaction, relevant information may be transferred as part of the transaction. In such cases, we will take reasonable notification measures as required by applicable laws.
Data in the current version may primarily be stored in:
We generally retain information for the minimum period necessary to fulfill the purposes of processing, unless a longer retention period is:
In the current version, vows, check-ins, profiles, partner relationships, and notification preferences are generally retained until:
Account Change Protection: When Vowlet detects that your iCloud account has changed, it automatically clears all locally stored application data, including vows, profiles, friend relationships, and more. This mechanism ensures that your data is not inadvertently disclosed or confused following an account change.
Based on the capabilities of the current version, you may generally:
To comply with Apple Guideline 5.1.1(v), Vowlet provides a complete account and data deletion feature. As Vowlet does not use an independent account system, the deletion process will clear all application data associated with you.
The deletion process includes the following steps:
Important Notice:
If you wish to exercise deletion, correction, or other requests regarding data within the scope of application support, you may contact us through the contact information provided at the end of this Policy. For data independently controlled by the Apple platform, you may also need to process it through Apple’s settings or service pages.
We implement reasonable security measures appropriate to the current product form, including but not limited to:
However, you understand that no application, device, local storage, network transmission, or cloud environment can be made absolutely secure. Please safeguard your own device, Apple account, and system access permissions.
Depending on applicable law, you may have the following rights:
You may manage your privacy through the following methods:
In certain circumstances, due to identity verification, technical limitations, legal obligations, or the protection of others’ rights, we may not be able to fully accommodate your request, but we will provide explanations within a reasonable scope.
Vowlet is not specifically designed for children. If applicable law requires you to obtain guardian consent before use, you should use the relevant services only after obtaining appropriate authorization. If we discover that information of minors has been collected in violation of applicable law, we will take reasonable measures to address the situation as promptly as possible.
As the current version relies on services provided by Apple, including iCloud / CloudKit, MapKit, HealthKit, and others, relevant data may be processed in data centers or service nodes operated by Apple in different regions, depending on Apple’s service architecture, your account settings, and applicable law.
The core functionality of our current version is not centered on self-built general-purpose business backends; however, this does not mean that cross-regional data processing does not exist. Processing activities involving Apple platform services may still be subject to Apple’s cross-border rules and related terms.
To ensure compliance with future product expansion, should future versions introduce the following capabilities, we may process corresponding information within the necessary scope and will notify you through updates to this Policy, pop-up explanations, permission request pages, or separate agreements:
The current version has already implemented subscription functionality through Apple’s in-app purchase mechanism, including monthly, annual, and lifetime subscriptions for individual and family plans. All payment processing is completed by Apple; Vowlet does not collect or store your payment information. Subscription status is used solely to control feature access and is not used for advertising targeting or user profiling.
Before the aforementioned capabilities are actually enabled, the relevant reserved provisions in this Policy do not constitute an indication that we have commenced corresponding processing activities.
We may update this Policy based on changes in law, regulatory requirements, product feature iterations, or changes in processing activities. Updated versions will be published through in-app pages, official website pages, release notes, or other reasonable methods.
If an update would have a material impact on your rights, we will provide you with more prominent notice to the extent required by applicable law.
If you have questions about this Policy, your personal information, how permissions are used, or data processing requests, you may contact us through the following methods:
feedback@littleboris.comWhen contacting us, please try to include:
To avoid inconsistencies between the Policy and implementation, as of May 6, 2026, the current version specifically notes the following: