Privacy Policy

This page explains what information YOMI (“the app”) handles, and how it is used.

This is a translation. The Japanese version is the authoritative text. 日本語の正本

The most important things first.

The fortune calculations are done only inside your iPhone. Your date of birth, time of birth and place of birth are not sent to any external AI.

Before we have an AI (OpenAI or Google) write your fortune text, we show you what will be sent and ask you. If you decline, your reading arrives as fixed text, and nothing is sent to the AI.

If you use Sign in with Apple, your records are backed up to Google’s Firebase and can be restored with the same account. “Delete account” inside the app erases that backup and the records held on our relay server.

1. Operator

Yuichi Tanaka (an individual)
Contact: latlon.design@gmail.com
We will provide our address without delay if you request it at the contact above.

2. Information stored on your device

The following information is stored on your device. Backup when signed in, and sending for readings, are as described in section 3.

Your stardust balance and your record of tips (including the wishes written on plaques) are backed up to your own iCloud (iCloud Key-Value Store) so that they are not lost when you change devices. This is stored inside your Apple account, and we cannot read it.

2-1. How the information is used

The information described in sections 2 and 3 is used for the following.

We do not use it to show advertising. We do not sell your information. If we change how it is used, we will let you know as described in section 10.

3. Information sent outside your device

The app communicates with the following services. No advertising, and no external analytics or crash-collection tools (SDKs), are built in. Only summaries of usage and crashes are recorded, by our own means, on our relay server (3-3).

We do not give your information to anyone other than those listed here. We do not sell it, and we do not give it out for advertising. However, when disclosure is required under law, we may comply to that extent.

Our relay server (Cloudflare Workers, United States)

Purpose To relay fortune requests to OpenAI and Google (Gemini) (a mechanism so that keys are not embedded in the distributed app). It is also used for managing limits against overuse, detecting fraudulent use, recording usage (3-3), sending notices as notifications, delivering stardust (in response to inquiries), and the shared plaque wall (3-6)

What is sent The material for readings (3-1 and 3-1-2; passed on as is to OpenAI and Google), a device identifier (a random value created on the device when the app is installed; unrelated to your Apple ID or any advertising identifier), a signature for verifying the device, and the numbers of stardust gained and spent (cumulative totals earned, purchased and used). For The Written Book, the purchase record signed by Apple is also attached. When a book finishes being written, and when that book is saved to your account (and also when you delete your account), only a flag for “whether it was saved to the account” is sent along with the same purchase record (the content of the book is not sent). Neither the identifier nor your IP address is passed on beyond the relay server (to OpenAI or Google)

What is stored The text you send in fortune requests is neither stored nor logged (wishes on plaques are as described in 3-6). The public key for verifying the device, and usage records (date and time, model used, character counts, amount of processing, country, device identifier, and the numbers of stardust gained and spent), are kept for managing limits and detecting fraudulent use. We do not receive Apple or Google account identifiers. The IP address itself is not stored (to count requests, a keyed digest that changes daily is used for 2 days only). For each purchase of The Written Book, we record the amount used and the number of devices that used that purchase (the transaction number, and an irreversible digest made from the device identifier). We also record whether a finished book was saved to the account (only the transaction number, the flag, and the date and time), in order to answer inquiries that “my book disappeared.” Retention periods are as described in 3-4

OpenAI, L.L.C. (United States)

Purpose To create fortune text. To check whether a wish written on a plaque may be posted (3-6)

What is sent As described in 3-1 below (sent only if you have agreed to sending to AI). If you hang a plaque on the shared plaque wall, the text of that wish (3-6)

Google LLC (Gemini API, United States)

Purpose To create fortune text (readings and answers to your questions in your early use; 3-1). To create the text of the books, The Written Book and the Rough draft

What is sent For readings and questions, as described in 3-1 below (sent only if you have agreed to sending to AI). For books, as described in 3-1-2 below. It is sent when you buy The Written Book and answer the questions, and when the free Rough draft (the one Yomi writes once 7 days of records have built up / “Have just the first half written” on the shelf) is written

Apple

Purpose Purchase processing, sign-in, device verification (App Attest), notifications, iCloud, weather (WeatherKit), place-name search and maps

What is sent Whatever Apple’s own systems handle (we do not touch your payment information). For weather, your approximate current location is sent to Apple. For place-name search and maps (when you type or pick on a map your place of birth or an event’s location, and when the places your photos were taken are shown on the calendar’s map), the place name you typed, the point you picked on the map, the event’s location, and the approximate location where photos were taken are sent to Apple’s map service

Google LLC (Firebase Authentication, Cloud Firestore, App Check)

Purpose Sign in with Apple, and saving and restoring records with the same account. Receiving feedback (3-5). Confirming that communication comes from the genuine app (App Check)

What is sent If you sign in: the account identifier issued by Apple (your name and email address are not sent), your profile, birth information and profile photo, daily records, people on your mind, the memory of your questions, the book questions, books and drafts, and the stardust ledger and purchase records. For events saved inside YOMI, the title, calendar date, time, duration, tags, location, notes, URL and notification settings are also saved. App settings (notification on/off and times, language, Yomi’s look, interaction preferences, when the day changes, calendar link on/off and the identifiers of the calendars you chose) are also saved. Your consent to sending to AI, the lock, and whether to share usage are decided per device and are not saved. Events imported from your device’s calendar are not included in this backup.

Storage and deletion Stored inside the account of the person who signed in, under rules that let only that person read and write from the app (we can view it from the administration console). If you remove your profile photo or a person on your mind, it is removed from the backup as well. Simply deleting the app does not erase the backup on the server (after reinstalling, signing in again brings it back). “Delete account” inside the app deletes the backup on the server and the authentication account (section 5).

3-1. What is sent to OpenAI and Google for readings and questions

We send the results of the fortune calculations in order to turn them into readable text. We send them only after first showing you what will be sent and obtaining your consent. Until you consent, and while Settings → “Use AI for readings” is off, nothing is sent (your reading is delivered as fixed text).

The AI that writes the text changes between your early use and afterwards. The morning reading (today’s card), the Deep read of a day, answers to your questions, and your very first reading are written by Google’s Gemini for roughly your first 30 times, and by OpenAI after that. When Gemini fails to produce one, OpenAI writes it on the spot. While Gemini is switched off, OpenAI writes as well.

The count is kept per device, counting the times Gemini wrote. Even if you have been using the app before, Gemini writes roughly the first 30 times after you update to the version that introduced this. When you reinstall the app, or after you delete your account, the count starts over.

Preparatory work — the month-end look back, the interviewer for the book questions, looking things up, telling what kind of question you asked, and so on — is handled by OpenAI from the start. For that reason, during your early use, the same question text is sent to both OpenAI and Google. Whichever it is sent to, the kinds of material are the same, as follows.

What is not sent: email address, Apple identifier, device identifier, advertising identifier, the date of birth, time of birth and place of birth of you or the people you registered, where you are now (neither coordinates, nor direction or distance from there), photos, contacts.

Because no identifier is sent along, what is sent is not linked to your account or device on OpenAI’s or Google’s side. However, your nickname is sent as it is. Also, from the combination of your sign and “birthday week,” the approximate time of your birthday can be inferred. We state this for the sake of accuracy.

To OpenAI, we send with the setting that tells OpenAI not to store the response on its side (store: false). Even so, how long it is retained on OpenAI’s side depends on OpenAI’s policies (linked in 3-2). When sending to Google (Gemini), this setting is not attached (Gemini’s endpoint has no equivalent setting). How what is sent is handled on Google’s side, and how long it remains, depends on Google’s policies and the Gemini API terms (linked in 3-2).

On whether what is sent is used to train AI, each company publishes the following (as we checked on October 13, 2026).

Both are what each company publishes; we have not verified the inside of either company. If a company changes its handling, we will revise this section.

The “people on your mind” entries and event titles contain information about people other than yourself. Because those people have no opportunity to consent to the app themselves, information that could identify them, such as date of birth, is not sent; only the signs needed for the reading are calculated on the device and sent. Even so, their name (the name you gave them) is sent in order to read about and answer about that person.

Event titles, too, may contain the names of people other than yourself. For that reason, neither event titles nor the line you write at night is sent by default. We ask you once, on the day a record is first made, and the app is built not to send until you allow it. After allowing, you can switch it at any time from Settings → “Readings.”

A line judged to contain words concerning a threat to life is automatically excluded from the material for readings and is not sent outside (as a record it is yours, so it stays on your device).

3-1-2. What is sent to Google (Gemini) when writing a book

What is sent to Google for readings and questions is as described in 3-1 (roughly your first 30 times). This section is about books.

The Written Book and the free Rough draft are written by Google’s Gemini. For a book, only when you buy The Written Book and answer the questions, and when the Rough draft (the one Yomi writes once 7 days of records have built up / “Have just the first half written” on the shelf) is written, the following is sent via our relay server (on the premise that you have given the consent described in 3-1). Because the Rough draft has no questions, what is sent is the planetary placements and the timing of their cycles, the names of the “people on your mind” who appear in the book, and, if allowed in Settings, a summary of your records.

What is not sent when writing a book: your nickname (the way the book addresses you is inserted inside the device), email address, Apple identifier, device identifier, the date of birth, time of birth and place of birth of you or the people you registered, your age as a number, photos, contacts. For readings and questions, as described in 3-1, your nickname is also sent to Google so that you can be addressed.

However, if you write your name, your workplace or the like in your answers to the book questions, it is sent as written. Also, from the timing of planetary cycles (for example, “the year Saturn returns to where it was when you were born”), your approximate year of birth can be inferred. We state this for the sake of accuracy.

For a book, only when the text could not be created with Google, the same content may be re-sent to OpenAI to create the text. Readings and questions work the same way: when one could not be created with Google, the same content is re-sent to OpenAI, and OpenAI writes it on the spot.

When we have Google (Gemini) write the text of a book, too, it is sent under the paid service, as described at the end of 3-1.

3-2. Provision to third parties in foreign countries

The app uses the services of the following companies outside Japan. All of them are companies in the United States of America.

Cloudflare, Inc. (United States)

Our relay server and where its records are kept (3 and 3-4), and this website

OpenAI, L.L.C. (United States)

Creating the text of readings, answers to your questions and books; looking things up; screening plaques (3-1 and 3-6)

Google LLC (United States)

Creating the text of readings, answers to your questions and books (Gemini API; 3-1 and 3-1-2). The backup of records if you sign in, and keeping feedback (Firebase; 3 and 3-5)

Apple Inc. (United States)

Purchases, sign-in, notifications, weather, maps and so on (the Apple entry in section 3)

Of these, sending to OpenAI and Google in order to create text is done, as described in 3-1, only after showing you on the app’s screen what is sent and where (OpenAI and Google in the United States) and obtaining your consent. You can withdraw consent at any time in Settings → “Use AI for readings.” A backup of your records is placed with Google (Firebase) only if you yourself use Sign in with Apple.

The system for protecting personal information in the United States

This is an outline based on the survey published by Japan’s Personal Information Protection Commission (information as of October 2021).

For details, see the pages of the Personal Information Protection Commission (in Japanese): Foreign systems (United States of America) / Legal systems of other countries and regions. Systems may change. Requests to us (disclosure, correction, suspension of use, erasure) are accepted by us as described in section 5, whichever company the information is placed with.

Measures each company takes to protect information

This is what each company publishes (checked on October 13, 2026).

The measures taken on our side are as described in section 6. On top of that, the app is built so that date of birth, time of birth and place of birth are not sent to any external AI, and no identifier is attached to what is sent to AI (3-1).

3-3. Records of usage and crashes (our relay server)

To improve the app, summaries of how it is used and of crashes are recorded on our relay server. No external analytics service is used.

3-4. Records that remain on our server, and for how long

Records on the relay server (Cloudflare) are automatically erased, or have their identifier removed, once the following periods have passed.

Usage records and records of usage events (including crash summaries)

Erased after 90 days

Records kept on suspicion of fraudulent use

Erased after 180 days

The public key for verifying a device, and that device’s record

Disappears 400 days after it was last used

Notification destination (the device token)

Only if you turned on receiving news as notifications. Erased 30 days after it becomes unusable, or if not updated for 180 days

The record of stardust gained and spent (a copy of the ledger)

Only if you sent it with “Show us your stardust log” in Settings. Erased 400 days after it is received

Stardust deliveries (placed by us in response to an inquiry)

180 days after receipt, the recipient identifier and the accompanying note are erased (the amount delivered and the date and time remain)

Plaques on the shared plaque wall

30 days after the hanging period ends, the text of the wish and the device identifier are erased (3-6)

Daily usage amounts for limits against overuse

That day’s usage amount per device and per origin (a keyed digest that changes daily). Erased after 2 days. The per-device signature counter and date of last use disappear, like the device’s record, 400 days after last use, and are also erased when the account is deleted

Results of looking up public information (companies, schools, places, products)

A cache so that the same thing is not looked up repeatedly. It is kept without being linked to who looked it up (neither a device identifier nor an origin is attached; the name is turned into an irreversible key). What was found disappears after 7 days, and what was not found after 1 day. Results of looking up people’s names are not kept

Number of lookups

For limits against overuse, only the number of lookups that day and that month is counted, per device and per origin (a keyed digest that changes daily). The daily count is erased after 2 days, and the monthly count when the month changes. The per-device counts are also erased when the account is deleted

The amount used for each purchase of The Written Book, and the number of devices that used that purchase

The transaction number, and an irreversible digest made from the device identifier. No time limit (to prevent the same purchase from being reused)

Whether a Written Book was saved to the account

Only the transaction number, the flag for whether it was saved, and the date and time (the content of the book, the device identifier and the account identifier are not held). Erased 1 year after the flag was last received. When making an inquiry, please tell us “Your book purchase number” from Settings

The relay server’s operating records (logs)

No text and no IP addresses are written, and only the leading part of an identifier is written. They disappear after Cloudflare’s retention period (a few days)

3-5. Feedback

Text you send from “Feedback” in My page is kept in Google’s Cloud Firestore, and only we read it. Kept together with it are the email address you wrote for a reply (optional), the app version, device model, iOS version, language, the date and time sent, and, when “Share usage” is on, the device identifier. No account identifier is attached.

The text you send is kept for up to 1 year and then erased automatically. Because no account identifier is attached, it is not erased along with your account when you delete the account. If you would like it erased before 1 year has passed, please contact us at the contact in section 1.

3-6. The shared plaque wall

Only if you hang a plaque written after a tip on the shared plaque wall, the text of the wish, your sign, the item, the purchase record signed by Apple and the device identifier are sent to our relay server.

4. Device permissions

Calendar

Used to show your events over the calendar / to add events from the app.

If you decline, you can use the app without events.

Photos

Used to show the photos you took that day over the calendar, and also to show on a map the places you went, from where the photos were taken (the photos’ location information), and to count the number of photos and the number of places you went toward “your patterns.” The location itself is not sent to our server or to AI (only the numbers are included in the backup when signed in and, if you allowed it, in the material for readings. To display the map, the approximate location where photos were taken is sent to Apple’s map service).

If you decline, you can use the app without photos.

Location

Used to add the weather where you are now.

If you decline, the weather and the “When the sky turns” notices do not appear.

Notifications

Used to deliver the morning and evening notices, notices before events, and changes in the sky.

If you decline, notices are not delivered. If you do not want event names to appear on the lock screen, you can choose “Hide names” in the event notification settings.

Face ID and passcode

Only if you turn on Settings → “Require Face ID / passcode,” it is used for confirmation when opening the app. Face data does not leave the iPhone, and the app never receives it.

On the app switcher screen, the content is hidden regardless of this setting.

All of these can be changed at any time from the iPhone’s Settings.

5. Storage and deletion

If you wish to have your own information disclosed, corrected, suspended from use, erased, or no longer provided to third parties, please contact us at the contact in section 1. If you tell us “Your stardust number” shown in Settings, we can find which records on the relay server belong to your device.

6. Measures taken for security management

7. Email addresses entrusted to us on this site (the TestFlight waitlist)

This section is about this website, not the app. Only if you enter your email address on the TestFlight waitlist page (in Japanese), we keep that address. If you do not enter it, we keep nothing.

8. Use by children

The app is not a service directed at children. People under 18 may not use it. If we learn that we hold information of a person under 18, we will erase it. For in-app purchases, you can use the purchase restrictions in the iPhone’s Screen Time.

9. The nature of the fortunes

What the app tells you is a guide calculated from the positions of celestial bodies, and reading material based on it. It is not a substitute for medical, legal, financial or other professional advice. If you have concerns about your health or state of mind, please consult a professional service.

10. Changes to this policy

If the content changes, we will update this page and revise the date of last update. When there is an important change, we will also let you know inside the app.