About the product
Manalyx is a personal asset dashboard for private users that aggregates crypto, stocks, real estate, metals, watches and more into one consistent view – with no recommendations and no forecasts.
Find answers to common questions about Manalyx, security, and features.
Short, factual answers to the questions we are asked most often – about what Manalyx is, how it handles your data, which assets it supports and how the free vs. premium tiers work. The structured FAQ list below is mirrored in the FAQ schema in the page source so search engines can pick it up.
Manalyx is a personal asset dashboard for private users that aggregates crypto, stocks, real estate, metals, watches and more into one consistent view – with no recommendations and no forecasts.
Sensitive fields are encrypted at rest using AES-256-GCM, storage runs on EU infrastructure (Supabase, Frankfurt), and every external integration is read-only by design. Personal and financial data is never sold or shared with third parties.
The free tier is fully usable on its own – not a 14-day trial – and Premium only removes a small set of quotas. You can cancel any time and a 7-day grace period applies before the free limits return.
This FAQ page is the short-answer version of questions we are asked most often. Every entry is reviewed when the underlying behaviour changes — a quota lift, a new bank parser, a security policy update — and obsolete entries are removed rather than rewritten into uselessness. For depth, each topic links to its dedicated page (security, pricing, integrations, individual asset modules), where the same answer is expanded with the architectural reasoning behind it.
A FAQ entry succeeds when it ends a question in two sentences. If a question genuinely needs four paragraphs, the right place is the topic page, and the FAQ entry's job is to point there. Resisting the urge to inflate every answer keeps the page scannable instead of turning it into a wall of text.
The questions on this page are mirrored into FAQPage JSON-LD inside the page source so search engines can render them as rich results. The schema is generated from the same content shown to users — there is no "SEO version" with answers that differ from what you see, which would be both dishonest and a Google policy violation.
Three escape hatches: the relevant module page (e.g. crypto, banking) usually answers narrow technical questions; the security page covers data, encryption and storage in one place; and direct support via email handles anything user-specific. The FAQ does not pretend to be exhaustive on purpose.
Get started for free today. No credit card required.