Privacy policy

This policy explains what Zuse Live Inc., a Delaware corporation ("Zuse", "we", "us"), collects and holds when it runs the service, why, who receives it, and what you can ask us to do about it. Zuse is the website, console, API, MCP server and recruiting workspace that link to this policy.

Two groups of people are covered, and their sections are separate:

• People who use Zuse: visitors to the site and people with an account.
• Licensed professionals in the index: people whose public license record Zuse holds, whether or not they have ever used Zuse.

Zuse is a service for businesses. It is not meant for personal, family or household use.

1. What this policy does not cover

Our customers decide what they do with the results Zuse gives them, such as contacting a person about a job. We do not control that use, and their own privacy notices apply to it. Our Terms of service limit what customers may do with results.

2. Information about people who use Zuse

What you give us

• Account details. Your name and email address: from Google when you sign in with Google, or as you type them when you sign up with an email and password. Sign-in is handled by WorkOS, which keeps your password. Zuse passes it to WorkOS when you sign in and never stores it.
• Teams. The names of teams you create, who is in them, and the email addresses you invite. Each team is also kept at WorkOS (its name and members), and WorkOS emails each person you invite a link to join, naming you and the team.
• Messages to us. What you send through the contact form, a booking request, or email: usually your name, email address, company and the message.
• Your team's records. The people your team has researched and what that research found, whichever way it was asked for (the API, the console, the MCP server, Slack or the recruiting workspace); and, if you use the workspace, the workspaces you create, the people you shortlist, and their stage and notes. This content belongs to the team it was saved in. Everyone in that team can see and change it, in the workspace and through Zuse in Slack if the team has connected it. It is not shared with other customers: another customer who saves the same licensed person starts from the license record and sees none of it.

What is created when you use Zuse

• API keys. Stored only as a one-way hash, with a short prefix so you can tell keys apart.
• Usage records. For each metered request: which operation, when, what it cost, how many records it returned, which key and team made it, and, for a location search, a keyed fingerprint of the search area. A usage record does not hold the name, license number, ZIP code or coordinates you searched for; those are in the request history, below, for 30 days.
• Request history. A line for each request your team makes: when, which operation, what was asked for (a ZIP code and filters, or a person's name), how it ended, how long it took, what it cost and how many records came back. It is what the console's Request history page shows. Only members of your team can see it, and each line is deleted after 30 days.
• Limit events. When a rate limit is reached or an account is restricted, we record the account, the calling IP address, and what was reached.
• Stored answers. A response sent with an Idempotency-Key is kept for 24 hours so a retry can be answered without a second charge.
• Server logs. The IP address, time, path and status of each request. Query strings are removed before a request is logged, because they can contain a person's name.

If you connect Slack

Connecting a Slack workspace is optional. If a team does, we store the workspace's id and name and an access token for it, encrypted. Slack sends us the messages that mention Zuse, direct messages to Zuse, and replies in threads Zuse has answered in. We use them to answer and do not keep them. A message addressed to Zuse that is not one of its commands is sent to OpenAI to work out what is being asked, and the figures of a result table are sent to OpenAI to word the sentence above it. Background and intro notes, and replies in a thread that are not addressed to Zuse, are not. We keep the list last shown in a thread for 24 hours, so a follow-up knows what it refers to. We keep the Slack member id of each person Zuse has welcomed, the first time they open its Messages tab, so they are not welcomed twice. When someone in Slack shortlists a person, changes a stage, creates a workspace or asks for research, that is saved on the team's records, together with the name of the person who did it. Their name is the only thing we read about a Slack member, and we read it only for that. Answers are posted to Slack, which holds them under your Slack workspace's own settings.

Cookies and browser storage

Zuse uses no advertising trackers. It uses PostHog for product analytics and error reports: which pages are visited, which buttons are pressed, how fast pages load, and the technical details of an error when a page breaks, so we can see what works and fix what does not. The text on a page is never sent, nor the address of a Zuse Talent profile, nor what you search for. A signed-in account is known to PostHog by an id and its kind (practice, developer or Talent), never by its name or email. Nothing is recorded if your browser asks sites not to track you (Do Not Track). You can turn analytics off at any time with Cookie settings at the foot of every page on zuse.live; the choice is kept in this browser.

Maps are drawn with image tiles that your browser requests directly from OpenStreetMap. OpenStreetMap therefore sees your IP address and the area of the map on your screen. Nearby clinics also lists clinics from OpenStreetMap's open data (© OpenStreetMap contributors), which Zuse downloads in advance: a search sends nothing about you to OpenStreetMap.

3. Information about licensed professionals in the index

What the index holds and where it comes from

Zuse keeps a copy of license records that state licensing boards publish as public records. Today that is the veterinary records published for Alabama, Arizona, Arkansas, California, Colorado, Connecticut, Florida, Idaho, Illinois, Iowa, Kansas, Maryland, Massachusetts, Michigan, Mississippi, Missouri, Montana, Nevada, New Jersey, Oregon, Rhode Island, South Dakota, Vermont, Washington, West Virginia, Wisconsin and Wyoming, by each state's board, on the state's open-data site, or from the board's own public directory. For each license the index holds what the board publishes: the licensee's name, license number and type, status, issue and expiry dates, any disciplinary notation the board shows, and the address of record where the board publishes one. Phone numbers and email addresses that some boards publish are not kept. The index is refreshed from the board, so a change at the board replaces what we hold.

Zuse also reads the public directories of a few professional bodies (specialty colleges, a technician specialist list, a state technicians' association and a practice managers' association) whose terms allow it. From them it keeps the name, the credential, and the city and state where the directory gives them, and attaches the credential to a license only when the match is not in doubt.

The street address is used to place a record on the map and to link a person to a practice at the same address. Zuse does not return street addresses to customers. Locations in results are at the level of a city and ZIP code.

Clinic team pages and web searches

Zuse reads the staff pages that veterinary clinics publish on their own websites, where the site allows it (its robots.txt and terms are checked first), and links each person a page lists to their license, so the index knows where they work. For people whose board publishes no address, and to settle which records belong to whom, Zuse also runs web searches on a person's name, profession and licensing state through search providers (Tavily, TinyFish). It keeps the passages of the results that are about that person, with their links, for Zuse's own team to check records against, and it may keep the town and practice a result names them at, shown as reported, with its source. These are used to keep the index accurate. They are not sold, not pooled into a contact database, and not returned to customers as search results.

Enrichment

When a customer asks Zuse to enrich one person, Zuse sends that person's name and locality to a research provider, which searches the public web for professional information: current employer, education, public professional contact details, and public profiles. Each finding is returned with the page it came from. The result goes to the customer who asked for it. It is saved on that team's own records, so the team can read it again without it being researched, or paid for, twice; it stays there until the team's account is deleted. We do not pool enrichment results into a shared contact database, and we do not return one customer's results to another.

Enrichment is a best-effort reading of the public web. It is labeled as derived, and it can be wrong.

Contact details

When a customer asks Zuse for a person's contact details (Reveal), or asks a web search to add them, Zuse sends what it already holds about that person (name, city and state, employer, school, public profile address, and any email or phone already on the team's record) to People Data Labs, a contact-data provider. People Data Labs returns the email addresses and phone numbers it holds for that person, which can include personal ones as well as work ones, together with the other professional details in its record. What it returns is kept on the records of the team that asked, and only there, until that team's account is deleted. It is not pooled into a shared database or returned to any other customer, and the team pays for each person it looks up.

Why we hold it

So that hospitals, recruiters and the software they use can find licensed professionals to offer work to, and can see that the people they contact hold a current license. Zuse is not a background check and is not offered for deciding whether to hire a particular person.

If you are a licensed professional

Email privacy@zuse.live from an address we can confirm is yours, and tell us your name, license number and state. You can ask us to:

• tell you what Zuse holds about you;
• correct a record that does not match your board's record;
• stop returning your record in location searches, and stop running enrichment on you.

Your license record itself is published by your board, and a correction to it has to be made there. Once the board's record changes, ours follows at the next refresh.

4. How we use information

• To run the service: answer requests, show results, keep you signed in.
• To meter usage and apply credit.
• To enforce limits and to detect and stop abuse, including bulk copying of the index.
• To answer support requests and tell you about changes to the service.
• To keep the service secure and to meet legal obligations.

We do not use account data or your searches to train machine-learning models, and we do not use them for advertising.

5. Who receives information

Service providers. Companies that process data for us, only to provide their service:

Your team. People on a team see that team's API keys (never the secret), and its usage broken down by person.

Customers. License records and enrichment results are what the service provides, so they are disclosed to the customers who request them, under the limits in our Terms of service.

Legal and safety. We disclose information when the law requires it, or when it is needed to protect people, our rights, or the security of the service.

A change of ownership. If the business is sold or merged, information moves to the new owner under this policy.

We do not sell the personal information of people who use Zuse, and we do not share it for advertising.

6. Google user data

If you sign in with Google, Zuse receives your name and email address, and nothing else from your Google account: Zuse does not ask for access to your email, calendar or files. Zuse's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• It is used only to sign you in and to name your account.
• It is not used for advertising, and it is not sold.
• It is not used to train general-purpose machine-learning models.
• No person at Zuse reads it, unless you ask us to for support, it is needed for security, or the law requires it.

You can remove Zuse's access at any time from your Google account's security settings.

7. How long we keep it

8. Your choices and rights

You can ask us to show you the personal information we hold about you, correct it, or delete it, and to delete your account. Email privacy@zuse.live. We answer within 45 days, and we will not treat you differently for asking.

Privacy laws in some states, including California and Texas, give residents specific rights to access, correct, delete and obtain a copy of their personal information, and to appeal a refusal. Use the same address for any of these. If we refuse a request, we will say why and how to appeal. An agent may make a request for you if they can show you authorized it.

9. Security

API keys are stored as hashes, sessions are signed, the service is served over TLS, and access is limited by account and by team. The details, including what is not in place yet, are on the Security page. No system is perfectly secure, and we cannot promise that ours is.

10. Where it is processed

Zuse is hosted in the United States. If you use it from another country, your information is processed in the United States.

11. Children

Zuse is for businesses and is not directed to anyone under 18. We do not knowingly collect information from children.

12. Changes to this policy

When this policy changes, we update the date at the top. If a change is significant, we also say so on the site or in the console before it takes effect.

13. Contact

Zuse Live Inc. is responsible for the information described here.

Zuse Live Inc.
8 The Green STE A, Dover, DE 19901
Email: privacy@zuse.live