Privacy Policy

Last Updated: April 1, 2026

Effective Date: April 1, 2026

This Privacy Policy ("Policy") is entered into by and between Digital Hubz LLC, operating under the brand name MindPod ("Company," "we," "us," or "our") and the individual accessing or using our services ("User," "you," or "your"). This Policy constitutes a legally binding agreement governing the collection, use, processing, storage, retention, disclosure, and protection of personal data and non-personal information obtained through our website located at mindpod.me, our mobile applications (including the MindPod app available on the Apple App Store and Google Play Store), and all related services, features, content, and applications offered by Digital Hubz LLC under the MindPod brand (collectively, the "Service" or "Platform").

By accessing, browsing, or otherwise using the Service, you acknowledge that you have read, understood, and agree to be bound by this Policy in its entirety. If you do not agree with any provision of this Policy, you must immediately cease all use of the Service and terminate your account. Your continued use of the Service following the posting of any amendments to this Policy shall constitute your acceptance of such amendments.

This Policy should be read in conjunction with our Terms of Service, which govern your use of the Platform. To the extent that any conflict exists between this Policy and the Terms of Service, the more privacy-protective provision shall prevail.

1. Definitions and Interpretation

For the purposes of this Policy, the following terms shall have the meanings ascribed to them below, unless the context clearly requires otherwise:

"Personal Data" means any information relating to an identified or identifiable natural person ("Data Subject"), including but not limited to a name, email address, an identification number, location data, an online identifier, or one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person, as defined under Article 4(1) of the General Data Protection Regulation (EU) 2016/679 ("GDPR").
"Processing" means any operation or set of operations performed on Personal Data, whether or not by automated means, including collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure, or destruction.
"Controller" means the natural or legal person, public authority, agency, or other body which, alone or jointly with others, determines the purposes and means of the Processing of Personal Data. For the purposes of this Policy, MindPod is the Controller.
"Processor" means a natural or legal person, public authority, agency, or other body which processes Personal Data on behalf of the Controller.
"Journal Entry" or "Journal Content" means any text, audio transcription, image-extracted text, or other user-submitted content provided by you through the journaling functionality of the Service, which is subsequently used as input for the generation of personalized podcast episodes.
"Episode" or "Podcast Episode" means the AI-generated audio content produced by the Service based upon your Journal Entries and questionnaire responses.
"Cryptographic Hash" means a one-way mathematical function that converts input data into a fixed-length string of characters, which is computationally infeasible to reverse, thereby rendering the original input unrecoverable from the hash output alone.
"Signed URL" or "Pre-Signed URL" means a time-limited, cryptographically authenticated Uniform Resource Locator that grants temporary access to a specific resource stored in a private cloud storage bucket, the validity of which is mathematically verified upon each request through digital signature verification.
"Sub-Processor" means any third party appointed by MindPod to process Personal Data on its behalf in connection with the provision of the Service.

2. Information We Collect

We collect and process various categories of information in connection with the provision of our Service. The specific types of information collected, the legal bases for such collection, and the purposes thereof are set forth in detail below.

2.1 Information You Provide Directly

Account Registration Information: When you create an account, we collect your email address, which serves as your primary identifier. MindPod utilizes a passwordless authentication system based on one-time passcodes ("OTP"). We do not collect, store, or process any passwords. Authentication is performed via a six-digit numeric code delivered to your registered email address, which expires after a single use or after a predetermined time period, whichever occurs first.
Questionnaire Responses: During the onboarding process, you may complete a comprehensive questionnaire designed to personalize your podcast experience. Your responses to these questions — which may include information regarding your interests, preferences, communication style, and areas of personal focus — are stored in our database and are used by our AI systems to tailor the content, tone, and thematic direction of your generated podcast episodes. Prior to account creation, questionnaire responses may be temporarily stored in your browser's local storage and are subsequently submitted to our servers upon email verification.
Journal Entries (Content Data): You may submit journal entries in the form of typed text, voice recordings (which are transcribed into text), or images (from which text is extracted via optical character recognition). These Journal Entries constitute the primary input data used by our AI-powered pipeline to generate your personalized podcast episodes. Please refer to Section 5 ("Journal Entry Data Protection and Cryptographic Hashing") for a comprehensive explanation of the extraordinary security measures we employ to protect this data, including irreversible cryptographic hashing that renders your journal content inaccessible to MindPod personnel.
Payment Information: All payment transactions are processed exclusively by our third-party payment processor, Paddle (Paddle.com Market Limited). We do not collect, receive, store, process, or have access to your credit card numbers, debit card numbers, bank account details, or any other financial instrument data. We receive from Paddle only the following: (i) a unique customer identifier, (ii) a unique subscription identifier, (iii) transaction confirmation status, (iv) the email address associated with the transaction, and (v) billing period metadata. All payment data is subject to Paddle's own privacy policy and PCI-DSS Level 1 compliance standards.
Communication Data: If you contact our support team, submit feedback, or otherwise communicate with us, we collect the content of such communications, your email address, and any metadata associated therewith, for the purpose of responding to your inquiry, resolving issues, and improving our Service.

2.2 Information Collected Automatically

When you access or use the Service, certain information is collected automatically through automated means, including but not limited to:

Usage Data and Telemetry: Information pertaining to your interactions with the Service, including pages viewed, features accessed, links clicked, the date and time of your visit, the duration of your session, the referring URL, navigation paths within the Service, and aggregate behavioral analytics. This data is collected for the purposes of service improvement, performance optimization, and understanding usage patterns.
Device and Technical Information: Information about the device and software you use to access the Service, including your Internet Protocol (IP) address (which may be anonymized or truncated for analytics purposes), browser type and version, operating system and version, device type and model, screen resolution, language preferences, time zone setting, and unique device identifiers.
Session and Authentication Data: We maintain encrypted session tokens stored in HTTP-only, secure cookies to authenticate your identity across requests. These session tokens are cryptographically generated, contain no personally identifiable information in plaintext, and expire after thirty (30) days of inactivity. A cookie-level cache with a five (5) minute time-to-live is employed to minimize redundant session validation queries.
Log Data: Our servers automatically record information ("Log Data") created by your use of the Service, which may include your IP address, browser type, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, and other diagnostic data. Log data is retained for security monitoring, incident investigation, and service reliability purposes.

2.3 Information from Third-Party Sources

We may receive information about you from third-party sources in connection with the provision of our Service. Specifically, we may receive transaction confirmation data and customer identifiers from our payment processor (Paddle), email delivery status information from our email service provider (Resend), and attribution data from advertising platforms (such as Meta/Facebook) to the extent you arrived at our Service through a paid advertising channel. We process such information in accordance with this Policy and the applicable third party's privacy policies.

3. Legal Bases for Processing (GDPR)

To the extent that the General Data Protection Regulation (EU) 2016/679 ("GDPR") or equivalent data protection legislation applies to the processing of your Personal Data, we rely on the following legal bases:

Performance of a Contract (Article 6(1)(b) GDPR): The processing of your account information, journal entries, questionnaire responses, and the generation of podcast episodes is necessary for the performance of the contract between you and MindPod (i.e., the provision of the Service as described in our Terms of Service). Without such processing, we would be unable to deliver the core functionality of the Platform.
Legitimate Interests (Article 6(1)(f) GDPR): We process certain data (usage analytics, device information, log data) on the basis of our legitimate interests in maintaining the security, integrity, and performance of the Service; preventing fraud and abuse; understanding aggregate usage patterns to improve the Service; and ensuring the stability of our infrastructure. We have conducted a balancing test and determined that such interests are not overridden by your fundamental rights and freedoms.
Consent (Article 6(1)(a) GDPR): Where required by applicable law, we obtain your explicit consent before processing your Personal Data for specific purposes, including but not limited to the sending of marketing communications and the use of non-essential cookies or tracking technologies. You may withdraw your consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal.
Legal Obligation (Article 6(1)(c) GDPR): We may process your Personal Data where necessary to comply with a legal obligation to which we are subject, including tax reporting requirements, anti-money laundering regulations, and responses to lawful requests from public authorities.

4. How We Use Your Information

We use the information we collect for the following purposes, each of which is predicated upon a lawful basis as set forth in Section 3 above:

Service Provision and Core Functionality: To operate, maintain, and deliver the core features of the Service, including the processing of your Journal Entries through our AI-powered pipeline to generate personalized podcast episodes. Your journal content is used as the primary input for our artificial intelligence script generation system, which analyzes the themes, sentiments, and subject matter contained therein to produce a tailored podcast script. The resulting script is subsequently converted into audio via text-to-speech synthesis. This constitutes the fundamental purpose for which your Journal Content is collected.
Personalization and Content Customization: To utilize your questionnaire responses to calibrate the AI models responsible for generating your podcast episodes, thereby ensuring that the tone, style, depth, and thematic focus of your episodes align with your individual preferences and interests.
Account Management and Authentication: To create and maintain your account, verify your identity through email-based one-time passcode authentication, manage your session state, and enforce access controls based on your subscription status and role-based permissions.
Subscription and Billing Administration: To process your subscription through our payment processor (Paddle), manage your episode generation quota, track your billing cycle, and ensure accurate allocation of service entitlements. Episode quotas are determined by the subscription tier you select and are reset upon each billing cycle renewal.
Transactional Communications: To send you service-related communications that are necessary for the operation of your account, including OTP verification codes, subscription confirmations, episode generation status notifications, and account security alerts. These communications are not marketing in nature and cannot be opted out of while maintaining an active account.
Service Improvement and Analytics: To monitor, analyze, and improve the performance, reliability, and user experience of the Service through aggregated and anonymized usage analytics.
Security and Fraud Prevention: To detect, investigate, and prevent fraudulent, unauthorized, or illegal activity, including abuse of the Service, rate limiting enforcement, and the protection of our infrastructure and other users.
Legal Compliance: To comply with applicable laws, regulations, legal processes, and governmental requests.

5. Journal Entry Data Protection and Cryptographic Hashing

MindPod recognizes that your Journal Entries contain deeply personal, sensitive, and private content. We have implemented extraordinary technical and organizational measures to ensure the confidentiality, integrity, and privacy of your journal data that go substantially beyond industry-standard practices. This section describes these measures in detail.

5.1 Cryptographic Hashing of Journal Content

All Journal Entries stored in our database are subjected to irreversible cryptographic hashing. This means that your original journal text is transformed through a one-way cryptographic hash function into a fixed-length, pseudorandom string of characters (a "hash digest"). The fundamental property of a cryptographic hash function is that it is computationally infeasible — both practically and theoretically within current technological constraints — to reconstruct or reverse-engineer the original plaintext content from its hash digest.

As a direct and intentional consequence of this architecture, MindPod personnel — including but not limited to our engineers, administrators, support staff, executives, and any other individuals — do not have access to, and cannot read, view, retrieve, reconstruct, or otherwise obtain the plaintext content of your Journal Entries. The hash digest stored in our database is a cryptographic representation that bears no human-readable resemblance to your original text. Even in the event of a data breach, unauthorized database access, or compelled disclosure, the hashed content cannot be converted back into your original journal entries.

Your journal content is processed in its plaintext form only during the active generation of your podcast episode, within a secure, isolated, and ephemeral processing environment. Once the episode generation pipeline has completed — including AI script generation and text-to-speech audio synthesis — the plaintext content is not retained in the processing environment and only the cryptographic hash persists in our primary database. This ensures that the window during which plaintext data exists in any system is minimized to the absolute operational necessity.

5.2 Purpose Limitation of Journal Data

Your Journal Entries are collected and processed for one, and only one, purpose: the generation of your personalized podcast episodes. Specifically, your journal text is submitted to our AI script generation pipeline, where artificial intelligence models analyze the content to produce a tailored podcast script reflecting the themes, sentiments, insights, and narratives contained in your entry. This script is subsequently converted into audio through text-to-speech synthesis.

We do not use your Journal Entries for any other purpose, including but not limited to: advertising or marketing; sale or licensing to third parties; aggregate data analysis for commercial purposes; training of general-purpose AI models; profiling for purposes unrelated to your podcast generation; or any form of content monetization. Your journal content is yours, and its use is strictly confined to delivering the Service you have requested.

5.3 Encryption in Transit and at Rest

In addition to the cryptographic hashing described above, all data transmitted between your device and our servers is encrypted using Transport Layer Security (TLS) 1.2 or higher, employing AES-256-GCM cipher suites. Data stored at rest in our database is encrypted using the storage-level encryption provided by our infrastructure provider, which employs AES-256 encryption with regularly rotated encryption keys managed through a dedicated key management service (KMS). This means your data benefits from multiple, independent layers of cryptographic protection.

6. Podcast Episode Privacy and Signed URL Technology

Your generated podcast episodes are treated with the same level of privacy and security as your Journal Entries. MindPod has implemented a zero-knowledge audio delivery architecture that ensures your podcast content remains private and inaccessible to unauthorized parties, including MindPod personnel.

6.1 Private Cloud Storage Architecture

All podcast episodes generated for subscribed users are stored in a private cloud storage bucket hosted on Google Cloud Storage ("GCS") infrastructure. The term "private" in this context carries a precise technical meaning: the storage bucket and all objects (audio files) contained therein are configured with access control policies that deny all public access. There is no publicly accessible URL, endpoint, or hyperlink through which any person — including MindPod staff — can directly access, download, stream, or listen to your podcast episodes.

Each episode audio file is stored at a namespaced path unique to your user account (structured as episodes/{userId}/{episodeId}.mp3), ensuring logical isolation of your content from that of other users at the storage layer.

6.2 Cryptographically Signed URLs — How Your Episodes Are Delivered

When you request to play a podcast episode, the Service does not provide you with a direct, permanent link to the audio file. Instead, our server generates a cryptographically signed URL (also known as a "pre-signed URL") at the moment of each individual playback request. This mechanism operates as follows:

Authentication Verification: When you initiate a playback request, our server first verifies your authenticated session and confirms that you are the owner of the requested episode through database-level authorization checks.
Signature Generation: Upon successful authorization, the server uses a private cryptographic key (held exclusively by our server-side service account and never exposed to client-side code or personnel) to generate a digital signature that is mathematically bound to: (a) the specific audio file being requested; (b) a strict expiration timestamp (currently set to sixty (60) minutes from the moment of generation); (c) the permitted HTTP method (GET only); and (d) additional security parameters.
URL Assembly: The digital signature, along with the expiration timestamp and other parameters, is appended to the resource URL as query string parameters, producing a complete signed URL.
Client-Side Delivery: This signed URL is transmitted to your device over an encrypted TLS connection. Your audio player uses this URL to stream the episode directly from the cloud storage provider.
Server-Side Verification: When the cloud storage provider receives the request bearing the signed URL, it independently verifies the digital signature using the corresponding public key, confirms that the expiration timestamp has not elapsed, and validates all other security parameters before serving the audio content. If any parameter is invalid, tampered with, or expired, the request is rejected with an HTTP 403 Forbidden response.
Automatic Expiration: After the sixty (60) minute expiration window elapses, the signed URL becomes permanently invalid. Any subsequent playback request requires the generation of a new signed URL through the same authenticated process. This means that even if a signed URL were intercepted or shared, it would cease to function within the expiration window.

6.3 Zero Persistent Access — MindPod Cannot Listen to Your Episodes

As a direct consequence of the private storage and signed URL architecture described above, MindPod personnel do not have routine, standing, or persistent access to your podcast episode audio files. The private cryptographic key used to generate signed URLs is held by an automated service account and is invoked programmatically only in response to authenticated user requests. There is no administrative interface, dashboard, or internal tool through which MindPod employees can browse, play, download, or otherwise access your episode audio content.

Access to the underlying cloud storage infrastructure is restricted through Identity and Access Management (IAM) policies that enforce the principle of least privilege. The service account credentials are stored as encrypted environment variables and are accessible only to the production server runtime — not to individual personnel.

7. How We Share Your Information

We do not sell, rent, lease, trade, or otherwise commercially transfer your Personal Data to any third party. We may disclose or share your information only in the following narrowly defined circumstances:

Sub-Processors and Service Providers: We engage a limited number of carefully vetted third-party service providers ("Sub-Processors") who process data on our behalf in connection with the operation of the Service. Each Sub-Processor is contractually bound by data processing agreements that impose obligations of confidentiality, data security, and purpose limitation. Our current Sub-Processors are enumerated in Section 10 of this Policy.
AI Processing for Episode Generation: Your Journal Content is submitted to third-party AI model providers (specifically, OpenAI for script generation and Google for text-to-speech synthesis) for the sole purpose of generating your podcast episodes. This processing occurs through API calls to these providers' services. We have reviewed the data processing terms of each provider and confirmed that content submitted through their APIs is not used for the training of their general-purpose models. This processing is performed on a transient basis — your content is submitted, processed, and the output returned, without persistent storage by the AI providers.
Legal Requirements and Lawful Requests: We may disclose your information if we are compelled to do so by applicable law, regulation, legal process, or governmental request, including but not limited to subpoenas, court orders, or requests from law enforcement authorities. In such cases, we will endeavor to provide you with prior notice of the disclosure to the extent permitted by law. Notwithstanding the foregoing, please note that due to the cryptographic hashing of Journal Entries described in Section 5, any compelled disclosure of journal data would yield only irreversible hash digests, not readable content.
Protection of Rights and Safety: We may disclose information where we believe in good faith that such disclosure is necessary to: (a) protect the rights, property, or safety of MindPod, our users, or the public; (b) prevent or investigate possible wrongdoing in connection with the Service; (c) enforce our Terms of Service; or (d) protect against legal liability.
Business Transfers: In the event that MindPod undergoes a merger, acquisition, reorganization, dissolution, sale of assets, or similar corporate transaction, your Personal Data may be transferred to the acquiring or successor entity. In such event, we will ensure that the transferee is bound by privacy obligations no less protective than those set forth in this Policy, and we will notify you of such transfer in advance to the extent practicable.
With Your Consent: We may share your information with third parties when you have provided your explicit, informed consent to such sharing.

8. Data Security Measures

We implement and maintain comprehensive technical and organizational security measures designed to protect your Personal Data against unauthorized access, alteration, disclosure, or destruction. These measures include, but are not limited to:

Transport Encryption: All data transmitted between your device and our servers is encrypted using Transport Layer Security (TLS) 1.2 or higher with industry-standard cipher suites, ensuring confidentiality and integrity in transit.
Encryption at Rest: All data stored in our databases and cloud storage systems is encrypted at rest using AES-256 encryption with key management provided by the underlying infrastructure provider.
Cryptographic Hashing of Sensitive Content: As described in Section 5, Journal Entries are subjected to irreversible cryptographic hashing, rendering them unreadable to any party, including MindPod.
Signed URL Audio Delivery: As described in Section 6, podcast episodes are delivered through time-limited, cryptographically signed URLs, preventing persistent or unauthorized access.
Access Control and Least Privilege: Access to production systems, databases, and cloud storage is restricted through role-based access control (RBAC) and Identity and Access Management (IAM) policies, enforcing the principle of least privilege. No individual employee has unrestricted access to user data.
Session Security: User sessions are managed through cryptographically generated session tokens stored in HTTP-only, Secure, SameSite cookies, which are resistant to cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks.
Rate Limiting: We employ server-side rate limiting using sliding window algorithms to prevent brute-force attacks, credential stuffing, and denial-of-service abuse against our authentication and API endpoints.
Webhook Verification: All incoming webhook payloads from third-party services (including payment provider notifications) are verified using HMAC-SHA256 digital signatures with timing-safe comparison functions, preventing forged or tampered webhook payloads from being processed.
Infrastructure Isolation: Our services are deployed on isolated infrastructure with network-level segmentation. Database credentials, API keys, and cryptographic secrets are stored as encrypted environment variables, never hardcoded in source code or committed to version control.
Secure Development Practices: Our engineering team follows secure development lifecycle practices including code review, dependency vulnerability scanning, and adherence to OWASP Top 10 mitigation guidelines.

Notwithstanding the foregoing, no system of electronic data transmission or storage is entirely impervious to all potential security threats. While we employ commercially reasonable and industry-standard measures to protect your Personal Data, we cannot provide an absolute guarantee of security. In the unlikely event of a security breach affecting your Personal Data, we will notify you and the relevant supervisory authorities in accordance with applicable data breach notification laws.

9. Cookies, Tracking Technologies, and Advertising

9.1 Essential Cookies

We use strictly necessary cookies that are essential for the operation of the Service. These include session authentication cookies (containing encrypted session tokens) and security cookies required for CSRF protection. These cookies cannot be disabled without rendering the Service inoperable.

9.2 Analytics and Performance Cookies

We may use analytics cookies to collect aggregated, anonymized information about how users interact with the Service. This data is used solely for the purpose of understanding usage patterns and improving the Service. We do not use analytics cookies to identify individual users or to build behavioral profiles for advertising purposes.

9.3 Advertising and Attribution Technologies

If you arrive at our Service through a paid advertising channel (such as a Meta/Facebook advertisement), we may collect and process advertising attribution identifiers — including click identifiers (e.g., fbclid) and browser-generated identifiers (e.g., _fbc, _fbp cookies) — for the purpose of measuring the effectiveness of our advertising campaigns and attributing conversions. This information is transmitted to the advertising platform through server-side Conversions API (CAPI) integration.

We transmit the following categories of data to Meta (Facebook) through the Conversions API for attribution purposes: hashed email address, hashed first name (if provided), click identifier, browser identifier, IP address, and user agent string. Meta's Conversions API processes this data in accordance with Meta's Data Processing Terms. You may opt out of personalized advertising through your advertising platform account settings.

9.4 Cookie Management

You may control and manage cookies through your browser settings. Most browsers allow you to refuse all cookies or to indicate when a cookie is being sent. However, if you disable essential cookies, you may be unable to access certain features of the Service or maintain an authenticated session.

10. Third-Party Sub-Processors

In connection with the provision of the Service, we engage the following categories of third-party Sub-Processors, each of which is contractually bound by data processing agreements:

Paddle (Paddle.com Market Limited): Payment processing and subscription management. Paddle acts as the Merchant of Record for all transactions and is PCI-DSS Level 1 compliant. Paddle's privacy policy is available at paddle.com/legal/privacy.
Google Cloud Platform (Google LLC): Cloud infrastructure, private object storage (Google Cloud Storage) for encrypted podcast episode audio files, and text-to-speech synthesis services. Google's Cloud Data Processing Addendum applies.
OpenAI (OpenAI, L.L.C.): Artificial intelligence model API services used for the generation of podcast scripts from journal content and for text extraction from images. Content submitted through OpenAI's API is governed by OpenAI's API Data Usage Policy, which provides that API inputs and outputs are not used to train their models.
Railway (Railway Corp.): Application hosting and deployment infrastructure for our server-side services.
Resend (Resend, Inc.): Transactional email delivery services for authentication one-time passcodes, account notifications, and service communications.
Meta Platforms (Meta Platforms, Inc.): Advertising attribution and conversion tracking through the Conversions API (CAPI), limited to hashed identifiers and attribution parameters.

We conduct due diligence on all Sub-Processors and require them to implement appropriate technical and organizational measures to protect your Personal Data. We maintain an up-to-date list of Sub-Processors and will notify users of any material changes to this list.

11. Data Retention

We retain your Personal Data only for as long as is necessary to fulfill the purposes for which it was collected, as described in this Policy, or as required by applicable law. The specific retention periods applicable to each category of data are as follows:

Account Information: Retained for the duration of your account's existence. Upon account deletion, your account information is permanently erased from our production database within thirty (30) days, subject to any legal retention obligations.
Journal Entry Hashes: The cryptographic hashes of your Journal Entries are retained for the duration of your account. Upon account deletion, all hash records are permanently deleted. As these are irreversible hashes, no readable content exists to be retained.
Podcast Episode Audio Files: Your episode audio files are stored in private cloud storage for the duration of your account. Upon account deletion, all audio files associated with your account are permanently deleted from cloud storage.
Questionnaire Responses: Retained for the duration of your account to enable ongoing personalization of your podcast episodes.
Session Data: Session tokens expire after thirty (30) days of inactivity and are automatically purged from our database.
Payment Transaction Records: Retained for a minimum of seven (7) years in accordance with applicable tax and financial record-keeping requirements.
Log Data: Server logs are retained for a maximum of ninety (90) days for security monitoring and incident investigation purposes, after which they are automatically purged.
Advertising Attribution Data: Click identifiers and attribution parameters are retained for a maximum of ninety (90) days.

12. Your Rights as a Data Subject

Depending on your jurisdiction, you may be entitled to the following rights with respect to your Personal Data. We will respond to any valid request within the time period required by applicable law (typically thirty (30) days for GDPR requests and forty-five (45) days for CCPA requests).

Right of Access (GDPR Art. 15 / CCPA § 1798.100): You have the right to request confirmation as to whether we are processing your Personal Data, and if so, to obtain access to such data along with information regarding the purposes of processing, the categories of data processed, the recipients or categories of recipients, and the retention periods. You may access your Journal Entries (in hashed form), questionnaire responses, and generated podcast episodes through your account at any time.
Right to Rectification (GDPR Art. 16): You have the right to obtain the correction of inaccurate Personal Data and the completion of incomplete Personal Data. You may update your account information directly through the Service settings.
Right to Erasure / Right to be Forgotten (GDPR Art. 17 / CCPA § 1798.105): You have the right to request the deletion of your Personal Data. Upon receipt of a valid erasure request, we will permanently delete your account, all Journal Entry hashes, all podcast episode audio files from private cloud storage, your questionnaire responses, and all other Personal Data associated with your account, subject to any overriding legal retention obligations. You may initiate account deletion through your account settings or by contacting us at the address provided in Section 18.
Right to Restriction of Processing (GDPR Art. 18): You have the right to request the restriction of processing of your Personal Data in certain circumstances, including where you contest the accuracy of the data or where the processing is unlawful.
Right to Data Portability (GDPR Art. 20): You have the right to receive your Personal Data in a structured, commonly used, and machine-readable format, and to transmit that data to another controller. You may export your journal entries and podcast episodes through the Service.
Right to Object (GDPR Art. 21): You have the right to object to the processing of your Personal Data on grounds relating to your particular situation, where such processing is based on our legitimate interests. Upon receipt of such objection, we will cease processing unless we can demonstrate compelling legitimate grounds that override your interests.
Right to Withdraw Consent (GDPR Art. 7(3)): Where processing is based on your consent, you have the right to withdraw that consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal.
Right Not to be Subject to Automated Decision-Making (GDPR Art. 22): You have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning you or similarly significantly affects you. The AI processing used in our Service (podcast generation) does not produce legal effects or similarly significant impacts on you; rather, it generates personalized creative content at your request.
Right to Non-Discrimination (CCPA § 1798.125): We will not discriminate against you for exercising any of your privacy rights, including by denying goods or services, charging different prices, providing a different level of service, or suggesting that you will receive a different level of quality.

To exercise any of these rights, please contact us using the information provided in Section 18. We may require verification of your identity before processing your request, which will typically involve confirming your email address through our OTP authentication system.

13. California Privacy Rights (CCPA/CPRA)

If you are a resident of the State of California, the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020 (collectively, "CCPA") provides you with specific rights regarding your Personal Information (as defined under the CCPA).

Right to Know: You have the right to request that we disclose the categories and specific pieces of Personal Information we have collected about you, the categories of sources from which such information was collected, the business or commercial purpose for collecting the information, and the categories of third parties with whom we share the information.
Right to Delete: You have the right to request the deletion of your Personal Information, subject to certain exceptions provided under the CCPA.
Right to Correct: You have the right to request the correction of inaccurate Personal Information.
Right to Opt-Out of Sale or Sharing: We do not sell or share (as those terms are defined under the CCPA) your Personal Information. Accordingly, there is no need to opt out.
Right to Limit Use of Sensitive Personal Information: To the extent that any information we collect constitutes "sensitive personal information" under the CCPA, we use such information only for the purposes expressly permitted under the CCPA and its implementing regulations.

In the preceding twelve (12) months, we have collected the following categories of Personal Information as defined under the CCPA: identifiers (email address), internet or electronic network activity information (usage data, log data), and other information that you voluntarily provide (journal entries, questionnaire responses). We have not sold or shared any Personal Information, and we have not used or disclosed sensitive personal information for purposes other than those permitted under the CCPA.

14. European Economic Area, United Kingdom, and Swiss Data Subjects (GDPR/UK GDPR)

If you are located in the European Economic Area ("EEA"), the United Kingdom ("UK"), or Switzerland, you have rights under the General Data Protection Regulation (EU) 2016/679 ("GDPR"), the UK General Data Protection Regulation (as incorporated into UK law by the Data Protection Act 2018), and the Swiss Federal Act on Data Protection ("FADP"), respectively. The rights enumerated in Section 12 apply to you in full.

14.1 International Data Transfers

Your Personal Data may be transferred to, and processed in, countries outside of the EEA, UK, or Switzerland, including the United States of America, where our servers and Sub-Processors are located. These countries may not provide the same level of data protection as your home jurisdiction. Where such transfers occur, we ensure that appropriate safeguards are in place, including:

Standard Contractual Clauses (SCCs): We rely on the European Commission's Standard Contractual Clauses (or UK International Data Transfer Addendum, as applicable) as the primary transfer mechanism for Personal Data transferred outside the EEA/UK.
Adequacy Decisions: Where available, we rely on adequacy decisions issued by the European Commission or the UK Secretary of State recognizing that the recipient country provides an adequate level of data protection.
Supplementary Measures: We implement supplementary technical measures (including encryption in transit and at rest, cryptographic hashing, and access controls) to ensure that your Personal Data is afforded an essentially equivalent level of protection regardless of where it is processed.

14.2 Supervisory Authority

If you are located in the EEA or UK, you have the right to lodge a complaint with your local data protection supervisory authority if you believe that our processing of your Personal Data violates applicable data protection law. We would, however, appreciate the opportunity to address your concerns before you approach the supervisory authority, and we invite you to contact us first using the information in Section 18.

15. Children's Privacy

The Service is not directed to, and is not intended for use by, individuals under the age of eighteen (18) years (or such higher age as may be required by applicable law in your jurisdiction). We do not knowingly collect, solicit, or process Personal Data from children under the age of eighteen (18). If we become aware that we have inadvertently collected Personal Data from a child under the applicable minimum age, we will take prompt steps to delete such information from our systems.

If you are a parent or guardian and you believe that your child has provided Personal Data to us without your consent, please contact us immediately at the address provided in Section 18. In compliance with the Children's Online Privacy Protection Act ("COPPA"), we will delete any such information upon verification.

16. Data Breach Notification

In the event of a Personal Data breach that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within seventy-two (72) hours of becoming aware of the breach, in accordance with Article 33 of the GDPR.

Where the breach is likely to result in a high risk to your rights and freedoms, we will communicate the breach to you without undue delay, in accordance with Article 34 of the GDPR, providing you with information regarding the nature of the breach, the likely consequences, the measures taken or proposed to address the breach, and recommendations for steps you can take to mitigate potential adverse effects.

It is important to note that, due to the cryptographic hashing of Journal Entries and the private signed-URL architecture for podcast episodes, even in the unlikely event of a database breach, an attacker would not be able to reconstruct the content of your Journal Entries (which are stored only as irreversible cryptographic hashes) or access your podcast episode audio files (which are stored in a separate, private cloud storage system accessible only through time-limited, cryptographically signed URLs).

17. Changes to This Privacy Policy

We reserve the right to modify, amend, or update this Privacy Policy at any time and for any reason, at our sole discretion. Any changes to this Policy will be effective immediately upon posting of the revised Policy on this page, with an updated "Last Updated" date. We will make reasonable efforts to notify you of material changes to this Policy by email (sent to the email address associated with your account) or through a prominent notice on the Service at least thirty (30) days prior to the change becoming effective.

Your continued use of the Service following the posting of any amended version of this Policy constitutes your acknowledgment and acceptance of such amendments. If you do not agree to any modified version of this Policy, you must discontinue use of the Service and delete your account.

We encourage you to periodically review this Policy for the latest information on our privacy practices. Prior versions of this Policy are available upon request.

18. Contact Information

If you have any questions, concerns, complaints, or requests regarding this Privacy Policy, the processing of your Personal Data, or if you wish to exercise any of your rights as a Data Subject, please contact us through the following channels:

General Privacy Inquiries:
Email: [email protected]

Data Subject Access Requests and Erasure Requests:
Email: [email protected]

Data Protection Officer:
Email: [email protected]

We will acknowledge receipt of your request within five (5) business days and will respond substantively within the time period required by applicable law (typically thirty (30) days for GDPR requests, forty-five (45) days for CCPA requests, extendable by an additional period where necessary due to the complexity or volume of requests).

19. Governing Law and Dispute Resolution

This Privacy Policy shall be governed by and construed in accordance with the laws of the State in which Digital Hubz LLC is registered, without regard to its conflict of law provisions. To the extent permitted by applicable law, any disputes arising out of or in connection with this Policy shall be resolved through good faith negotiation between the parties. If such negotiation fails to resolve the dispute within thirty (30) days, the dispute shall be submitted to binding arbitration in accordance with the rules of the applicable arbitration authority.

Nothing in this section shall limit your right to lodge a complaint with a supervisory authority or to seek judicial remedies as provided under applicable data protection law, including the GDPR and CCPA.

20. Severability

If any provision of this Privacy Policy is found to be invalid, illegal, or unenforceable by a court of competent jurisdiction, such invalidity, illegality, or unenforceability shall not affect the remaining provisions of this Policy, which shall continue in full force and effect. The invalid, illegal, or unenforceable provision shall be deemed modified to the minimum extent necessary to make it valid, legal, and enforceable while preserving the original intent of the parties.

21. Entire Agreement

This Privacy Policy, together with our Terms of Service, constitutes the entire agreement between you and Digital Hubz LLC (operating as MindPod) with respect to the subject matter hereof and supersedes all prior or contemporaneous communications, representations, or agreements, whether oral or written, with respect to your privacy and the handling of your Personal Data in connection with the Service.