Privacy Policy

Effective and last updated: 14 October 2026

The short version. inCommon keeps your charts and your journal on your own device unless you sign in and choose to keep them with your account. We do not sell your information, we do not show advertising, and we do not track you across other websites. When you consult the Oracle, a summary of your chart is sent to our server and to the company whose AI model writes the reading, as described in section 6. You can ask us for a copy of your information or to delete it at any time through Contact Support.

  1. Who we are
  2. What this policy covers
  3. Information that stays on your device
  4. Your account
  5. Keeping your record with your account
  6. The Oracle
  7. Codex Luminary payments
  8. Support requests
  9. The newsletter
  10. Information collected automatically
  11. Service providers
  12. How we use information, and our legal bases
  13. What we do not do
  14. Information about other people
  15. How long we keep information
  16. Your choices and rights
  17. Children
  18. International transfers
  19. Security
  20. Changes to this policy
  21. Contact

1. Who we are

inCommon is operated by Nathaniel J. Figueroa, an individual based in the State of Florida, United States (“inCommon”, “we”, “us”). For the information described in this policy we are the “controller” or “business” responsible for it. If inCommon is later operated by a company we form for that purpose, that company will become the controller and we will update this policy to name it.

You can reach us at any time through Contact Support, which is in Settings in the app.

2. What this policy covers

This policy covers the inCommon website and web app and the inCommon apps for iPhone and Android, including the sign in page, the app itself, the Oracle, Codex Luminary and Contact Support (together, the “Service”). It should be read together with our Terms & Conditions. It does not cover websites or services run by others that the Service links to, such as crisis lines, the payment pages run by Stripe, Apple or Google, or the websites of our service providers, each of which has its own privacy policy.

3. Information that stays on your device

You can use most of inCommon without an account. When you do, what you enter is stored in your browser’s storage on your device and is not sent to us. This includes:

Because this information lives in your browser, anyone with access to your unlocked device may be able to see it, and clearing your browser’s data for this site deletes it. You can download a copy with Export in Settings and delete a profile and its information from Settings at any time.

Two things can leave your device even without an account:

4. Your account

An account is optional. It is needed for the Oracle, for Codex Luminary, and to keep your record with you across devices. When you create or use an account we collect:

If you choose “Remember me”, your login (not your password) and your signed in session are kept in your browser so you stay signed in. Your password is left to your browser’s own password manager, if you use one.

5. Keeping your record with your account

When you are signed in, the app keeps a copy of your profiles with your account so they are available to you and protected if your device is lost. This copy includes each profile’s name, birth date, birth time, birth place and its coordinates and time zone, profile picture, and hashed PIN.

Journal entries and similar records are copied to your account only for the kinds you have switched on under Memory & Privacy in Settings, and the record of what you switched on and off is kept with your account so every device you use respects the same choices. An entry you chose to keep while a switch was off is not copied. People you have saved on your device are not copied to your account.

Switching a setting off stops future copying for that kind of record. To have copies already stored with your account removed, delete them in the app or ask us through Contact Support.

6. The Oracle

The Oracle writes a personal reading for a day, a week or a month. Readings are generated by an artificial intelligence model. The Oracle only runs after you press Consult the Oracle, and only while you are signed in.

What is sent

When you consult the Oracle, the app prepares a summary of your chart and sends it to inCommon’s server, which passes it to our AI provider, Moonshot AI, whose model (Kimi) writes the reading. The summary contains:

What is not sent

Your birth date, birth time and birth place are not sent, and neither are your journal entries, dreams, sightings, moods, saved people or email address. However, the chart positions in the summary are precise enough that someone could work out approximately when you were born from them, so please treat the summary as personal information, as we do.

What is kept

Each reading is stored with your account on our server, together with the period it covers, so that opening the Oracle again for the same period shows the same reading without writing a new one. A copy is also kept on your device. To recognise a reading it has already written, the server keeps a fingerprint (a one way hash) of the summary rather than the summary itself. We also keep a count of the readings you request each day so we can apply the daily limit described in the Terms.

Moonshot AI

Moonshot AI receives the summary only to write your reading, and processes it under its own terms and privacy policy. Moonshot AI is located outside the United States, and the summary may be processed in countries other than yours (see section 18). We do not send Moonshot AI your name beyond the first name in the summary, your account details, or your contact information.

Your choice

Consulting the Oracle is entirely optional, and everything else in inCommon works without it. If you have asked for an in-depth reading before, the app may prepare the current period’s in-depth reading in advance while you are signed in so that it is ready when you open it; that preparation sends the same summary described above. You can ask us to delete your stored readings at any time through Contact Support.

7. Codex Luminary payments

Codex Luminary is an optional paid subscription. Payments are taken by Stripe on Stripe’s own checkout and billing pages. Your card number and billing details are entered with Stripe and are never sent to or stored by us. From Stripe we receive and keep a customer identifier, a subscription identifier, your plan, whether the subscription is active, when the current period ends, and whether it is set to cancel. We use these only to give you access to what you paid for. Stripe’s handling of your payment information is governed by Stripe’s privacy policy, and Stripe may use it to prevent fraud.

In the iPhone and Android apps, Codex Luminary is bought through Apple’s App Store or Google Play, which take the payment under their own terms and privacy policies; we never receive your payment details. We use RevenueCat to check those purchases: RevenueCat receives your account’s user identifier and the purchase records the store provides. From it we receive and keep which store sold the subscription, your plan, whether it is active, when the current period ends, whether it renews, and where you manage it. We use these only to give you access to what you paid for, wherever you use inCommon.

8. Support requests

When you use Contact Support we receive what you write, the topic you choose, the email address you give us so we can reply, and, if you are signed in, your account identifier. We use this only to answer you, to act on your request (including privacy requests) and to keep a record that we did.

9. The newsletter

When you create an account with an email address you can choose whether to receive the inCommon newsletter. We record your choice and when you made it. If you said yes, we may send you occasional email about inCommon. Every newsletter will include a way to unsubscribe, and you can also unsubscribe at any time through Contact Support. Saying no, or unsubscribing later, does not affect your account.

10. Information collected automatically

11. Service providers

We share information with the following providers only so they can run parts of the Service for us. They are bound by their own terms to protect it.

ProviderWhat they doInformation involved
SupabaseAccounts, sign in, our database and server functionsAccount details, synced profiles and records, Oracle readings, subscription status, support requests
Moonshot AIWrites Oracle readings with its Kimi modelThe chart summary described in section 6
StripeTakes and manages Codex Luminary payments on the websitePayment and billing details you give Stripe; your account email
Apple and GoogleSell Codex Luminary in the iPhone and Android appsThe purchase, under your Apple or Google account; we receive no payment details
RevenueCatChecks Codex Luminary purchases made in the appsYour user identifier; purchase records from Apple or Google
CloudflareTurnstile sign in protectionBrowser and device signals, IP address
NetlifyHosts the websiteIP address, browser details, pages requested
GoogleSupplies typefaces (Google Fonts)IP address, browser details
OpenStreetMap FoundationNominatim place searchThe birth place text you typed, only when it is not in the built in list; IP address
SMS providerSends sign in codes, only if signing in by phone is enabledYour phone number and the code

We may also disclose information if the law requires it, to protect the safety of any person, to protect the Service or our rights, or as part of a transfer of the Service to a company that continues it (for example, a company we form to operate inCommon), in which case this policy will continue to apply to your information.

12. How we use information, and our legal bases

We use information only to provide the Service you ask for, to keep it secure, to answer you, to meet our legal obligations, and, if you agreed, to send the newsletter. If you are in the European Economic Area, the United Kingdom or Switzerland, our legal bases are:

Journal entries can contain information about your health, beliefs or other sensitive matters. We only receive them if you switch on copying for that kind of record, which we treat as your explicit consent, and we use them only to keep them for you.

13. What we do not do

14. Information about other people

inCommon lets you add profiles for other people, save people on your device, read two charts together, and send or receive a card. A card is a link that contains the birth details and first name it was made from; it is created on your device, and the part of the link that carries those details is not sent to our server when it is opened. Please only enter or share another person’s details if you have their permission. If you are an individual whose details someone else added and you want them removed from anything we hold, contact us.

15. How long we keep information

Deleting your account in the app (Profile, then Delete account) removes the account and everything kept with it straight away, including the record RevenueCat keeps of your app purchases, and cancels a Codex Luminary subscription bought on the website. A subscription bought in the App Store or Google Play is not cancelled by deleting your account: cancel it in your Apple or Google account settings. How to delete your account explains it, including how to ask us when you cannot use the app. We act on a request to delete your account within 30 days, and copies in backups expire on our providers’ normal schedule.

16. Your choices and rights

Wherever you live, you can ask us to:

Much of this you can do yourself: Export in Settings downloads your on device information, Settings lets you edit or delete profiles and switch copying off, Delete account in your profile deletes your account and everything kept with it, and Log Out leaves your information on the device. For anything else, use Contact Support and choose the privacy or account deletion topic. We may need to confirm the request comes from the account holder before acting on it. We will respond within 30 days, or sooner where the law requires, and we will not treat you differently for exercising your rights. If we decline a request, you can ask us to reconsider by replying to our answer.

If you are in the European Economic Area, the United Kingdom or Switzerland, you also have the right to object to processing based on our legitimate interests and to complain to your local data protection authority. If you live in a US state with a consumer privacy law, you have the rights that law gives you, and you may use an authorised agent to make a request.

17. Children

inCommon is not intended for anyone under 16, and we do not knowingly collect information from anyone under 16. If you believe a child under 16 has given us information, contact us and we will delete it.

18. International transfers

We are based in the United States, and our providers process information in the United States and other countries, which may have data protection laws different from yours. Moonshot AI, which writes Oracle readings, is headquartered in China and may process the chart summary there or in other countries where it operates. Where the law requires it, we rely on appropriate safeguards for these transfers, such as standard contractual clauses offered by our providers. By consulting the Oracle you acknowledge that the summary described in section 6 will be processed by Moonshot AI outside your country.

19. Security

We use reasonable technical and organisational measures to protect information, including encrypted connections, hashed passwords, access rules that keep each account’s records to that account, optional two-step sign in, and protection against automated sign in attempts. No method of storage or transmission is completely secure, so we cannot guarantee absolute security. If we become aware of a breach affecting your information, we will notify you and the authorities as the law requires.

20. Changes to this policy

We may update this policy as the Service changes. We will change the date at the top when we do, and if a change is significant we will tell you in the app or by email before it takes effect. Where the law requires your consent to a change, we will ask for it.

21. Contact

For questions about this policy or to make a request, use Contact Support in the app (Settings, Contact Support). The operator of inCommon is Nathaniel J. Figueroa, Florida, United States.