Privacy Policy

InnateGlyph is an independent project that turns your birth details into a reflective personality reading. We collect only what the app needs to work, we don’t run advertising or cross-site tracking, and we don’t sell your data. You can delete your account at any time. The sections below spell out the details, including the parts that are less tidy than that sentence.

This policy covers InnateGlyph (the “Service”), at innateglyph.com. The Service is operated by InGemino LLC, a Massachusetts limited liability company, at 160 Alewife Brook Pkwy, STE 1163, Cambridge, MA 02138, United States. In this policy, “we” and “us” mean InGemino LLC. For any privacy question or request, contact us at customer.service@innateglyph.com.

• Account info: the signed-in app requires an account; there is no anonymous or guest tier inside the app. When you sign in with Google or Apple we receive your name, email address, and profile picture from that provider. A few public pages on the website (the brand landing, Find your glyph, Explore the network, and the games) can be opened before you sign in; see “Public website pages” and “Games on the website” below.
• Birth details: birth date, and optionally birth time, birthplace and gender, used to compute your chart. Gender is the classical male or female reading that sets which way your ten-year luck runs and which partner star your chart report reads, and you can skip it. In the signed-in app these are saved to your account, and a copy is kept in your browser’s local storage so the app can show your reading before it has finished loading. Your reading itself is not stored on our servers: it is recomputed from these details each time. Find your glyph on the public website is a separate path. See below.
• Friend data: nicknames and birth details for people you add as friends. Real friends are only added with that person’s consent (they scan your invite and accept, or accept your request). “Added by you” friends, created from a date alone, are stored only on your own device, never on our servers. If you answer it, a friend’s gender too: Pair Orbit asks once, the first time you open it with that friend, because their ten-year luck needs it. It is your answer, kept on your own copy of that friend, and the friend never sees it.
• What a mutual friend can see of your network: on the Network screen, someone you and they have both accepted can open your network as a layer branching off your dot. What that shows them about each of your other mutual friends is: the nickname you gave that person, that the two of you are connected, a compatibility score between the viewer and that person, and where that person ranks inside your network. It does not show them any birth date, birth time, birthplace or chart pillar, and it does not show them anyone you have not mutually accepted. For anyone who is not already their own friend, the hour-related part of the reading is removed as well. The birth details stay on our servers and are used only to compute the scores. This works both ways: you can open theirs. It starts on for every account. To decline, open the drawer, tap your name, and turn off “Let mutual friends open my network”. That stops anyone opening yours and also takes you out of other people’s. It does not reach a compatibility score someone has already seen.
• Oracle chat content: the messages you send to the Oracle chat feature and the answers it gives back, kept so a conversation can be reopened later, plus (if enabled) a short summary of context you’ve shared so it carries into future chats.
• Feedback and votes: resonance/like-dislike reactions you leave on readings, used to personalize future narration and ordering. This never changes your underlying computed chart or type.
• Usage records: attendance/streak dates, favorited celebrities or friends, and similar in-app activity tied to your account.
• Plan and subscription state: whether your account has Oracle Plus (or an equivalent admin grant), including entitlement fields synced from a store purchase when that path is used. We do not put card numbers on our servers; App Store or Play Billing handle payment when a purchase is offered.
• Crash and problem reports: when a screen fails, the app sends us the error’s name and message, the first few lines of its stack, which kind of screen you were on, the build you are running, and whether it is iOS, Android or the web. If you tap Report a problem, the note you type is sent the same way. Anything that looks like a token, a key, or an email address is removed before the report leaves the device, and the on-device technical log described further down is never attached to it. While you are signed in the report is tied to your account, so that one person hitting a bug ten times can be told from ten people hitting it once; a failure that happens before sign-in is sent with no account attached. Reports go to our own server. There is no third-party crash or error service in the app.
• Reports about content: if you report an Oracle answer, we keep a copy of that answer and of the question you asked just before it. If you report a friend request or a name, we keep a copy of the name and note which account wrote it. Either way we keep the reason you chose, any note you add, and your account. We use these only to review the report and act on it. The person you report is not told who reported them.
• Analytics and performance measurements: see the next section. We run no advertising or ad-targeting trackers.

The brand site at innateglyph.com/home and two explore pages linked from it are available before you sign in. They are not a guest tier of the app: they do not create an account, do not keep a chat history, and do not unlock the signed-in screens.

• Find your glyph (/home/glyphs): if you enter a birth date and ask the page to reveal a glyph, that birth date and your browser’s timezone are sent to our backend on Render for a one-off computation. Hour and birthplace are not collected on that page. The values are not saved to an account and are not written to local storage by that page; Render still processes the request the way it processes any other chart request (including standard web request logs such as IP address).
• Explore the network (/home/network): opening the public map of figures alone does not send your birth details. If you already have birth details saved on the device from a signed-in session and the map places You, those saved details (birth date, timezone, and birth time or birthplace when you saved them) are sent to Render for that placement (the same kind of chart request as elsewhere in the app), not read only on the device.
• Brand landing (/home): marketing content only. Like every other page, it loads the analytics described below.

The website has a few short games the app does not include: Element Grove, The Great Race, Daily Draw, Feed or Control and Samhap. Each can be played before you sign in. When one asks for your birth date, your browser works out your character from it, and the date is not saved or sent to us. Daily Draw, when you are signed in, reads the birth date already on your account for the same purpose. Results are kept in your browser’s local storage: a best score, today’s round, a streak, your album of cards. If you play signed out, they stay there, except Feed or Control’s daily rounds, which move to your account the next time you open it signed in.

When you are signed in, four more records are kept on your account:

• Your place on the game boards: if you post to a game’s board, which game, the name you choose for the board, your score, for Element Grove the stage you reached, the character the board draws you with (an animal and an element, in the games that have one), and the month you played. Each board keeps your best for each month; Samhap’s adds up the month’s daily results, and Daily Draw’s is how many cards your album holds.
• Days you open InnateGlyph: one row for each day you open the app or the website while signed in, whether or not you play. Seven days running is part of how a board pass is earned.
• Board passes: each pass you earn, when it was earned and spent, and which five of your accepted friends counted toward it.
• Your Feed or Control rounds: your first try at each day’s deal, with its score, how many cards you got right out of how many, your best streak, and whether each card was right or wrong. A later try on the same day does not replace it.

The boards and their halls of fame are public. Anyone, signed in or not, can see your place on each, the name you chose, your score, the stage for Element Grove, your character in the games that draw one, and for a finished month whether you came first, second or third. Each hall of fame keeps the first three of every finished month. None of them shows your account, your email address, your birth date, or the day you played. Your days, your passes and your Feed or Control rounds are visible to you alone.

Deleting your account deletes all four: your rows on every board, including a place in a hall of fame, your days, your passes and your Feed or Control rounds. Results still kept in your browser stay there until you clear this site’s data.

Every page loads Vercel Web Analytics and Vercel Speed Insights, which record page views and page-load performance. We send them no custom events, so what they see is which pages get loaded and how fast, not your birth details, your chart, your chat messages, or anything you typed.

We do not run advertising networks, ad-targeting pixels, or cross-site tracking, and we do not sell your data.

• Google and Apple: for sign-in (OAuth). We only receive the profile fields the provider shares at sign-in.
• Supabase: our database and authentication provider. Your account data is stored on Supabase’s infrastructure with row-level security so only you (or, for shared readings, the person you’ve explicitly connected with) can read your rows.
• Render: hosts the backend that computes your chart. Birth details are sent there when the app builds a reading, when Find your glyph reveals a type (birth date and timezone only), when a Network map places You from a saved birth profile (birth date and timezone, plus birth time or birthplace when those were saved), and when Orbit or Pair Orbit draws a life (that person’s birth details, with a gender when one was given: yours, or the answer you gave about a friend). The server keeps recently drawn lives in memory, not on disk, so the same life draws again quickly. Render also processes standard web request logs (e.g. IP address). Each request the app makes also names the build of the app it came from and whether it is iOS, Android or the web. The server keeps only an hourly count of those two values, with no account or address attached, so we can tell when an old version of the app has stopped being used.
• Google: the Oracle chat feature and some narration text is generated by Google’s Gemini models. Your chat messages, your chart facts, and (if applicable) your saved context summary are sent to Google to generate a response. When the Oracle looks up your chart, the lookup it receives includes your birth date, birth time, timezone, and birthplace alongside the computed chart facts. Nothing is sent to Google until you agree to it. See “Sending your data to Google” below.
• Vercel: hosts the app’s frontend, processes standard web request logs, and provides the analytics described above.
• Wikipedia: portraits of public figures on the comparison screens are loaded by your browser directly from Wikipedia, so Wikipedia sees that request (including your IP address) the way any site you visit does. Nothing about you or your chart is sent with it.
• YouTube: the videos and picture posts on our website and in the Library are on our YouTube channel. Nothing loads from YouTube until you press play or open a post. On the web a video then plays in YouTube’s privacy-enhanced player (youtube-nocookie.com) and a post opens on YouTube; in the app both open on YouTube. Google sees that request (including your IP address), and YouTube’s own privacy policy applies to it. Nothing about you or your chart is sent with it.

We do not sell your data.

The Oracle composer can use your device’s speech-to-text (the browser or operating system recognition API) when you dictate a question. That audio is processed by the platform’s speech service (often Google or Apple, depending on the browser or OS) before a transcript appears in the composer. Once you send the message, the transcript is handled like any other Oracle question under “Sending your data to Google” below. We do not run our own speech server.

The live Oracle chat is the one feature that sends your personal data to a third-party AI company: Google, whose Gemini models write the answers. We ask you first, in the app, before the first message is sent, and the request is refused by our server until you have agreed. The check is not only in the app’s screens.

• What is sent: your birth date, birth time, timezone and birthplace; your computed chart and reading; the questions you type or speak and the answers, for the rest of that conversation; your saved chat context if you have that on; and the nicknames of friends you ask about.
• What is not sent: your name, email address or profile picture, and your friends’ birth dates, times or birthplaces.
• If you say no: everything else keeps working. Your chart, your reading, the Match, Network and Library screens, daily readings and pair readings are all computed on our own servers with no AI involved. Only the live Oracle chat stops.
• Turning it off later: open the account settings from the menu and switch “Send my chart to Google” off. It takes effect on the next request. It cannot undo what was already sent: messages Google has already received are covered by Google’s own terms, not ours.

• Friends you connect with hold their own copy of the birth details you shared when the connection was made, so the app can compute your pair reading for them.
• Invite links carry your birth details to whoever opens them, which is what lets them accept and get a pair reading. They stop working 24 hours after they are created, and you can turn them off before that. See “Your rights” below.
• Your feedback votes are pooled with every other signed-in user’s into a population aggregate, which the project’s admins can view. The aggregate is grouped by chart type and by what was voted on. It carries no account identifier, name, or email, so it shows what people with a given type thought, not what you thought.
• Your place on a game board is public once you post a run. See “Games on the website” above for what it shows.

The app includes about twelve thousand public figures, so you can compare your chart with people you know of. For each one it holds a name, a birth date and place, sometimes a birth time, a short introduction and sometimes a photograph. All of it was already public.

• Birth data comes from VedAstro’s published dataset (MIT License) and from Wikidata (CC0). A birth time is used only where VedAstro’s dataset carries it, and for a living person the app reads every public screen from the birth date alone.
• Introductions are the opening sentence of each person’s English Wikipedia article (CC BY-SA 4.0).
• Photographs come from Wikimedia Commons and are used under the licence each author released them with, every one credited on Photo credits. Photographs that are not freely licensed are not shown. Nor are photographs of living people known for Korean entertainment, whatever their licence: a free licence is the photographer’s permission, not theirs. A silhouette means one of those two.

We process this on the basis of a legitimate interest in offering information about public figures. None of these people is connected with InnateGlyph or has endorsed it, and no photograph of them is used in advertising or in the images the app lets you share.

If you are one of these people, or act for one, you can ask us to correct your entry, remove your photograph, or remove you entirely: email customer.service@innateglyph.com. We act on a request within one month.

• A copy of your reading and birth details, keyed to your account, so the app can paint before the network answers. On the website this is the browser’s local storage; on the installed app it may be the app’s on-device store instead. A different account signing in on the same device does not read it.
• Your “added by you” friends, friend categories, favorites, map preferences, which friends you skipped when Pair Orbit asked their gender, and any timeline year notes you type on Chart (notes stay on the device).
• A note of the friend requests you have sent from this device: the friend code or email address you typed, and when. The database keeps no record on your side until the other person accepts, so without this there would be no way to tell a request you sent from one you never sent. It is not uploaded, no other account can read it, and you can clear each entry from the Friends card on Match.
• A short technical log (the last 100 entries of things like which screen was opened, whether a gesture completed, and when the app was backgrounded), kept so problems on real devices can be diagnosed. It never leaves your device: nothing uploads it, and the only thing that reads it is a page running on that same device. The crash and problem reports described above are a separate thing, sent separately, and they never carry this log. It records no names, emails, birth details, chart values, account identifiers, or text you typed.
• If you used the app before sign-in was required, the first time you sign in on a device the reading and friends left on it are adopted by your account (they stay on the device), and any day-visit dates recorded then are added to your account’s attendance record.

• Account data is kept until you delete your account (see below) or request deletion.
• Compatibility invite links expire automatically after 24 hours and stop being usable, though the record of who invited whom may persist until the account is deleted.
• The copies held on the device (browser local storage, or the app’s on-device store) stay there until you clear this site’s data in your browser or uninstall the app. Signing out or deleting your account does not erase them from the device. It signs you out and reloads the app.

• Delete your account: from Profile, choose “Delete account.” This permanently removes your profile, friends, Oracle chats, feedback, and the rest of the data stored under your account on our servers. This cannot be undone. A few things it does not reach: copies on your own device, the birth details someone else accepted from you, problem reports, and the store’s own billing records. Deleting your account sets out the steps and names each of them.
• Access or export your data: email customer.service@innateglyph.com to request a copy of the data we hold about you.
• Withdraw consent for a friend connection: remove a friend at any time from the Match screen. Removing deletes your copy of their details; the copy of yours they accepted stays on their list. To take that back as well, block them from the same row (the three dots, then Block): blocking removes the connection on both sides, stops their friend requests, and keeps each of you off the other’s view of a mutual friend’s network. They are not told. Blocked people are listed in the settings sheet, where you can unblock them; unblocking does not restore the connection.
• Revoke an invite link: open the Match screen, expand Invite & manage, and choose Turn off this link. Every invite link on your account stops working at once: opening one after that shows an expired link, and nobody new can accept it. It does not reach backwards: someone who already accepted keeps the copy of the birth details you shared with them, and a pair reading they have already opened is theirs. Removing them as a friend, above, is what ends that.
• Withdraw consent for Google: switch “Send my chart to Google” off in account settings. See the section above for what that does and does not reach.

If you’re in the EU/UK or California, these correspond to your GDPR/CCPA rights to erasure, access, and portability. Email us and we’ll help.

The Service is not directed at children. You must be at least 16 years old to use InnateGlyph, including the public website pages. We do not knowingly collect data from anyone under that age. The signed-in onboarding flow asks you to confirm you meet this requirement before creating a reading.

If this policy changes in a meaningful way, we’ll update the date at the top of this page and, for significant changes, note it in the app. Continued use after an update means you accept the revised policy.