Privacy Policy

How MeetResult processes and protects data. Effective 22 July 2026.

Data controller: ADVELES GLOBAL LLC, state reg. No. 999.110.1553070, TIN 02939551, Republic of Armenia, Yerevan, 20/1 Kajaznuni St., apt. 8/1. Data enquiries: legal@meetresult.app.

1. What data we process

• Account: Telegram identifier, @username, name, registration date, minutes balance and usage.
• Content: uploaded audio recordings and derivatives — transcript, summary, tasks.
• Review template settings: the name, section selection and — on paid plans — the free-text instructions and context you enter for the meeting summary. The instructions and context text is sent to our AI subprocessor (§5) together with the transcript to produce the summary. Do not enter special categories of personal data or third parties' personal data in these fields. These settings are deleted when you delete your account.
• Technical: processing service logs.
• Payment: processed by our payment providers — Telegram (in-app Stars payments) and Polar.sh (Merchant of Record for card payments on meetresult.app); we do not store card details. For recurring subscription charges, Polar (as Merchant of Record) securely stores your payment method until you cancel the subscription; the legal basis is performance of the contract. When you delete your account, the subscription is cancelled and the stored payment token is destroyed, so no further charges can be made.
• Referral: if you take part in the referral program — the inviter↔invitee link and a salted hash of the phone number (for abuse protection). We do not store the raw number. This data is deleted when the account is deleted.
• Content submitted by link: if you submit a link to a video on a public video platform (for example YouTube), the Service downloads only the audio track of the video (no video stream, frames, or facial images) and processes it like an uploaded recording. We keep the link and the video's service metadata (id, title, channel) in your library and in the record of your rights confirmation.
• Acquisition source: where the Operator has enabled this measurement and only if you accepted analytics, we record once — at sign-up — how you found us: the campaign parameters of the link you arrived on (utm_source, utm_medium, utm_campaign, utm_content, utm_term), the advertising click identifier (gclid), the domain of the site that referred you (hostname only, never the full referring URL) and the path of the landing page you opened (never its query string). A value that looks like personal data (an e-mail address, a phone number, a token or a long identifier) is discarded in full and is not stored at all. This is a first-touch record: it is written once and never overwritten by later visits. Separately, if you open our Telegram bot through one of our campaign links, we store the short channel label of that campaign taken from our own closed campaign registry (an unrecognised label is stored as "other", the raw value is never stored). Withdrawing your analytics consent erases the campaign parameters, the advertising click identifier, the referring domain and the landing path; only the short channel label remains. All of it is deleted when you delete your account.

2. Purposes and legal bases

• Providing the Service (transcription, summary, tasks) — performance of a contract (the offer).
• Minutes accounting and billing — performance of a contract and legal requirements.
• Support and security — legitimate interest.
• Marketing messages — only with the User's separate consent.
• Attributing sign-ups to marketing campaigns (measuring acquisition cost and channel performance) — for the acquisition data collected on the website, your consent to analytics, which you can withdraw at any time; for the short channel label of our own Telegram campaign links, our legitimate interest in measuring our own channels (that label identifies a channel of ours, not you).

3. Audio and its storage

By default, the meeting recording is stored (in mp3) in the Operator's object storage so the User can listen to and download it from their library. The recording is accessible only to its owner and is deleted when the meeting or the account is deleted.

The original audio is kept for a limited time: by default about 90 days from upload (configurable by the Operator), after which the original recording is automatically deleted and only the derived materials (transcript, summary, tasks) remain. The User may also delete a recording earlier — manually from their library. The Operator may additionally enable a «delete after analysis» mode — in which case the original audio is not stored at all.

Where a recording comes in via a link to a video (for example YouTube), only its audio track is downloaded; the temporary audio file is deleted as soon as the video is queued for processing, and the resulting recording is then kept under the same rules as an uploaded one (see above). For linked videos, speaker diarization is not applied — no cross-recording voiceprints of participants are built.

4. Storage and location

Results (transcript, summary, tasks) are stored in the Operator's infrastructure to the extent needed to provide the Service, and are deleted on the User's request or when the account is deleted.

When the User deletes a meeting, it is moved to the Trash and kept there for a period set by the Operator (30 days by default), after which it is permanently and irreversibly deleted (including the audio, transcript, summary and tasks). The User can delete a meeting immediately and irreversibly via "Delete permanently" or "Empty trash"; meetings in the Trash are also erased when the account is deleted. The right to immediate erasure is preserved.

In addition, if the Operator has set an inactivity-based retention period, meeting content (recording, transcript, summary, tasks) may be automatically deleted after a prolonged period of User inactivity: if the User has not used the Service (web account or Telegram) within a period set by the Operator, such content may be deleted. By default no such period is set (inactivity-based auto-deletion is off). Where a period is set, the User is warned in advance — at least 7 days — via an available communication channel (Telegram or e-mail); any activity in the Service renews the storage period. Data the Operator is legally required to retain (payment documents and fiscal receipts, consent records) is not affected by this deletion.

Acquisition source data (§1) is cleared automatically by a daily job: the advertising click identifier (gclid) is erased 90 days after it was recorded, and the remaining campaign parameters, the referring domain and the landing path 24 months after. The short channel label of a campaign link is kept while the account exists. In your browser, the stored acquisition entry expires after 90 days (see the Cookie Notice).

5. Disclosure to third parties (sub-processors)

To operate the Service, audio and transcript data may be passed to the following sub-processors:

• pyannote.ai (EU/EEA processing region) — speech recognition and speaker diarization for paid-tier meetings (processes audio);
• OpenRouter (United States) — routing gateway to the language model that turns the transcript into a summary and tasks, and — if you use the AI chat — answers your questions about the meeting (including across several of your meetings), and — if you generate document artifacts (follow-up email, status report, proposal) — drafts them from the meeting content;
• OpenAI (United States) — language-model provider (OpenAI models via OpenRouter) for paid-tier meetings;
• DeepSeek — language-model provider behind OpenRouter for free-tier meetings;
• Telegram — message delivery and in-app payments (Stars);
• Polar.sh — payment processing (Merchant of Record) for card payments on meetresult.app;
• Google Analytics (Google, United States) — for meetresult only, and only if you accept analytics: (a) web analytics on the meetresult.app website (browser cookies), and (b) server-side product analytics, in which de-identified funnel events (start, consent, meeting completed, task export, purchase) are sent to Google Analytics using a pseudonymous client identifier, without your IP address and without writing additional cookies or identifiers to your device (see our Cookie Notice);
• Google Ads (Google, United States / Ireland) — for meetresult only, and only if you accept analytics and advertising measurement in the cookie banner: when you reach the site from one of our search ads, the click identifier (gclid) and the fact that the click later led to a sign-up, an activation or a purchase are made available to Google, so that we can measure which campaign works. For this advertising measurement Google acts as an independent controller under its own terms rather than as our sub-processor. We do not upload customer lists, do not use remarketing audiences and keep personalised advertising switched off;
• the Operator's SMTP provider — delivery of e-mail reports and notifications you request;
• trackers, channels and services connected by the User themselves — the meeting output is sent there per the User's own setup (confirmed tasks, and — if channel broadcast is enabled — the meeting summary too): for example Todoist, Yandex Tracker, Bitrix24, Kaiten, YouGile, Weeek, Jira / Confluence (Atlassian), Asana, Trello, ClickUp, Linear, Monday, GitHub, GitLab, Megaplan, Planfix, Airtable, amoCRM, HubSpot, Salesforce, Pipedrive, Attio, Notion, an MCP server, a custom webhook, Slack, or the User's own Telegram channel/group. Confluence is a document connector: it receives a meeting page (summary and task list), not a separate tracker task. To assign tasks to a real tracker user and to sync task statuses, the Service may also READ service data from your connected tracker (its user list, a task's status).
• Zoom (Zoom Video Communications, Inc., United States) — only if you connect your own Zoom account: with your authorization (OAuth), the Service calls the Zoom API to list your cloud recordings and import the recording you select into processing. Access tokens are stored encrypted and deleted when you disconnect Zoom or delete your account. Without such a connection the Service does not contact Zoom.

Speech recognition for free-tier meetings, and the underlying object storage, run on operator-controlled (self-hosted) infrastructure rather than a third-party sub-processor.

We may add, remove or replace a sub-processor — in particular the language-model provider behind OpenRouter — as our technical needs evolve. We will update this list; for business Users under the DPA (§4), we provide notice of sub-processor changes with a reasonable opportunity to object, as required by applicable law.

Acquisition source data (§1) is not shared with advertising networks and is not uploaded to any advertising platform: we do not perform offline-conversion uploads, enhanced conversions or audience matching, and we do not sell this data. The de-identified funnel events described above may carry only a short campaign label; the advertising click identifier, the referring domain and the utm_content / utm_term values are never sent to Google Analytics or to any other third party.

6. Cross-border data transfer

The Operator is based in the Republic of Armenia. To provide the Service, data may be transferred to and processed in other countries by the sub-processors listed in §5 (speech recognition and language-model providers, payment providers, analytics), and — if you connect your Zoom account — when importing your recordings from Zoom (United States). All such transfers happen over an encrypted channel (TLS in transit). By using the Service you acknowledge this cross-border transfer; we select sub-processors that provide appropriate safeguards for the data they process.

If you submit a link to a video on a public video platform (for example YouTube), the Service contacts that platform (Google LLC / YouTube, servers outside your country) to download the audio track; this outbound request is made over an encrypted channel. We send the platform only what is needed to fetch the video you specified (an ordinary download request) and do not disclose your other personal data or the content of your meetings to it.

For transfers to sub-processors in the United States, the safeguard is appropriate contractual protection — Standard Contractual Clauses (SCC) or an equivalent data-processing agreement — where applicable. We contract directly with OpenRouter and, if you connect Zoom, with Zoom; OpenAI is engaged by OpenRouter as its sub-processor, so protection for that leg is provided through OpenRouter's arrangements rather than a direct agreement with OpenAI. For DeepSeek (the language-model provider for free-tier meetings, reached via OpenRouter and processed in the People's Republic of China) there is no European Commission adequacy decision; that transfer relies on OpenRouter's contractual safeguards together with supplementary technical measures (encryption in transit, data minimisation).

In particular, Google (Google Analytics and — for advertising measurement — Google Ads; United States and Ireland) processes data both from the website (browser cookies) and, for meetresult, from server-side funnel events; we rely on Google's participation in the EU-US Data Privacy Framework and, where applicable, on the EU Standard Contractual Clauses as the safeguard for this transfer.

7. Third-party data (voices of meeting participants)

Audio may contain personal data of other participants. The User confirms that they have notified the participants and have a legal basis to upload the recording (see Terms, §7).

The audio track of a video submitted by link may likewise contain the voices and other personal data of third parties. The User confirms they have a legal basis to process such material (see Terms, §7). The Operator processes third-party voices in such audio on the User's instructions and under the User's responsibility; the legal basis is performance of the contract with the User together with the legitimate interest in providing the processing the User requested. Speaker diarization is not performed for such audio.

8. Data subject rights

Access, rectification, erasure, restriction of processing, portability, and withdrawal of consent — to the extent applicable under law. Send requests to legal@meetresult.app; we respond within a reasonable time, normally within 30 days.

The acquisition source fields described in §1 are included in the data export of your account and are deleted together with the account. You can also stop that processing and have those values erased at any time by withdrawing your analytics consent — no request to us is needed.

9. Security

Reasonable technical and organisational measures are applied (secret encryption, access control). Absolute security cannot be guaranteed. The Service relies on third-party sub-processors (speech recognition, language-model, and payment providers) to operate; the Operator is not liable for their independent acts, omissions, or security incidents beyond the Operator's reasonable control. The confidentiality of any information contained in the Content (audio, transcripts, summaries) is the User's own responsibility — the Operator does not review, and is not liable for, the substance of any Content uploaded by the User.

10. Children

The Service is not intended for persons under the age of 16.

11. Changes to this policy

The current version is published on meetresult.app with an effective date.

12. Contacts

ADVELES GLOBAL LLC · legal@meetresult.app. Full details are in the block below.