Privacy Policy

Last updated: November 4, 2026 · Notice version 2026-11-04.1

Introduction

Welcome to Merak. The Merak app and related services are operated by Merak Intelligence, Inc., a Delaware corporation ("Merak," "we," "our," or "us"). We are committed to protecting your privacy and handling your data in an open and transparent manner. This Privacy Policy explains how we collect, use, store, and protect your information when you use the Merak mobile application and related services.

This notice explains how Merak Intelligence, Inc. handles personal information and the choices available to you. Accepting the Terms, acknowledging this notice and giving permission for a particular use of information are separate. Where a purpose requires your permission, a general statement that you use Merak does not replace that choice.

1. Information We Collect

1.1 Information You Provide

Account Information

When you create an account, we collect:

1.2 Information We Generate

Learning Progress Data

As you use the app, we automatically collect:

Learner-Submitted Text and Support

When you choose a feature that accepts text, we collect the text needed to provide it, including path-chat messages, free-form answers, content reports, and support feedback. Do not include information you do not want processed as part of that request.

Usage Analytics

We collect:

Diagnostics Data

To maintain app quality, we automatically collect:

1.3 Information We Do NOT Collect

1.4 Investor-Room Access

When you sign in to the investor room, we use your assigned username and password to authenticate access and create a short-lived session. We record successful sign-in times and requests for pages or files, including the assigned login, time, requested material without query strings, request method, response status, bytes sent and response duration. We use these records for security, troubleshooting and diligence discussions, not advertising. They do not trigger outreach automatically. A sign-in or request identifies use of an assigned account; it does not verify who personally used it, whether a document was read, or investment interest. Response duration is not reading time.

Our structured access records exclude passwords, session tokens, authorization headers, request bodies, query strings, referrers and IP addresses. Unrecognized routes are grouped rather than recorded verbatim, and rejected requests do not retain the attempted login. The hosting provider may keep separate service and HTTP logs under its settings and terms. Retention follows the applicable hosting configuration and operational or legal requirements. For investor-room privacy requests, email erhan@usemerak.com.

2. How We Use Your Information

2.1 Core Functionality

We use relevant learning records to provide the practice, feedback, progress and review features available to your account. Completion and activity record participation; they do not certify knowledge or skill. Additional adaptive features are planned and would require the notices and choices applicable when they become available.

2.2 Service Improvement

App usage and feedback do not by themselves establish learning effectiveness. A separate teaching-research study would have its own explanation of the purpose, data and applicable choices before it begins. This service-improvement section is not blanket permission for unrelated research, model-provider training or commercial use of private learning history.

2.3 Communication

2.4 We Will Never

3. AI-Generated Content and Learning Models

Learning content in Merak is generated by AI. Artificial-intelligence models turn topics into paths, write the learning material, and evaluate some learner responses. Automated source checks and independent model reviews run before content reaches the app. Routine path production is autonomous, with no human review step. When you use path chat or submit a free-form answer, the text and the minimum curriculum context needed for that request may be sent to Groq, OpenRouter, and a model provider selected through OpenRouter. We exclude direct account identifiers from model input. Text can still contain personal information even when an account identifier is removed. This notice does not by itself grant permission for an AI operation: any required permission is a separate choice and must precede the relevant sharing. It does not authorize optional analytics, separate research or publication of personal information.

How a path is built. A Merak path is not a single prompt to a chatbot. Merak uses its configured retrieval route to gather source material for the topic and records the evidence used for that build; it plans the factual content as a ledger of individual claims; it renders cards and questions against those claims; it re-checks grounded claims against the evidence set; and it submits the finished material to two other model families acting as a review jury, neither of which wrote it. When a check fails during a build, Merak tries to rewrite the specific card, question or claim that failed rather than the whole path. Every build runs inside fixed time, call and cost limits, and what its checks find is recorded.

What that means for your data. The configured retrieval route may use a source corpus or gather evidence just in time for a build. Just-in-time retrieval does not maintain a reusable topic corpus. Merak still retains build records, which can include source URLs, titles, excerpts, content hashes and source-pack records; those retained records are separate from a reusable topic corpus. The search and model requests made during a build are derived from the topic and objectives of the path being generated. For a path you asked for, that includes the topic text you typed. Direct account identifiers are excluded from those requests.

Web search during generation. Whether a build uses web search depends on its configured retrieval route. When web search is used, requests may be sent through OpenRouter to Perplexity or a configured fallback such as Exa; a build can reach both. Those companies receive search queries built from the topic, objectives and specific factual claims being checked. Direct account identifiers are excluded. Merak reaches them through OpenRouter. Search requests carry configured domain exclusions and source-selection instructions; these do not guarantee that every social network, forum or aggregator is excluded. Configured retrieval and retry controls limit this process; a retry or fallback may make additional external calls.

4. Tracking and Advertising

We do not use advertising tracking. Merak does not participate in ad networks, does not use tracking pixels, and does not share data with advertising services. We do not use the Apple Identifier for Advertisers (IDFA) or any cross-app tracking technology.

Our iOS app does not use cookies. Your authentication token is stored securely on your device using the iOS Keychain.

The investor-relations website uses a first-party session cookie to keep you signed in to the private investor room. It is used for authentication, not advertising or cross-site tracking. Signing out ends the server session and clears the cookie; sessions also expire automatically.

Because Merak does not use cross-app advertising tracking, the App Tracking Transparency (ATT) prompt is not required or shown.

5. How We Store and Protect Your Data

5.1 Data Storage

5.2 Security Measures

5.3 Data Retention

6. Data Sharing and Third Parties

6.1 Third-Party Services We Use

6.2 Apple

When you download and use Merak through the Apple App Store, Apple may collect certain data in accordance with their own privacy policy, including app usage data, crash logs, and performance metrics via TestFlight or App Store. This data is governed by Apple's Privacy Policy.

6.3 Legal Disclosure

We may disclose your information if required by law, such as in response to valid legal process, to protect our rights, to prevent fraud, or in connection with a merger or acquisition (users will be notified).

7. Your Rights and Choices

7.1 Access Your Data

Create a portable JSON export from Settings → Export my data when signed in to a permanent account. The app verifies the file's integrity before presenting the iOS share sheet. The export covers Merak's primary account, profile, learning, progress, rewards, reports, support, entitlement, and transaction records. It includes the primary records you provided and account decisions covered by this export, with their recorded reasons. The self-service file does not include reviewer identities or internal notes. Requests for additional personal information are assessed through the support process under applicable law; the limits of the self-service file do not waive your statutory rights. Processor-held diagnostics and analytics require the manual rights process described on Merak Support.

7.2 Correct Your Data

You can update your display name directly in the app. Your username is generated by Merak and cannot be changed. For other corrections, use Merak Support.

7.3 Delete Your Data

Delete your account through the app when signed in: Settings → Delete account and work. Guest journeys can be cleared from this device in Settings. During beta, use the current request instructions on Merak Support for any manual account request.

When the in-app deletion transaction succeeds, Merak removes the authentication account and owner-linked private learning and request records. Successfully published learner-created paths remain public in the shared library without the deleted account as author. The published path may still reflect the topic requested. Merak removes private request text and learner-specific diagnostics from retained generation records while keeping numeric generation cost fields for accounting. Processor logs, legally retained transaction records, and disaster-recovery copies may remain until their applicable retention cycle expires. Use Merak Support if you need a processor-specific rights request or a deletion problem investigated.

7.4 Control Notifications

Manage notification preferences in iOS Settings → Merak → Notifications, or within the app under Settings → Notifications.

8. Children's Privacy

Merak's general eligibility is 13 years or older. We invite adults first; that is the order of our invitations, not a different minimum age. Eligibility does not guarantee an invitation or availability in every country. Applicable age, parental-permission, privacy and safety requirements govern access and particular features; see the Terms. Merak stores the version of the age confirmation and does not ask for a date of birth. If you believe a person under 13 is using Merak, use Merak Support so access and deletion can be investigated.

Product experiments are disabled for the current controlled pilot. If a later release enables experiments, Merak will store stable assignment and actual exposure as separate records and will not place raw prompts, answers, support messages, or direct contact details in experiment context.

9. International Users

Merak is operated by Merak Intelligence, Inc., a Delaware corporation run from Türkiye, and uses providers that may process data in other countries. Where required, international transfers must rely on an applicable legal mechanism rather than consent language alone.

9.1 European Users (GDPR)

If you are located in the European Economic Area (EEA), you have the following rights under the General Data Protection Regulation:

Legal Bases for Processing: Where the GDPR applies, the basis depends on the purpose: steps requested toward a contract and contract performance for the requested service; legitimate interests where permitted for proportionate service improvement and fraud prevention; consent for uses for which that is the applicable basis; and legal obligations for required records and disclosures. A notice acknowledgement is not itself consent. Contact Merak Support for the basis and rights relevant to a particular use of your information.

Data Controller: Merak Intelligence, Inc.

9.2 California Users (CCPA)

California residents can use the access, correction and deletion request process described above. Additional statutory CCPA rights apply where the law covers Merak and the processing concerned. Those rights can include:

To exercise these rights, use the in-app account tools or the current request instructions on Merak Support.

10. Changes to This Policy

We may update this policy. Material changes will receive a new notice version and an appropriate in-app or service notice before they apply. Where consent is the legal basis, a material purpose change requires a new choice rather than assumed acceptance.

11. Contact Us

Privacy: Use Settings → Export my data in the app when signed in. During beta, use the current request instructions on Merak Support for manual privacy requests.

Support and privacy contact: erhan@usemerak.com, or Merak Support. You can email us without signing in.

Response Time: During beta, manual privacy requests are handled through the current support instructions and applicable legal timelines.

Summary (TL;DR)