MeetinglyHome

Privacy Policy

Last updated: 3 October 2026

This policy explains what data the Meetingly application and services handle, why, and what you can do about it. It is written to be read, not skimmed; the short version is in the first section.

The short version

1. Who we are

AI Prime Tech, Pokhara, Nepal, is the controller of the data described here. Contact: support@aiprimetech.io.

2. Data handled by the application

Audio. When you press Listen, audio from the sources you selected (microphone, system audio or both) is captured and streamed over an encrypted connection to our relay, which forwards it to Deepgram, Inc. for speech recognition. The relay does not store audio. Deepgram processes it under its own terms and privacy policy.

Transcripts. The live transcript is held in the application's memory during a session and, when you finish a session, saved as a meeting on your computer.

AI requests. Your typed messages, the recent transcript, the active prompt and its background notes, and screenshots you explicitly request are sent through our relay to an AI model provider to generate answers and reports. The relay does not store these requests. Model providers may retain requests briefly for abuse monitoring under their own policies.

Screenshots. Taken only when you press the screenshot action or shortcut, never automatically, and sent only for that one request.

Settings and prompts. Stored on your computer in the application data folder.

Logs. The application writes a diagnostic log on your computer (session status, errors, audio device names). It contains no transcript text and never leaves your computer unless you send it to us.

3. Data handled by our servers

Device identifier. A random identifier created on first run. It is sent with every request so we can apply per-device daily limits. It is not linked to you unless you connect an account.

Usage counters. The number of answers and minutes of audio per device per day. Kept for the current day and discarded.

Server logs. Standard web-server logs (IP address, time, request path, status) kept for up to 30 days for security and troubleshooting.

Account data (only if you connect an account). Your email address and password hash, your synced settings and prompts (including any background notes you entered), your meetings (title, times, transcript, generated report), and the list of devices you connected. Stored on our servers in the United States. Each item is readable only by the account that owns it.

4. Why we process this data

To provide the features you use (contract performance); to enforce usage limits and keep the Service secure (legitimate interest); and, for account data, because you asked us to store it (consent, which you can withdraw by disconnecting or deleting the account).

5. Who else sees it

We do not sell personal data and do not share it with advertisers.

6. Retention

Audio and AI requests: not stored. Usage counters: one day. Server logs: up to 30 days. Account data: until you delete the item, disconnect the device, or delete the account, after which it is removed within 30 days from live systems and backups.

7. Your rights

You can read, export and delete your meetings, prompts and settings at any time in the application or the web dashboard. You can delete your account from the dashboard. Depending on where you live you may also have rights of access, rectification, portability and objection, and the right to complain to a supervisory authority. Email us to exercise any of them.

8. Other people's data

Meetings usually involve other people. You are responsible for having the right to record and transcribe them under the laws that apply to you and to them, and for telling them where that is required.

9. Children

The Service is not directed at children under 16 and we do not knowingly collect their data.

10. Security

All connections use TLS. API keys for our providers are held on our servers, never in the application. Account passwords are stored hashed. Device tokens are kept in the application's protected data folder.

11. Changes

We will post changes here with a new date. Material changes will also be shown in the application or the dashboard.