MOHLIO legal information

1. Scope and current status

These terms govern the personally authorised, free trial of the MOHLIO desktop app and test customer portal. Your contracting party is Laurin-Aaron Evert, trading as DRIMIN Studio's. The public website currently provides information. Visiting it, registering, accepting these trial terms or using a trial code creates neither a paid subscription nor a direct-debit mandate. The prices below describe a planned model; accepting these terms does not make them payable.

These texts reflect development as of 1 October 2026 and have not yet been reviewed by a lawyer. Public sales, automated real-money trading offered as a service and international distribution require separate legal and technical clearance. Selecting a language does not authorise availability in a country.

2. Eligibility and formation

The trial is intended for adults with full legal capacity who may lawfully use their own accounts. Personal access requires express acceptance of the supplied trial terms and activation. The portal additionally requires a valid invitation and confirmation of the invited email address. There is no entitlement to an invitation or extension. Individual agreements and mandatory law take precedence.

3. Services and limitations

Depending on the enabled version, MOHLIO provides account displays, historical analysis, simulations, research views and technical connections to Kraken. The specific version description and displayed operating mode determine the scope. Historical excerpts are not a complete account history; missing data is not replaced with invented results. The new portal's test invoices, payment states and entitlements are simulations and are not payable. Linking the portal does not authorise real-money trading.

A mobile app with independent cloud trading, continuous availability, particular returns and complete automatic synchronisation are not included without express activation. Desktop operation may require a running computer and internet connection. Roadmaps describe plans, not guaranteed delivery dates.

4. Licence and third-party software

During the authorised trial you receive a non-exclusive, personal, non-transferable right to use the software as intended. Codes and accounts may not be sold, shared or used to bypass access controls. Testing the security of other people's accounts or disrupting services is prohibited. Legally permitted backups, interoperability, observation and examination of software remain permitted. Open-source components retain their respective licence terms and rights.

5. Accounts, API keys and your cooperation

Use only accounts you are authorised to operate. Protect devices, passwords and API keys, install required security updates and back up important data. Grant only the API permissions needed for the chosen function; withdrawals and management of withdrawal addresses must remain disabled. Prefer read-only access for analysis alone. Never email us passwords, private API keys or recovery phrases.

If misuse is suspected, revoke the affected keys directly at Kraken and contact us. Independently check the mode, budget, open orders and balance. These responsibilities neither replace our own security and performance obligations nor automatically exclude your statutory claims.

6. Duration, termination and suspension

The invitation or code specifies the trial duration; initial portal trials normally last seven days from activation. You may end participation at any time by notifying keepdrimin@gmail.com. A cancellation offered in the test account records the displayed end date. There is no automatic paid renewal. We may end the trial with reasonable advance notice; specific security risks, unlawful conduct or misuse may justify proportionate immediate suspension. Where practicable, we explain the reason and remedy.

Closing or uninstalling the app, code expiry and account suspension do not cancel or close existing orders or positions at Kraken. Check and manage them directly at the exchange. Statutory rights to obtain data, access and erasure remain unaffected.

7. Changes, faults and statutory rights

Material changes to agreed services or terms are explained before taking effect and expressly agreed where required. Silence is not acceptance. An update must not introduce hidden price changes or retroactive trial charges. Necessary security measures remain possible. Trial status does not exclude statutory rights concerning defects, required updates, termination or privacy. Report faults with the version and a sanitised description; do not include secret keys.

8. Liability

Our liability is governed by applicable law, including liability for intent or gross negligence, culpable harm to life, body or health, an assumed guarantee, fraudulent concealment of defects and mandatory statutory liability. These terms contain neither a blanket release nor a cap at one monthly fee. The trading risks described do not transfer all responsibility for our technical or organisational errors to you. They also do not establish liability merely because markets develop differently from expectations.

9. Law, language and disputes

German law applies. Consumers retain mandatory protections of their habitual residence where required by law. Statutory jurisdiction is not restricted; there is no mandatory private arbitration or blanket waiver of remedies. Translations provide understandable information and must not diminish mandatory rights. You may request clarification before accepting; we do not impose automatic precedence of a language you cannot understand.

We do not voluntarily participate in consumer dispute-resolution proceedings. Any statutory participation and information duties remain unaffected. An invalid provision is replaced by the applicable statutory rule; the rest of the contract continues insofar as legally permissible.

Trading risks: capital and markets

Crypto-assets can fluctuate sharply and rapidly. You may lose all invested capital. Insufficient liquidity, price gaps, spreads, trading fees, slippage, failed or partially filled orders and exchange outages can cause losses. A stop-loss guarantees neither a particular price nor execution. MOHLIO does not remove exchange or issuer risks or promise deposit protection for crypto-assets.

Trading risks: technology and models

Historical results, backtests, simulations, metrics and examples do not predict profits. Models can contain errors and fail to capture changing markets. Network interruptions, stale data, API limits, software faults, security incidents or a switched-off device can interrupt monitoring and execution. Check displays against the exchange's original records. Automation does not remove the need for ongoing supervision.

No individual advice; regulatory boundaries

General software information does not replace investment, legal or tax advice tailored to you. You remain responsible for tax filings; MOHLIO fee calculations are not tax calculations. No regulatory authorisation is claimed here. Whether a function constitutes a regulated financial or crypto-asset service depends on its actual operation and applicable law, not the label “software”. Such functions require prior clearance; in particular, there is no blanket approval to sell in the USA.

Planned fees: evidenced MOHLIO results only

The planned monthly base fee is EUR 19.99 plus a 4.99% performance fee. Nothing is collected during the current trial. Only trades whose MOHLIO instruction, exchange order, actual fills and ledger entries match unambiguously qualify. An editable label or account balance is insufficient. Manual trades, other bots, deposits, withdrawals, pre-existing holdings and unproven income do not generate performance fees. Unsupported or inconsistent data blocks the affected close; missing data is not treated as zero profit.

Net calculation and month boundary

The trial calculation offsets all attributed realised gains and losses, after evidenced trading fees, across the included MOHLIO strategies. Acquisition costs use FIFO and fees are counted once. The base subscription is separate and is not deducted from the performance-fee base. The current technical settlement uses EUR and full calendar months in Europe/Berlin, including daylight-saving changes. A different display currency or IP-derived country does not alter settlement.

Loss carry-forward, open positions and high-water mark

Previously charged profits are not charged again. The trial rule tracks cumulative realised net profit from the start of the attributed ledger and the profit high-water mark already charged. Negative valuations of open MOHLIO positions reduce the base as a loss reserve; positive unrealised gains do not increase it. Valuations require documented month-end prices with sufficient order-book depth and estimated sale costs, not subsequently chosen prices. Missing or inadequate valuations block the close.

The new fee base is the positive remainder, if any, of cumulative net profit plus the negative open-loss reserve minus the previously charged high-water mark. Earlier losses must therefore first be recovered. Subsequent losses do not automatically refund correctly calculated fees for earlier months in this trial model, but delay further performance fees. Corrections and statutory refund rights remain unaffected.

Examples and cent rounding

With no earlier high-water mark or other loss reserve: profit first reaches EUR 100, then falls to EUR 50 by month-end → 4.99% of EUR 50 rounds to EUR 2.50; adding EUR 19.99 gives EUR 22.49. Zero profit or a loss generates no performance fee; the agreed base fee would generally continue in the future paid model.

If EUR 100 was previously charged, then EUR 40 is lost and EUR 60 subsequently gained, only EUR 20 exceeds the earlier high-water mark. The trial calculation rounds the cumulative fee to the nearest cent, with halves rounded up, then subtracts fees already charged. This can produce a separately shown cent adjustment compared with rounding each month independently. Examples are fictitious and do not promise returns.

Statements, collection and disputes

The future model is intended to bill the base subscription and verified performance fee together after month-end. Evidence must separately show the period, fee-policy version, attributed trades, costs, loss carry-forward, position valuations, high-water mark and rounding. Corrections must preserve the earlier statement for traceability. Duplicate billing must be prevented. Questions can be sent to keepdrimin@gmail.com; a short review window must not extinguish statutory objections.

Actual collection requires a separate paid contract, an appropriate payment provider and valid payment authorisation. A Kraken API key is not a debit mandate. MOHLIO is not intended to withdraw its fees using exchange withdrawal permissions. Taxes, binding total prices, payment deadlines, advance notice, partial months and country rules must be fully specified before purchase. No payment provider is claimed to be active here.

Ending the free trial

You may end the free trial at any time without a penalty or trial fee. An unambiguous email to keepdrimin@gmail.com is sufficient. If needed, also delete local data and revoke exchange keys directly at Kraken. Accepting these terms does not waive any statutory right of withdrawal.

Before a future paid contract

The applicable withdrawal information, model form, duration and cancellation rules will be provided on a durable medium before ordering. An ordinary distance software-service contract that carries a right of withdrawal generally has a 14-day period from conclusion; its start, exceptions and consequences depend on legal classification. Regulated financial services may be subject to different rules. Immediate performance and any resulting loss of withdrawal rights must not be concealed in general terms: required declarations must be separate, express and not preselected.

Before relevant online sales, the legally required electronic withdrawal function and, where applicable, cancellation button must be available. They serve different purposes. The current test-account cancellation does not replace those sales requirements.

Notice by email or post

For voluntary trial termination or an applicable withdrawal right, you may write: “I hereby end my free MOHLIO trial / withdraw from my MOHLIO contract. Name: …; account email or contract identifier: …; contract date, if known: …; date: …”. Send it to Laurin-Aaron Evert, DRIMIN Studio's, Amselring 9, 19300 Grabow, Germany, or keepdrimin@gmail.com. This wording is optional and does not replace the complete information required before a future purchase. Do not include credentials.

Privacy: controller and scope

The controller is Laurin-Aaron Evert, DRIMIN Studio's, Amselring 9, 19300 Grabow, Germany; contact: keepdrimin@gmail.com. These notices distinguish the public website, desktop app and test portal. Portal and delivery processing starts only when you use a correspondingly activated service. Browsing the website requires no account. Accepting trial terms is neither blanket privacy consent nor marketing consent.

Website and Cloudflare

Cloudflare Workers Static Assets delivers the information website. Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA, processes connection and security data, particularly IP address, time, requested address and browser information. The basis is GDPR Article 6(1)(f): our legitimate interest in secure delivery and attack detection. Processing outside the EU/EEA is possible. Cloudflare describes processing arrangements, standard contractual clauses and applicable adequacy mechanisms in its Data Processing Addendum.

We maintain no visitor database or separately configured Worker request logs. Infrastructure retention follows the provider's documented security purposes; immediate erasure of all connection data is not promised. Provider information: https://www.cloudflare.com/privacypolicy/ and https://www.cloudflare.com/cloudflare-customer-dpa/.

Test portal, hosting and legal bases

The portal is prepared on a Hetzner server in Helsinki, Finland. The host is Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Once enabled, the portal processes names, email addresses, password hashes, verification status, accepted text version, language and time, sessions, device links, trial contract states and test statements. This supports the requested trial and contract documentation under GDPR Article 6(1)(b). Abuse prevention, access control and necessary evidence rely on Article 6(1)(f). Actual statutory recordkeeping obligations rely on Article 6(1)(c).

The operator records invited addresses as part of requested or agreed trial participation. Hosting and attack prevention may process technical access data; the portal uses hashes rather than directly readable identifiers for repeated-access limits. Information: https://www.hetzner.com/legal/privacy-policy/.

Account messages and Brevo

Brevo is planned for verification and password-link delivery; an account exists, but production sending is still being configured. Sending transfers the recipient address, message content including the time-limited action link, and technical delivery data to Brevo. These messages serve the requested account function, not advertising. GDPR Article 6(1)(b) applies; necessary delivery and abuse records rely on Article 6(1)(f). Templates contain no remotely loaded images or tracking pixels. Provider-wide open and click tracking must be disabled and verified before any external delivery.

The actual Brevo contracting entity, subprocessors, retention settings and transfer mechanisms must be documented from the account contract before activation. External portal sending remains disabled until then. Information: https://www.brevo.com/legal/privacypolicy/ and https://www.brevo.com/legal/termsofuse/. Local development writes messages only to a private test mailbox.

Local app data and exchange connection

The desktop app stores language, appearance, currency, trial licence, acceptance version/hash/language/time, settings, reports and technical logs locally. Credentials use the existing operating-system protection and, where required by the local account service, a local configuration file with restricted access. We do not claim every local file is encrypted. Device access and unprotected backups can expose data.

When you configure a connection, the app communicates with Kraken's API. Depending on permissions, it retrieves balances, orders, fills and ledgers or executes authorised functions. Kraken receives required connection and authentication data and processes exchange data under its own agreement, which acceptance of MOHLIO terms does not replace. Trial codes are checked locally; this integration does not automatically transfer your private exchange keys to the customer portal.

Automatic currency and reference rates

Automatic country detection calls https://api.country.is/, which receives your public IP address; MOHLIO retains only the country code and query time. A non-EUR display queries https://api.frankfurter.dev/ with EUR and the target currency. Both services see connection data but receive no MOHLIO account balances, trades or API keys. Country, currency and reference rates are stored locally. Manual currency selection prevents further automatic country requests; EUR needs no foreign-exchange rate.

Requests support the currency function you choose (GDPR Article 6(1)(b)). VPNs or travel may make IP location inaccurate. Reference rates are estimates, not execution prices. Operator, hosting and transfer details of these public APIs still need verification before broad distribution; exclusively European processing is not promised. Selecting manual EUR display avoids these external requests.

Cookies, storage and tracking

The public page itself sets no cookies or persistent browser identifiers. Animations, help search and the example calculator run locally without transmitting inputs. There are no embedded advertising trackers, external fonts or social-media profiles. Necessary infrastructure protection may still operate.

The activated portal uses essential session and CSRF cookies for login and form protection. Sessions normally expire after eight hours; the CSRF cookie may remain for a year and alone grants no account access. Strictly necessary device access relies on section 25(2)(2) TDDDG; subsequent processing follows the GDPR bases described above. Optional analytics or advertising would require separate information and consent where necessary before introduction.

Support, recipients and international transfers

If you write to us, we process sender details, the message and voluntary attachments to answer: GDPR Article 6(1)(b) for contractual requests, otherwise Article 6(1)(f). The contact mailbox keepdrimin@gmail.com uses Google and may involve international infrastructure. Information: https://policies.google.com/privacy. Provide only necessary, sanitised evidence, never secret keys.

Only authorised operators receive task-necessary access to portal, contract and billing evidence; cockpit access is logged. Data is not sold for advertising. Processors must be engaged under GDPR Article 28. Transfers outside the EEA require compliance with Articles 44 onwards, including applicable adequacy decisions or safeguards such as standard contractual clauses. Evidence for planned portal email remains a prerequisite for activation; blanket consent to unsafe transfers is not requested. You can ask us for information about applicable safeguards.

Retention and erasure

Local app data generally remains on your device until deleted; uninstalling may leave data folders and backups. Stop running services first and retain evidence you need. Portal data is needed only for access, security, unresolved requests or specific recordkeeping obligations. Contract termination and erasure are separate processes. Contact us to request deletion; data required by law or specific legal claims is restricted to that purpose and erased when the period ends.

Verification links expire after 24 hours and password links after one hour. Link expiry does not automatically erase all associated account data. Before external trial users enter the still-disabled portal, an implemented deletion plan, security-log and delivery-record periods and backup expiry must be documented. We do not promise automated deletion schedules that have not been implemented.

Your privacy rights

Subject to legal conditions you may request access, rectification, erasure, restriction and portability (GDPR Articles 15–20). You may object to Article 6(1)(f) processing on grounds relating to your situation (Article 21). Any actual consent can be withdrawn prospectively; earlier lawful processing remains unaffected. Contact keepdrimin@gmail.com. Proportionate identity verification may be needed to prevent unauthorised disclosure; we do not request exchange passwords or API secrets for this.

You may complain to a supervisory authority, particularly where you live or to the Mecklenburg-Vorpommern Commissioner for Data Protection and Freedom of Information: https://www.datenschutz-mv.de/. We answer within statutory periods, normally one month, explaining any legally permitted extension.

Required details and automated decisions

Connection data is necessary to deliver the service. Voluntary trial registration needs email, password and necessary contractual details; without them personal portal access cannot be supplied. Support details and attachments are voluntary but may be necessary to handle a request. The current trial makes no solely automated decision with legal or similarly significant effects under GDPR Article 22. Simulated contract states and fees create no payment obligation. Actual automated trading or payment decisions require separate assessment of effects, legal basis and safeguards before introduction.

Provider information

MOHLIO is a product of DRIMIN Studio's. Provider and controller: Laurin-Aaron Evert, sole proprietor; business address for service: Amselring 9, 19300 Grabow, Germany. Email: keepdrimin@gmail.com. No incorporated company, commercial registration or financial regulatory licence is claimed. The current website does not offer paid contracting. Any issued VAT or business identification numbers and additional contact details required before sale will be added from verified operator information; a private tax number will not be published.