This is a development environment. For the production version, please visit mindfulflowjournal.com.
Last updated: October 8, 2026
Welcome to MindfulFlow Journal ("we," "our," or "us"). We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our application.
We may collect information about you in a variety of ways. The information we may collect on the Service includes:
Having accurate information about you permits us to provide you with a smooth, efficient, and customized experience. Specifically, we may use information collected about you via the Service to:
We do not sell or rent your personal information. We may share information we have collected about you in certain situations. Your information may be disclosed as follows:
We use cookies and similar tracking technologies to help customize the Service and improve your experience. Most browsers are set to accept cookies by default. Analytics and advertising tracking is described under "Analytics and Advertising" below.
We use cookies for essential functions such as:
Because these cookies are strictly necessary for the operation of the website, they do not require prior consent under GDPR. By using our Service, you agree that we can place these types of cookies on your computer or device.
In your browser. If you allow analytics and advertising cookies in our cookie banner, Google Tag Manager loads Google Analytics 4 (GA4) and the Meta (Facebook/Instagram) Pixel. This is one choice that covers Google and Meta together; you cannot currently allow one and not the other.
From our servers. Our servers also send events directly to Google (GA4 Measurement Protocol) and Meta (Conversions API) when you sign up, start a checkout, or complete a purchase. These events can include:
A hashed identifier is pseudonymous, not anonymous: Google or Meta may be able to match it to data they already hold. These signup, checkout and purchase events are sent whether or not you have allowed analytics and advertising cookies, including after you withdraw that choice.
Signup attribution. If you had allowed analytics and advertising cookies on the device you signed up from, we may also hold browser and campaign identifiers from that device (Meta's _fbp/_fbc values, Google's analytics client and session IDs, and UTM source, medium and campaign values) on our servers. They are added to the signup event only if the browser that completes email verification also has analytics and advertising cookies allowed, and only within 7 days of signup. A Meta click identifier is used only if the ad click was no more than 90 days earlier. This record is deleted when your email is verified, or when our servers confirm a withdrawal you make while signed in. Otherwise it can no longer be used 7 days after signup and is marked to expire then. Expired records are automatically deleted after expiry. Deletion is asynchronous, so it happens some time after expiry rather than at an exact time.
Withdrawing consent. You can withdraw through the cookie banner, from Privacy in the account menu once your email is verified, or on the Withdraw tracking consent page, which also works before verification. This stops browser tracking on that device; if your browser does not let us save the choice, it may apply only to the page you are on. If you are signed in, we also ask our servers to delete any pending signup-attribution record and record the withdrawal against your account, so the attribution record cannot be used even if you verify on another device. From the cookie banner this request is made in the background and may fail without telling you; the Withdraw tracking consent page tells you whether our servers recorded it. The withdrawal record is marked to expire after 7 days; as above, expired records are automatically deleted after expiry, and deletion is asynchronous, so it happens some time after expiry rather than at an exact time. Withdrawing while signed out affects only that browser, and a browser that has never signed in to your account cannot be linked to your withdrawal. Withdrawal does not stop the server events described above, and it cannot recall data already sent to Google or Meta; their own retention and deletion policies apply to it.
The events described in this section do not include your journal entries, mood logs, or AI analysis results.
We use administrative, technical, and physical security measures to help protect your personal information. We leverage secure cloud infrastructure provided by Google Firebase to store your data. While we have taken reasonable steps to secure the personal information you provide to us, please be aware that despite our efforts, no security measures are perfect or impenetrable, and no method of data transmission can be guaranteed against any interception or other type of misuse.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. We use this service to protect against spam and abuse.
You have certain rights regarding your personal information:
We do not knowingly solicit information from or market to children under the age of 13. If you become aware of any data we have collected from children under age 13, please contact us using the contact information provided below.
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. You are advised to review this Privacy Policy periodically for any changes.
If you have questions or comments about this Privacy Policy, please contact us at: support@mindfulflowjournal.com.
We use essential cookies for security (like reCAPTCHA), and — with your permission — analytics cookies to understand how the site is used. You can change your mind any time. See our Privacy Policy.