dolcam Privacy Policy
Effective: 2026-10-27 / Last updated: 2026-11-07
1 Operator and scope
桜谷俊輝 handles information in dolcam as described here. The address will be disclosed without delay upon request. Contact rebirth.sakuraya@gmail.com about information handling or deletion.
This Policy covers the app and its Faves outline service. Apple and services you share to also apply their own policies to information they handle independently.
2 Photos and settings on your device
Camera photos, ordinary photo processing, editing, and frame composition are handled on your device. We do not send photos to our servers for those tasks. External processing of Faves photos is the exception described in section 4. User-initiated sharing is described in section 6.
The app handles the following locally:
- Captured photos and thumbnails.
- Original and corrected photos, with correction settings, capture dates, and other information for re-editing.
- Reduced-size imported Faves photos and outlines, names, shooting settings, shot counts, and last capture dates.
- Saved poses and pose collections, including collection names and usage dates.
- Camera and correction preferences, including your external outline processing choice.
- Paid access status, verification time, and purchase evidence including expiration dates and transaction identifiers.
- First launch date, cumulative successful save count, and dates when the app requested a review dialog.
- Identifiers of poses used for shooting, photo save counts, edited photo save counts, and notification dates scheduled based on the last time you used the app.
- Notification preferences and permission status, counts of permission explanations shown and permissions granted or declined, and notification scheduling and opening counts.
- Onboarding completion status, whether you have previously subscribed, and the number of times you closed the paid plan screen.
Imported Faves photos are saved as reduced-size images with a longest side of up to 1,024 pixels. The app does not keep its own copy of the full-size imported original. The source image in your photo library is unaffected.
The iOS photo picker supplies the photos you select. The app does not request permission to read your entire photo library. Exporting requests permission to add photos. Camera access also requires iOS permission. You can manage permissions in iOS Settings.
3 Skin correction and face and body detection
Skin correction models run on your device. The app temporarily detects facial landmarks and skin regions, and uses body and hand positions for pose guidance. These results support corrections and composition guidance, not identity recognition or authentication.
The app does not store detection results as a separate face data record. They are updated or released in processing memory. Photos and detection results are not sent externally for skin correction. Saved photos themselves may contain faces.
The current skin correction path uses detection models bundled with the app. It does not send correction photos to the model provider.
4 External processing of Faves photos
Your choice and the image sent
The app sends a selected photo for external outline creation only if you choose cleaner outlines. You can choose to create outlines only on this device instead. You can change the choice in the app's settings. A saved choice applies to later imports too. Changing it does not undo past transmissions.
Before sending, the app places the photo in a 2:3 canvas and creates a JPEG with a longest side of up to 768 pixels. Faces and background details may remain visible. Check that you have the necessary permission to use and send the photo.
Transmission to Supabase
The app uses Supabase authentication and a relay server. It creates an anonymous account without asking you to register a name or email address. Checking the remaining allowance also involves authentication traffic. “Anonymous” does not mean the server cannot distinguish repeated use under the same ID.
A generation request to the relay contains the photo, a request identifier, and an authentication token. For paid access, it may also contain Apple-signed purchase evidence with product and transaction identifiers, expiration information, and other transaction details. This verifies allowances and paid access. Purchase evidence is not forwarded to OpenAI with the photo.
The free allowance is limited to one per device. To check this, the app sends a temporary device token issued by Apple to the relay, which queries Apple's DeviceCheck service. Apple records only a marker showing that the device has started its free allowance. The token itself is not stored on the server. To prevent duplicate use, a one-way hash of it is kept for one day. The marker is not removed when you delete the app or your account.
Authentication session credentials are saved in your device's Keychain to reuse the anonymous account. They may remain after you delete the app.
Transmission to OpenAI and image retention
The relay sends the photo to OpenAI's image editing API with fixed instructions to create a pose outline. The resulting outline is returned to the app. The request to OpenAI does not include your anonymous account ID or any Faves name you enter.
Our relay application processes photos and outlines in memory. It does not save photos in its database or files. Outlines are stored only when covered by the collection described in the next section. Its application logs do not contain images or authentication tokens.
OpenAI's handling follows its API services agreement and data retention policy. Under the standard policy, API data is not used for training unless explicitly shared for that purpose. Abuse monitoring logs are generally retained for up to 30 days, with legal and safety exceptions. Content, including images, suspected of violating usage policies may be retained and reviewed by people. This app's implementation does not disable OpenAI's retention.
Records retained on the server
The server stores successful generation counts associated with an anonymous account ID. It also stores request identifiers, processing states, start and completion times, and estimated and actual processing costs. These records manage allowances, prevent duplicate execution and excessive use, and control costs.
Application error logs include error types and request identifiers. They may also include upstream response status and limited error codes. They are not used to log image bodies or purchase evidence.
Receiving infrastructure also receives network information such as IP addresses. Supabase and OpenAI may process infrastructure logs for security and operations. Our relay not storing photos does not mean that the entire infrastructure leaves no records.
4a Collection of outlines used for photos
Help improve poses is on by default. When it is on and you have not chosen to create lines only on this device, the app sends one outline to the operator's Supabase server after you first successfully take a photo using that imported pose. Imported poses already used for a photo before this feature was introduced are also sent if not yet submitted, for example when you open the app. Each pose is sent only once. Imported poses that have never been used for a photo are not sent. Failed transfers are retried when the app next returns to the foreground or you take another photo.
We send the outline used for the photo, its line type and aspect ratio, and a random ID for each pose to prevent duplicates. The existing anonymous account authenticates the request; the server also stores its anonymous account ID and the time received. Reference photos, captured photos, entered names, shooting modes, and camera height are not sent. Collected outlines are not automatically sent to OpenAI.
We use this information to identify frequently used poses and as a reference for new sample poses. Samples are recreated with fictional people. Submitted outlines themselves are not published in the app.
Turn the setting off to stop future transfers, including pending ones. Nothing is sent while you choose to create lines only on this device. Changing settings does not delete outlines already sent. Collected outlines are retained without a fixed end date as references for improving poses. They remain after account deletion in a form that is no longer linked to an individual. Once the account link is removed, we cannot identify your outlines or locate and delete them in response to a deletion request. Contact rebirth.sakuraya@gmail.com about deletion. The procedure in section 8 also applies.
5 Purchase information
Monthly and annual subscriptions use Apple's StoreKit. The app receives purchase status, expiration information, and related transaction data to verify and restore access. It caches this status locally. We do not receive your card number or Apple Account password.
Section 4 describes transmission of purchase evidence to verify paid outline access. Apple processes the payment itself.
We also use RevenueCat (United States) to verify and record purchases. The app sends RevenueCat purchase records, an anonymous ID created on the device, the device identifier for vendors (IDFV), and connection information such as the IP address. When the measurement in section 7 is on, it also sends the AppsFlyer ID.
6 Sharing and Apple services
When you choose to share, the app passes images to the selected destination using iOS sharing or an Instagram handoff. The recipient's policies govern its handling. Deleting an image inside dolcam does not delete the recipient's copies.
After export, iCloud Photos or other services may sync your photo library. Apple's settings also govern device backups. dolcam has no independent cloud sync service. Describing processing as local does not disable syncing you have configured.
7 Advertising and tracking
To measure how well our ads work, the app includes the SDK of AppsFlyer, a measurement service. To find out which ad led to an install, the app sends AppsFlyer records of the install and of app launches. Purchase records are sent to AppsFlyer by RevenueCat, described in section 5.
The information sent is identifiers created on the device (the IDFV and the AppsFlyer ID), launch times, the purchased product with its price and currency, the device and OS type, and connection information such as the IP address. AppsFlyer sends this information to the ad platforms we use, Meta and X, to measure ad results. Those platforms handle it under their own policies.
The app does not use the advertising identifier (IDFA) and does not ask for iOS tracking permission. It does not send your name, email address, or photos.
You can stop this measurement by turning off "Measure ad results" in the app's settings. After you turn it off, the app stops sending to AppsFlyer, and RevenueCat no longer forwards your purchase records to AppsFlyer. Turning it off does not delete information already sent.
The app includes no other usage analytics SDK. Functional records such as import counts are handled as described in section 4.
The app saves first launch dates, successful save counts, and related information locally to decide when to request the operating system's standard review dialog. It does not send these decision records to our server. Review submission uses Apple's systems.
The app uses onboarding completion, save counts, and records such as permission grants or declines to decide when to explain notifications. When notifications are enabled, it selects their content using poses you have photographed, saved pose collections, edited photo save counts, and paid access status. It determines notification dates from the last time you used the app and schedules them on your device through iOS local notifications.
Notification scheduling and opening counts are saved as local operational records. The app also uses information such as the first launch date, past subscription status, and paid plan screen dismissal counts to select shortcuts shown when you press and hold the app icon. Usage records handled for these notification and shortcut features are processed only on your device. These features do not send those records to our servers or external services. Device backups and similar Apple features remain subject to your Apple settings as described in section 6.
8 Retention and deletion
Local deletion
Local records remain until you delete them. We do not provide cloud sync. The temporary-file and history cleanup described below are exceptions.
Deleting an imported pose removes its reduced-size photo, outline, name, and shot records from the app. The captured-photo deletion action in Settings removes the app's capture history, including stored originals where present. These actions do not remove photo library images. Delete exported copies in the Photos app.
Capture history retained for correction re-editing remains until explicitly deleted. Other history may be removed when count or storage limits are reached. Temporary burst candidates are removed after saving and during other cleanup. Candidates older than 24 hours are cleaned up on a subsequent launch or use, rather than by an exact-time timer. Sharing files are cleaned up on the next share or app launch. There is no blanket 24-hour deletion rule for all photos.
Deleting the app normally removes its ordinary local files and preferences. Manage backups and photo library copies separately. Keychain authentication credentials and server records are not necessarily deleted automatically.
Delete your server account
In the app’s Settings, go to Photo Import and choose Delete server account. After confirmation, the account and usage counter are deleted immediately. On success, the app removes its authentication session from the device and stops sending pending outlines. Photos, poses, and the contribution preference on your device are unchanged.
Collected outlines remain with their account ID link removed. Sample images already created from those outlines and catalog poses also remain, in a form not linked to an individual. Request records lose their account ID link and remain for the retention period below. Daily cost totals that are not linked to individuals also remain.
Deleting an account does not cancel a subscription. Apple will continue billing unless you cancel. Please cancel in Manage Subscriptions before continuing. You may also delete your account without canceling.
Server retention periods
Processing records become eligible for deletion 90 days after completion. Records still being processed are not deleted. Anonymous accounts and usage counters become eligible for deletion 12 months after their last authenticated server use, including imports, allowance checks, and outline submissions. Automatic cleanup runs once daily and defers accounts with requests still being processed. You can delete your account in Settings even while processing is underway.
Collected outlines and samples created from them have no fixed retention end date. Once the account link is removed, we cannot identify your outlines or locate and delete them in response to a deletion request. Daily cost totals have no fixed retention end date because they are not linked to individuals. Uninstalling the app does not notify the server. The next import after account deletion creates a new anonymous account.
The relay retains anonymous IDs, import counts, and request records to manage allowances and prevent abuse. It does not store photos. Outlines are stored only under section 4a. Infrastructure log and backup retention follow Supabase’s terms. We retain support contact details and messages for as long as necessary to respond.
Information independently retained by OpenAI or Apple follows their policies and applicable law. Local deletion does not imply immediate deletion from their systems.
9 Service providers and international processing
OpenAI (United States) creates outlines from Faves photos. Supabase (Singapore) provides authentication and relay infrastructure. The relay's processing region is Tokyo, Japan. Retention and other processing locations follow each provider's terms. We require each provider to offer protection equivalent to this Policy. Except as required or permitted by law, we do not provide information to third parties for purposes other than those described here. We do not sell personal information.
For ad measurement and purchase management we use the following services. AppsFlyer (Israel) measures ad results. RevenueCat (United States) verifies and records purchases. Meta Platforms (United States) and X Corp. (United States) receive result records as the platforms where our ads run. Retention and processing locations follow each company's terms. Sending information to companies in the U.S. may count as a provision to a third party in a foreign country; see the Personal Information Protection Commission survey below for the U.S. system. For each company's handling, see the policies of AppsFlyer, RevenueCat, Meta, and X.
The photos described in section 4 are sent to OpenAI in the United States of America (U.S.) as a provision to a third party in a foreign country. The U.S. has no comprehensive federal personal information protection law; personal information is protected by state laws and sector-specific laws. For an overview and details, refer to the Personal Information Protection Commission of Japan's survey of foreign personal information protection systems (U.S.).
OpenAI's safeguards are based on its API data handling policy and business data privacy policy. API data is not used for training unless explicitly shared for that purpose. OpenAI also applies encryption in transit and at rest and access controls.
See Supabase's Privacy Policy and Data Processing Addendum for its safeguards.
10 Security and support correspondence
Communication with the relay uses HTTPS. Keychain manages authentication sessions. Access controls protect server counters and ledgers. No transmission or storage method can be guaranteed completely secure.
If you contact us, we receive your reply address and message. We use them as necessary to respond and verify requests. Do not send unnecessary photos or confidential information.
11 Children and information rights
The app is not intended for children under 13, who must not use it. Minors need parent or guardian consent. Contact rebirth.sakuraya@gmail.com if you believe we received information from a child under 13. We will investigate and take appropriate action, including deletion where necessary.
Contact rebirth.sakuraya@gmail.com to request access, correction, deletion, or restriction of information we hold. We will verify requests as needed and respond under applicable law. If the anonymous account design limits our ability to identify the relevant records, we will explain that limitation.
12 Changes and governing law
We will announce material changes on the public page or through another appropriate channel and obtain renewed consent where necessary. This Policy is governed by Japanese law without limiting rights under other mandatory applicable laws.
Operator: 桜谷俊輝
Address: Disclosed without delay upon request
Contact email: rebirth.sakuraya@gmail.com