How we touch your data (and where we refuse to)

Effective date: 17 May 2026

Last updated: 17 May 2026

Your money story is sensitive. DebtEase asks for digits and context so charts and simulations mean something—not so we can build a dossier for advertisers or whisper your EMI schedule to strangers.

This Privacy Policy is the boring-but-important map of what we collect, why we keep it, who might see it anyway (hint: infra + law, not shady data brokers), and what you can ask us to do about it.

If reading policies usually feels like chewing cardboard: skim the headings, linger where you’re curious, and email Mihir anytime at mihir@debtease.app. Legitimate indie shop—feedback actually arrives in one inbox.

By using DebtEase, you agree to the practices described here (alongside our Terms of Service).

DebtEase is a financial wellness and debt-awareness product built by Mihir, an independent developer based in India.

Throughout this Policy, “DebtEase”, “we”, “our”, or “us” means the folks operating the service (which, practically, rounds to a small founder-sized team—even when we sound corporate in plural form).

DebtEase focuses on clarity: debt structure, cashflow sensitivity, hypothetical stress sketches, repayment visibility—not lending decisions, brokerage, or spooky default prophecies.

This document explains:

It doesn’t magically replace localized privacy laws—you may have additional rights depending on where you live. If there’s tension between this Policy and what the law says, the law wins (and please tell us if you think we drifted—we fix things).

When you sign up or authenticate, we may collect things like:

You choose what to enter. That might include fields such as:

These pieces often assemble into structured snapshots, debt lists, onboarding answers, repayment notes—whatever the product needs so your view isn’t hallucinated fiction.

Stress simulations and scenario calculators may store:

Some flows may crunch numbers ephemerally and never park the full worksheet in durable storage—we’ll still say “may” because implementation evolves during alpha/beta.

To keep the lights on (and crashes down), modest technical telemetry routinely exists:

Nobody loves IP logs—we use them sparingly for security/abuse arcs, not voyeur tours.

Typical lawful purposes include:

We aim to minimise surprise uses. Fancy AI training on your ledger line-items? Not the default plan—silence ≠ consent for unrelated experiments.

Engines may chew your voluntary numbers to spit out:

Reminder (because regulators like repetition):

They’re consistent arithmetic costumes on your volunteered stage.

DebtEase doesn’t pursue these business clichés:

If we pivot later (honesty clause), we refresh this Policy conspicuously beforehand rather than ninja-editing paragraphs at 3 a.m.—that’s rude.

Hosting, databases, auth vendors, transactional email pipes, uptime monitors—they process data strictly to deliver DebtEase-shaped functionality, ideally under sane confidentiality guardrails modern platforms expect.

Courts, regulators, subpoenas—not Pokémon cards. If lawful, narrowly tailored requests arrive, we respond responsibly and proportionally—not performative leaks.

If DebtEase merges, reorganises, sells assets, successor entities may steward data consistent with successor privacy promises (we’ll trumpet material changes plainly).

Outside those lanes: no promiscuous financial data yard sales.

Measures we reach for commonly include HTTPS, password hashing hygiene, partitioned access concepts, infra vendors with reputations brighter than floppy disks—but perfect security exists only in marketing fairy tales.

Do your side: unique passwords, don’t authenticate on shady café Wi‑Fi heroes without VPN common sense.

We keep data:

Stale experiments may vanish sooner—retention evolves as product exits alpha awkwardness.

Depending on geography and practicality, you can often request:

Ping Mihir at mihir@debtease.app with plain-language requests—we’re not burying tickets behind enterprise portals.

Identity checks may precede nuking accounts so random strangers cannot grief-delete you.

Deleting doesn’t teleport every neutron immediately:

We’ll articulate blockers plainly if deletion hits a snag so you aren’t existential-pinging in suspense.

Understanding funnels beats guessing. We analyse:

Prefer pseudo-anonymous tallies whenever engineering allows.

DebtEase-ish surfaces may stash:

You can sabotage cookies—some features politely protest and stop cooperating.

DebtEase expects users 18+. We aren’t knowingly building playground debt simulators—if minors slip through inadvertently, revoke access and yell at mihir@debtease.app so we rectify.

Infrastructure vendors host bits across regions; cross-border hops may occur. Continuing to use DebtEase signifies awareness that processing may transcend your apartment’s postal radius when legally permissible.

India remains operational home base for us—outside transfers still deserve sensible safeguards—not duct tape diplomacy.

We edit when features, stacks, laws, paranoia tiers shift. Revised versions post here; materially spicy changes merit clearer signalling (banner, email for registered users—we’ll act proportionately to the churn).

Continuing after updates implies reading responsibility on you—we’ll still aspire to humane diff summaries when chaos isn’t mid-outage panic.

Name: Mihir

Email: mihir@debtease.app

Role: Independent developer / operator

Location: India

Security disclosures, privacy meltdowns, philosophical debates about amortisation UX—welcome.

Choosing DebtEase means you understand we:

You can revoke participation by deleting and walking away—even if echoes persist briefly as described.

DebtEase illuminates structural storytelling about money pressure—it never becomes:

Treat outputs as scaffolding for thought, spiced with scepticism and accountants when stakes skyrocket.

Thanks for staying curious—not complacent—with your privacy. If we mess up transparency, flag it—we’d rather iterate Policy tone than prestige-laundering silence.