1. About this policy and how to contact us
ZenvoJournal ("we", "us", or "our") provides the trading journal and performance-review service at zenvojournal.com. This policy explains how ZenvoJournal collects, accesses, uses, stores, shares, and deletes personal information when you visit our website, create an account, sign in with Google, save journal content, or contact us.
For privacy questions, access or correction requests, or account and data deletion, email support@zenvojournal.com. For subscription or payment questions, email payments@zenvojournal.com.
2. Information we collect and where it comes from
- Account and authentication information: your email address, username or display name, Firebase user ID, sign-in provider, email-verification status, and account creation and sign-in timestamps. Firebase Authentication processes passwords for email/password accounts; passwords are not saved in your journal records. Google sign-in data is described in section 3.
- Content you enter or upload: trade symbols, dates, prices, position sizes, fees, profit and loss, strategies, journal notes, emotions, ratings, chart screenshots, and prop-firm account details such as balances, targets, and rules. We also store summaries and performance statistics derived from your records.
- Preferences and subscription records: settings such as theme, currency, trading symbols and risk preferences, plus your selected plan, displayed price and currency, activation and expiry dates, cancellation preference, and subscription status. When payment processing is enabled, billing records may also include the payment provider's customer, transaction, and subscription references, payment status, and billing contact information needed to manage your purchase.
- Support and feedback: the title and description of messages or bug reports you submit, your account identifier, submission time, and any information you choose to send by email. Do not send passwords, card numbers, or unnecessary sensitive information.
- Technical and usage information: Firebase Analytics, where supported in the signed-in app, collects interaction and session events, page views, browser/device information, and analytics identifiers. Our hosting, authentication, and other infrastructure providers process request information such as IP addresses, browser details, and timestamps to deliver and secure the service. App error reports include your account ID, error message and stack trace, source file, page path, and time.
Trading records come from information you choose to provide. The current app does not connect to a broker or bank to obtain your trading history or financial credentials.
3. Google sign-in: data accessed and permitted use
Signing in with Google is optional; email/password registration is also available. When you choose Google, Google and Firebase Authentication provide your basic account information: your Google account identifier, name, email address, email-verification information, and profile picture URL, when available. Firebase uses authentication tokens to establish and maintain your signed-in session.
We use your Google account identifier and email to create or recognize your ZenvoJournal account, authenticate you, associate your journal and settings with the correct account, and support account security and service communications. Your name can supply your initial display name; the profile picture URL may remain in your Firebase authentication profile. We do not use these details for advertising or to build a marketing profile.
The current Google sign-in integration requests basic identity, email, and profile information only. It does not request access to Gmail messages, Google Drive files, Google Calendar, contacts, or other Google Workspace content. ZenvoJournal does not receive your Google password.
ZenvoJournal's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. We limit Google user data to providing and improving the account and journal features described here. We do not sell it, use it for personalized advertising, creditworthiness or lending decisions, or use or transfer it to train generalized artificial-intelligence or machine-learning models.
We share Google sign-in information only with providers needed to operate these features, at your direction or with your consent, or as necessary for security or legal obligations. A transfer during a merger or sale of the service would require your prior explicit consent where required by Google's policy. Human access to Google user data is limited to your affirmative permission for specific support needs, necessary security investigations, or legal requirements.
4. How we use information
- Authenticate you, verify account ownership, recover access, and keep each user's records associated with their account.
- Save and sync your journal, screenshots, settings, and prop-firm records; calculate charts, summaries, risk metrics, and trade insights; and provide available exports.
- Manage subscription access and respond to account, privacy, support, and payment-related questions.
- Diagnose errors, understand feature usage, maintain reliability, prevent abuse, and secure the service.
- Meet applicable legal obligations and handle disputes or valid legal requests.
The Insights feature calculates statistics and narrative comparisons in your browser. It does not send your trading records to an AI provider for analysis or model training. We do not sell or rent your personal information, journal content, or Google user data.
5. Storage, service providers, and sharing
We use Google Firebase and Google Cloud to operate the service. Firebase Authentication stores account and sign-in information. Cloud Firestore stores journal records, settings, derived summaries, subscription status, support submissions, and error reports. Cloud Storage for Firebase stores uploaded screenshots. Firebase Hosting and Cloud Functions deliver the website and its backend features. Firebase Analytics uses Google Analytics infrastructure to process usage measurements.
These providers process the information needed for their functions under their applicable service and data-protection terms. See Firebase privacy and security information and Google's Privacy Policy. Loading fonts and software libraries from Google and Cloudflare's cdnjs also sends ordinary web-request metadata, such as your IP address and browser information, to those providers.
Authorized administrators can review account details, subscription status, support submissions, and error reports to administer accounts and resolve issues. Journal content is private to your account under our access rules; it is not published to other users. Access by service personnel is limited to operating the service, support you request, security, or legal needs, with the Google-data restrictions in section 3 applying to Google user data.
We may disclose necessary information at your request or with your consent, to investigate abuse or protect users and the service, or to comply with applicable law or a valid legal request. If the service changes ownership, this policy continues to govern the information, with notice and any required consent before a transfer or change in use. We do not share personal information with advertisers or data brokers.
6. Subscription and payment information
Subscription records are used to manage access to paid features, plan changes, renewals, cancellations, and billing support. The price, currency, subscription period, and applicable billing and renewal conditions are shown before purchase.
When payment processing is enabled, the payment provider identified at checkout will process the payment details you submit under its own privacy policy. ZenvoJournal does not store full card numbers or card security codes. We may receive payment confirmations, transaction and subscription references, and billing contact information needed to reconcile payments, manage subscriptions, and handle billing inquiries or refunds. Payment information is used for these purposes and applicable legal obligations, not for advertising.
We will identify the provider and link its privacy policy before collecting payment details. Do not send card details, wallet credentials, or passwords through support or email. For subscription and payment questions, contact payments@zenvojournal.com.
7. How long we retain information
We retain your account profile, Google sign-in information, journal content, screenshots, settings, and subscription records while your account remains open and the information is needed to provide the service, unless you remove records or request deletion earlier. Signing out, an expired subscription, or disconnecting Google does not automatically delete your ZenvoJournal records.
Support correspondence, bug reports, error reports, and security or administrative audit records are kept for as long as needed to resolve the issue, protect the service, handle disputes, or meet applicable legal obligations. They are held separately from journal records and are reviewed as part of a deletion request. We delete or anonymize personal information when it is no longer needed for these purposes.
Provider-managed analytics, infrastructure logs, and backup copies follow the relevant provider's retention and deletion lifecycle and may remain temporarily after active records are removed. Any records retained for legal or security reasons are limited to that purpose. Information that has been irreversibly anonymized may be kept for service statistics.
8. Your choices, account deletion, and Google access
You can edit or delete available journal records, update supported profile details and settings, and export available trades as CSV from the app. Depending on your location, applicable law may also give you rights to access, correct, delete, or receive a portable copy of personal information, restrict or object to processing, withdraw consent, or complain to your local data-protection authority.
To request account deletion or exercise a privacy right, email support@zenvojournal.com from your registered email address, using the subject "Account and data deletion" for deletion requests. We may ask for reasonable proof of account ownership. Do not send a password or authentication token. We respond within the time required by applicable law.
After verifying a deletion request, we remove your Firebase authentication account, associated journal records and settings, subscription records, uploaded screenshots, and username ownership records from active storage. Separately held support, error, security, and audit records are reviewed for deletion or anonymization, subject to the limited retention reasons in section 7. Deleting your account removes access to the journal; export records you want to keep first.
You can revoke ZenvoJournal's Google connection through your Google Account connections settings. Revocation stops future Google authorization, but does not itself delete information already stored in ZenvoJournal. Email support to request that deletion. Deleting a ZenvoJournal account does not delete your Google Account.
9. Cookies, analytics, and browser storage
Firebase Authentication uses browser storage to maintain your sign-in session. ZenvoJournal also stores session timing and preferences such as your theme locally. The app's sign-in session normally expires 72 hours after your last successful authentication; this session limit does not erase cloud-stored records.
Where supported, Firebase Analytics uses cookies or similar identifiers to measure usage in the signed-in app. This is separate from the performance statistics calculated from trades. We do not intentionally send journal notes, screenshots, or Google profile details as analytics event content, and we do not use Google sign-in data for advertising.
You can clear or block cookies and site storage, or control analytics requests, through your browser's privacy settings and available blocking tools. Clearing or blocking essential storage may sign you out or prevent authentication and saved preferences from working. Clearing browser data does not delete your cloud account; use the deletion process above.
10. Security and international processing
We use HTTPS, Firebase authentication, and per-user Firestore and Storage access rules to help protect account information and journal content. Administrative actions require additional authorization. Google Cloud and Firebase apply their own infrastructure security protections, as described in their privacy and security documentation linked above.
Our providers may process or store information in the United States and other countries outside your country of residence. Data-protection laws may differ. Where applicable law requires international-transfer safeguards, we rely on the relevant provider's data-processing terms and applicable safeguards.
No online service can guarantee complete security. Protect your credentials, sign out on shared devices, and report suspected unauthorized access to support@zenvojournal.com.
11. Children's privacy
ZenvoJournal is intended for people aged 18 and over. We do not knowingly collect personal information from children under 18.
If you believe a child has provided personal information, email support@zenvojournal.com so we can investigate and remove the information where appropriate.
12. Changes to this policy
We will update this page and its revision date when our data practices change. We will notify users of material changes through the service or email. Before using Google user data for a new purpose or requesting additional Google permissions, we will explain the change and obtain any required consent. Questions about this policy can be sent to support@zenvojournal.com.