About this policy
Tryndexp is a free, private, noncommercial trading-journal project for a limited circle of users, including its owner and friends. It is operated by an individual, not a registered company or sole trader. Tryndexp is the product name. Contact the operator about personal data at support@tryndexp.com. The operator’s personal name is not published in this review version; this does not establish that legally required identification has been fulfilled.
Registration and profile
We process your email address, display name, account identifiers, verification status, optional avatar and profile settings. Email/password registration stores an Argon2 password hash, never the plaintext password. Verification and recovery credentials are stored as hashes with expiration and invalidation controls. Information is used to create and protect your account, verify email, sign you in and recover access.
Google Sign-In
When configured, you may choose Google Sign-In. We request openid, email and profile information, validate Google identity claims and store a stable Google account identifier and verified-email metadata for sign-in or explicit linking. Google access, ID and refresh tokens are not retained as persistent account data. Matching email addresses do not automatically merge accounts. Supported linking and unlinking controls are available in your profile, with security checks and another usable sign-in method required to unlink. Google processes information under its own privacy policy when you use its service.
Workspace information and preferences
Your account stores trading-account metadata, including names, provider/platform, currency, initial balance, mode and lifecycle state. Methodologies may contain descriptions, criteria, notes, links, revisions and private uploaded images. Profile and presentation preferences include language, palette, navigation, density and supported date, time and currency display options. These data provide your workspace and synchronize supported settings. Display currency does not convert stored financial facts. Avoid uploading unnecessary personal information about other people.
Email, hosting and recipients
Verification and password-reset emails contain your address and a time-limited link. Delivery uses the configured SMTP service, which receives message content and delivery metadata. Hosting and storage infrastructure process application data to run the service. The actual providers, processing countries and any transfer safeguards have not been confirmed for this review version and must be verified before publication. We do not identify an unconfirmed provider as deployed. We do not sell your private workspace data or use it for advertising or AI training.
Current integration boundaries
This version stores account metadata, methodologies and manually entered or CSV-imported trading records, including timestamps, prices, declared financial results, journal notes and classifications. It uses these records for journal views and supported closed-trade analytics. Revision history and import identities are retained when a trade is hidden from active views. If you explicitly connect the Windows MT5 Collector, it sends the approved broker/server/login identity, account currency, orders, deals and position observations over HTTPS. Device credentials are scoped and revocable; the server stores token hashes and source revisions. Local credentials and queued payloads use Windows user-scoped DPAPI. Broker equity observations, AI-provider processing and payment collection are not implemented. We do not collect MT5 trading passwords or place trading orders. Future integrations or new processing purposes require a revised disclosure before activation; this policy does not authorize them in advance.
Storage and protection
Application records use PostgreSQL; private images use an operator-controlled local storage adapter with authenticated ownership checks. Image normalization removes embedded metadata. Password hashing, hashed session credentials, revocable sessions, CSRF protection, rate limiting, backend ownership checks and database row-level security reduce risk. Security and policy events and technical request information may be recorded to operate and protect the service. No system is completely secure. This policy does not certify unverified production encryption, backup, monitoring or recovery arrangements.
Retention and deletion requests
Workspace information remains stored until it is changed or removed through supported functions or an operator-handled request. A complete retention and purge schedule, including logs, revisions and backups, has not yet been established. Session and token expiration or revocation does not delete all associated records. Archiving a trading account does not delete it. There is no self-service user-account deletion workflow. Request account closure or deletion at support@tryndexp.com; we must verify your connection to the account and assess the request and any applicable obligations. No unconfirmed deletion period or backup-erasure guarantee is promised.
Your choices and privacy requests
You can edit supported profile fields and preferences, manage sign-in methods and revoke supported sessions. For access, correction, a copy of your information, deletion or another privacy concern, email support@tryndexp.com. Describe your request and account email, but never send passwords, recovery links or authentication codes. Depending on applicable law, rights may also include portability, restriction, objection and complaints to a competent authority. Applicable legal bases, authorities and statutory response duties depend on the operator’s and users’ jurisdictions and remain to be confirmed; the private, free nature of the project alone does not remove them.
Policy updates
We will review this policy when processing or service functionality changes, including before commercialization or a wider public launch. Approved revisions will display a last-updated date on this page. Material changes should be communicated through the service or account email before new processing begins. This version awaits owner approval and resolution of required legal disclosures; no effective or last-updated date has been assigned.