You Told URIEL Everything. Here's Where It Goes.

This article is available in English. Spanish and Arabic translations will follow after legal review.

Most companies bury this in a privacy policy nobody reads. We're not doing that.

Here's the thing. URIEL asks you for more than almost any software ever will: your faith, your upbringing, what's keeping you up at night. It has to. You cannot be coached well by something that doesn't know you.

But you should never hand over that much of yourself without knowing exactly where it goes and who touches it.

Dr. Young describes the moment people meet URIEL: "Damn, this thing really sees me." And the truth is, it's just responding to data sets. The seeing is real, and it is built entirely from what you chose to share. That's why this page exists.

So this is the plain version, and where something isn't finished, we say so. It sits alongside our formal Privacy Policy: that one's the legal document, this one's the human one.

What URIEL asks you, and what you can refuse

Onboarding covers 37 fields, and they exist for one reason: two people can bring the same problem and need completely different coaching. Your answers are what let URIEL respond to who you are, not just what you typed. (Five of those fields are military follow-ups. If service doesn't apply to you, you never see them.)

Some questions sit in categories the law treats with extra care: religious belief, sexual orientation, and answers about your upbringing, health or circumstances that reveal more than they appear to. So here is exactly what your choices are.

• Faith, and how closely you follow it. These need an answer, and "Prefer not to say" is one of the answers. Choose it and that is what we store.

• Sexual orientation. Leave it blank. There is deliberately no "Prefer not to say" option, because we didn't want a record of you declining either. Skip it and there's nothing there.

• Your social and cultural perspective. Skip it, or choose "Prefer not to say."

• Military service. Follow-up questions appear only if they apply to you, and every one of them can be declined.

Your answers save as you move through the steps, but a skipped question is stored as a blank, nothing more. No answer gets recorded that you didn't choose, and skipping holds nothing up.

Those four are the questions we built a formal skip into. Free text, uploaded documents and the things you say in session can reveal sensitive information too, and no skip button covers that. Treat everything here as something you've chosen to share.

The four kinds of memory URIEL keeps

URIEL is built to feel like it's known you a while. That only works because it keeps four kinds of memory.

The conversation itself. Your sessions are saved in full, the way a transcript is.

A short recap of each session. When a session ends, a few lines get written on what it was about and where you landed. URIEL reads that first next time instead of re-reading everything.

A private notebook. Short notes about you, written by the system after each exchange rather than by you: how you prefer to be challenged, what you've said matters most, moments worth holding onto. Some notes keep the exact line you said. They're held separately from the conversations that produced them. That last part matters; we come back to it below.

Deep memory. Your sessions, profile, documents and any connected public posts also become lists of numbers called embeddings, stored beside the text they came from. That's what lets URIEL search by meaning: mention something from four months ago and it finds the moment instead of hunting for a keyword. Each message you send is also embedded on the spot, purely to run that search.

None of this is hidden. Before your first message, and beside the box you type in, the app says it plainly: this conversation is saved, and useful context may be remembered for future sessions.

Where your data lives and how it's protected

Everything you share lives in a managed, access-controlled database, with the deep-memory embeddings held right beside the text they came from. Uploaded documents live in separate managed file storage.

Both are encrypted at rest with AES-256 and in transit with TLS. That encryption happens at the infrastructure level, by the platforms that run it. We don't layer our own cryptography on top of it.

Every query the application makes is scoped to the person signed in. One user's data isn't reachable from another user's account, enforced at the query level rather than just hidden in the interface. The tools URIEL itself uses to look things up carry the same restriction, and none of them accepts an identity from the AI: who you are always comes from your login, never from the model.

Every AI system that reads your words

URIEL isn't one AI. It's several systems, each doing one job. We don't publish which models or vendors sit under the hood: that changes as we improve URIEL, and a name on a box tells you nothing about your privacy. What protects you is knowing exactly what each system is allowed to see, so that's what we list. All of these calls travel through a single AI gateway, with one exception we name below.

Three of those rows need spelling out.

The small conveniences aren't blind. Your greeting is built from almost nothing. The suggestion chips are a different story: they draw on your profile summary and your latest recap, including named breakthroughs and action items. And every session title is made from the first message you sent in it, word for word.

Voice changes one thing. Speak to URIEL instead of typing, and your audio goes to a dedicated speech-to-text system before URIEL reads a word. That's the one call that doesn't pass through the gateway. Type, and there's no audio to send at all.

Your profile travels early. To make URIEL's first response fast, the app warms up the coaching system when the page loads, and that warm-up carries your profile summary and onboarding answers. In plain terms: your profile is in play the moment you open the app, not only when you send a message.

Every one of these systems runs on paid, business-grade APIs, not consumer chat products. You'll also notice this article makes no promise about model training or retention periods. That's deliberate: those promises are only worth making once the signed agreements are verified, that review isn't finished, and we won't print a "never" we can't yet stand behind. When we can, it will be here.

The other services that hold pieces of your account

Each of these does one job, and nothing more. A hosting platform runs the app and routes the AI calls. A managed database holds your records. Object storage holds your uploads. If you upload a document, a document-parsing service reads its full content to turn scans and PDFs into text URIEL can use. If you hand URIEL a link, a page-fetching service retrieves it. A payment processor takes payment, and your card details never touch our servers. An email service sends your account email. A job queue runs our background work. And if you connect a social profile, a crawling service fetches its public posts for us.

Our analytics and error-reporting tool is the one that touches your identity: it receives your email address and name so a crash can be traced back to an account. It never receives session content, and session recording is switched off. It also only runs if you allow analytics cookies; decline them, or change your mind later in settings, and nothing more is sent.

Every one of these services is under a formal agreement with us, and the complete named list lives in our Privacy Policy, where the law requires it. This page is about what each one touches.

What you control

• Skip it. Optional questions can be left blank, and "Prefer not to say" is a real answer where it's offered.

• Change your mind. Every onboarding answer is editable from your profile, and the optional sensitive ones can be cleared outright. Saving rebuilds the coaching profile URIEL works from, so the change actually reaches how it talks to you. The deep-memory copy refreshes as part of that, though if the refresh fails, the old passages can linger until your next save.

• Delete a session. Removing a session takes its transcript, its record, its recap and its deep-memory passages with it. Read the caveat below before you rely on that.

• Disconnect a social profile. Social Connections only ever reads a public profile you typed in yourself. Disconnect it and the connection, the imported snapshot, the posts and their embeddings go.

• Privacy Shield. Always on. Your conversation veils itself when you switch tabs or click away, resists in-tab screen capture, and copying is blocked inside the transcript. The limit is real: no web page can block an OS screenshot, a screen recorder, or a phone camera pointed at your screen. It's the strongest honest deterrent a browser allows, not a lock.

• Download all of it. "Download your data" in settings gives you a JSON file: your account record, full chat history, document list, coaching profile with all raw answers and the analyses built from them, plus every session, summary, goal, notebook note and social connection.

• Delete your account. This cascades through your coaching data: profile, answers, sessions, summaries, notebook, goals, social connections, embeddings. Your uploaded documents are purged from file storage, your billing record is purged from the payment processor and any subscription is cancelled at the same time.

Deleting a single session does not remove the notebook notes that session produced. Those are stored separately, on purpose, so that what URIEL has learned about you survives you tidying up your history, and some of them keep a line you actually said. If you want a session gone in every sense, closing your account is the only thing that clears the notebook too. We'd rather you hear that from us than discover it.

And your export leaves things out rather than let you assume the file is everything: the number-vectors behind deep memory, the chunked text deep memory reads from, and the original uploaded files, which you already have. It also doesn't contain your billing records, which live with the payment processor, or the technical login records of your account. Everything human-readable that URIEL knows about you is in there.

How long we keep things: until you delete them

Straight answer: until you delete them.

There's no automatic clock. Nothing expires on its own. Your sessions from your first week will still be there in your second year unless you delete them or close your account. That's a deliberate trade: URIEL's memory is the product, and memory with an expiry date is a worse coach.

Documented retention periods are on our roadmap. We won't imply a schedule we haven't built yet; when they land, we'll update this page, not before.

Questions we expect you to ask

Is what I tell URIEL used to train AI models? We use paid APIs, not consumer chat products, and paid terms are a different world from free ones. But we won't print "never" until legal has verified every signed agreement, and that review isn't finished. When it is, the answer will be here in plain words.

If I delete a session, is it really gone? The transcript, the record, the recap and the deep-memory passages: yes. The private-notebook notes it produced: no, those stay until you delete your account.

What happens if I just stop showing up? Nothing expires. Your data waits, unchanged, until you delete it or close the account. Walking away doesn't erase anything, and we don't want you assuming it does.

Does using my voice change anything? One thing: your audio passes through a dedicated speech-to-text system before URIEL reads it. Typing skips that step entirely, because there's no audio to transcribe.

Your data is yours to take or delete from your settings, without asking anyone. But if something here doesn't sit right, or you want the parts the export leaves out, write to us at inquiries@youngethicalintelligence.com and a person will answer you.

A tall tree has deep roots. Trust works the same way: it doesn't come from what a company says about itself, it comes from what holds when you dig. We'd rather you trust us because you checked than because we asked.