Legal Notice and Trust Information

This page brings together the company information required by the Law of the Republic of Lithuania on Information Society Services and Regulation (EU) 2022/2065 (Part A), our subprocessor list and data-location, international-access and switching information (Part B), the AI Transparency Notice under Regulation (EU) 2024/1689 (Part C) and the Recording and Participant Notice Guidelines (Part D).

Part A — Company Information (Legal Notice)

1. Service Provider

Such Much Voice (https://suchmuch.ai/ and related domains, and the application at https://suchmuch.ai/app) is operated by:

UAB Such Much AI is the principal operating company of the Such Much AI brand. SIA “Such Much AI” (registration number 40203701469, Ropažu iela 7–8, Rīga, Latvia) and Such Much AI, Inc. (Delaware, United States) are affiliated companies that do not operate Such Much Voice and are not parties to contracts for it.

2. Supervisory and Regulatory Authorities

• Information society services and Digital Services Coordinator under Regulation (EU) 2022/2065: Communications Regulatory Authority of the Republic of Lithuania (Lietuvos Respublikos ryšių reguliavimo tarnyba, RRT), Mortos g. 14, LT-03219 Vilnius, www.rrt.lt.
• Data protection: State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija, VDAI), L. Sapiegos g. 17, LT-10312 Vilnius, vdai.lrv.lt.
• Consumer protection: State Consumer Rights Protection Authority (Valstybinė vartotojų teisių apsaugos tarnyba, VVTAT), Vilniaus g. 25, LT-01402 Vilnius, www.vvtat.lt.
• Taxation: State Tax Inspectorate under the Ministry of Finance (Valstybinė mokesčių inspekcija), Vasario 16-osios g. 14, LT-01514 Vilnius.
• Artificial intelligence: the national market-surveillance authority designated by the Republic of Lithuania under Regulation (EU) 2024/1689; we will name it here once the designation is in force.

The Services do not require a specific authorization and are not a regulated profession.

3. Points of Contact

• General, legal and privacy enquiries: info@suchmuchai.com
• Reports of illegal content, abuse or security vulnerabilities: info@suchmuchai.com (subject “Abuse Report” or “Security Report”)
• Single point of contact for authorities and recipients under Regulation (EU) 2022/2065: info@suchmuchai.com, in English or Lithuanian
• Postal notices: UAB Such Much AI, Bukčių g. 6-38, Vilnius, LT-04127, Lithuania

4. Out-of-Court Dispute Resolution for Consumers

The Services are intended for business and public-sector use. If a consumer nevertheless uses them, disputes may be referred to the State Consumer Rights Protection Authority (www.vvtat.lt) under the Law of the Republic of Lithuania on Consumer Protection. The European Commission’s online dispute resolution platform was discontinued in July 2025 and is no longer available.

5. Intellectual Property

The Such Much Voice and Such Much AI names, logos and the content, design and software of the websites and application are protected by copyright, trademark and other intellectual-property rights of UAB Such Much AI or its licensors. Microsoft, Azure and other product names are trademarks of their respective owners and are used for identification only.

6. Liability for Content and Links

We take care to keep the information on our websites accurate and current but give no guarantee as to its completeness or accuracy. Links to third-party websites are provided for information only; we have no control over their content and accept no responsibility for it. Allegedly illegal content can be reported to the address in Section 3 and will be handled in accordance with the Terms of Service and Regulation (EU) 2022/2065.

7. Governing Documents

Use of the Services is governed by the Terms of Service (suchmuch.ai/terms), including Annex 1 (Data Processing Agreement) and Annex 2 (Acceptable Use Policy); the Privacy Policy (suchmuch.ai/privacy), including its cookie section; and this Legal Notice and Trust Information page (suchmuch.ai/legal), including the AI Transparency Notice (Part C) and the Recording and Participant Notice Guidelines (Part D).

Part B — Subprocessors, Data Location, International Access and Switching

This Part serves four purposes: it is the subprocessor list referred to in the Data Processing Agreement (Annex 1 to the Terms of Service); it states the jurisdictions in which the ICT infrastructure used for Such Much Voice is located and the measures taken to prevent unlawful third-country government access, as required by Article 28 of Regulation (EU) 2023/2854 (the “Data Act”); it is our online register of data structures, formats and switching procedures under Article 26 of the Data Act; and it supports the transfer transparency required by Chapter V of the GDPR.

1. Where Customer Data Is Stored and Processed

All Customer Data (recordings, transcripts, summaries, files, settings and metadata) is stored and processed in Microsoft Azure data-center regions located in the European Union. The ICT infrastructure is therefore subject to the jurisdiction of the EU Member States listed below.

We will not move Customer Data outside the European Union, and will not add a non-EU region, without the prior written agreement of affected customers.

2. Subprocessors for Customer Data

The entities below process Customer Data on our behalf. Payment, CRM, marketing and website-analytics providers named in the Privacy Policy and Cookie Policy process controller-side data only and do not receive recordings, transcripts or summaries. Product-analytics, session-insight, error-monitoring and in-app support tools used inside the application are configured to mask transcript, summary and recording content and to capture only interaction events and technical data; any such tool that cannot be configured in this way is listed below as a subprocessor.

UAB Such Much AI’s affiliates SIA “Such Much AI” and Such Much AI, Inc. are not subprocessors and have no access to Customer Data.

3. Measures Against Unlawful Third-Country Government Access

3.1Hosting and access. Customer Data is hosted only in the EU, is encrypted in transit and at rest and is accessible to our personnel only from the European Economic Area (except as agreed in writing with a customer), under role-based, logged, least-privilege access.

3.2Microsoft. Microsoft Ireland Operations Limited is an Irish company and a subsidiary of Microsoft Corporation, which is established in the United States and may be subject to US legal process. Microsoft has committed, under its EU Data Boundary programme and its Data Protection Addendum, to store and process Customer Data within the EU, to challenge government requests for customer data that it considers unlawful, to redirect requesters to the customer where possible and to notify the customer unless legally prohibited. Microsoft publishes a law-enforcement requests report.

3.3Our policy on requests. We do not voluntarily disclose Customer Data to any public authority. If we receive a request from a non-EU authority, we will not comply unless the request is recognized or enforceable under Union or Lithuanian law (for example through a mutual legal assistance treaty or Article 48 GDPR), we will assess its lawfulness, challenge it where there are reasonable grounds, notify the affected customer before disclosure unless legally prohibited and disclose only the minimum information required. Requests from EU authorities are handled under Lithuanian procedural law and Section 14 of the DPA.

3.4Remote access by Microsoft. In limited cases documented in Microsoft’s EU Data Boundary documentation, such as resolving a security incident or a support request that we initiate, Microsoft engineers outside the EU may access Customer Data remotely. Such access is covered by the Standard Contractual Clauses in Microsoft’s Data Protection Addendum and is logged by Microsoft.

4. Azure OpenAI Abuse Monitoring

By default, the Azure OpenAI Service may retain prompts and completions for up to 30 days in the same geography for abuse monitoring by Microsoft. [We have obtained Microsoft’s approval for modified abuse monitoring, so transcripts sent for summarization are not stored by Microsoft for this purpose / We have not yet applied for modified abuse monitoring; customers who require it should contact us.] Microsoft does not use prompts or completions to train its models.

5. Switching and Portability Information (Data Act Article 26)

5.1Methods. Customers can export their data in two ways: in-app download of an individual recording, transcript or summary; and an account export from Settings that delivers all Exportable Data in a single JSON file. Exports are available to the account holder.

5.2Formats.

The JSON schemas follow open, documented structures so that data can be imported into other systems without proprietary tools.

5.3Known limitations. The in-app search index is a service function rather than data and is not exported; it stops working when the subscription ends. Very large exports may be delivered as several files.

5.4Known risks to continuity during switching. Until the switch is complete, recordings and uploads continue to be processed; recordings made after an export must be exported separately.

5.5Timing and charges. A switching request may be made at any time; the notice period is one month and never more than two months; the transitional period is 30 calendar days from the end of the notice period, and data remain retrievable for at least 30 days after it. We impose no switching or data-egress charges. Any early-termination fee for a committed term is stated in the Order Form.

6. Changes to This Part

We give customers at least 30 days’ notice of a new or replacement subprocessor, a change of hosting region or a material change to switching methods, by updating this Part and by email or in-app notice to workspace administrators. Customers may object to a new subprocessor as described in Section 6 of the Data Processing Agreement (Annex 1 to the Terms of Service). To receive change notifications by email, write to info@suchmuchai.com with the subject line “Subprocessor notifications”.

Part C — AI Transparency Notice

This Notice explains how Such Much Voice uses artificial intelligence, what its outputs are and are not, how AI-generated content is marked and what users should do to review it. It is published by UAB Such Much AI (company code 306405204, Bukčių g. 6-38, Vilnius, LT-04127, Lithuania) to meet the transparency obligations of Article 50 of Regulation (EU) 2024/1689 (the “AI Act”), to support the AI-literacy obligation in Article 4 of the AI Act and to give customers the information they need as deployers. It forms part of the Documentation referred to in the Terms of Service.

1. What the AI in Such Much Voice Does

Such Much Voice converts speech in recordings and meetings into text and derives notes from that text. Every feature below is probabilistic: it predicts the most likely output and can be wrong.

2. Roles Under the AI Act

UAB Such Much AI is the provider of the Such Much Voice AI system. Customers are deployers when they use it under their own authority. Such Much Voice is built on general-purpose speech and language models supplied by Microsoft through Azure AI services in European Union regions; the providers of those general-purpose models bear the obligations of Chapter V of the AI Act that apply to them. In its intended purpose (transcription and note-taking assistance), Such Much Voice is not a high-risk AI system under Annex III of the AI Act. A customer who uses it as part of a high-risk use case, for example to evaluate employees or pupils, becomes responsible for the deployer obligations that apply to that use case, and must not do so without the assessment and written agreement described in the Terms.

3. Knowing When You Interact with AI

Such Much Voice does not join meetings and does not include a chat or question-answering assistant. Transcripts and notes are labelled as AI-generated, and the application does not present AI-generated text as coming from a human.

4. How AI-Generated Content Is Marked

4.1Labels in the application. Transcripts are labelled as AI-generated transcripts. Summaries, notes and action items are labelled as AI-generated.

4.2Machine-readable marking. Where technically feasible, exported summaries, notes and other generated text carry machine-readable metadata identifying them as AI-generated and naming Such Much Voice as the generating system, in line with Article 50(2) of the AI Act and the Code of Practice on the transparency of AI-generated content. Exported transcripts carry metadata identifying them as AI transcripts of a recording. [Specify the marking method actually implemented, for example document metadata fields, a content-credentials manifest or an invisible text watermark.]

4.3Limits of marking. Markers may not survive copy-paste, format conversion, editing or re-authoring. Once content leaves the application, the customer is responsible for any labelling or disclosure that the law requires for its own use, including the deployer obligation under Article 50(4) of the AI Act to disclose that a published text on a matter of public interest was artificially generated unless it has undergone human review and editorial responsibility is held by a person.

5. What Such Much Voice Does Not Do

It does not generate synthetic speech, clone voices or create deepfakes. It does not create voiceprints or identify people by their voice. It does not perform emotion recognition or biometric categorization. It does not make decisions about people. If any of these capabilities were ever introduced, this Notice and the Terms would be updated before release and the relevant AI Act obligations applied.

6. Accuracy and Known Limitations

Accuracy depends on audio quality, the language and its support level, the number of speakers, the amount of cross-talk, accents and vocabulary. Supported languages and indicative accuracy information are listed in the Documentation. No transcript or summary should be treated as verbatim, complete or certified. Figures, dates, names, commitments and quotations are the items most often wrong and should always be checked against the recording.

7. Human Oversight: What Reviewers Should Do

• Listen to the passage before quoting, citing or acting on a statement, especially commitments, figures and dates.
• Confirm speaker attribution before attributing a statement to a named person.
• Treat summaries as a starting point for minutes, not as minutes; confirm decisions with Participants.
• Verify action items with the people they are assigned to.
• Do not use Output as the basis for a decision about a person without independent review.
• Report systematic errors or unexpected behaviour to us so that we can investigate.

8. Data Used by the AI

Recordings and transcripts are processed only to deliver the features the customer uses. They are not used to train or fine-tune models unless the customer has expressly opted in through a written agreement. Processing takes place in European Union Azure regions, and recordings are not sent to external foundation-model APIs. Retention is controlled by the customer as described in the Data Processing Agreement.

9. AI Literacy

Article 4 of the AI Act, as amended by Regulation (EU) 2026/1744, requires providers and deployers to take measures to support the AI literacy of the people who use AI systems on their behalf. To support this we provide this Notice, in-app guidance, onboarding sessions on request and the Recording and Participant Notice Guidelines. Customers remain responsible for training their staff and for deciding where and how Output may be relied on.

10. Feedback, Incidents and Contact

To report an inaccurate, biased or harmful output, a transparency issue or a suspected serious incident involving the AI, contact info@suchmuchai.com with the subject line “AI Report”. We investigate reports, correct systematic issues where possible and meet our incident-reporting obligations under the AI Act where they apply.

11. Changes

We update this Notice when features, models, marking methods or legal requirements change. The current version states its effective date.

Part D — Recording and Participant Notice Guidelines

These Guidelines help customers of Such Much Voice record and transcribe conversations lawfully in Lithuania and the European Union. They summarize the main rules and provide template notices. They are general information published by UAB Such Much AI, not legal advice; the customer remains responsible for its own compliance, and the law of other countries may be stricter.

1. The Rules in Brief

1.1A recording of a person’s voice is personal data. Under the GDPR you need a lawful basis to record and transcribe (Article 6), you must tell participants that you are recording and why (Articles 13 and 14), you must keep recordings only as long as needed and you must protect them. Where recording is systematic or involves people in a position of dependence (employees, pupils, patients, applicants), a data-protection impact assessment under Article 35 GDPR is usually required.

1.2Lithuanian law protects private life and the confidentiality of communications. Article 2.23 of the Civil Code gives every person a right to privacy, which covers private conversations. Articles 166, 167 and 168 of the Criminal Code make it an offence to unlawfully intercept communications to which you are not a party (Article 166), to unlawfully collect information about a person's private life (Article 167) or to unlawfully disclose or use information about a person’s private life. Recording a conversation you take part in may be lawful in some circumstances, but Lithuanian courts have treated covert recording of a participant, and later use or disclosure of the recording, as capable of infringing Article 2.23, with civil or administrative liability as the result. Video recording also engages the right to one’s image under Article 2.22 of the Civil Code. Informing everyone is both the safe course and a GDPR requirement.

1.3Employees. Article 27 of the Lithuanian Labour Code requires employers to respect employees' privacy and the confidentiality of their private communications, and Article 5 of the Law on the Legal Protection of Personal Data requires employers to inform employees, in writing or in another provable way, before audio or video monitoring at the workplace begins. Where the Labour Code's information and consultation rules apply, employee representatives must be informed and consulted before monitoring rules are adopted. Recording of internal meetings is monitoring in this sense. Consent is rarely a valid basis in the employment relationship; rely on legitimate interest or a legal obligation after a documented balancing test.

1.4Public bodies. Meetings of public authorities may be subject to openness and record-keeping rules; a transcript or summary may become an official document subject to the Law on Documents and Archives and the Law on the Right to Obtain Information. Agree in advance whether the AI output is a working aid or an official record and who approves it.

1.5Professional secrecy. Lawyers, doctors, auditors, notaries and others bound by professional secrecy must ensure that recording and cloud transcription are compatible with their professional rules before using the Services for client or patient conversations.

1.6Other countries. Some jurisdictions require the consent of every participant to any recording and treat recording non-public spoken words without consent as a criminal offence. For cross-border calls and meetings, inform every participant and obtain express consent where any participant is in such a jurisdiction.

2. Before You Record: Checklist

• Define the purpose of the recording and who will have access to the transcript and notes.
• Identify the lawful basis (and, for employees, document the balancing test).
• Prepare the notice and, where consent is the basis, a way to record consent.
• Set retention: delete source audio after transcription where you do not need it, and set an expiry for transcripts.
• Limit access to people who need the output.
• Carry out a data-protection impact assessment for systematic or sensitive recording.
• Check meeting-platform rules and any host restrictions on recording.

3. How to Inform Participants

Inform participants before the recording starts, in a way they will actually see or hear: in the calendar invitation, in the first minute of the meeting, by a pre-recorded message on telephone lines, by a written policy for employees and by signage at in-person events. The notice should say that the conversation is being recorded and transcribed with an AI tool, why, who will have access, how long it will be kept, who the controller is and how to exercise data-protection rights or object. Keep it short in the meeting and link to a fuller privacy notice.

4. Template Notices

Replace the bracketed text. “We” in the templates means the customer, not Such Much AI.

Calendar invitation line:

This meeting will be recorded and transcribed with Such Much Voice, an AI transcription tool, so that organization can prepare notes and action items. The recording and transcript will be available to participants / the project team and kept for period. Organization is the controller; see privacy notice link. If you would prefer not to be recorded, tell the host before the meeting or at the start.

Spoken notice at the start of a meeting:

Before we begin: this meeting is being recorded and transcribed by an AI tool so that we can share notes afterwards. The notes will go to the people on this call and will be kept for period. If anyone would rather not be recorded, please say so now and we will pause the recording for your contribution.

Telephone or voice-line announcement:

This call is recorded and transcribed with an AI tool for quality assurance / record-keeping. Information about how organization uses your data is available at link. If you do not wish to be recorded, please let the agent know at the start of the call.

Email to external participants before an interview or consultation:

Subject: Recording of our interview/meeting on date

Dear name, we plan to record and transcribe our conversation on date using Such Much Voice, an AI transcription tool, to produce an accurate written record. The recording and transcript will be accessible only to names/roles and deleted after period. Organization is responsible for this data; our privacy notice is at link. Please reply to confirm that you agree, or let us know if you would prefer that we take written notes instead.

Written notice for employees (to include in an internal policy):

Organization records and transcribes which meetings using Such Much Voice, an AI transcription tool, in order to purpose. Recordings and transcripts are stored in the European Union, are accessible to roles, are kept for period and are not used to evaluate individual performance or to make decisions about employees. The legal basis is legitimate interest in accurate record-keeping / legal obligation. You may object to a specific recording by informing contact and may exercise your data-protection rights by contacting contact. This notice was issued on date after consultation with employee representatives, where applicable.

Sign for in-person events:

This session is being recorded and transcribed with an AI tool. Recordings are managed by organization and used for purpose. For details and to exercise your rights, see link or contact email.

Consent wording where consent is the lawful basis:

I agree that organization may record and transcribe this meeting/interview using Such Much Voice for the purpose of purpose, that the recording and transcript may be accessed by roles and that they will be kept for period. I understand that I may withdraw my consent at any time by contacting email, without affecting processing carried out before withdrawal.

5. Handling Objections and Requests

If a participant objects before or during a meeting, pause the recording and take written notes for that part. If a participant objects afterwards, assess the objection, stop any processing you cannot justify and delete or redact that person’s contributions where required. Respond to access, correction and deletion requests within one month; Such Much Voice lets you search, export and delete transcripts to support this. Share transcripts and summaries only with people entitled to receive them, and correct misattributed or inaccurate passages before circulating minutes.

6. After the Meeting

Review the AI output before relying on it, particularly names, figures, dates and commitments. Delete the source audio where the transcript is sufficient. Apply the retention period you announced. If you publish or circulate AI-generated notes on a matter of public interest, disclose that they were generated by AI unless a person has reviewed them and taken editorial responsibility, as required by Article 50(4) of Regulation (EU) 2024/1689.

7. Questions

Questions about these Guidelines may be sent to info@suchmuchai.com. For advice on your specific situation, consult your data-protection officer or legal counsel.