Privacy Policy

Privacy Policy

Last updated: 2026-11-08

1. Who we are (data controller)

  • Company name: SODADI
  • Legal form: EURL, incorporated under French law
  • Registered office: 7 avenue Jacques Cartier, 77600 Bussy Saint Georges, France
  • RCS: Meaux 914 818 802
  • SIRET: 914 818 802 00011
  • Intra-EU VAT: FR13914818802
  • Contact: legal@sodadi.fr

SODADI is the data controller within the meaning of the GDPR for the personal data described in this Policy. SODADI publishes the macOS application pepito (the "App").

Data Protection Officer: SODADI has not appointed a Data Protection Officer, as the conditions of Article 37 GDPR are not met (no large-scale processing of sensitive data, no systematic monitoring of individuals at scale). Privacy enquiries are handled directly by SODADI at legal@sodadi.fr.

2. Privacy at a glance

pepito records and transcribes your meetings locally on your Mac. By default, transcription uses the speech recognition built into macOS; the App sends no audio. If you set up your own transcription command, it receives the audio on your Mac, and what it does with it is up to the command. macOS downloads the transcription model from Apple's servers.

To generate summaries and titles, the App sends a language model the transcript together with the meeting context: the date, time and duration of the recording, calendar event details (title, time, organizer, participant names, location, notes), your meeting notes and your guidelines (the PEPITO.md file of your recordings folder), if any. Where this content goes depends on the option you configure:

  • (a) A model running on your Mac (e.g. Ollama, LM Studio): the content stays on your Mac.
  • (b) An endpoint you configure: you enter the URL yourself (e.g. OpenAI, Anthropic, your corporate server). The content is sent directly to that endpoint.
  • (c) A third-party tool you install (an AI command-line tool, or your own command): the App passes the content to that tool on your Mac. Your own commands (transcription, LLM and post-processing commands) receive the locations of the recording's audio, transcript, summary, metadata and notes, and of your guidelines, and can read them; your transcription command also receives the audio prepared for it, and your LLM command the request. What they do with them is up to them. The tool may then send it to its publisher's service or anywhere it is configured to send it, under that publisher's terms.

If you turn on external sources (Settings > External Sources), the App reads, on your Mac, the audio files of the folders you choose, and, for a Bluetooth recorder, listens for nearby Bluetooth devices. Nothing is imported without your confirmation.

If you enable the MCP server, AI tools you connect to it can read your recordings, transcripts, summaries and notes on your Mac, and may send them to their publisher.

If you use the Prompt Bar, each instruction you send starts your AI command-line tool on your Mac. It can read your whole recordings folder and may send what it reads to its publisher.

In every case, SODADI is never in the data path.

The App contacts one server on its own: if you allow automatic update checks (the App asks on second launch; you can change this in Settings > General), it periodically downloads the update feed from GitHub (raw.githubusercontent.com), which receives your IP address. Nothing else is sent. We do not run any analytics, telemetry or crash reporter. License validation is entirely on-device via a cryptographic signature.

3. Information we collect

3.1 On the website (pepito.sodadi.fr)

The website is statically served and does not load third-party analytics or tracking cookies. If you submit the newsletter form, your email address is sent to our newsletter provider (Brevo) for the sole purpose of sending you product updates; you can unsubscribe at any time from any email.

3.2 When you purchase pepito

Purchases are processed by Paddle (see section 5). After your purchase, Paddle shares with us your name, email address and transaction reference so that we can deliver your license, provide support and meet our accounting obligations.

3.3 When you use the App

The App processes your recordings locally on your Mac. None of this data is transmitted to SODADI's servers. Specifically:

  • Recording & transcription: audio recordings stay in the folder you choose. By default, transcription runs on your Mac, using the speech recognition built into macOS; the App does not send your audio anywhere. If you set up your own transcription command, it receives the audio on your Mac, and what it does with it is up to the command. The transcription model for the language you choose is downloaded and updated by macOS from Apple's servers, not by the App, the first time you use a language and whenever macOS reinstalls the model. Only the model is downloaded.
  • Auto-record: if you enable it, the App can start a recording by itself in two ways, which you can use together. On calls, the App listens to the sound of the call apps you select, on your Mac, to start a recording when a call is in progress. While Auto-record is on and a selected app is running, the App keeps the last 20 seconds of that app's sound in memory only, so that the beginning of a call is not lost when a recording starts automatically. On conversations, if you turn on the Conversation trigger and choose a microphone, the App listens to that microphone continuously, on your Mac, to start a recording when a conversation begins. Voice detection runs on your Mac, and the App does not send the audio anywhere. While it listens, the App keeps less than a minute of that microphone's sound in memory only, overwritten continuously, so that the beginning of the conversation is not lost when a recording starts. The orange microphone indicator of macOS stays on while the App listens, and listening continues while the screen is locked; stopping a recording does not stop the listening, and turning off auto-start does. In both cases, this audio is never written to disk outside a recording, and leaves memory when the listening stops or the app quits. When a recording starts automatically, the seconds that triggered it are placed at the beginning of that recording, in your recordings folder: up to 20 seconds of the call app's sound, or up to 30 seconds of the microphone before the conversation began. A recording you start yourself never includes them.
  • External sources: if you add a watched folder, the App reads, on your Mac, every audio file in that folder (not its subfolders) to recognize it, including the ones you do not import. Your recordings folder keeps a fingerprint of each file you import or ignore, but neither its name nor its audio. The App changes and deletes nothing in the folder, except with the option to move an imported file to the macOS Trash, which you turn on folder by folder. If you turn on a Bluetooth recorder, the App listens for nearby Bluetooth devices to recognize the one you designated, and keeps nothing else from them. The FOCASE REC recorder transmits its recordings over Bluetooth without encryption, and the App copies to your Mac the recordings it does not know yet, before you decide; a copy is erased once the recording is imported or ignored. The App deletes nothing from the device unless you turn on that option. Nothing is sent to SODADI.
  • Calendar: if you grant calendar access, the App reads your calendar events on your Mac to match a recording with a meeting. It stores the details of the matched event (title, time, organizer, participant names, location, notes) in the recording's metadata file, in your recordings folder. These details leave your Mac only as part of the meeting context described below.
  • Summary, title and tag generation: for a summary, the App builds a request containing the transcript and the meeting context: the date, time and duration of the recording, calendar event details or the context you entered, your meeting notes and your guidelines (the PEPITO.md file of your recordings folder), if any. To suggest a title, the request contains the summary and your guidelines, if any. To choose tags (Auto-Tag), it contains the summary, the recording's title and tags, the tags of your tag catalog that can still be added (their names and descriptions) and your guidelines, if any. Tags are chosen when you run Auto-Tag, and also after each summary the App generates if you turn on "Auto-Tag after each summary" in Settings > Summary (off by default). Where it goes depends on your configuration:
    • (a) a model running on your Mac (e.g. Ollama, LM Studio): the request stays on your Mac;
    • (b) an endpoint you configure: the request is sent directly from your Mac to the URL you entered, following your Mac's network settings (including its proxy, if any);
    • (c) a third-party tool you install (an AI command-line tool, or your own command): the App passes the request to the tool on your Mac; the tool may send it to its publisher's service. Your own commands (transcription, LLM and post-processing commands) receive the locations of the recording's audio, transcript, summary, metadata and notes, and of your guidelines, and can read them; your transcription command also receives the audio prepared for it, and your LLM command the request. What they do with them is up to them.
  • MCP server: off until you enable it in Settings > MCP. It listens only on a local connection on your Mac and accepts no network connections. AI tools you connect can read your recordings, transcripts, summaries and notes. They can also add notes, tags, titles and artifacts, replace summaries and transcripts, and start a new summary generation, which sends content as described above. What a connected tool does with this content, including sending it to its publisher, depends on that tool.
  • Prompt Bar: available when your AI provider is an AI command-line tool (Claude Code, Codex or opencode) and the MCP server is on. Each instruction you send starts that tool on your Mac, with your configuration, and allows it to use the App's MCP tools without asking you. The tool can read your whole recordings folder, not only the recording on screen, and can change your recordings. The App does not restrict the tool's other capabilities. What the tool does with this content, including sending it to its publisher, depends on that tool.
  • When content leaves your Mac (options b and c, AI tools connected to the MCP server, and the Prompt Bar):
    • the App acts as a transmission tool only;
    • SODADI does not access, store or process the transmitted data;
    • you are the sole data controller vis-à-vis the participants of your meetings, including the people listed in your calendar events;
    • the provider of the endpoint or tool is your processor where you have a data processing agreement with them; otherwise, it acts under its own terms;
    • you are responsible for selecting a provider compatible with your own legal obligations (GDPR, sectoral confidentiality, professional secrecy);
    • you are responsible for informing meeting participants and obtaining their consent where applicable.
  • Software updates: if you allow automatic update checks (the App asks on second launch; Settings > General), the App periodically downloads the update feed from GitHub (raw.githubusercontent.com); "Check for Updates" does the same on demand. Installing an update downloads it from GitHub (github.com). GitHub receives your IP address and the App's name and version; no system profile is sent.
  • License validation: performed entirely on-device using a cryptographic signature embedded in the license key. The App does not contact SODADI or Paddle servers to validate your license at launch.
  • Telemetry & analytics: the App collects no telemetry, analytics or crash reports.

3.4 When you contact support

If you email us, we receive your email address and the content of your message.

If you use the App's feedback form, the App prepares a report that you can review and edit before sending it. The App sends nothing itself: it either opens a message to support@sodadi.fr in your mail app, or copies the report and saves it to your Downloads folder. Besides your message and the contact address you enter, the report can include, each part optional:

  • system information: App version, macOS version, processor architecture, locale (included by default);
  • the App's non-secret settings, such as the LLM endpoint URL and model, microphone name, Auto-record apps, the Conversation trigger setting and the name of its microphone; API keys, passwords and the license key are never included, and folder paths are masked (included by default);
  • the App's logs from the last 30 minutes, with email addresses, IP addresses, identifiers, URLs, user paths and file names masked; masking is pattern-based and may not catch everything, so please review the report (included by default);
  • license information: license type and a short hash of the license email (not included by default).

We use this information solely to respond to your request.

4. Cookies and similar technologies

The pepito website uses the following cookies and trackers:

  • Paddle.js (checkout): strictly necessary cookies set during the purchase process by our payment provider Paddle. These cookies enable the checkout, prevent fraud, and remember your cart during the transaction. They qualify as strictly necessary under Article 82 of the French Data Protection Act and the CNIL guidelines on cookies (Délibération 2020-091); no prior consent is required, but they are disclosed here for transparency.
  • Newsletter (Brevo): no cookies are set on our website by Brevo. The newsletter form is a native HTML form; only the email address you submit is transmitted to Brevo via API for the sole purpose of sending you product updates.

We do not use any analytics, advertising or tracking cookies. There is no Google Analytics, Meta Pixel, Hotjar, or similar tool on this site.

5. Payments and Paddle

All purchases are processed by Paddle.com, our Merchant of Record. Paddle collects and processes your payment information, billing details and email address in accordance with their Privacy Policy. We receive only your name, email and transaction metadata; we never receive or store credit-card or full payment information.

For questions or rights related to billing data held by Paddle, contact Paddle directly via paddle.net.

6. Legal basis (GDPR)

  • Performance of the contract (Art. 6(1)(b) GDPR): processing your order, delivering your license, providing support.
  • Legal obligation (Art. 6(1)(c) GDPR): keeping accounting and tax records as required by French law.
  • Legitimate interest (Art. 6(1)(f) GDPR): responding to support requests.
  • Consent (Art. 6(1)(a) GDPR): newsletter subscription, withdrawable at any time.

7. Data sharing

We share personal data only with:

  • Paddle (payment processor and Merchant of Record).
  • Brevo (newsletter provider, only if you subscribe).
  • Netlify (website host, processes server logs to keep the site online).

GitHub, Inc. hosts the App's update feed and installers. It receives your IP address when the App checks for or downloads an update, or when you download the App through Homebrew, and processes these connection data under its own Privacy Statement.

We never sell your data, never share it for advertising and never disclose it to third parties for marketing purposes.

Note on AI providers and tools: endpoints, third-party tools and AI tools connected to the MCP server that you configure (see section 3.3) are not SODADI's processors and are not listed here. You manage these relationships directly with the chosen provider. Likewise, Apple provides the transcription model through macOS, under Apple's terms.

8. Hosting provider (LCEN art. 6-III)

The website pepito.sodadi.fr is hosted by Netlify, Inc., 44 Montgomery Street, Suite 300, San Francisco, California 94104, United States — phone: +1 (415) 691-2375 — www.netlify.com. Netlify processes server access logs to operate and secure the site; see section 7 above for data-sharing details.

9. International transfers

Some of our processors (Paddle, Brevo, Netlify) may process data outside the European Economic Area. They rely on the European Commission's Standard Contractual Clauses (SCCs) and other GDPR-compliant transfer mechanisms.

GitHub, Inc. is based in the United States; the connection data it receives (see section 7) are processed there under its own Privacy Statement.

10. Data retention

  • License and transaction data: kept for the duration of the customer relationship and for the legally required accounting period (10 years under French Commercial Code).
  • Support emails: kept for the duration of the exchange and up to 1 year afterwards.
  • Newsletter subscription: until you unsubscribe.

11. Your rights

Under the GDPR, you have the right to:

  • access your personal data (Art. 15);
  • rectify inaccurate or incomplete data (Art. 16);
  • erase your data (Art. 17);
  • restrict processing (Art. 18);
  • portability of your data (Art. 20);
  • object to processing based on legitimate interest (Art. 21);
  • withdraw consent at any time, without affecting the lawfulness of past processing.

To exercise these rights, email us. We respond within one month at the latest.

You also have the right to lodge a complaint with the French Data Protection Authority, the CNIL (www.cnil.fr), or the supervisory authority of your country of residence.

12. Security

We apply reasonable technical and organisational measures to protect personal data against loss, misuse and unauthorised access. Because the App processes audio locally on your Mac, the security of the recordings stored on your device depends on your own device security (full-disk encryption, account password, etc.).

13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new "Last updated" date.

14. Contact

Data controller: SODADI (full identification in section 1). Contact: legal@sodadi.fr.