Privacy Policy

The controller of the personal data described in this Policy is the developer of Morion, established in the Republic of Lithuania ("Morion", "we", "us"). The legal entity name and registered address will be stated in this section upon registration; until then, the contact details in section 15 apply.

This Policy covers the Application, Morion Cloud, Sync and the Website. It does not cover third-party services that you connect to Morion (for example an AI client or a model provider), which process data under their own terms and policies.

Definitions used below: "Content" means notes, tasks, folders, tags, comments, attachments and workflow definitions you create or import in the Application; "Account Data" means the data described in section 4; "Telemetry" means the usage statistics described in section 5.

The Application stores Content in a single database file on the device on which it is installed. Content is not transmitted to Morion in the ordinary operation of the Application. The Application connects to the network only for the purposes set out in this Policy: sign-in and entitlement verification (section 4), Telemetry (section 5), AI features (section 6), Sync where enabled (section 7), and update checks (section 9).

The Application exposes a Model Context Protocol ("MCP") server on the local device. AI clients that you connect (for example Claude Code, Codex, Cursor, Cline or Zed) communicate with the Application locally. That traffic does not pass through Morion Cloud. Whatever an AI client transmits to its own model provider, including Content that the Application returned in response to the client's tool calls, is processed under the client's and the provider's terms and policies. Tool calls are recorded in a local audit log on your device.

Per-folder and per-note access settings in the Application (visible, create, update, delete) determine which Content is available to AI clients and to the Application's own AI features. Content in folders hidden from AI is not indexed, not searchable by AI clients and not included in any AI request.

Depending on how you use Morion, we process the following categories of personal data:

• Account Data: email address; the name you enter; a salted hash of your password where you set one (never the password itself); the answers you give when setting up the account (personal or team use, your role); trial start date; plan and subscription state as mirrored from Stripe (status, period, dates); a hashed identifier of the device bound to the account; the count of MCP calls in the current month and the AI usage of the account; timestamps of sign-ins and entitlement refreshes; marketing attribution parameters of the link from which you first arrived at the Website, where present.
• Telemetry: usage statistics from the Application and from Morion Cloud’s own records, as described in section 5.
• AI request data: the task-scoped excerpt of Content included in a request to a model provider, as described in section 6. Requests routed through our gateway are counted but their content is not stored by us.
• Sync Data: none today; described in section 7 once Sync is released.
• Website Data: server request metadata processed by our hosting provider and, subject to your consent, aggregate analytics events, as described in section 8.
• Correspondence: messages you send to our support or privacy addresses.

We do not process payment card numbers. Payment details are collected and held by Stripe (section 4).

Account creation. On first launch, the Application sends you to the Website to sign up or log in. The account is created in Morion Cloud once you have confirmed a one-time code sent to your email address; you may set a password, which we store only as a salted hash, or sign in with a code each time. The Application then connects to the account through a short-lived code exchanged between your browser and the Application. Account creation is necessary to provide the trial, the Free plan and any subscription.

Entitlement verification. On launch and periodically while it runs, the Application requests a signed entitlement from Morion Cloud. The request contains the device identifier and a session token. It does not contain Content. The response is cached so that the Application works offline.

Payments. Subscriptions are sold by Stripe, through its Link service ("Link"), acting as merchant of record; payments are processed by Stripe Payments Company or Stripe Technology Europe, Limited. Stripe collects the data required to complete a purchase (email address, billing country and address, payment method, tax information) and issues receipts and invoices. Stripe is an independent controller for that data under its own privacy policy. Stripe transmits subscription events (activation, renewal, cancellation, payment failure) to Morion Cloud so that the plan on your account can be updated.

Account events in usage statistics. Sign-up, the start and end of the trial, subscription changes, connected devices and the days on which the account is active are also recorded as usage statistics under section 5 and follow the same switch.

Emails. We send transactional email only: the one-time code for sign-up and sign-in, a welcome message, a single reminder on the day before the trial ends, and replies to your correspondence. Receipts, invoices, refund notices and renewal reminders for paid subscriptions are sent by Link, not by us. We do not send marketing email without your prior opt-in.

Legal bases. Performance of the contract with you (Article 6(1)(b) GDPR) for account, entitlement and payment processing; compliance with legal obligations (Article 6(1)(c) GDPR) for accounting records.

To see which features are used and where people get stuck, we collect basic usage statistics ("Telemetry"). They record that something happened, never what it contained: for example, that a note was created, not its title or text.

On by default, off at any time. You can switch Telemetry off in the Application (Settings → General → Account → "Help improve Morion") or at morion.ai/account/settings. The setting applies to your whole account; when it is off, nothing described in this section is sent. It does not affect entitlement verification (section 4).

What it includes. Counts and fixed categories only:

• the Application’s version, operating system and the days on which it is used, and the country from which the Application or the Website connects, as determined by our hosting provider at the time of the request;
• which features you use, how often, and when for the first time: notes, tasks, imports, connected AI clients (by type, such as Claude Code or Codex), Mo, Mo Assistant and Auto-code, including the outcome and size of Auto-code runs;
• the steps of the first-run setup you complete or skip, which upgrade prompts you open, and, as counts, which actions were taken by you and which by a connected AI client, Mo or Auto-code;
• account events recorded by Morion Cloud: sign-up (with the campaign parameters of the link you arrived from, where you consented to them on the Website), the trial, subscription changes and connected devices.

What it never includes. Content, note titles, tags, folder or project names, comments or Mo Assistant conversations; your code, repositories, diffs, commits, branch names or merges; what coding agents write, read or say during a run; file names or paths, prompts, model responses or error messages. There are no crash reports and no device identifiers.

Where it goes. Morion Cloud receives it, drops anything outside the fixed list and forwards it to Mixpanel, a product analytics service, under your account identifier, a random value. It sends no name, email address, IP address or any other detail that would let Mixpanel identify who you are; only Morion can link the identifier to your account. The IP address is used only to determine the country and is neither sent to Mixpanel nor stored.

How we use it. To improve Morion: to see which features work, which go unused and where people get stuck, and to decide what to fix or build next. It may also be used to suggest a next step, in the Application or by email; promotional emails are sent only with your separate consent. Legal basis: our legitimate interest (Article 6(1)(f) GDPR), balanced by the exclusion of Content, the pseudonymous identifier and your ability to switch Telemetry off at any time or to object by writing to us (section 13).

The Application includes AI features that call large language models: Mo’s retrieval of context (it reads a ticket or a question, searches your notes and picks the ones that matter), answers and overviews with citations, Mo Assistant (a chat over your Content and tasks), and Auto-code (workflows that run tickets through AI agents). They apply only to folders where AI access is on. We do not build or keep summaries, keywords or other derived indexes of your Content on our infrastructure.

Our gateway. Mo’s retrieval, its answers and Mo Assistant run through a gateway operated by Morion Cloud. For each request the Application sends the gateway the question or ticket and the excerpts of your Content needed for it; the gateway forwards them to OpenRouter under our own account, which routes them to the model providers that generate search queries, score relevance, select notes and write answers. The gateway records the account identifier, the timestamp, the models used and the cost of the request. It does not store the content of requests or responses. OpenRouter and those providers process the forwarded request under their own terms and privacy policies, and some of them, including the relevance-scoring service, may retain request content for a limited period; we have configured our account to disable the use of prompts for provider training where that option is available. Without a network connection, Mo falls back to local search on your device.

Agents you run. Auto-code runs the coding agents and models you choose, on the subscriptions, API keys or model providers you set up for them. The agents send data directly to those providers under your accounts with them; we do not receive or process it. The Mo stages of a workflow go through our gateway as described above.

What an AI request contains. Only the material required for the current task: the question or instruction, the ticket, and the excerpts of related notes, comments and decisions from folders where AI access is on. The Application does not transmit your entire database.

Legal basis: performance of the contract with you (Article 6(1)(b) GDPR) for features you enable. You determine which folders are included.

Sync, a way to synchronise and share folders, is planned but not available, and its technical design is not decided. We do not process Sync Data today. Before Sync is released, this section will describe what data it stores, where, for how long and how it is protected, and we will announce the change as described in section 14.

Hosting. The Website is hosted by Netlify. As part of delivering pages, Netlify processes request metadata (IP address, user agent, requested URL, timestamp) under its own privacy policy. Pages under /auth and /account are served by Morion Cloud on Cloudflare and process the same request metadata together with the session cookie described below.

Analytics, subject to consent. The Website uses Google Analytics 4 to measure aggregate page views and referrers. The analytics script is loaded by Klaro, an open-source consent manager, only after you accept the consent notice. If you decline, no analytics script is loaded and no analytics cookie is set. If you accept, Google sets the _ga cookie family and the Website reports page-view events with IP anonymisation enabled. Google Signals and advertising features are disabled, and the property is not linked to any advertising account. You may change your choice at any time through the "Cookie settings" link in the footer.

Strictly necessary cookies. Klaro stores your consent choice in a first-party cookie named "klaro" for 180 days; it contains no personal identifier. Pages under /auth and /account use a first-party session cookie ("morion_session") to keep you signed in; it is set only when you sign in.

Campaign attribution, subject to consent. If you allow campaign attribution in the consent notice, the Website stores the tracking parameters (utm_*) of the link you arrived from and the path of the page it opened in a first-party cookie named "morion_utm" for 90 days; the first link with tracking parameters is kept. When you sign up or start a checkout on morion.ai, Morion Cloud reads this cookie, together with the Google Analytics client identifier where you accepted analytics, and records them with your sign-up in the usage statistics (section 5) and as metadata of the checkout and subscription at Stripe (sections 4 and 10). Morion Cloud does not keep the cookie itself. If you decline, the cookie is not set; if you withdraw consent, its content is replaced with the word "withdrawn" and is no longer read. Within a visit, the Website also keeps these parameters in your browser's session storage and, where you accepted analytics, adds them to the page events it reports. No profile is built across websites.

The Website contains no other third-party scripts, fonts loaded from third parties, tracking pixels or advertising cookies. Legal bases: consent (Article 6(1)(a) GDPR and the ePrivacy rules) for analytics and campaign attribution; our legitimate interest (Article 6(1)(f) GDPR) in operating and securing the Website for hosting metadata and necessary cookies.

The Application periodically checks a release manifest hosted on GitHub to determine whether a newer version is available and, if you choose to update, downloads the signed installer from the same host. GitHub processes the standard request metadata under its privacy policy. Automatic update checks can be disabled in the Application settings.

The following third parties process personal data on our behalf or receive it as independent controllers:

We do not sell personal data, do not share it with advertising networks or data brokers, and do not use session-replay or fingerprinting tools. We may disclose personal data where required by law, to enforce our Terms, or in connection with a merger, acquisition or sale of assets, in which case this Policy continues to apply.

Our processors operate in the European Union and the United States. Transfers of personal data outside the European Economic Area are made under the European Commission's Standard Contractual Clauses or, for recipients certified under the EU-US Data Privacy Framework, on the basis of that framework. Mixpanel stores our usage statistics on its servers in the European Union; Mixpanel, Inc. is based in the United States and may access them from there, relying on its certification under the EU-US Data Privacy Framework (with its UK and Swiss extensions) and on the Standard Contractual Clauses in its data processing agreement. Model providers you connect yourself may be located anywhere; their transfer safeguards are set out in their own policies.

• Account Data: for the duration of the trial or subscription and for 90 days thereafter, then deleted or anonymised. Accounting records are retained for the period required by law (10 years in Lithuania).
• Telemetry: event records in Mixpanel for no longer than 13 months, then deleted.
• Gateway request logs: 90 days.
• Website analytics: 14 months, as configured in Google Analytics.
• Campaign attribution cookie: 90 days in your browser; the parameters recorded with your sign-up and subscription follow the periods for Telemetry and Account Data above.
• Correspondence: for as long as needed to handle the request and for up to 24 months thereafter.

Subject to applicable law, you have the right to access the personal data we hold about you, to have it corrected or deleted, to receive it in a portable format, to restrict or object to its processing, and to withdraw consent where processing is based on consent. Residents of the European Economic Area, the United Kingdom and Switzerland may lodge a complaint with their supervisory authority; in Lithuania this is the State Data Protection Inspectorate (VDAI). Residents of California and other US states have equivalent rights under their state privacy laws.

To exercise these rights, write to privacy@morion.ai. We respond within 30 days. Because Content that is not synced never leaves your device, requests concerning such Content are satisfied by the export function in the Application.

Security. All transfers to Morion Cloud use HTTPS. Entitlements are signed and verified on the device. Access to production systems is restricted to the persons who operate them. In the event of a personal data breach affecting you, we will notify you and, where required, the supervisory authority without undue delay.

Children. Morion is not directed at persons under 16 years of age, and we do not knowingly process their personal data. If you believe such data has been provided to us, contact us and it will be deleted.

Changes. We may amend this Policy to reflect changes in the product, our processors or the law. The date at the top of the page indicates the current version. Material changes will be announced on the Website and, where we hold your email address, by email before they take effect.

Requests, questions and complaints regarding this Policy: privacy@morion.ai. General support: support@morion.ai.