Effective 23 September 2026 · Version 2026-09
Morphiz Voxera ("the Service", "the App") is provided by Morphiz.
Morphiz is the trading name of Arbenit Kryeziu, a sole trader (Einzelunternehmen) registered in Germany.
Morphiz — Arbenit Kryeziu
Gutenbergstraße 73
70197 Stuttgart
Germany
+49 155 10627738
privacy@morphiz.ai
morphiz.ai
In this policy, "Morphiz", "we", "us" and "our" mean Arbenit Kryeziu, trading as Morphiz. We name the registered business because the law requires you to know who is responsible for your data and where to reach them. Morphiz is a trading name, not a separate legal person: the controller is the named individual.
We are established in the European Union. Article 27 GDPR — which obliges controllers outside the EEA to designate a representative in the Union — does not apply to us, and there is no such representative to name.
Our competent supervisory authority is the data protection authority of Baden-Württemberg, the federal state of our registered seat:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
Heilbronner Straße 35, 70191 Stuttgart, Germany
(postal: Postfach 10 29 32, 70025 Stuttgart)
poststelle@lfdi.bwl.de · +49 711 615541-0
The Service is sold to businesses. That gives us two distinct roles, and your rights differ depending on which applies.
We are the controller of the data needed to run your account: the name and email address you register with, your organisation's name, your role, your interface language, and records of your use of the Service.
We are the processor of the working content you put into the Service: report text, transcripts, photographs, project details and your customers' information. Your employer — the organisation whose account you use — is the controller of that content. They decide what is recorded and why. If you are an employee and want that content corrected or deleted, ask your organisation first; we will act on their instruction.
Where we act as processor for a business customer, we do so under a Data Processing Agreement. Business customers can request one at the address above.
| Data | Why |
|---|---|
| Name, email address | To create and identify your account, and to contact you about the Service |
| Password | Stored only as a PBKDF2-HMAC-SHA256 hash (600,000 iterations). We never store or see your password |
| Organisation name, your role, seat membership | To separate your company's data from every other company's, and to control who may do what |
| Interface language | To show the app in the language you chose |
| Date and version of the terms you accepted | Legal record that consent was given |
| Session tokens | To keep you signed in |
| Data | Why |
|---|---|
| Transcripts of what you dictate | To generate the report |
| Report text, section by section, including your edits | It is the document you are creating |
| Photographs you attach, and their captions | They form part of the report |
| Project names, site addresses, client names, reference numbers | To organise reports and to print them on the document |
| Your company's letterhead details — name, address, phone, email, VAT ID, logo | To put your firm's identity on documents you send to your customers |
| Custom report templates | Your own report formats |
Your recording never leaves your device. The App carries a speech recognition model and converts your speech to text on the phone itself. Only the resulting text is sent to us. We never receive the audio.
This is not a setting and it is not best-effort. Our servers refuse to accept a recording: if the App cannot convert your speech to text on your phone, the recording stays on your phone, we tell you so, and you can try again. Nothing is uploaded in the meantime and nothing is uploaded instead.
Because of this, recording is only available in the App. A web browser cannot run the speech model, so the website does not offer recording at all — everything else there works as normal: reading and editing reports, photographs, sharing and exports.
We therefore store no voice recordings, and there is no speech-to-text processor in section 6.
| Data | Why |
|---|---|
| A device identifier generated by the App | So that an upload interrupted by poor signal resumes rather than duplicating. It is not Apple's advertising identifier and is not used to track you |
| IP address, recorded in our audit log alongside significant actions | Security, fraud prevention, and so that an organisation can see who changed what |
| Audit records: who did what, to which record, when | Security and accountability. Business customers rely on this |
| Server logs and error records | To keep the Service running and to diagnose faults |
We want to be specific, because most apps cannot say this:
The App requests exactly three permissions: microphone (to record your report), camera (to photograph the work) and photo library (to attach existing photos). Nothing else.
The Service uses a large language model to turn what you dictated into a structured written report.
What is sent to the model: the transcript of your dictation, the report format, your industry and sub-sector, and basic job context such as the project name and date. What is not sent: your password, your payment details, your photographs, or any of your other reports. Your photographs are never sent to the model — no AI system looks at them.
The model is instructed not to add any quantity, measurement, part number, date, name, location, cost or safety incident that was not present in what you said. The report is a draft. You are responsible for reading it and correcting it before you sign it or send it to a customer. See our Terms of Service.
Our AI provider does not use your content to train its models.
| Purpose | Legal basis |
|---|---|
| Providing the Service under our contract with you or your employer | Article 6(1)(b) — performance of a contract |
| Keeping the Service secure, preventing abuse, maintaining audit records | Article 6(1)(f) — legitimate interests |
| Sending service emails such as password resets and team invitations | Article 6(1)(b) |
| Meeting our legal and accounting obligations | Article 6(1)(c) |
Where we act as processor for a business customer, that customer determines the legal basis for the content they process.
We do not process special categories of personal data (Article 9). The Service deliberately does not offer healthcare or legal-professional report types for this reason.
We use a small number of service providers. Each is bound by contract to process data only on our instructions.
| Provider | What it does | Where |
|---|---|---|
| Render | Hosts the Service, the database, and stored photographs and PDFs | Frankfurt, Germany (EU) |
| Scaleway | Will hold an encrypted second copy of photographs and PDFs, so that a failure at Render cannot lose them. Being introduced; no data has been transferred to it yet | Paris, France (EU) |
| Anthropic | Generates the written report from your transcript | Stored in the United States; processed internationally — see below |
| Resend | Sends service emails: password resets, team invitations | United States |
Where Anthropic processes it. Two different things happen in two different places, and we separate them because the short answer would be misleading:
We could write "the United States" and it would read better. It would not be accurate, and a privacy policy that is easier to read than it is true is worth nothing.
What happens to the text sent to Anthropic. Writing your report is the one step that leaves our own infrastructure, so we state its terms plainly rather than leaving you to ask.
What Anthropic receives is the transcript, the findings from any photographs, and the job context needed to write the report — which can include the name of the person preparing it, the customer's name, the site location and the date. It does not receive your email address, your password, or the identifiers of your account and organisation.
Speech-to-text. Your speech is converted to text on your own device and no provider is involved. There is no fallback: our servers refuse to accept a recording, so no speech-to-text processor is engaged and none appears in this list. See section 3.3.
If we begin selling subscriptions through an online payment provider, that provider will be added to this list before any payment is taken. We do not currently process card details, and card details are never stored by us.
We will update this list before adding a new provider. We do not sell your personal data, and we do not share it for advertising.
Your content is kept for as long as your account exists. We do not delete your reports on a timer. A site report may be the only record of what was found on a job, and deleting it on a schedule you did not agree to would be worse than keeping it.
Specifically:
What deletion means in the backups. When you delete something, it is removed from the live Service straight away, as described above. Backup copies are then swept, and the deleted file is erased from them within 90 days at the latest. We keep that window on purpose: a backup that erased itself the moment the live copy was deleted would be no protection at all against the very thing backups exist for — an accidental or malicious deletion.
Business customers who require a shorter, fixed retention period can request one; the Service supports automatic deletion after a defined age.
Under the GDPR you have the right to access your data, correct it, delete it, restrict or object to its processing, receive it in a portable format, and lodge a complaint with a supervisory authority.
Two of these are built into the App, and are real rather than a request queue:
If you own an organisation that has other members, we will not let you delete it from the App, because doing so would take your colleagues' data with it. Contact us and we will help you transfer ownership or close the organisation properly.
For anything else, write to privacy@morphiz.ai. We respond within 30 days. If we act as processor for your employer, we will forward your request to them.
Your content is stored in the European Union, in Frankfurt, Germany. A second, backup copy in Paris, France is being introduced. Neither location is outside the EEA.
Transfers outside the EEA happen only to our service providers, and we disclose them:
Both are made under the European Commission's Standard Contractual Clauses, together with the supplementary measures those providers publish.
We do not access your content from outside the EEA. Our own support and administration are performed from Germany.
A copy of the relevant safeguards is available on request.
No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to your rights, we will notify the relevant supervisory authority within 72 hours and inform you where required.
The Service is a business tool and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has provided us with personal data, contact us and we will delete it.
We do not sell or share personal information as those terms are defined by the California Consumer Privacy Act, and we have not done so in the preceding twelve months. We do not use personal information for cross-context behavioural advertising.
The categories we collect are set out in section 3: identifiers, customer records, visual information, internet activity limited to security logging, and the professional content you create. We do not collect audio.
California, Colorado, Connecticut, Utah, Virginia and other state residents may request access to, correction of, deletion of, or a portable copy of their personal information, and may appeal a refusal. Write to privacy@morphiz.ai. We will not discriminate against you for exercising these rights.
We will update this policy when the Service changes. Material changes will be notified in the App or by email before they take effect, and the version number at the top will change. Continuing to use the Service after that means you accept the updated policy.
Morphiz — Arbenit Kryeziu
Gutenbergstraße 73, 70197 Stuttgart, Germany
+49 155 10627738 · privacy@morphiz.ai · morphiz.ai
If you are in the EEA and are not satisfied with our response, you may lodge a complaint with your national data protection authority.