Privacy Policy

What this covers

FTT Trading Journal is operated by Arun Manoharan under FalconTraderTamil. This policy explains how the journal handles your Google sign-in, records you enter and chart images you upload. For privacy questions or requests, contact arunmanotrade@gmail.com.

Google sign-in and purchase access

We use Firebase Authentication to identify your Google account. We use your Google account identifier, email address and sign-in status to provide the journal and check whether your purchase has been activated. We do not receive your Google password. The seller can manage purchase activation in the Firebase project.

Journal records

Your trade entries, P&L, strategies, rules, reviews, account settings, branding text, and deposit or withdrawal history are saved as an application data file in the Google Drive account you connect. The journal may hold unsynced changes in this browser until you can reconnect. Earlier versions stored journal records in the FTT Journals Firestore project; older records are copied into the buyer's Drive after authorization, verified, then removed from Firebase. If migration fails, the original Firebase copy is kept until migration can be completed. The project operator can administer any records still awaiting migration. Firebase continues to hold sign-in and purchase access records.

Chart images and Google Drive

If you choose Connect my Google Drive, we request the drive.appdata permission so the journal can create, read, update and delete your journal records, chart images and logo in your Google Drive application-data folder. This folder is hidden from the normal Google Drive interface; its files count toward your Google Drive storage. We do not request permission to read all your Google Drive files. The journal reads images when you open chart views or export a backup. Older images are copied to your Drive and verified before the older Firestore copies are removed. If migration fails, the remaining originals stay in Firebase until the migration can be retried.

Use and sharing

We use this information to provide sign-in, purchase access, cross-device journal sync, chart viewing, backup export and customer support. Firebase, Google Cloud and Google Drive process data to provide these functions. We do not sell your Google user data or use your Drive images for advertising. We do not share access to your private Drive app-data folder with other buyers.

Google API data use

We use Google sign-in data to authenticate your account and check access. If you authorize Google Drive, the journal uses its app-data permission only to store, retrieve and delete your journal records, images and optional logo for use in the journal. We do not use Google user data to train artificial intelligence models, target advertising or sell personal data. Access to your Drive application-data folder is limited to the permission you grant the journal; you can withdraw that permission in your Google Account.

Retention and your choices

You can edit or delete individual trades and chart images in the journal and export a JSON backup. Deleting a trade in the journal also requests deletion of its attached images. If an upload, deletion or sync fails, check the journal status and retry. Access revocation does not itself erase stored records. To request deletion of your account records or ask about data retained in the Firebase project, email the support address above from the Google account you use for the journal. You may revoke Drive access through your Google Account settings; this prevents the app from reading those images until you reconnect, and does not by itself delete data already stored.

Security and updates

Purchase records and any journals awaiting migration are separated by authenticated account and protected by Firebase access rules. Drive access for current journal records and images is requested from the signed-in buyer for the app's own folder. No online service can guarantee complete security; keep your Google account secure and export backups when needed. We may update this policy as the product changes and will publish the revised version here.