Cullwise Privacy Policy
Effective date: November 8, 2026
This is an English translation of the Japanese policy. If there is any difference between them, the Japanese version prevails.
The developer of Cullwise (“we”) handles information in the iPhone app “Cullwise” (the “App”) as described below.
1. Summary
- The App sends the photos it is judging to an external AI service (OpenAI), only to judge them. We ask for your permission before photos are sent.
- Our server does not store your photos, and does not write them to logs. It only passes each photo to OpenAI, in memory.
- After a photo reaches OpenAI, OpenAI’s terms apply: to monitor for abuse, it normally stays with OpenAI for up to 30 days. It may stay longer when the law requires it or when needed to prevent harm. OpenAI states that it does not use the photo to train its AI.
- There is no sign-in, and no name or email address is collected. To tell users apart, we use an identifier taken from the purchase data that Apple signs. Our server does not keep that identifier as it is. We store a hash of it.
- The App never deletes photos on its own.
2. Information we handle
2.1 Information sent for AI judging
For each photo that is judged, the App sends the items below. You choose the categories and the frame on the photo strip (the range and the number of photos). Every photo inside the frame is judged, oldest first by date taken. Photos that are not judged are not sent.
| Information | Details | Sent to |
|---|---|---|
| Photo | Resized to a JPEG with a long edge of 1,536 pixels or less, with metadata such as location removed | Our server, OpenAI |
| Date taken | When the photo was taken. Our server gets it to the second; OpenAI gets the date only | Our server, OpenAI |
| Whether it is a screenshot | Yes or no | Our server, OpenAI |
| Categories | The criteria text you wrote for each category, and the category identifier (up to 10 per request) | Our server, OpenAI |
| Date of judging | Today’s date (in the time zone determined from the connection’s origin; UTC if unknown) | OpenAI |
2.2 Other information our server receives
It is not sent to OpenAI.
- An identifier that tells photos apart. It is the ID the Photos app keeps. When the same photo can be recognized, for example if you use iCloud Photos, we treat it as the same photo after you change phones.
- A key that identifies a combination of categories.
- The app transaction data that Apple signs (AppTransaction). We take from it the identifier that tells you apart. After that, we do not store this data in the database.
- The purchase data for tickets (transaction data signed by Apple). We verify it and add tickets to your balance. We do not store this data itself in the database.
- Refund notifications that Apple sends (App Store Server Notifications). This is data signed by Apple. It includes the transaction ID of the refunded purchase, the product ID, the refunded share, and the notification ID and time. We use it to find which purchase was refunded and deduct it from your balance (we put it back if the refund is reversed). We do not store the signed data itself in the database.
- Device check (App Attest) data: key ID, certificate, and signature.
- A token for communication that is valid for one hour (a session token). We do not store it.
2.3 Information our server stores
| Information | Why | How long |
|---|---|---|
| Hash of your identifier | To tie ticket balance and purchases to you | For as long as we provide the service |
| Ticket balance and a record of every change | To keep the balance correct and never charge twice | For as long as we provide the service |
| Purchase records (transaction ID, product ID, number of tickets, whether refunded) | To never credit the same purchase twice, and to deduct on a refund | For as long as we provide the service |
| Judged records (photo identifier, key for the category combination, category identifiers, judgment probabilities, time) | To return an earlier result without using tickets when the same photo is judged again with the same combination | For as long as we provide the service. Deleted on request (section 7) |
| Recent judgment requests (request ID, an irreversible hash made from the photo and the category text, judgment probabilities, an in-progress marker) | To avoid judging twice when a request is resent | 24 hours |
| App Store notification IDs | To avoid applying the same notification twice | 30 days |
| Device check (App Attest) key ID, public key, and counter | To confirm calls come from the genuine app | For as long as we provide the service |
| Server logs | To investigate problems and watch costs | Kept in Cloudflare Workers Logs. Deleted after up to 7 days (3 days on the free plan) |
Our program writes to the server logs the request ID, the path called, a result code, processing time, a hash of your identifier, and similar items. Our program does not write photos, category text, the original identifier, purchase data, or tokens. According to Cloudflare’s documentation, the communication records that Cloudflare keeps automatically (Workers Logs invocation logs) contain the request, the response, and related metadata. The server configuration turns these records off.
2.4 Information we do not store
- Photos. We store them neither in our database nor in logs.
- The criteria text of your categories. We handle it in memory while judging, and store it neither in the database nor in logs. (The hash in 2.3 cannot be reversed.)
- The original value of the identifier taken from the signed purchase data. Our server keeps only its hash. The exception is the Support ID you send us when you contact us (2.7).
- Location. It is removed from the photo before sending.
2.5 Information on your iPhone
Your categories, settings, and the time you gave permission to send photos to AI are only on your iPhone. We do not send the permission record to our server. Your judgment records are on your iPhone, and some of them also remain on our server, as described in 2.3.
In regions where some U.S. state laws apply, we use Apple’s mechanism (Declared Age Range) to check your age group (under 13, or 13 and over). We check only on iOS 26.2 or later, only when you are in such a region, and only when you open the App. We do not check in other regions. iOS shows the prompt. Please follow iOS’s instructions. Even in such a region, if your age is not known (you did not answer, your account cannot share it, a network problem, and so on), AI judging and ticket purchases stay off, as they do for under 13. When they are off because your age is not known, you can check again with “Check age” on the screen (it does not appear if you are found to be under 13). We do not stop anything when we cannot tell your region. The App uses the result only in your iPhone’s memory while it is running. We do not store it on your iPhone or on our server, and we do not send it anywhere. If you are found to be under 13, or your age is not known in such a region, you cannot use AI judging or buy tickets (section 9).
2.6 Information that comes with a connection
When the App connects to our server, your IP address and similar information reach Cloudflare (the company we use to run our server), because of how network connections work. To protect a server with no sign-in, our program hashes the IP address and uses it only to count calls over a short time. Our program does not store the original IP address. How long Cloudflare keeps IP addresses on its side is governed by Cloudflare’s privacy policy.
2.7 Information we receive when you contact us
We use what you send through the contact form (your message, your reply address, your Support ID, and so on) to answer you. The form is a Google Form, so its contents are stored in Google’s service. We delete them when we no longer need them for your request.
3. Permission to send photos to AI
- Before the first judgment, the App shows on screen what is sent, where it goes (an outside AI service; this policy names the company), and how photos are handled, and asks for your permission. If you do not allow it, no photo is sent.
- The screen reads “Nothing is kept on Cullwise servers”. We only pass photos to OpenAI. Sections 1 and 4 cover how OpenAI handles them.
- You can stop allowing it at any time in the App’s Settings. After that, the App asks again before the next judgment. A running judgment stops.
4. Where information goes
| Recipient | Purpose | Information | Notes |
|---|---|---|---|
| OpenAI OpCo, LLC (United States; 1455 3rd Street, San Francisco, California 94158) | Judging photos | The items marked “OpenAI” in the table in 2.1 | Normally kept for up to 30 days to monitor for abuse. May be kept longer when the law requires it or when needed to prevent harm. Not used for training. If an image is flagged as suspected child sexual abuse material, OpenAI keeps the image for review. Country or region of processing: the United States and others. We have not specified a processing country or region, so data may be processed in the United States or in other countries and regions that OpenAI uses for its services |
| Cloudflare, Inc. (United States; 101 Townsend St., San Francisco, California 94107) | Running our server (Workers, Durable Objects) | The information in 2.1 to 2.3 | Data is kept in Durable Objects. We do not choose a country or region; it is placed in a Cloudflare data center near where the first request arrives |
| Apple | Processing purchases, checking the app is genuine (App Attest) | Information about purchase transactions | Subject to Apple’s privacy policy |
| The contact form | The information in 2.7 | Subject to Google’s privacy policy |
How OpenAI and Cloudflare handle the information we pass to them is governed by the terms each of them publishes. We read those terms before using them. Where their handling differs from ours (for example, how long OpenAI keeps data), we have written it in the Notes column of this table.
We do not use information for advertising. We send nothing to advertising or analytics companies. The App and the server contain no analytics or advertising component.
5. Purposes of use
- To judge photos and return results.
- To manage ticket balance, purchases, and refunds.
- To answer questions and requests for disclosure or deletion.
- To prevent abuse and sudden cost increases.
- To investigate and fix problems.
- To comply with the law.
6. Disclosure to third parties, and use of companies abroad
- Except where Japan’s Act on the Protection of Personal Information allows it, such as when the law requires it, we do not give your personal data to third parties without your consent.
- We send photos, and the items marked “OpenAI” in the table in 2.1, to OpenAI OpCo, LLC, which is located in a foreign country (the United States). Before the first judgment, we ask for your consent in the App (section 3). Here is what you should know before you consent:
- Country: the United States and others. We have not specified a processing country or region, so data may be processed in the United States or in other countries and regions that OpenAI uses for its services.
- That country’s system for protecting personal information: the United States has no comprehensive federal law on personal information. It has federal laws for specific sectors, and state laws (such as the California Consumer Privacy Act). For details, see the Personal Information Protection Commission’s page Foreign systems (United States) (in Japanese).
- What OpenAI does: OpenAI says it does not use data received through the API to train AI. How long it keeps data to monitor for abuse is shown in the table in section 4.
- Our server runs on services from Cloudflare, Inc. in the United States. Data is placed in whichever of Cloudflare’s data centers around the world is near where the first connection came from (we have not specified a country). The U.S. system is described above.
7. Requests for disclosure, correction, or deletion
The App has no name or email registration. To make a request, use the form on the Support page and include the “Support ID” shown in the App’s Settings. We use this ID to find your information, and for nothing else.
To prevent requests by someone else, we may ask for a screenshot of the Settings screen or the order ID on your Apple receipt.
When we receive a disclosure request, we give you a copy of your information. When we receive a correction request, we check it and make the correction.
When we receive a deletion request, we delete your judged records. After that, judging the same photo again uses tickets. Deleted records can remain for up to 30 days in our server’s recovery system. We keep your ticket balance, the record of its changes, and your purchase records, because we need them to keep the balance correct and to process refunds. We also keep device check records and short-term counters, which the service needs to run and to prevent abuse. We also keep information that the law requires us to keep.
8. Security measures
- Communication is encrypted with HTTPS.
- Calls from the App to our server are checked with Apple’s mechanism (App Attest) to confirm they come from the genuine app.
- The OpenAI API key is not in the App. It is kept only in the server’s secret storage.
- Your identifier is hashed with a secret key before it is stored.
- We define which items our program may write to logs, and write nothing else.
9. Children
The App is intended for people aged 13 or older. If you are under 13, please do not use it. If you are under 18, please use it with the consent of a parent or guardian.
The App does not check your age by itself. In regions where some U.S. state laws apply, however, it checks your age group with Apple’s mechanism, as described in 2.5. If you are found to be under 13, or your age is not known in such a region, AI judging and ticket purchases stop. Sorting screenshots (which does not use AI) still works. Even then, opening the App starts a connection to our server, and your identifier (the one we store as a hash) reaches it. We do not receive the result of Apple’s check. If a parent or guardian, or someone else, contacts us and we learn that information belongs to a child under 13, we delete it. A parent or guardian can request deletion of a child’s information in the way described in section 7.
10. Changes to this policy
When we change it, we update this page. For major changes (when we add information we send, recipients, or purposes), we post the change on this page at least 30 days before it takes effect. Where we can, we also tell you in the App.
11. Contact
Please use the form on the Support page.
We are an individual developer. If you ask through the form, we will tell you our name and address without delay.