Security overview

Network surface, in full

JesRecap does not automatically upload meeting content. If you export it, paste a prompt into an external AI service, or include content in a support email, you choose to share it. The app uses these services:

Endpoint	When	What it carries
models.jesrecap.com	Once per model, or never if pre-seeded	A file request for the speech models and, only if you enable AI notes, the roughly 530 MB language model. No license key, no meeting data. Public mirrors are used as a fallback if our host is unreachable.
License API	Activation, then periodic validation	License key, device fingerprint, device name: enough to enforce the license's device limit
Stripe checkout	At purchase, in your browser	Payment details, entered on Stripe's page. We never see or store card data.

The app can also ask the license API which version is currently published, so it can tell you an update exists. That is the same host as license validation and carries no meeting data.

If you restrict egress: allow license validation, handle the model downloads once (or pre-seed them). Paid licenses require a successful check at least every 30 days to continue recording; plan for that before disconnecting a device. The deployment guide has the details.

Optional Outlook calendar connections use Microsoft sign-in and calendar services. These connections are available only in builds that include the integration, and are off by default.

What we do not collect

• No accounts. No usernames, no passwords, no sign-in.
• No telemetry. Not usage events, not feature counters, not anonymised aggregates.
• No crash reporting to us. If something breaks, you tell us.
• No analytics or cookies on this website. The fonts are self-hosted; there are no third-party scripts.
• No calendar, contact, or email access. The app does not ask for it, because it does not integrate with anything.
• No cloud AI. There is no model provider in the stack and no inference endpoint. The optional AI notes feature runs its model on the device, so enabling it adds a file download, not a data flow.

The full field-by-field list of what we do process is on the privacy page. It fits in one small table.

Where the risk actually sits

Local-first moves risk rather than deleting it, and it is worth being direct about where it lands.

• The endpoint. Sensitive recordings sit on a laptop. Full-disk encryption, a short screen-lock timeout, and per-user OS accounts are doing real work here. If the machine is unmanaged and unencrypted, that is your weak point.
• Backups. Time Machine, File History, or a backup agent will copy the meetings folder. Encrypt the destination or exclude the folder, deliberately either way.
• Exports and pasting. The moment a transcript leaves the app it is governed by wherever you sent it. JesRecap has no cloud AI, and its optional on-device notes never create this risk at all. But its meeting actions can also copy a prompt to your clipboard for you to paste into an assistant of your choosing, and that paste is an upload to that vendor. If that matters for a given conversation, generate the note locally instead.
• Consent. A silent local recorder is technically discreet and socially loaded. Tell people you are recording; see the GDPR and HIPAA guides.

Where we are honest about the gaps

JesRecap is preview software from a small independent developer, and we would rather say the awkward parts out loud than let you discover them in a questionnaire:

• No external security audit or penetration test has been performed. We are not going to imply otherwise with a badge.
• No SOC 2, ISO 27001, or similar certification. Not in progress, not "coming soon". If it becomes necessary for the customers we serve, we will say so plainly and then do it.
• Not open source. You cannot read the source to verify our claims. What you can do is watch the network: run a proxy or a packet capture and confirm that meeting content never goes anywhere. We would rather be checked than believed.
• Preview release channel. Expect bugs and expect changes. Keep your own copies of anything important.
• No formal support SLA. Support is email, answered by a person, but not contractual response times.

Responsible disclosure

If you find a security issue, email support@jesrecap.com with enough detail to reproduce it. We will confirm receipt, work on a fix, and credit you if you want the credit. Please give us reasonable time before publishing, and please do not test against other people's licenses or data. There is no bug bounty programme. We are a small operation and would rather be straight about that than advertise rewards we cannot pay.