This page describes the personal data Savi Gurus LLC handles when you visit savicomms.com, start a Savi Comms trial, pay for Savi Comms, or receive its updates. Savi Comms itself runs on your own Mac or Linux server. What your agents read and write stays in your installation and your own accounts, and it is not sent to us.
Last changed: 20 October 2026
Savi Comms is built and run by Savi Gurus LLC, Kirkwood, Missouri.
Questions about this page: support@savicomms.com.
The pages of savicomms.com that describe Savi Comms set no cookies and run no scripts. Every image and style on it comes from savicomms.com itself, and it has no forms.
The site is served through Microsoft Azure Front Door, which records each request: the page asked for, the time, and the network address it came from. Those records are kept for 30 days and then deleted.
Before a trial starts, your installation confirms your email address, so that each company gets one trial. There are two ways to confirm it.
Signing in with Google or Microsoft. Your installation opens the provider's own sign-in page and asks for your email address and nothing else. The provider sends back a signed token, and your installation passes it to our billing service with the trial request. The billing service checks the token and reads two things from it: your email address, and the provider's statement that the address belongs to you. At Google that statement is that the address is verified. At Microsoft it is that the account is a personal one, or, for a work account, that your organisation owns the address's domain. The token can also carry your name. The billing service does not read the name, and neither the billing service nor your installation keeps the token.
An emailed code. If you have neither account, the billing service emails a six-digit code to the address you type, and you type the code back. The email is sent through Azure Communication Services, Microsoft's email service. The billing service keeps only a fingerprint of the code, in its memory, for fifteen minutes or until the code is used. It also counts, in memory, the codes sent to each address, so that no address receives a flood of them. Neither is written to storage, and both are lost whenever the service restarts.
The trial record. Once your address is confirmed, the billing service records the trial on Stripe, as a customer record that is never billed. The record holds your installation's id, the day the trial started, a public key your installation made for itself, and the one entry that limits your company to one trial. For a company address that entry is only the domain, such as acme.com. For an address at a free mail provider such as Gmail, the entry is the address itself, with any tag such as +work removed. The record holds no name and no card. Trial records on Stripe are deleted 24 months after the trial ends.
Separately, our licence service keeps your installation's id and the day its trial started, in private storage on Microsoft Azure, so that reinstalling Savi Comms cannot start the same trial again. That record names no person and no email address. We keep that record with no end date.
The billing service also counts trial requests from each network address, in memory, and refuses more than twenty an hour from one address.
When you add a card, your installation sends our billing service its id, your company's name, your email address, the plan you picked, the number of agents, and its public key. The billing service opens a Stripe checkout page with these, and you enter your card on Stripe's page. Your card never reaches us. Stripe keeps your email address and payment details, and your subscription on Stripe carries the installation id, company name and public key. Our billing service has no database of its own.
After that, your installation reports to the billing service: its id, the number of agents billed, its Savi Comms version, the time, and a sequence number. Stripe sets your subscription to that number of agents.
Cancelling, changing your card and reading invoices all happen on Stripe's own billing pages. To reach those pages without your installation, you type your billing email address and Stripe sends you a one-time code. Stripe's own privacy policy covers what Stripe does with your data.
Billing records are kept for seven years, for tax and accounting.
A licence names your installation's id, the number of agents, the day it ends, its own id, and your installation's public key. It names no person and no email address. When a licence is first used, our services record the installation and key tied to it, with the time, in private storage on Microsoft Azure.
When your installation checks for or downloads an update, it sends our download service its licence or trial pass and its installation id. The download service logs each request: the file requested, the installation id, and whether the file was served. When it hands out the key that unlocks a release, it logs the installation id, the product and version, and the licence id. These logs are kept for 30 days and then deleted.
Nothing beyond the trial, billing, licence and update requests above. Savi Comms has an optional setting that sends a count of how often each of its permission checks refused something, with no message content and no file names. It is off unless you set it up.
Your agents use your own Anthropic account, and Anthropic bills you directly. What your agents send to Anthropic goes under your account, not ours.
We do not sell personal data. We share it only with the services named above, which handle it for us.
To see the personal data we hold about you, or to have it deleted, email support@savicomms.com. We answer within 30 days. People in the European Union and in California have these rights by law.
The date at the top of this page is the date it last changed.