Privacy Policy
Effective Date: 2nd September 2026
We respect your privacy and are committed to protecting your personal data.
What we collect
We may collect:
- Information you provide. This may include information you voluntarily provide relating to mood, wellbeing, or general lifestyle patterns.
- Account and authentication data
- Technical data (e.g. IP address, browser type)
- Analytics/Usage data (how you interact with the site e.g. pages visited, links clicked, geolocation such as city, town, country)
- Transaction related identifiers, such as invoice numbers, customer IDs and subscription IDs, to manage billing and provide our services. We do not collect or store sensitive billing details. We use a secure third party provider (as detailed below).
How we use your data
We use your data to:
- Provide and improve our service
- Generate your results/report
- Manage accounts and subscriptions
- Monitor and analyse usage
- Improve and develop our service
- Communicate with you (if you contact us)
Legal basis
We process your data based on:
- Your consent (when you submit information or accept cookies or consent banners or consent related tick boxes)
- Performance of a contract (providing a service)
- Legitimate interests (improving and operating the service, maintaining a secure, functional, and optimised website and /or mobile application)
Cross-Device Tracking
We may use aggregated or pseudonymised data to understand general usage patterns across devices and improve the user experience.ours.
Third-Party Processors
We use Supabase to host our database and store user data, including identifiers related to push notifications, subscriptions and billing.
We use Resend to send emails (such as account or service-related communications). By providing your email address, you agree to receive service-related communications.
We use Stripe to process payments securely. Stripe acts as a payment processor on our behalf and handles payment information in accordance with it’s own privacy policy and applicable data protection laws. We do not store full payment card details on our servers. Payment information is processed by our third-party payment provider, Stripe.
We use Paddle to process payments, manage subscriptions, and handle billing securely. Paddle acts as a payment processor on our behalf and handles payment information in accordance with it’s own privacy policy and applicable data protection laws. We do not store full payment card details on our servers. Payment information is processed by our third-party payment provider, Paddle. Paddle may act as the merchant of record for transactions and will process your payment and billing information in accordance with it's own privacy policy.
We use Google Analytics, also known as Firebase Analytics in the mobile application context, and PostHog to analyse usage of our website and mobile application. This helps us understand how users interact with our app and improve functionality, performance and user experience. We may collect information about your interactions with the app, such as events, features used and other usage information.
We use Expo Application Services (EAS) to manage our app.
These providers act as a data processors on our behalf.
Analytics, Performance, and App Infrastructure Disclosure
The data collection and tracking mechanisms depend strictly on the platform you are using and your explicit consent preferences:
1. Website Analytics
- With Consent: If you accept analytics cookies via our website consent banner, we deploy both Google Analytics and PostHog in standard tracking modes. This collects standard usage data (such as page views, clicks, and session duration) utilizing cookies stored on your browser.
- Without Consent: If you reject or ignore the consent banner, Google Analytics is completely blocked. PostHog will run exclusively in a restricted, cookieless mode. In this mode, no tracking cookies are placed, no cross-site profiling occurs, and data is aggregated via a temporary privacy-preserving hash to record basic traffic without identifying you.
- Regardless of Consent: No Individual Profiles: We do not create persistent personal profiles. No Aggressive Tracking: Auto-capture is turned off; we do not log random clicks or raw text inputs. Individual IP addresses are automatically anonymized and/or discarded immediately upon collection, they are used only temporarily for approximate geographic locations (such as town, city, region, and country) and bot detection.
2. Mobile Application Infrastructure and Services
We separate our mobile application services into two distinct categories: Operational Infrastructure and Optional Analytics/Messaging.
- Core Operational Infrastructure (Always Active): To ensure application stability, manage your account data securely (via Supabase), and deliver over-the-air bug fixes and check for updates (via Expo Application Services / EAS), our app utilizes core backend services. These infrastructure services run automatically when you use the app to check for updates or authenticate, and require the collection of basic, non-identifiable technical logs.
- Optional Tracking and Notifications (Consent required): We do not activate behavioural tracking mechanisms or register your device for communication services unless you explicitly opt-in via our app's consent banners. Once consent is given, the mobile SDKs for Google Analytics, PostHog, and Expo Push Notifications are authorized to initialize.
3. Storage of Confidential Journal Entries
As a journaling platform, we understand that the text, notes, and reflections you write ("Journal Entries") are highly personal and confidential. To safeguard this data, our backend infrastructure provider, Supabase, adheres to strict enterprise-grade security standards:
- Data Encryption: All data transmitted between your device and our servers is secured using Transport Layer Security (TLS) encryption. Once stored, your Journal Entries are protected using advanced Advanced Encryption Standard (AES-256) encryption at rest.
- Compliance Standards & Infrastructure: Our database environment is hosted on infrastructure that maintains a verified SOC 2 Type 2 compliance certification. To satisfy strict international data residency regulations, we utilize European server locations to host and process database infrastructure. Furthermore, a formal Data Processing Agreement (DPA) is maintained with Supabase to enforce regulatory compliance.
- Database Infrastructure: Your Journal Entries are uploaded, synced, and stored securely within cloud-hosted databases provided by Supabase. This infrastructure handles data in transit using industry-standard SSL/TLS encryption and stores data at rest using advanced encryption standards.
- Authentication and Access Controls: To ensure total privacy, your Journal Entries can only be accessed through an authenticated account. We require all users to register and validate their email address via Supabase Auth. Upon successful validation and login, the infrastructure issues a secure JSON Web Token (JWT) and an encrypted Refresh Token to your device. These cryptographic tokens act as a digital passport, authenticating your identity for every database interaction and keeping your session secure
- Row-Level Isolation (UUID): Your validated account is assigned a unique, randomized database identifier (UUID). We enforce strict Row-Level Security (RLS) protocols within our Supabase database architecture. This ensures your Journal Entries are physically isolated at the database level and are only readable or mutable by your specific authenticated UUID session.
- Strict Confidentiality: We enforce isolation protocols within our database architecture. We do not employ automated text-scanning, natural language processing, or manual developer auditing to read or index the contents of your journal. Your text is treated as strictly confidential and is accessible only to your authenticated account session or in the case of Administrative database access. Administrative database access is strictly restricted to authorized system personnel for core technical maintenance and system infrastructure management. We maintain a strict internal policy never to inspect, read, or audit your written journal text unless explicitly requested by you to resolve a technical support issue, or where strictly required by applicable law.
- Special Category Data & Explicit Consent: Because journal text is entirely self-authored, your entries may voluntarily include sensitive personal disclosures (such as information regarding your physical health, mental well-being, personal relationships, or philosophical beliefs). In alignment with global data protection frameworks, we obtain your explicit opt-in consent during the account registration process to collect and process your journal entries and wellbeing information to deliver mood reports and dashboards and operate the service. This data is processed through Supabase strictly for the purpose of syncing, securing, and rendering your journal entries across your devices. You may withdraw this consent at any time by requesting the deletion of your account.
4. Mobile-Specific Data Elements Collected and Linked Identities
In addition to standard behavioural events (like button clicks and screen views), our mobile environment collects specific device-level data points. By using our app and providing consent where prompted, you acknowledge the processing and linking of:
- Linked Account & Device Identifiers (Consent required): To target and route notifications directly to you, our application generates an Expo Push Token (ExpoPushToken). This token is stored securely within your user profile in our Supabase database, where it is directly linked to your account indicators, such as your User ID and email address.
- Decoupled Analytics: Please note that while your push token is linked to your account profile, your analytics data collected via Google Analytics and PostHog is strictly pseudonymised. We do not use identity synchronization methods to link your behavioural analytics data back to your personal Supabase account profile or email address.
- Core Infrastructure Data: An anonymous, installation-specific ID generated by Expo EAS, along with your current app version number and operating system variant. This data is used solely to securely stream essential app updates and measure cold-start performance metrics.
- Underlying Mobile Notification Delivery Tokens: The ExpoPushToken maps back to underlying native device tokens generated by Apple Push Notification Service (APNs) for iOS and Firebase Cloud Messaging (FCM) for Android.
- Unique Analytics Identifiers (Consent Required): Mobile-specific advertising and analytics identifiers including the Google Advertising ID (GAID/AAID), Apple Identifier for Advertisers (IDFA) (where system permission is explicitly granted), and Firebase/PostHog unique App-Instance IDs.
- Technical Hardware Specifications: Exact device manufacturer, hardware model, operating system version, screen resolution, system language, and device orientation.
- Network & Connectivity Data: Mobile carrier name, network connection type (e.g., Wi-Fi vs. Cellular 4G/5G), and approximate geographic location derived from your IP address.
- Application Diagnostics & Lifecycle Events: Critical performance metrics such as app installation events, application updates, background/foreground state transitions, app crashes, and screen rendering performance data.
5. Third-Party Data Processing for Notifications & Updates
When we send a push notification, the delivery lifecycle relies on a chain of secure processors:
- Supabase references your account profile, pairs your email/User ID with your stored push token, and triggers the notification payload request.
- The payload and token are sent via API to the Expo Push Service, which processes and acts as an orchestration layer.
- Expo routes the message payload to the native system gateways: Apple Push Notification Service (APNs) for iOS devices, and Firebase Cloud Messaging (FCM) managed by Google for Android devices.
These intermediaries act strictly as data processors on our behalf. Expo briefly stores the push tokens required to target your device and securely flushes the notification payload immediately after it has been successfully handed off to the native Apple or Google systems for final device delivery.
6. Your Controls: Managing Consent, Permissions, and Account Deletion
You maintain full control over your data and how we communicate with you. You can adjust your preferences directly within our ecosystem at any time:
- Revoking Push Notifications: You can opt-out of receiving push notifications by navigating to your device's native system settings (Settings > Notifications > Select our App) and disabling permissions. This will prevent our systems from waking your device or displaying alerts.
- Withdrawing Analytics Consent: If you wish to change your mind regarding behavioural tracking via Google Analytics or PostHog, you can update your consent status at any time. On the website, clear your browser cookies and cache and/or select the “Cookie Preferences” link in the footer of the website. In the mobile app click the link “Analytics Preferences” either at the bottom of the logged out landing page, or on the logged in settings page within your account on our app.
- Account and Data Deletion Requests: In compliance with mobile platform guidelines (Apple App Store & Google Play) and global data privacy regulations (GDPR & CCPA), you have the right to request the permanent erasure of your account and personal data.
- How to Request: You can initiate a deletion request directly within the mobile application by logging into your account, navigating to Settings Screen, Click Delete Account Button at the bottom of the page, or by visiting our website www.humijin.com/contactus, select “Data Deletion Request” as email subject. Alternatively, you can contact us directly via email at info@humijin.com
- Fulfilment Process: Once a deletion request is verified via email, our team will manually purge your record from Supabase within 30 days. This process permanently wipes your core account profile, your email address, your app settings, and removes your linked ExpoPushToken from our active systems.
- Legal Exception for Financial and Transaction Data: Please note that if you have made purchases within our platform, your transaction history, invoicing data, and payment logs managed by our payment processors (Stripe and Paddle) cannot be deleted immediately. In compliance with statutory corporate tax, anti-money laundering (AML), and financial administrative compliance laws in both Europe and California, this transaction data must be securely archived and retained for a mandatory period (typically 6 to 7 years) before it can be permanently purged.
Data storage and international transfers
To operate our global ecosystem, we process data using infrastructure in multiple geographic regions depending on the service provider:
- United Kingdom and European Union: Your core account profile, validated credentials, and confidential journal entries (stored via Supabase) along with your product usage analytics (stored via PostHog) are hosted and processed exclusively on secure servers within the European Union.
- United States and Global Networks: Technical notification routing, transactional email dispatch logging, application update deployment, and payment processing engines (Expo EAS, Resend, Google Analytics, Stripe, and Paddle) utilize secure infrastructure located in the United States.
Where personal information is transferred outside the United Kingdom or the European Economic Area (EEA), we ensure appropriate safeguards are in place in strict accordance with UK and EU data protection laws. This includes enforcing Standard Contractual Clauses (SCCs) approved by the European Commission or relying on the Data Privacy Framework to guarantee an equivalent level of security and data privacy.
Data sharing
We do not sell your data.
We use trusted third party service providers to host and process data on our behalf (as listed above). These providers only process personal data in accordance with our instructions and applicable data protection laws.
Data retention
We keep your data only as long as necessary to provide the service, manage accounts and subscriptions, or comply with legal obligations
Your rights
You have the right to:
- Access your data
- Request correction or deletion
- Withdraw consent or change your preferences.
To exercise these rights see above sectionYour Controls: Managing Consent, Permissions, and Account Deletion or contact us at: info@humijin.com
Children’s Data
This service is not intended for individuals under the age of 18. We do not knowingly collect personal data from children.
Cookies
We may use cookies or similar technologies for analytics and functionality. We use analytics tools such as Google Analytics and PostHog to understand how users interact with our website and mobile application. Where required by law, we will request your consent before placing non-essential cookies (such as analytics cookies).
Google analytics and PostHog collect information on pages visited, time spent on the site, device/browser information. We use this information to improve our website, mobile application and services.
We have enabled IP anonymization where possible to reduce the amount of personal data collected.
Types of Cookies We Use:
- Essential Cookies: These Cookies are necessary for the functionality of the website, and cannot be switched off. They are use for core functionality such as security , authentication, managing your session and enabling features such as secure login areas.
- Analytics Cookies: These Cookies help us gather insights into how users interact with our site, such as which pages are visited most frequently, which buttons are clicked, how long users stay on certain pages, and how visitors navigate through the site. This helps us improve both the functionality and the effectiveness of our content. Where possible, IP addressed are anonymised to reduce identifiability. We only use analytics cookies with your consent. .
- Marketing Cookies: These Cookies are used to track users across websites to display relevant advertising. We only use marketing cookies with your consent.
