Privacy Policy
Last updated 19 October 2026
The short version
- Your trades, notes and screenshots are yours. We do not sell them, share them for advertising, or use them to train any model.
- We never ask for and never hold broker credentials, API keys, or bank and card details.
- These pages load nothing from third parties — no analytics, no trackers, no external fonts. View source and check.
- Export everything as a ZIP whenever you like, and delete your account from account settings. This removes your account and journal records from the live database; backup and service-provider retention are explained below.
- Deleted data survives in backups with a 14-day retention target. Expiry checks run hourly; outages or deletion failures can delay removal. See section 6.
1. Who this is and how to reach us
TradeTattva Journal is an independently operated trading-journal service reached at
journal.falconn.app. For any question about your personal data — including
access, correction, erasure, or a grievance under the Digital Personal Data Protection
Act, 2023 — write to hello@falconn.app. Mail sent there reaches the
person who runs the service and is able to answer questions about how your data is
processed. We aim to respond within seven days.
2. What we collect
| What | Detail | When |
|---|---|---|
| Account | Your email address, a password stored only as an Argon2 hash, and the date you signed up. | At signup. |
| Profile | First name, last name, display name, timezone and display currency. | Only if you fill them in. All optional; the journal works without any of them. |
| Google identity | Your Google account's stable identifier and the email address Google returns. Nothing else — no contacts, no Drive, no profile photo. | Only if you choose "Continue with Google". |
| Trading data | The contents of the tradebook you upload: instrument, side, quantity, price, timestamp, segment, order and trade identifiers, and the account label you give it. Plus trades you enter by hand. | When you upload or enter them. |
| Your writing | Notes, tags, grades, setup names, planned risk and target amounts, and any screenshots you attach. | When you write them. |
| Session | An opaque session token, stored only as a SHA-256 hash, with its expiry and the browser's user-agent string so you can recognise your own devices in the sessions list. | When you sign in. |
| Operational and security records | Account-linked active-day, request, import and AI-usage counters; timings, error counts and successful sign-in history, including sign-in method and a limited user-agent description. These support reliability, security and product operation. | When you use account features or sign in. |
| Server logs | Standard web-server logs: request path, status, timestamp and the connecting IP address. Rotated by size; no maximum number of days is guaranteed. Infrastructure providers may retain their own security records. | Every request, as with any website. |
What we do not collect
- No broker credentials. TradeTattva Journal never connects to your broker. You give it a file your broker already gave you. There is no login, no API key, no TOTP seed, and therefore nothing here that could ever place an order.
- No payment details. The service takes no payment today. When paid plans begin, card and UPI details will go directly to a licensed payment gateway and will not pass through or rest on our servers.
- No tracking. No analytics scripts, no advertising pixels, no third-party cookies, no session recording, no external fonts or CDNs. The only cookie we set is the one that keeps you signed in.
- No device-location or contacts permission is requested, and no advertising identifier or device fingerprint is deliberately collected by Journal. Network providers still receive IP addresses and connection metadata; provider processing is described below.
3. Why we hold it, and on what basis
We process your personal data for one purpose: to run the journal you asked for — to store the trades you upload, compute statistics from them, show them back to you, sign you in, and send the small number of service emails described below. Under the DPDP Act the basis is your consent, given when you create an account and again each time you upload a file. We do not process your data for advertising profiles or resale, and there is no secondary purpose hiding behind the primary one.
Emails we send
Only transactional ones: verify your address, reset your password, and — if you opt in — a summary of your own activity. No marketing email without you asking for it first, and anything periodic carries an unsubscribe link.
4. Who else touches your data
The providers below support the service. Their service, security and legal-retention terms also apply, and provider retention can differ from Journal account-deletion timing. Identity providers also operate their own sign-in services.
| Who | What they see | Why |
|---|---|---|
| DigitalOcean | Everything, as the operator of the server the database runs on. Bangalore, India. | Hosting. |
| Cloudflare | Your requests in transit. TLS terminates at their edge, which means they can see traffic as it passes. | DNS, TLS and the tunnel that lets the server serve you without exposing a single inbound port to the internet. |
| Cloudflare R2 | Nightly encrypted database backups and uploaded attachment objects when object storage is configured. | Backup recovery and attachment storage. |
| Resend | Your email address and the contents of service emails. If you enable the weekly digest, this includes trading summaries: net results, trade counts, win rate, symbols, dates and rule-adherence observations. It does not include uploaded screenshots or the full text of your journal notes. | Email delivery. |
| OpenAI | Context sent when you use an enabled AI feature: depending on the feature, this can include your question, selected trade or session data, notes, plans, strategy rules, relevant history or aggregate performance. Screenshots are included only where a feature explicitly offers image processing and you select them. | Optional AI help and reviews. Review the feature-specific data preview and confirmation before sending. AI feedback saved in Journal is part of your account data. |
| Only that you signed in — and only if you chose "Continue with Google". Google never receives your trading data. | Sign-in, at your option. Use email and password instead and Google is not involved at all. |
We do not sell your personal data, and we do not share it with anyone not listed above, except where the law requires it of us.
Optional AI features use OpenAI when enabled. The context depends on the feature and is described in its preview or confirmation; not every request includes all of the data listed above. We do not use your journal data to train our own models. Requests reviewed for the current AI features disable response storage with the provider, but this setting does not itself establish Zero Data Retention or eliminate provider security logs. Provider processing and retention depend on the applicable service terms and configuration; this policy does not promise zero provider retention. You can use the core journal without requesting AI feedback.
5. Where it lives
Your journal lives in a PostgreSQL database on a server in Bangalore, India. Backups go to Cloudflare R2 object storage. Email is delivered through Resend, whose infrastructure is outside India — so your email address and email contents cross borders. If you enable the weekly digest, those contents include trading information. Cloudflare also processes traffic and backups; we do not promise that all processing stays within India. The DPDP Act permits transfers of this kind except to countries the Central Government restricts.
6. How long we keep it
| Data | Kept |
|---|---|
| Your journal — trades, notes, attachments, profile | Until you delete it, or delete your account. |
| Sessions and sign-in history | Session validity is normally 30 days. Expiry prevents login but does not guarantee immediate removal of every expired row. Sign-in history remains with the account unless removed by a separate cleanup. |
| Email verification and reset tokens | Normally valid for 7 days and 30 minutes respectively, single-use and hashed at rest. Validity is separate from physical record cleanup. |
| Operational metrics and AI-help records | Older usage buckets become eligible for cleanup after 90 days during subsequent activity. Tavya conversation rows and request records become eligible after one day and 30 days respectively when cleanup runs. Opted-in retained help questions follow the request-record cleanup. Inactive accounts or cleanup failures can retain eligible records longer. |
| AI reviews | Saved evidence and feedback remain with your account. Unsaved review drafts become eligible for cleanup after one day when review expiry runs. |
| Server logs | Size-based rotation, not a guaranteed day-based limit. Provider logs and delivered email have separate retention. |
| Backups | 14 days is the retention target, with hourly expiry checks. Scheduling and service failures can delay expiry; failures are logged and retried. See below. |
Deletion, told properly. Deleting your account removes every row we hold about you — account, sessions, imports, trades, notes, attachments, linked identity — in a single database transaction. It is immediate and it is not a soft delete or a "marked as deleted" flag.
Backups created before deletion may still contain your records. They are eligible for removal after 14 days, with hourly checks independent of new backup creation. This is not a guarantee of deletion at an exact hour: storage or service outages can delay removal. Failed expiry attempts are logged, alerted through the configured operations channel and retried.
We do not use backups to recover an account at a former user's request. Before any disaster-recovery restore returns to service, prior deletion requests must be reconciled and the affected records removed again.
Account deletion does not automatically erase service emails already delivered to your inbox or records retained by email and infrastructure providers. Provider records and security logs are subject to their applicable retention and any legal obligations. Contact us for an erasure request covering those records; we will explain any retention exception.
For step-by-step instructions or to request deletion without installing the app, visit Delete your Journal account. For other help, visit Support.
7. Your rights
Under the DPDP Act you have the right to know what we hold, to have it corrected, to have it erased, and to complain. All of it is built into the product rather than sitting behind an email queue:
- Access and portability — Export from your account. You get a ZIP with your trades, notes and attachments in open formats. No limit on how often, no charge.
- Correction — Edit any trade, note or profile field directly, or write to us if something is wrong that you cannot reach.
- Erasure — Delete account, in your account settings. See the caveat above and mean it.
- Withdraw consent — Deleting your account withdraws it. The service cannot function without processing the data you give it, so there is no partial withdrawal that leaves a working journal behind.
- Grievance — hello@falconn.app. If we do not resolve it to your satisfaction, the DPDP Act gives you a route to the Data Protection Board of India.
8. How it is protected
- Passwords are hashed with Argon2. We cannot read yours, and neither can anyone who steals the database.
- Session tokens and email tokens are stored as SHA-256 hashes, not as the tokens themselves.
- Every request is served over HTTPS. The session cookie is
HttpOnly,SameSite=LaxandSecure. - The server publishes no inbound port to the internet for the application. The database is not reachable from outside the machine at all.
- Tenancy is enforced in every query — your rows are fenced by your account id, and that fence is covered by automated tests that fail the build if it slips.
- Disks and backup storage are encrypted at rest by the hosting providers.
- Backups are taken nightly and the restore is rehearsed, because an untested backup is a belief rather than a backup.
No service can promise it will never be breached, and we are not going to be the ones who do. If a breach affects your personal data we will notify you and the Data Protection Board as the DPDP Act requires, and we will tell you what actually happened rather than a sentence of public relations.
9. Children
TradeTattva Journal is not intended for anyone under 18 and we do not knowingly create accounts for children. If you believe a child has signed up, write to us and we will remove the account.
10. Changes to this policy
If we change it, the date at the top changes, and anything that materially affects your data will be announced in the product's What's new page rather than slipped in quietly.