Privacy Policy for Markly

Markly is a meeting recorder application for Android and Windows developed by Adrián Garrido Pazos. It captures audio from your meetings, lets you add timestamped notes during recording, and optionally uploads sessions to a personal backend server for AI-powered transcription, speaker diarization, and summarization.

1. Audio Recording

Markly requests the RECORD_AUDIO permission (Android) or access to your audio device (Windows) solely to capture meeting audio. Recordings are stored locally on your device inside the app's private folder (Documents/Recorder/sessions/) and are never transmitted anywhere without your explicit action (tapping "Upload").

2. Data Stored Locally

The following data is stored on your device only:

• Audio files (.m4a on Android, .wav on Windows) — your meeting recordings.
• Notes CSV — timestamped notes you add during recording.
• Session metadata — title, labels, and speaker names you assign.

This data remains on your device unless you explicitly upload a session to the server.

3. Authentication

Markly uses Firebase Authentication with Google Sign-In. When you sign in, Google provides a secure token that identifies your account. No additional personal data is stored by the app beyond what Firebase Auth provides (user ID and email). For more information, see Firebase Privacy and Security.

4. Data Uploaded to the Server

When you tap "Upload" on a session, the following data is sent to a personal backend server operated by the developer:

• The audio file of that session.
• The notes CSV associated with that session.
• Any metadata you have added (title, labels).

This server is hosted on infrastructure controlled by the developer and is accessible only to authenticated users. Data is not shared with third parties except as described in Section 5.

5. Third-Party AI Services

Once uploaded, your audio and transcript are processed by the following third-party services to generate transcription, speaker diarization, and an AI summary:

• Deepgram — audio is sent to Deepgram's API for speech-to-text transcription and speaker identification. Deepgram processes audio in accordance with their Privacy Policy.
• Google Gemini — the diarized transcript text (not the audio) is sent to Google Gemini for correction and summarization. Google processes this data in accordance with their Privacy Policy.

Neither service receives your account credentials or any data beyond what is described above.

6. Data Retention and Deletion

You can delete any session at any time from the app's history screen. Deletion removes both the local files (if present) and the server-side copy, including the audio, notes, and generated transcript. Once deleted, this data cannot be recovered.

7. Usage and Credits

To manage service usage, Markly records anonymized consumption events on the server: the duration of each transcribed audio (in seconds) and the number of tokens processed by the AI summary. These events are associated with your account ID and are used exclusively to calculate your monthly credit balance. They are never shared with third parties and are not used for profiling or advertising purposes.

You can view your monthly credit consumption at any time from the Account tab inside the app.

8. Access to Your Content

Your transcripts, summaries, notes, and recordings are processed automatically by the server and the AI services described in Section 5. The developer does not manually read, listen to, or access the content of your sessions. Access controls ensure that each user can only retrieve their own data.

9. Analytics and Advertising

Markly contains no analytics SDKs, advertising networks, or tracking of any kind. No crash reports or behavioral telemetry is collected beyond the credit usage described in Section 7.

10. Permissions Summary (Android)

• RECORD_AUDIO — required to capture meeting audio. The app does not record in the background without your active session.
• FOREGROUND_SERVICE / FOREGROUND_SERVICE_MICROPHONE — keeps the recording active while the screen is off or the app is in the background during an active session.
• INTERNET — required to authenticate and upload sessions.