Trust & Security
The facts you'd check before working with us.
Who you contract with, where your data sits, and what you own when the engagement ends. The answers, stated plainly — so you can verify them before you book a call.
A Swiss company you can verify
Amula AI is the brand of Recica Tech, a Swiss sole proprietorship registered in Wollerau, canton Schwyz — UID CHE-265.201.817, active in the Schwyz commercial register. There is no offshore structure and no intermediary: the entity on your contract is the entity doing the work.
The founder, Rinor Recica, is the named lead on every engagement. If you want to check any of this before a first call, the commercial register entry is public — and so are we: hello@amula.ai, +41 44 505 62 12.
Legal entity
Recica Tech (brand: Amula AI), Swiss sole proprietorship
UID
CHE-265.201.817 — Schwyz commercial register, active
Registered seat
Wollerau SZ, Switzerland
Named lead
Rinor Recica, founder
Your data stays in your tenant — we build inside it
We don't operate a platform you upload your data into. Systems are built in your environment, on the Microsoft stack you already run — Power BI, Excel, SharePoint, Azure. The pipeline lives in your tenant, under your access controls, from the first working session onward.
That answers the data-residency question at the architectural level: your data sits wherever your tenant sits, governed by the agreements you already have with Microsoft. Working with us adds no new hosting relationship and no Amula-side copy of your data.
Our access is access you grant — scoped to the engagement, exercised inside your environment, and revocable by you at any time.
You own the result, documentation included
Every system we build is delivered as something you own outright: the pipeline, the reports, and the documentation that explains how it works. There is no per-fund licence, no platform fee, and no dependency on Amula infrastructure to keep it running.
The handover is designed for a blunt test: if Amula disappeared tomorrow, your reporting would still run next month. The system sits in your tenant, your team holds the access, and the documentation is written so a competent engineer — yours or anyone's — can operate, maintain, and extend it.
How engagements are governed
Every engagement runs on a written agreement between you and Recica Tech. Confidentiality, data processing, and liability are governed contractually per engagement — your legal and compliance teams review a document, not verbal assurances.
Delivery is led by a named senior lead — Rinor Recica — who is your counterpart from the first call to the final handover. You always know who is accountable; it is never a rotating cast.
What we deliberately don't do
In this market, what a partner refuses to do says as much as what it delivers. Four commitments that are structural, not aspirational:
No hosting of your data
The systems we build run in your tenant, not on Amula infrastructure. There is no Amula-hosted store of client data.
No lock-in
No per-fund licence, no proprietary runtime, no standing dependency. When the engagement ends, the system is yours and keeps running without us.
No reselling, no model training on your data
Because we don't host your data, there is nothing on our side to resell, repurpose, or train models on. This isn't a policy we ask you to trust — it's how the architecture works.
No black-box deliverables
Every build is handed over with documentation. We don't keep the keys as a retention strategy — the work has to stand on its own.
Tested where the stakes are real
This operating model isn't theoretical. It's how we delivered reporting automation across 39+ funds for a leading Zurich investment foundation — inside their environment, on their Microsoft stack, documented and handed over.
One engagement is documented in detail in a published case study: around 20 bilingual factsheet funds in German and French, monthly reporting effort reduced from more than 20 hours to 3–4 hours, delivered in roughly two months.
FAQ
Trust & security, answered
- Where does our data actually sit?
- In your Microsoft tenant. We build inside your environment — Power BI, Excel, SharePoint, Azure — so residency follows your tenant configuration and the agreements you already have with Microsoft. Working with Amula adds no new hosting location and no Amula-side copy of your data.
- What happens if you're unavailable — or Amula stops existing?
- The system keeps running. It lives in your tenant, not on our infrastructure, and it is handed over with documentation written so your own team or any competent engineer can operate, maintain, and extend it. Continuity does not depend on us.
- Who owns the code, the pipeline, and the reports?
- You do — outright. Deliverables are documented and handed over as part of the engagement. There is no per-fund licence and no dependency on Amula's infrastructure to keep the system running.
- Who are we actually contracting with?
- Recica Tech, a Swiss sole proprietorship registered in Wollerau SZ — UID CHE-265.201.817, active in the Schwyz commercial register. Amula AI is its brand. Your named counterpart on every engagement is the founder, Rinor Recica.
- How are confidentiality and data processing handled?
- Contractually, per engagement: confidentiality, data-processing terms, and liability are set out in the written engagement agreement, so your legal and compliance teams review a document rather than assurances. Operationally, our access happens inside your environment, under permissions you grant and can revoke.
Checked the facts? Let's talk.
Bring the questions this page didn't answer to a quick chat — Rinor takes those calls personally.