Privacy policy
Effective November 6, 2026. How Sentito handles information.
Summary
Sentito runs on hardware you control. It doesn’t require an account, and it doesn’t collect, sell, or share personal information for advertising, profiling, or cross-context tracking. The requests it makes to DWMM Holdings, including anonymous trial reports you can turn off, are each described below.
Buying it
Stripe handles payment. You enter your card details on Stripe’s checkout page and Stripe processes them. DWMM Holdings never sees, receives or stores them.
The email address you enter at checkout, so we can send you your key, and send it again if you ask.
Your key, encrypted, so it can be sent again. It’s looked up by a one-way hash of the key, so a copy of the database on its own doesn’t give anyone a working key.
Stripe’s record of the transaction (amount, date, country and payment reference), which is what accountants and tax authorities require.
Sentito has no account with us, no relay and no usage tracking. We can’t see your recordings, transcripts or questions, or who uses your server. The only things a server ever tells us are the details it sends when it’s activated or released, a daily check of whether its key was revoked, and anonymous trial reports you can turn off, all described below.
Stripe is a separate controller of the payment information it processes, under its own privacy policy. DWMM Holdings keeps the transaction record for as long as tax and accounting law requires, and keeps your purchase email address and key for as long as it's needed to support the license you bought.
Activating and releasing a server
When you enter a key, the server sends one HTTPS request to scribe.dwmmholdings.com. It contains the key; the server’s device ID, which is a fingerprint of an identity key the server makes for itself the first time it starts; the server’s name; the platform it runs on, such as macOS; the product, Sentito Server; and Sentito’s version. Releasing a server’s seat sends the same details. Neither request contains anything about your recordings, transcripts, devices or users.
We keep that record against your key: the device ID, name, platform, version, and when the server was activated and last seen. It’s what makes the two-server limit work, and it’s what the My servers page shows you. We don’t use it for anything else.
Your IP address is used while the request is handled, to limit how often anyone can try keys. It’s stored only as a keyed one-way hash in a short-lived counter, which is deleted after it expires, normally within a day.
The service’s logs record that a request was made, the license ID it concerned and the platform. They don’t record the key, the server’s name or your email address, and they’re kept for 30 days.
Emails about your key
Your key is emailed through Resend, which sends mail on our behalf. Resend receives your email address and the message, and keeps delivery records under its own privacy policy.
The resend page sends keys only to the address they were bought with. It answers the same way whether or not an address has bought anything.
Downloading and updating
The download buttons on this site pass through our server on the way to the file, which adds one to a count of downloads for that day, version and type. The count is only a number and isn’t linked to you. Your IP address is used the same way as for activation, so one address can’t run the count up.
When you press Check for updates in the Sentito Server app, it reads one small file, scribe.dwmmholdings.com/releases/latest.json, to see whether a newer version exists. The request carries nothing but what any web request does. The app never downloads or installs anything by itself.
The speech models and the language model are downloaded when you set a server up, from where their publishers host them: Hugging Face for most, and GitHub for the speaker-recognition model. The search model comes from Hugging Face too, the first time the server indexes a meeting or runs a search. Each sees those requests under its own privacy policy. They’re ordinary file downloads and carry nothing about your recordings.
Reaching your server from outside
Remote access is yours, not ours. There’s no relay: your phone connects straight to your server over HTTPS, and checks your server’s own key, or the certificate on your own domain if you set one up.
With UPnP on, which it is unless you turn it off, the server asks your router to forward one port to it, and reads your public address from the router. That conversation stays on your local network, between the server and your router. If UPnP is off or the router refuses, you can have the server look up its public address from a service you choose, such as api.ipify.org; that service sees your address, as any website does. It’s off unless you set it.
If you use your own domain, the server gets a certificate for it from Let’s Encrypt, which sees the domain name and your public address. If you set up dynamic DNS, the server sends your public address, with the credentials you gave it, to the provider you chose (Cloudflare, Duck DNS, or a dyndns2 provider such as No-IP or Namecheap) whenever the address changes. None of this goes to DWMM Holdings.
On your local network
Sentito Server doesn’t announce itself on your local network. Your phone learns where the server is from the pairing code you scan.
The iPhone and iPad app can look for Sentito servers on your network using mDNS (Bonjour), which is why iOS asks it for local network access. Looking sends a question on your network and nothing about you or your recordings.
Reaching the server isn’t enough to use it. A phone needs a pairing code from you, and a browser needs your password.
Checking your licence
Once a server is activated, your Sentito server asks scribe.dwmmholdings.com whether its key has been revoked: when it starts, and then about once a day while it’s online. The request carries the signed license the server already holds, which names the license ID and the server’s device ID, and nothing else. The answer is only whether the key was revoked.
We don’t keep a record of these checks. The service stores nothing about them, not the time, the version or your IP address, not even as a hash, and doesn’t write them to its logs. Its rate limit is counted in the service’s memory only. Like any web request, it passes through our hosting providers, whose standard request logs can include your IP address. If a check fails, for example because you’re offline, nothing changes.
Trial reports
When a trial starts on a new install, your Sentito server sends one anonymous report to scribe.dwmmholdings.com. It contains the product, Sentito’s version, the operating system (macOS or Windows, or Linux for a server in Docker) and an install ID: a random number made on that install for these reports and nothing else. It sends one more if that install later activates a key, or if its trial ends without one.
The install ID isn’t linked to your key, your device ID, your name, your email address or your IP address. We keep it only as a keyed one-way hash, so each install is counted once, and delete it after about 13 months. What we keep longer is counts per day, version and operating system. The service doesn’t store your IP address, not even as a hash: its rate limit is counted in memory only. Like any web request, it passes through our hosting providers, whose standard request logs can include your IP address.
You can turn trial reports off: clear the checkbox under Trial reports on the desktop app’s Licence screen, or the same checkbox in the Licence section of the web app’s Settings. While they’re off, nothing is sent, and a report still waiting to be sent is dropped, not sent later.
Sentito for iPhone and iPad, and the web app
The iPhone and iPad app talks only to your own server: it sends it what you record, the notes you type and the questions you ask. It sends nothing to DWMM Holdings. It has no license, no activation, no update check and no analytics. It uses the microphone while you record, the camera to scan the pairing code, and your local network to reach your server at home.
The app also sends your server the audio and video files you share to Sentito from other apps, and the vocabulary, summary templates and speaker names you set.
If you allow it, the app reads your calendar on the device to name a recording after the meeting it was made in, to offer the people invited when you name speakers, and to remind you to record when a meeting starts. The meeting’s title and the invitees’ names, or their email addresses where the calendar has no name, go to your server with the recording. If you choose to add a summary’s action items to Reminders, the app adds them to the Reminders list you pick, with the recording’s title and a link back to it in Sentito, and that list syncs the way your Reminders already do, such as through iCloud. Notices that a transcript is ready come from the app checking your server in the background, not from a push service.
The web app is served by your server, to browsers on your local network and, through the port your router forwards, from outside too. It talks only to your server. Signing in sets one cookie, which keeps you signed in to your server and isn’t used for anything else.
Recording on the computer
When you record a meeting in the Sentito Server app, it uses your microphone and the sound your computer plays, which is why macOS asks for both and Windows asks for the microphone. The recording goes to the server on the same computer and nowhere else.
On a Mac, if you allow it, the app reads your calendar to name a recording after the meeting it was made in, and the meeting’s title and invitees go to the server with the recording. On a Mac or a Windows PC, if you turn on recording suggestions, the app notices when another app starts using the microphone and offers to record. It doesn’t record by itself, and what it notices stays on the computer.
Features that send things where you choose
Share links, email delivery and webhooks are off until you use them, and none of them involve DWMM Holdings.
A share link lets anyone who has it read what you chose to share from one recording: its title, date, length and summary, and the transcript with speaker names and the audio if you included them. The page is served by your own server, so whoever opens it connects to your server and sees its address. Unless you’ve set up your own domain, their browser will warn about your server’s certificate. The link stops working when it expires, if you set an expiry, or when you revoke it.
If you set up email delivery, your server sends each new recording’s title, summary, action items, decisions and topics, with a link to the recording on your server, through the mail server you give it to the addresses you list. That mail server and those recipients receive it. If you set up a webhook, your server sends the same, plus the recording’s date, length and tags, to the address you give it, such as a Slack channel, and that service receives it under its own privacy policy.
What stays on your machine
Audio, transcripts, summaries, speaker names, search indexes and the questions you ask are stored on your server, in its own database and folders. Transcription, summaries and search run on the server, with no cloud APIs. Apart from the activation details, the licence check and trial reports, all described above, none of it is sent to DWMM Holdings.
Sentito doesn’t ask for your contacts, location or advertising identifier.
Network activity
Apart from activating or releasing a server, the licence check, trial reports, checking for updates, downloading the models, and the email and webhook deliveries you set up yourself, all described above, Sentito makes no Internet requests to us or to anyone else. Recordings go from your phone or computer to your server, and leave it only in the share links, emails and webhooks you choose to send. UPnP talks only to your router, and Let’s Encrypt and dynamic DNS are used only if you set up a domain. The licence check and trial reports are the only requests it makes to us by itself. There’s no advertising SDK and no third-party analytics.
Retention and deletion
Sentito keeps your data on your server, so deleting a recording there deletes it. Uninstalling the server and removing its data folder removes everything. DWMM Holdings has no copy of any of it.
The purchase and activation records described above are kept while the key exists. If you want the activation records for your key deleted, write to us; deleting them also frees the seats they hold.
Support messages
If you contact support, we receive whatever you choose to send, usually an email address and the details we need to answer you. We use it to reply, keep it only as long as reasonably necessary, and don’t sell it or use it for advertising.
Write to dmoore@
Changes
Changes are posted on this page with a new effective date. If a future version adds a feature that changes these practices, this policy and any applicable app store disclosures will be updated before that version is released.