Privacy Policy
This English version is a reference translation provided for convenience. The Japanese version is the official version and prevails.
LUMINAS Compass (宿命鑑定アプリ; hereinafter “the Service”) is a service that provides destiny readings based on date of birth, through AI apps such as ChatGPT and Claude and through the Service’s website. We set out below the information the Service handles and how it is handled.
In the ChatGPT and Claude app directories, the Service is listed under the name “LUMINAS Destiny Reading 宿命鑑定”.
1. Information we receive
| Information | When we receive it | How we use it |
|---|---|---|
| Name and email address | When you apply (trial, start or renewal) | To manage your contract, and to send emails about your user code, expiry and procedures |
| Email address | When you request a check for a forgotten user code | To check your registration and send a notice to the registered email address |
| User code and email address | When you go through the procedure to move from the GPTs version to the MCP version | To check your registration, and to send a confirmation email and notify you of your new user code |
| User code | When entered on the AI app login screen or on our procedure pages | To confirm your contract (checked at login and for each reading) |
| IP address of the connection | When you use this site, the AI app login screen or the MCP version (with each communication) | To stop repeated incorrect entries on the login screen (this record is deleted after 1 hour). It may also be included in the operation logs at Cloudflare used to investigate errors and misuse, which are deleted after 7 days (table in section 2) |
| Your notice of a bank transfer (amount and date) | When you press “I have transferred” (振り込みました) for a paid application or renewal, or when you offer support on the support page | To start or renew your contract, confirm payment, and record support |
| Bank account for a refund (bank, branch, account type, number and account holder) | When you ask for a refund (by replying to an email from the operator) | To send the refund by bank transfer |
| Name of the payer of a bank transfer (the name shown in the bankbook), amount and date | When we receive your bank transfer (as a bank transaction record) | To confirm payment and to start or renew your contract |
| Date of birth and gender of the person being read (including people other than yourself, such as family members or acquaintances) | For readings, consultations, the universe board and detailed items | To calculate the chart |
| Consultation text and lookup terms | When answering a consultation, and when checking the basis for an explanation of Sanmeigaku theory | To choose the relevant Sanmeigaku materials (the text itself is not stored; only Sanmeigaku terms remain in the usage log) |
| Sexagenary (kanshi) names and numbers | When finding a date of birth from a chart | To calculate candidate dates of birth |
| Non-disclosure agreement (NDA) document (name and signing date) | When you agree to the non-disclosure agreement in an application (trial, start or renewal) | To create the non-disclosure agreement document, send it to your registered email address, and keep a copy |
| Survey answers (how you use AI, what you use it for, comments, etc.) | When you answer a survey | To improve the Service. Comments you give may be published on this site as “user voices” (利用者の声) without parts that identify an individual, such as your name (if you do not want them published, please let us know through the inquiry page. No name, email address or user code is attached to answers) |
| Inquiry details (name, email address and inquiry text) | When we receive an inquiry email or form | To reply to the inquiry and to check what is needed for that |
| Name, email address and message for support | When sent from the support page | To record support (name and message). Comments and messages you give may be published on this site, protecting your privacy, without parts that identify an individual, such as your name. The email address is used only to send the email with the transfer details for support, and is not kept in the record |
Names (the names you go by) are not used for the reading calculation. There is no name field in the reading input sent from the MCP version (names used to address people are used only within the AI app conversation). In the GPTs version (until December 11, 2026), the names (the names they go by) of the person in the conversation and the person being read are also sent together with the reading input, but they are used only for the headings of the results and are not kept in the calculation records. However, if consultation text or lookup terms sent from an AI app for a consultation or a Sanmeigaku check contain names or similar information, the Service may receive them (consultation text is not stored). Please do not put unnecessary names or contact details in consultation text. Please also avoid, as far as possible, writing information that requires special care, such as illness, disability, beliefs or crime victimization. Even if such information is written, the Service does not store that text and uses it only to answer that consultation. When entering the date of birth of a family member or acquaintance, please obtain that person’s consent. People 13 or older may apply. Anyone under 18 should obtain a parent’s or guardian’s consent before applying. Use through Claude is limited to people 18 or older (or, where a higher age is set in your location, that age or older) under Anthropic’s Consumer Terms. The content of conversations is handled by the AI app you use (OpenAI, Anthropic, etc.) under its own policies.
2. Information we store and for how long
| What we store | Contents | Period |
|---|---|---|
| Contract records | Name, email address, user code, plan, expiry, procedure records, and notices of bank transfers | The contract period and 7 years after it ends |
| Refund records | Bank account for the refund, amount and date, and the email exchanges | 7 years from the date of the refund |
| Payment confirmation records | Bank transaction records (name of the payer, amount and date) | 7 years from the date of the bank transfer |
| Support records | Name, amount and message for support, and the date and time of the notice | 7 years from the date of the support application (notice) |
| Records of sending the email with the transfer details for support | An identifying mark created from the recipient email address (in a form that cannot be turned back into the original email address), date and time, and whether it was sent. Used to stop repeated sending to the same recipient. The email address itself and the content of the sent email are not kept (a partly masked recipient remains in the operation logs) | Records older than 30 days are deleted periodically |
| Records of requests to move from the GPTs version to the MCP version | Date and time of the request, expiry of the confirmation link, date and time the move was completed, status of the check and confirmation, the link to your contract, the previous and new user codes, and information for checking the email address and the confirmation link (in a form that cannot be reversed). The confirmation link itself is not kept in this record | 7 years from the date of the request |
| Records of checks for a forgotten user code | The email address entered, date and time, whether a registration was found, and records of sending the notice email (including the recipient and the user code notified. The sent email itself remains only on the mail server used to send email) | Records older than 30 days from receipt are deleted periodically. However, notices not yet sent, being sent or waiting to be resent, and the related check records, are kept until sending is finished or resending is stopped. Those older than 30 days from receipt for which sending is finished or resending is stopped are deleted in the next periodic process |
| Inquiry emails | Emails received (name, email address and inquiry text) and reply emails | 1 year after the inquiry has been dealt with. They remain on the mail server used to send and receive email |
| Notification email records and sent emails | The recipient, name, user code, expiry and other contents of notification emails, and the sending records (notices for a forgotten user code are as in the check records above). The sent emails themselves remain on the mail server used to send email | 1 year after sending |
| Confirmation link records | Records of the link used to confirm your email address when you apply (the email address and information for checking the link [in a form that cannot be reversed]) | 1 year |
| Non-disclosure agreement (NDA) records | The non-disclosure agreement document exchanged when you applied (including your name) | The same period as the contract records (the contract period and 7 years after it ends) |
| Survey answers | Answers received in surveys | 3 years |
| Login records | User code (stored encrypted) and login expiry | 30 days from the last day of use (up to 90 days) |
| Calculation records | User code, date of birth and gender of the person being read, whether the result succeeded, and date and time (names are not recorded) | 365 days |
| Temporary store of reading results (MCP version) | Reading results used to return the same result when the same reading is repeated right away (including the date of birth and gender of the person being read; not including the user code or name) | 10 minutes |
| Temporary store of calculation results (engine) | Results used to avoid repeating the same calculation (including date of birth and gender; not including the user code or name) | About 2 days |
| Usage counts | Number of readings per user code per day | 365 days |
| Counts for the daily limit | Number of readings, consultations and Sanmeigaku checks per day | 2 days |
| Usage logs | The type of feature used and a summary of the input (style number, number of people, Sanmeigaku terms looked up [only those in a fixed list of terms], names of detailed items, the purpose of the consultation, and the number of characters in the consultation text), date and time, duration, success or failure, an identifier created from the user code (in a form that cannot be turned back into the original code), and the type of AI app connected | 30 days |
| Operation logs (Cloudflare) | The same summary as the usage logs, communication details (date and time, URL of the page opened, browser type, approximate region, etc.; may include the IP address of the connection), and error details | 7 days |
| Statistics | Counts by gender and age group, etc. (in a form that does not identify individuals) | 365 days |
Consultation text and question text sent from AI apps are not stored (inquiry emails are as in the table above). Only the operator can view the records. In operational work (checks and fixes), the operator uses AI tools (Anthropic and OpenAI, United States) and may have them read part of the records as needed (table in section 3-1).
3. Provision to third parties
Except as based on laws and regulations, we do not provide or sell the information we receive to third parties.
The following two are separate from such “provision”.
- Use in operations (decided by the operator): using services of providers chosen by the operator to run and operate the Service (3-1). The use is limited to what is needed to operate the Service
- Returning results to AI app providers (at the user’s request): returning reading results, at the user’s request, to the AI app that the user connected themselves (3-2)
3-1. Services of foreign providers used by the Service (use in operations)
The Service runs using the services of the following foreign providers. Information is stored and processed on these providers’ servers (which may be located outside Japan).
| Provider | Country | Use |
|---|---|---|
| Cloudflare, Inc. | United States | Website, calculation and storage of information, sending the email with the transfer details for support (Email Sending), and receiving and forwarding email sent to info@luminas-compass.com |
| Google LLC | United States | Sending notification emails, receiving and storing inquiry emails (Gmail), creating and storing non-disclosure agreement (NDA) documents (Google Docs and Google Drive), displaying text on this site (Google Fonts), and checking search status (Search Console) |
| Anthropic, PBC | United States | Having part of the records read in operational work (checks and fixes) (AI tools; only as needed) |
| OpenAI, L.L.C. | United States | Having part of the records read in operational work (checks and fixes) (AI tools; only as needed) |
The personal information protection system of the United States can be seen in the material compiled by the Personal Information Protection Commission (“Survey on systems for the protection of personal information in foreign countries” (外国における個人情報の保護に関する制度等の調査)). Each provider has published its efforts to protect personal information.
3-2. Returning reading results to AI app providers (at the user’s request)
When you use the Service in an AI app, the reading results (chart, interpretation materials, relevant source excerpts and the universe board diagram, including the date of birth and gender you entered) are returned, at your request, to the AI app that you connected yourself. The main AI app providers are OpenAI (ChatGPT, United States) and Anthropic (Claude, United States). The returned content and conversations are handled under each provider’s policies and may be stored in that country.
4. Cookies, etc.
This site does not use cookies for advertising or for tracking behavior. On the AI app login screen, only the information needed to keep you logged in is used.
5. Security measures
To prevent the information we receive from leaking or being lost, we do the following.
- We have set rules: this policy is our basic policy, and we have set procedures for receiving, using, storing and deleting information.
- We limit who handles information: information is handled by the operator. When AI tools are used in operational work, they are given only what is needed to read. If there is a risk of a leak, we check promptly and, in accordance with laws and regulations, notify the person concerned and the Personal Information Protection Commission.
- What those handling information observe: information is handled only to the extent needed to operate the Service.
- Devices and locations: the storage of the devices used for operations is encrypted, and the devices are locked (with passwords, etc.) so that others cannot use them. Temporary files containing personal information are deleted after use.
- Technical measures: all communication is encrypted (HTTPS). User codes are stored encrypted in the login records. Only the operator’s accounts can access the admin screens and the places where records are kept. Readings are not performed when a contract has ended or cannot be confirmed.
- Services of foreign providers: as in the table in 3-1 above, we use services of providers in the United States. We take security measures after checking the system in that country.
6. Requests for disclosure, correction, deletion or suspension of use
For your own information, you may request notice of the purpose of use, disclosure (including disclosure of records of provision to third parties), correction, addition, deletion, suspension of use, erasure, and suspension of provision to third parties.
- How to request: please send an email to info@luminas-compass.com with the subject “Personal information request” (個人情報のご請求).
- How we verify your identity: please send it from your registered email address; we will ask you about some of your registered details to verify. For requests from an agent, we verify the person’s authorization.
- Fee: there is no fee.
- How we answer: as a rule, we answer by email.
Records that must be kept for laws and regulations or for contracts, such as contract, payment and tax records, are not erased even on request. Other records are deleted in turn once the retention periods in section 2 have passed. Requests based on laws and regulations are handled in accordance with laws and regulations.
You can disconnect the Service at any time from your AI app’s settings (login records expire after 30 days if not used). Please choose how conversations are handled in your AI app’s settings (data and training settings).
7. Operator and contact point for questions and complaints
- Name of the operator: LUMINAS (trade name)
- Name and address of the operator: disclosed without delay on request (to info@luminas-compass.com).
- Contact point for questions and complaints about the handling of personal information: info@luminas-compass.com
8. Changes
When we change this policy, we will announce it on this page.
Established: May 22, 2026. Revised: November 1, 2026. Operator: LUMINAS. Contact: info@luminas-compass.com