Privacy Policy

Photos, Videos, and Permissions

• The App reads photos and videos you select through the system media picker or a similar selection flow. It does not request access to your entire photo library. For cloud assets, services such as Google Photos or the OS may download the selected file before providing it to the App. Their own policies apply to that transfer.
• On iOS, the App requests add-only photo access to save exported photos and videos. On Android 10 and later, it saves shared media through MediaStore. On Android 8–9, saving photos requires storage write permission; video saving is not supported on these versions.
• Photos, videos, and exported files are not uploaded to the developer, PostHog, RevenueCat, or Meta. Media filenames, image or audio content, embedded media location, preset names or complete preset configuration, and exact custom color values are not included in analytics events. Limited classifications of editing settings, such as frame type or layer count, may be included in usage analytics.
• Exported photos may retain metadata from the source, including capture time or GPS coordinates. This happens on-device. Check metadata when sharing an exported file if necessary.

Information Stored on Your Device

• The App stores a temporary copy and settings to resume a photo edit, along with presets, favorites, and guide progress. Android also uses temporary video copies for reliable reading and export.
• Cached media can be removed when another asset is selected, processing finishes, or the App or OS clears its cache. The previous edit may then be unavailable. Presets contain no photos, videos, or location data. Deleting the App removes its local data.

Usage and Technical Data

• The App uses PostHog (PostHog, Inc.) for product improvement and troubleshooting. It sends pseudonymous app or device instance identifiers, events such as app opens, screen views, editing, and export success or failure, and technical details such as app version, OS, device type, screen size, language, time zone, and network state. Pseudonymous identifiers are not names, but are treated as information associated with a user or device.
• For loading or export failures, the App may handle the error type, processing stage, and limited diagnostic information. PostHog and Meta SDK components bundled with iOS may also handle limited technical or operational diagnostics and crash reports.
• Services receiving network requests and hosting providers handle IP addresses and access logs. PostHog does not store raw IP addresses in analytics events. Its standard GeoIP processing derives country or region, city, postal code, and approximate latitude and longitude from an IP address for usage analytics. This is separate from photo GPS metadata or access through a device location permission.
• The App retrieves a publicly hosted update information file to display release announcements. The hosting provider also receives technical information associated with that request.

Purchases and Inset Lab

• Purchases are processed through Apple (App Store and StoreKit) on iOS and Google (Google Play) on Android. The App does not collect or store card numbers or bank account details.
• RevenueCat (RevenueCat, Inc.) receives receipt or transaction information, product IDs, purchase, renewal, expiration and restore status, and a pseudonymous App User ID. These are used to validate purchases, unlock Inset Lab, restore purchases, and analyze purchases.
• The App passes a pseudonymous PostHog identifier to RevenueCat. RevenueCat sends purchase lifecycle events to PostHog, where they are associated with usage analytics. This integration may create a pseudonymous person record in the service; it is not an account for signing in to the App. RevenueCat automatic device-identifier collection is disabled in the App. The App does not set names, email addresses, telephone numbers, or Apple or Google account information on these identifiers.

Service Codes (Android)

When you use a service code on Android, the entered code and your pseudonymous RevenueCat App User ID are sent over HTTPS to a validation service hosted on Cloudflare. Cloudflare also receives network metadata such as your IP address. The service validates the code and sends the App User ID and a request for complimentary Inset Lab access to RevenueCat.

The validation service application does not record raw codes, App User IDs, or IP addresses in its logs or database. To limit abuse, it derives an HMAC identifier (a hash made with a secret key) from the IP address and uses it for a short-lived rate-limit counter that is automatically cleared. Separately, a customer-derived HMAC identifier and grant-status record are retained to prevent duplicate grants, with no automatic expiry. HMAC identifiers are also treated as pseudonymous information. Network and service records handled by Cloudflare and RevenueCat remain subject to their own retention practices.

iOS Advertising Measurement

• For Apple Ads attribution on iOS, the App may send Apple’s attribution result, campaign, ad group, keyword and ad IDs, claim or conversion type, country or region, and placement to PostHog. The attribution token, raw Apple API response, and ad click or impression timestamps are not stored or sent.
• In a supported iOS production release, the Meta SDK is enabled only after permission through App Tracking Transparency (ATT), sending app activation and first photo export completion events. On iOS, RevenueCat’s Meta delivery also requires ATT authorization and an explicitly enabled integration, and may send trial start, purchase, subscription, renewal and similar events server-to-server. iOS server-to-server delivery without ATT authorization is not enabled. Purchase and revenue events are not sent to Meta from both the App and RevenueCat. Apple defines this purpose as tracking.
• When ATT is not authorized, is denied or restricted, or required production configuration is unavailable, the App does not initialize the Meta SDK or send Meta’s anonymous identifier or in-app events. Your choice does not affect using the App, purchasing, or restoring purchases. You can change permission in iOS Settings. After permission is withdrawn, new iOS tracking data is no longer sent to Meta; previously sent data remains subject to the recipient’s retention and deletion practices. The Android version does not include these iOS Meta SDK, Apple Ads, or ATT flows.

Third-party Services and Protection

The App sends data to the services above as needed for usage analytics, purchases, and advertising measurement. It does not display third-party ads, sell data, or provide data to data brokers. These services may process information outside Japan. When RevenueCat’s Meta integration is enabled for a configuration, purchase and subscription lifecycle information may be sent to Meta. The absence of a Meta SDK on Android is separate from service-to-service delivery. Conditions for iOS advertising measurement are described above. Communication with PostHog uses HTTPS, and temporary media copies are managed in App-private storage.

See the privacy policies of PostHog, RevenueCat, Cloudflare, Apple, Google, and Meta for their practices.

Retention and Deletion Requests

• Local App data and purchase or pseudonymous analytics records held by services are managed separately. Deleting the App does not cancel a subscription or delete service-side records.
• Service-side information may be retained for as long as needed for analytics and purchase validation, under the providers’ retention practices, and for security, fraud prevention, accounting, or legal requirements.
• For a privacy inquiry or deletion request, email contact@atelier-yohaku.com. The App has no personal account system, so pseudonymous records may not be identifiable from your name or email address. We do not currently provide a dedicated method that reliably matches and deletes anonymous records. We may request only the information needed to locate records and explain what can be located and deleted, as well as information that must be retained for legal or other applicable requirements.

Support Inquiries and Website

The email address and content you send in a support inquiry are used to respond and provide support. Do not send unnecessary private photos or videos, verification codes, or payment information. See also the operator website privacy policy for use of that site.

Children’s Privacy

The App is intended for users aged 13 and older. It does not ask you to enter directly identifying information such as your name or email address.

On Android, depending on the region and Google Play settings, the App processes age ranges and age-verification status supplied by Google Play only in memory while running, to determine access to the App. The App does not send these signals or the resulting access status to our servers, PostHog, RevenueCat or advertising services, or save them in application logs or persistent storage. The App does not ask you to enter a date of birth, identity document or facial photo for this process. If Google Play requires age verification, the App directs you to Google Play. Google’s policies govern processing performed by Google Play itself.

Changes and Contact

Material changes will be announced in release information or on this page. For questions about the App or privacy, contact Atelier Yohaku (Yohaku Seisakusho) at contact@atelier-yohaku.com.