What JOURNY knows, and what it never will.

JOURNY is built and run by Jagesh Pandey, an individual based in India, not a registered company. There is no company behind it and no team. When this page says “we”, it means one person.

For anything on this page, write to hi@jageshpandey.com. A person reads every message.

Three groups, and nothing outside them.

Your account

• Your email address, and either a password or the fact that you signed in with Google. Passwords are handled by Supabase Auth and JOURNY never sees them.
• A display name, an optional avatar, and an optional gender you can leave blank. The gender field picks a default avatar and warms the greeting. Nothing else reads it.

What you record

• Transactions, accounts, budgets, goals, investments, people you lend to or borrow from, and recurring commitments. In other words, exactly what you type in.
• Notification preferences, and a push subscription if you turn on reminders.

On your device

• A copy of your records, so the app opens instantly and keeps working with no signal.
• Your appearance settings, your analytics choice, and your AI key if you add one.

JOURNY does not connect to your bank. There is no account aggregation, no screen scraping and no read access to any financial institution. Nothing arrives here unless you enter it or import it yourself.

It also never asks for an Aadhaar number, a PAN, or a full account number. Card and account records keep the last four digits at most.

Your records live in a Postgres database hosted by Supabase, in their Mumbai region. Every table is protected by row-level security, which means the database itself refuses to return one person’s rows to anyone else. That check sits below the application, so a bug in JOURNY’s code cannot talk its way past it.

The site is hosted on Vercel. As with any web host, their servers handle the requests your browser makes.

More detail on how this is built is on the security page.

JOURNY asks before it measures anything. Until you answer that banner, no analytics tool starts. Choose “No thanks” and none ever does. You can change your mind later in Settings.

If you say yes, two tools run:

• Google Analytics, which records page views so it is possible to see how people find JOURNY. It receives no custom events at all.
• PostHog, which records twelve product events: signing up, signing in, finishing setup, creating or editing or deleting a transaction, finishing a CSV or portfolio import, viewing or acting on an AI insight, and using a named feature.

What those events never contain

No amount, balance, total or budget limit. No transaction name, note or merchant. No category or tag names, because you write those yourself. No account names or numbers. No investment symbols or values. No AI prompts or responses. No email address.

This is not a promise held up by good intentions. Every property of every event passes through one function that drops anything not on a short approved list, then drops it again if the name reads like money or identity. That function is unit tested against a realistic Indian transaction, so the rule fails the build rather than failing quietly. You are identified to PostHog by your account’s random ID and never by your email. Session recording and automatic click capture are both switched off, because on screens full of rupee amounts they would be leaks by design.

JOURNY’s numbers are all worked out in its own code. The AI layer only puts them into sentences, and it is off until you add your own Google Gemini key.

• Your key is stored in your browser and nowhere else. It never reaches any server of ours, and Settings only ever shows its last four characters.
• When narration runs, your browser talks to Google directly. The request does not pass through JOURNY.
• It sends summaries, not your ledger: monthly totals, category shares, and up to five of your largest expenses for texture. Your full transaction list never goes.
• Remove the key in Settings and the feature stops. Nothing else changes.

Google decides what happens to data you send them under your own key. That relationship is between you and Google, and their terms apply to it.

The complete list. There is no advertising network and no data broker.

• Supabase — database, and the sign-in system.
• Vercel — hosting.
• Google Analytics and PostHog — only after you allow analytics.
• Google Gemini — only if you add your own key.
• Resend — delivers a message to me if you use the contact form. It sees what you typed there and nothing from your account.

JOURNY does not sell your data, share it for advertising, or hand it to anyone for any commercial purpose. There is no arrangement of that kind and no plan to make one.

• Export everything as a JSON file from Settings, at any time, without asking.
• Delete your account from Settings. That removes your records by database cascade rather than by a list someone has to remember to maintain, so nothing is left behind.
• Turn analytics off, in Settings, whenever you like.
• Remove your AI key, in Settings.
• Correct anything, by editing it. It is your ledger.

If you want something these controls do not cover, or you want to know what is held about you, write to hi@jageshpandey.com and I will answer.

• JOURNY is an early product run by one person. It is not certified, audited or accredited by anyone, and this page does not claim otherwise.
• India’s data protection law is still being rolled out in stages. I have tried to describe honestly what happens to your data rather than claim a compliance status I cannot yet demonstrate. If a rule turns out to require something JOURNY does not do, I would rather fix it than argue.
• No online service can promise perfect security, and I am not going to be the first to pretend otherwise.
• If this page ever changes in a way that matters, the date at the top changes with it.

This policy takes effect on 11 August 2026, and is governed by the same terms as the rest of JOURNY. See the terms of use.