Crodo Privacy Policy

Crodo is a voice-first Mac app, so privacy starts with being explicit about what each feature captures, where it is processed, and what controls you have.

Last updated June 30, 2026

1. Scope of this policy

This policy explains how Crodo handles information when you use the Crodo website, macOS app, backend services, AI features, transcription features, screen-aware features, and meeting-note features. It is intended to describe the product behavior in plain language, including what the Mac app may capture, what may be sent to the backend, what may be stored, and what controls are available to you.

This policy applies to Crodo's website and macOS application.
This policy covers voice dictation, voice AI chat, screen-aware AI, and meeting notes.
This policy does not override the privacy terms of third-party services that may process data on Crodo's behalf.

2. Account and authentication data

When you sign in or create an account, Crodo may process account information needed to authenticate you, maintain your session, provide access to your saved history, and connect your Mac app to the backend.

Account identifiers, such as user ID and email address, may be stored by the backend.
Session tokens may be stored locally in macOS Keychain so the app can keep you signed in.
Basic account state may be used to restore your session, sync feature history, and route backend requests to your account.

3. Microphone audio

Crodo uses microphone access for features that require speech input, including dictation, spoken AI questions, screen-aware spoken questions, and meeting recordings. Microphone capture is tied to user actions such as holding a hotkey, starting a recording, or using a voice feature.

Dictation audio is used to convert speech into text.
Spoken AI questions are used to create a transcribed prompt for AI processing.
Meeting microphone audio is used to create transcripts and meeting notes.
You can revoke Microphone permission in macOS System Settings.

4. Dictation text and cleanup

When you use dictation, Crodo converts your spoken words into text. The feature is not intended to follow broad instructions like a chat prompt. Its purpose is to transcribe what you said and clean obvious writing issues before placing the text into your workflow.

Cleanup may fix grammar, spelling, punctuation, capitalization, and spacing.
Cleanup may remove filler words such as um, ah, and similar verbal pauses.
The final text may be pasted into the focused app or copied to the clipboard.
Transcript history may be stored if the product history feature is enabled for your account.

5. Selected text and Accessibility permission

Crodo may use Accessibility permission for global hotkeys, reading selected text, and pasting text back into the focused application. Selected text is used only when a feature needs it, such as using highlighted text as context for an AI question or rewrite.

Accessibility permission helps global hotkeys work across apps.
Accessibility permission may allow Crodo to paste dictated or generated text into the focused app.
Selected text may be sent to the backend when you use it as context for AI processing.
You can revoke Accessibility permission in macOS System Settings.

6. Screen capture and screen-aware AI

Screen-aware AI uses macOS Screen Recording permission to capture visual context from your display when you trigger the feature. This allows Crodo to answer questions about an error, page, document, dashboard, UI, or other visible content.

Screenshots are captured only when you use the screen-aware feature.
Screenshots may include visible app windows, documents, browser content, or other information on the active display.
Crodo may attempt to avoid including its own windows when possible, but you should assume visible screen content may be captured when the feature is triggered.
You can revoke Screen Recording permission in macOS System Settings.

7. Meeting recordings, transcripts, and notes

Meeting notes require recording audio, uploading the recording, transcribing it, and generating structured notes. Depending on your system permissions and recording mode, meeting data may include microphone audio and system or meeting audio.

Large meeting recordings may be uploaded directly to storage through presigned upload URLs.
The backend may transcribe recordings into text.
The backend may generate summaries, decisions, key points, and action items.
Meeting transcripts and notes may be stored to your account so you can review them later.
Local recordings may also exist on your device for playback or upload workflows.

8. Backend and AI processing

Crodo's macOS app communicates with backend services to provide transcription, AI cleanup, AI chat, vision-capable screen understanding, meeting transcription, and meeting-note generation. The backend may use third-party infrastructure or AI providers to perform these tasks.

API keys and model configuration are handled server-side rather than being stored directly in the Mac app.
Feature inputs may be sent to AI or transcription providers as needed to produce the requested result.
The type of data sent depends on the feature: audio for transcription, text for cleanup/chat, screenshots for vision requests, and recordings for meeting notes.
Crodo aims to send only the data needed to perform the feature you triggered.

9. Local storage on your Mac

The Mac app may store some information locally so the product works reliably between sessions. Local storage is separate from data stored on the backend.

Session tokens may be stored in macOS Keychain.
App preferences and settings may be stored in Application Support or similar local app storage.
Temporary files may be created while recording, uploading, transcribing, or processing audio.
Meeting recordings may be saved locally when needed for playback, retry, or upload workflows.

10. Product history and saved content

Crodo may save history so you can return to previous dictations, AI chats, transcripts, and meeting notes. History can make the app more useful, but it also means generated content may remain associated with your account until deleted or otherwise removed under applicable product controls.

Dictation transcripts may be saved as transcript history.
AI chat messages and responses may be saved as conversation history.
Meeting transcripts and generated notes may be saved for later review.
Saved history is used to display previous work and support continuation of relevant workflows.

11. Website information

When you visit the Crodo website, standard technical information may be processed by hosting, analytics, security, or logging systems. This information is separate from the richer content handled by the Mac app features.

Website logs may include IP address, browser information, requested pages, timestamps, and error logs.
The website may use basic analytics to understand performance, traffic, and product interest.
The website may process contact information if you submit support requests or contact forms.

12. How information is used

Crodo uses information to provide the product features you request, keep the service reliable, maintain your account, improve the app, troubleshoot problems, and protect the service.

Provide dictation, transcription, AI answers, screen-aware AI, and meeting notes.
Authenticate users and maintain signed-in sessions.
Store and display saved transcripts, conversations, and notes.
Debug errors, investigate failures, and improve reliability.
Protect against abuse, misuse, fraud, or service disruptions.

13. Sharing and third-party processors

Crodo may share data with service providers that help operate the product, such as cloud hosting, storage, authentication, database, analytics, transcription, and AI-processing providers. These providers process information to help Crodo deliver the requested features.

Audio may be processed by speech-to-text systems.
Text may be processed by AI systems for cleanup, answers, or note generation.
Screenshots may be processed by vision-capable AI systems for screen-aware answers.
Meeting recordings may be stored and processed to create transcripts and notes.
Crodo does not need to sell personal information to provide the product.

14. Retention

Different categories of data may be retained for different periods depending on product needs, user settings, technical requirements, legal obligations, and backup or security practices.

Session and account data may be retained while your account remains active.
Saved transcripts, chat history, and meeting notes may remain available until removed through product controls or account deletion processes.
Temporary processing files may be deleted after processing, but backups, logs, or retry systems may retain limited copies for a period of time.
Support messages may be retained as needed to handle requests and maintain a support history.

15. Security

Crodo uses technical and organizational measures intended to protect information from unauthorized access, loss, misuse, and alteration. No online service can guarantee perfect security, but the product is designed with clear boundaries between local permissions, backend processing, and saved account data.

Sensitive session tokens are stored locally in macOS Keychain where applicable.
Backend access is authenticated through account/session mechanisms.
Presigned upload URLs may be used so large recordings can be uploaded without routing the full file through the app server.
Access to production systems should be limited to what is needed to operate, debug, and support the product.

16. Your choices and controls

You control when Crodo records audio, reads the screen, asks AI, or creates meeting notes. You also control macOS permissions at the operating-system level.

Do not trigger a feature if you do not want that feature's input captured or processed.
Revoke Microphone, Accessibility, or Screen Recording permissions in macOS System Settings.
Avoid using screen-aware AI when sensitive information is visible on your display.
Avoid recording meetings unless you have the rights and consent needed for your context.
Contact support for help with account data, saved history, or privacy questions.

17. Meeting consent and sensitive information

Meeting recording can involve other people, confidential business information, customer information, or regulated data. You are responsible for using Crodo in a way that is appropriate for your workplace, location, and meeting participants.

Tell participants when you are recording if required by your organization or applicable law.
Do not record conversations you are not allowed to record.
Avoid capturing highly sensitive information unless you are authorized to do so.
Review generated notes before sharing them, because AI-generated summaries may be incomplete or incorrect.

18. Children

Crodo is intended for productivity and work use. It is not designed for children or for collecting information from children.

Do not use Crodo to intentionally collect information from children.
If you believe a child has provided information through Crodo, contact support so the issue can be reviewed.

19. Changes to this policy

Crodo may update this privacy policy as the product, infrastructure, legal requirements, or data practices change. The date at the top of the page indicates when this policy was last updated.

Material changes may be reflected by updating this page.
Continued use of Crodo after an update means the updated policy applies to future use.

20. Contact

If you have questions about this privacy policy, data handling, account history, recordings, transcripts, or permissions, contact Crodo support.

Email: support@crodo.ai
Include enough detail to identify your account and the feature or data you are asking about.
Do not include passwords, secrets, API keys, or unnecessary sensitive information in support messages.