Privacy Policy

Design Buff LLC, a New Jersey limited liability company, trading as Tulpa. Questions to hello@tulpatalk.com.

Last updated 6 November 2026

The short version. Your audio is transcribed on your Mac and is never sent to us or anyone else. Dictated text leaves your Mac only if cleanup is switched on with a model that is not on your Mac. What we collect is the contact, account, billing, download and cleanup usage information needed to run and sell the software, listed below with the reason for each.

What stays on your device

Recorded audio is transcribed on your machine and is not saved: Tulpa 1.0 keeps no audio. Transcripts are inserted into whatever application you are typing in, or copied to your clipboard if no text field is selected. Recent transcript text is kept in your history on your Mac (the last five dictations by default), and you can clear it. Recordings made by older versions stay on your Mac where they were. Audio is never sent to us or anyone else.

The app sends no telemetry about what you dictate. We never store your words on our servers, and apart from the team cleanup usage records described below, we do not collect their length or how often you speak.

What we collect

  • If you use a form on this website. Your email address, your name if you give it, a short note about what you plan to use Tulpa for if you write one, what you asked for (a download, a waitlist), your platform, which form you used, and whether you agreed to marketing email. A copy is emailed to our inbox. We use it to reply, to send the download and to keep a list of people who asked to be told about other platforms.
  • If you download the app. The platform, the time, the email address you gave on the form, your IP address and your browser's user agent, so we can count downloads and spot abuse.
  • If you sign in or buy. Your email address, your name and marketing choice if you give them, and when you last signed in. Sign-in is a 6 digit code sent to your email; there is no password. We store the codes and the sign-in sessions only in hashed form, along with the IP address a code was requested from, the type of device or browser, and a record of failed attempts, so we can run sign-in securely and block guessing.
  • If you subscribe. Stripe sells the subscription and holds your payment details (see below). We keep what Stripe reports back so the app can unlock: your Stripe customer and subscription IDs, the plan, its status, the number of seats, the renewal date and whether it is set to cancel. We never see or store a card number.
  • If you use Tulpa Teams. The team's name, the email address of each person invited, their seat status (invited, active or removed), who the administrators are, and the dates involved. We use this to run the team and bill for its seats.
  • If your team uses team cleanup. The team's cleanup provider settings: the endpoint address, the model name and a label the administrator chose, and the provider's API key, which we store encrypted. For each cleanup request we also keep a usage record: your team's identifier, your user identifier, the model used, the tokens processed and the time. Your administrator can see the usage for the team. We never store the text.
  • When the app talks to our servers. Checking for updates and downloading a speech model fetch files from our servers, so your IP address reaches us, as with any download. If you are signed in, the app also checks your account and subscription. None of this carries your audio or your transcripts.

The one case where text leaves your machine

Tulpa has an optional cleanup pass that rewrites your dictation. It is off unless it is switched on. It can run entirely on your Mac with Apple Intelligence, on Apple silicon Macs. When it uses a model elsewhere, it sends text only, never audio.

If you connect a cloud model with your own API key, you confirm a warning that the provider handles the text under its own terms, and turn cleanup on with it. The text then goes directly from your machine to that provider, and we never receive it.

If you are on a Tulpa team and the administrator has set a team cleanup provider, the text goes from your Mac to our server and from there to the team's provider. The provider's API key is stored encrypted on our server and is never sent to any Mac. We do not store the text. We keep only the usage record described above (who, when, which model, how many tokens), and the provider's own terms apply to the text it receives.

On Macs managed by an organisation, a policy file installed by its IT team can pin cleanup to this Mac only, or to an endpoint the organisation names. The app follows that file.

Who else is involved

  • Cloudflare. Runs our API and the account site, stores and serves the app installer, app updates and speech model files (from models.tulpatalk.com), sends our email (sign-in codes, team invites and notices), and runs DNS for tulpatalk.com. It sees request details such as IP addresses, as any hosting provider does.
  • Neon. Hosts our database (in the United States), which holds the account, billing status, team, lead, download and usage records described above.
  • Stripe, through Link. Stripe is the merchant of record for purchases: it sells you the subscription, collects your payment details and billing address, calculates and remits sales tax and VAT, sends receipts, and handles payment support, refunds and disputes, under its own terms and privacy policy. Card statements show LINK.COM. We give Stripe your email address and account identifiers so the purchase can be linked to your account.
  • Hostinger. Hosts this website.
  • Apple. If you choose Apple Speech, macOS downloads each language from Apple the first time you use it. Apple Intelligence cleanup runs on your Mac.
  • A cloud model provider. If you connect one for cleanup, or your team administrator does, it receives the text sent to it, under its own terms.

Some of these providers process data in the United States and in other countries. Installs of older versions of Tulpa may still fetch update files from a former hosting provider until they update. We do not sell your personal information, and we do not share it for advertising.

Fonts, analytics and cookies

This site loads no third-party analytics and no third-party fonts, and sets no cookies of its own. The typeface is served from our own domain so that reading this page does not hand your IP address to a font CDN. The account site at account.tulpatalk.com sets one cookie, which is strictly necessary: it keeps you signed in until you sign out.

How long we keep things

We keep personal data only as long as we need it to run the service, answer billing or support questions, and meet our legal obligations. An automatic job runs every day and deletes records once their period below has ended, so removal happens within a day or so after that.

  • Sign-in codes. A code stops working after 10 minutes. We delete it 7 days after it was sent.
  • Records of wrong sign-in attempts. Used to limit guessing. Kept for 30 days.
  • Signed-in sessions on a device. Deleted 30 days after the session is signed out, or once it is over 120 days old and no longer in use.
  • Records of team invite emails sent. Kept for 30 days.
  • Former team seats. Invites that were declined or expired, and members who were removed. Kept for 90 days.
  • Payment events received from Stripe. Kept for 90 days after we have processed them.
  • Download form submissions. Your name, email, what you are working on and your marketing choice. Kept for 24 months.
  • Download records. Kept for 13 months.
  • Team cleanup usage counts. Counts only, never text. Kept for 13 months.
  • Account, subscription and team records. Kept while your account exists, and deleted when you ask. Write to hello@tulpatalk.com.

If your own account is deleted, your user identifier is removed from the cleanup usage records. Stripe keeps its own billing records of your purchases as the seller, under its own policies and legal duties.

Your choices

Write to hello@tulpatalk.com and we will give you a copy of what we hold, correct it, or delete it. Deleting your account also cancels your subscription. If you are in the EEA, the UK, or California you have rights to access, correction, deletion, portability, and to object to processing; we honour those requests wherever you live rather than only where we must.

Marketing email is sent only if you agreed to it, and every marketing email has an unsubscribe link. Service email about your account, such as sign-in codes and team invites, is not marketing and does not carry one.

Children

Tulpa is not for use by anyone under 16, and we do not knowingly collect their information.

Changes

If we change what we collect or where it goes, we will update this page and change the date at the top. Material changes will be emailed to account holders rather than quietly published.