Privacy Policy — s1ft

Last updated: October 17, 2026

s1ft is a macOS meeting assistant that records, transcribes, summarizes, and coaches. We built it with a simple principle: your data is yours. This policy explains exactly what we collect, what stays on your device, and what goes to the AI provider you choose.

1. What We Collect

The s1ft app does not send your audio, transcripts, or summaries to s1ft servers, and it does not ask you to sign in. It contains no analytics SDKs, no tracking pixels, and no behavioral profiling. What we hold falls into two groups:

  • Purchase and license data — When you buy a license, Paddle takes your payment and we receive your name and email address so we can email you your license key and answer support requests. See Section 7.
  • Transcripts and summaries — not collected by us — Transcripts are created and kept on your Mac. When you ask for a summary, the app sends the transcript to the AI provider you chose, not to us. See Section 3.

2. Audio & Recordings

s1ft records meeting audio — both your microphone input and participant audio — directly on your Mac. This audio is stored locally on your device. It is never uploaded to s1ft servers or any third-party service. We do not have access to your audio files, and we have no mechanism to retrieve them. You have full control over your recordings, including when to delete them.

3. Transcript Processing

s1ft summarizes your meetings with an AI engine that you set up in Settings. You either add your own API key for a provider such as Anthropic or OpenAI, or point s1ft at an engine running on your own network, such as Ollama or LM Studio. s1ft servers are not part of this path. The request goes from your Mac straight to that engine.

  • Cloud provider (your own API key) — The provider receives the meeting name, date, duration, participant count, the speaker-labelled transcript text, and the speaker turns, and, only if you checked My voice numbers, voice statistics s1ft calculated on your Mac (pitch range, level, and silences for each span of your own voice), together with your prompt. The provider, not s1ft, receives and handles this data, under the provider's own terms and privacy policy and your agreement with it. s1ft asks for your explicit consent for each cloud provider before the first request and stops sending if you revoke it.
  • Local engine (Ollama or LM Studio) — Nothing leaves your device for the summary step as long as the engine runs on your Mac. If you point s1ft at another machine on your network, the transcript goes to that machine.

Your API key is stored in your Mac's Keychain. s1ft does not receive it.

s1ft measures the pitch and level of your own microphone, only for the segments labelled Me. It does not analyze other people's voices and does not use these numbers to identify you. The numbers are saved on your Mac in the meeting folder (telemetry.json) until you delete the meeting. s1ft does not receive them. They leave your Mac only if you check My voice numbers for a summary (see above) or connect an AI agent (below).

With S1ft 1.3 you can connect an AI agent that reads the meeting folder on your Mac. This includes the transcript, speaker turns, and voice numbers. You choose the agent and what it can access. The agent sends this data to its own provider under that provider's terms and privacy policy. s1ft does not receive it and does not control it.

If you do not set up an engine, or you never request a summary, your transcript text stays on your Mac.

4. On-Device Processing

Transcription is performed entirely on your Mac using WhisperKit, an on-device speech recognition framework. Your audio is converted to text locally — no audio data is sent to any cloud service for transcription. The transcription model runs on Apple silicon, and all intermediate processing happens on your hardware.

4A. Calendar Access

s1ft uses the Calendar permission in macOS to name your recordings after the meeting on your calendar. The app reads calendar data on your Mac, through macOS. It does not ask for a calendar login or password and does not store one. If you do not grant Calendar access, s1ft reads no calendar data.

What the app reads depends on whether you turned on calendar accounts in Settings:

  • Calendar accounts turned on (Settings → Calendar accounts) — After a recording is transcribed, s1ft reads the events on your enabled accounts that overlap the recording. For each event it reads the title, the start and end times, whether it is an all-day event, whether it is cancelled, and whether you declined it (it looks at the attendee list only to find your own response). It uses these to pick one title. It keeps the title it picks as the meeting name. It discards the rest. The local "On My Mac" calendar is not read.
  • No calendar accounts turned on — While s1ft detects a meeting, it reads the events on your Mac's calendars that overlap the five minutes before and after that moment. It reads the event title, start time, description, location, URL, and attendee list. It uses the description, location, and URL only to look for a conference link. An event with a conference link names the meeting. From the attendee list it works out how many people were invited, the work email domains of the guests (free providers such as Gmail are skipped), the organizer's domain, whether you are the organizer, and whether the event repeats.

What s1ft stores. It stores the meeting name. In the second case it also stores the derived values in that recording's entry in your history on your Mac: the invited count, the guest and organizer domains, whether you are the organizer, and whether the event repeats. It does not store the attendee list, guest names, or guest email addresses. It does not store the event description, location, or URL.

What leaves your Mac. s1ft does not send calendar data to s1ft. The only calendar-derived item that can leave your Mac is the meeting name, when it comes from a calendar event. It is part of the meeting details in the request described in Section 3, so it goes only to the AI provider or local engine you set up, and only when you ask for a summary. The attendee data, the invited count, and the domains are not part of that request.

Choosing which meeting title fits a transcript uses sentence embeddings that ship with macOS. It runs on your Mac. You can turn each calendar account off in Settings, or revoke Calendar access in System Settings → Privacy & Security → Calendars.

5. AI Training

We do not use your data — audio, transcripts, summaries, or coaching results — to train AI models. Not ours, not anyone else's. Your AI provider's own terms govern what it does with the transcript you send it (Section 3). Section 8 lists what we retain.

6. Recording Consent

s1ft captures audio natively on your Mac without joining your calls as a bot. Because no bot appears in the meeting, other participants may not be aware that audio is being captured. You are responsible for obtaining consent from all meeting participants before recording, in accordance with the laws that apply to you.

s1ft includes built-in consent disclosure templates that you can share with participants before or at the start of a meeting. Recording laws vary by jurisdiction — some places require all parties to consent, others require only one party. It is your responsibility to understand and comply with the legal requirements in your area.

7. Third-Party Services

We use a limited set of third-party services, each for a specific purpose. The list below says what each one receives and what it does with it:

  • The AI provider you choose (not our service provider) — If you add your own API key, the provider you pick (for example Anthropic or OpenAI) receives your transcript directly from your Mac. We do not receive it, we do not contract with the provider on your behalf, and its terms govern what it does with the data. See Section 3. With a local engine, no outside party receives it.
  • Paddle — Our merchant of record for license purchases. Paddle receives your name, email address, billing address, and payment details, and handles checkout, sales tax, and refunds. Paddle is the seller on your receipt and acts as an independent controller for your checkout data, under its own privacy policy.
  • Email delivery provider (license keys) — Your license key is emailed to you by our license service, which runs separately from the app. The provider that delivers that email receives your email address and the contents of that message.
  • Cloudflare — Serves this website and terminates TLS for traffic to our API, so your requests pass through Cloudflare in transit. It is used for service operation and abuse protection. The website s1ft.app and the buy page also use Cloudflare Web Analytics. It counts visits, pages, referrer sites, country and device type. Cloudflare Web Analytics uses no cookies, and it does not follow a visitor across sites.

Each of these providers receives only the data described above, and uses it to perform the function described. Paddle also handles checkout data under its own privacy policy, as the seller of record for your purchase. We do not sell your personal information, and we do not share it with advertisers, data brokers, or anyone else for their own purposes.

8. Data Retention

  • Audio recordings, transcripts, and summaries — Stored locally on your Mac. You control them entirely and deletion is up to you. The app never sends them to s1ft, and s1ft has no access to them.
  • Data sent to your AI provider — Retained by that provider under its own terms. We cannot delete it for you. Check your provider's settings and policy.
  • License record — Your name, email address, license ID, and Paddle transaction ID are kept for as long as your license is valid, so we can resend your key or retire it if needed. Paddle, as merchant of record, keeps the financial record of your purchase under its own privacy policy.
  • Download log — The website keeps a log of DMG downloads. Each entry holds the date, status, bytes, referrer page and browser type. The log has no IP address. We keep the log for 12 months and use it only to count downloads.
  • Deleting your data — Email [email protected] from the address you used and ask us to delete the personal data we hold about you.

9. EEA and UK Users (GDPR)

If you are in the European Economic Area or the United Kingdom, the General Data Protection Regulation applies to how we handle your personal data. The controller of your personal data is Pavel Azaletskiy, an individual trading as s1ft, reachable at [email protected]. Our legal basis for processing the data we hold is the contract between you and s1ft (your license and support). When you send a transcript to an AI provider, you do so under your own agreement with that provider. The app asks for your consent before it first does so.

You have the right to access, correct, or delete the personal data we hold about you; to request a copy of your data in a portable format; to object to or restrict processing; and to lodge a complaint with your local data protection authority.

Some processing involves transferring your data outside the EEA and the UK, including to the United States. This applies to the third-party services listed in Section 7 — Paddle, Cloudflare, and the email delivery provider used for license keys. Those transfers rely on the provider's standard contractual clauses and commercial terms. It can also apply to the AI provider you choose, if it processes data outside the EEA and the UK. That transfer is between you and the provider.

To exercise any of these rights, email [email protected].

10. California Users (CCPA)

If you are a California resident, the California Consumer Privacy Act gives you rights over your personal information. The categories we hold are described in Sections 1 and 8 — identifiers (your name and email address) and commercial information (your purchase and license record).

We do not sell your personal information, and we do not share it for cross-context behavioral advertising.

You have the right to know what personal information we hold about you, to request a copy, to correct it, to request deletion, and to not be discriminated against for exercising any of these rights.

To exercise any of these rights, email [email protected].

11. Children's Privacy

s1ft is intended for users who are 18 years of age or older. We do not knowingly collect information from anyone under 18. If we learn that we have collected data from someone under 18, we will delete it promptly.

12. Changes to This Policy

We may update this privacy policy from time to time. We do not email about changes. We announce them by updating this page and its "Last updated" date at the top.

13. Contact

If you have questions about this privacy policy or how s1ft handles your data, reach out to us at [email protected]. The controller is Pavel Azaletskiy, an individual trading as s1ft.