MeetinglyHome

Privacy Policy

Last updated: 10 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

Meetingly is the controller of the data described here. Contact: support@aiprimetech.io.

2. Data handled by the application

Audio. By default, speech recognition runs on your computer after the model downloads. When you select the cloud engine available on Unlimited, selected microphone and system audio is sent over an encrypted connection through our relay to Deepgram for recognition. Our relay does not persist that audio. Deepgram handles 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. In own-key mode, these requests go directly to your configured provider instead of our relay. A local endpoint can keep answer processing local if the model server itself runs locally.

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. Per device or account and per day: the number of AI requests, answers, screen analyses, live suggestions and reports, the AI tokens and minutes of audio used, and how often a limit was reached. Used to apply the daily limits, spot abuse and plan capacity.

Server logs. Standard web-server logs (IP address, time, request path, status) kept for up to 30 days for security and troubleshooting. From them we keep daily totals (visitors, downloads, installed apps checking for updates, referring sites) that contain no IP addresses.

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.

Account activity log (only if you have an account). Sign-ups, sign-ins and failed sign-in attempts, devices connected and disconnected, and the steps of a checkout or payment (opened, abandoned, paid, failed), with the time and IP address. Used for security, to prevent abuse of the free plan and to support you with billing.

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

Our relay does not persist audio or AI request bodies. Usage counters: 12 months. Account activity log: 180 days. Server logs: up to 30 days. Synced meeting records remain until you delete them or delete the account. Unlinking a device stops its future sync but does not delete records already stored in the account.

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

Hosted service connections use TLS. Provider API keys used by our relay remain on our servers. Account passwords are hashed. Device tokens are kept in the application data folder. Own-key providers use the endpoint you configure, which may use local HTTP; version 1.2.3 requires a secure OS keychain before saving a nonempty API key.

11. Changes

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