Privacy Policy

Last updated: July 24, 2026 · YelloWho is operated by KDO Services Inc., an Illinois corporation ("we", "us").

What YelloWho does

YelloWho synchronizes a company's driver and staff contact information from its fleet management platform (such as Samsara) into contact stores its team members choose to connect (such as Microsoft Exchange mailboxes or a company phone system), so that names appear on incoming calls.

Information we access and store

• Fleet data: driver names, phone numbers, vehicle assignments, tags and attributes, read from your fleet platform with your authorization. We store a synchronized copy of this roster to operate the service.
• Contact folders: with each team member's explicit consent, we create and maintain a dedicated contacts folder ("Drivers") in their mailbox. We only manage contacts we created; we do not read, modify, or delete personal contacts.
• Account data: names, email addresses, and authentication tokens for the integrations you connect. Tokens are stored server-side, encrypted at rest, and are never exposed to other users.
• Operational logs: synchronization activity (what changed and when) so administrators can audit the service.

What we do not do

• We do not sell or rent your data to anyone.
• We do not use your data for advertising.
• We do not read mailbox content — our Microsoft permission is limited to contacts.
• We do not share one customer's data with another. Each company's data is isolated.

Where data lives

YelloWho runs on Google Cloud / Firebase (United States). Integrations communicate directly with Samsara, Microsoft, Google, and your phone system provider over their official APIs.

How we protect your data

We apply the following technical and organizational safeguards to all data we handle, including sensitive data such as contact information and authentication tokens:

• Encryption in transit: all connections between your browser, our servers, and third-party APIs use TLS 1.2 or higher (HTTPS). We never transmit data over unencrypted channels.
• Encryption at rest: all stored data — rosters, configuration, tokens, and logs — is encrypted at rest with AES-256 on Google Cloud infrastructure, which is independently certified (SOC 1/2/3, ISO 27001).
• Credential protection: OAuth access and refresh tokens are stored in server-side documents that no client application can read; API client secrets are held in Google Secret Manager, never in code or configuration files.
• Access control: our database enforces deny-by-default rules — end users have no direct database access; every operation passes through server-side functions that verify the caller's identity and company membership. Each company's data is logically isolated; no customer can access another customer's data.
• Least privilege: we request the minimum API scopes needed (read-only access to fleet data; contacts-only access to mailboxes), and internal administrative access is limited to the service operator.
• Minimal retention: we store only the fields needed to render contacts (names, phone numbers, email, vehicle assignment, tags) — no location history, messages, or documents.
• Incident response: if we become aware of a security breach affecting your data, we will notify affected customers without undue delay and take prompt steps to contain and remediate it.

Google user data

When a team member connects a Google account, YelloWho requests the Google Contacts permission solely to create and maintain a dedicated "Drivers" contact group in that account. We create, update, and remove only the contacts we created, inside that group; we do not read, modify, or delete the user's other contacts. Google user data is never sold, never used for advertising, never used to train artificial-intelligence or machine-learning models, and is not read by humans except with the user's explicit consent for support, for security purposes, or where required by law.

YelloWho's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data retention and deletion

When a team member's access is revoked, the contacts folder or group we created is deleted from their account and their tokens are permanently discarded. When a company deletes its account (available self-service in Settings), its stored roster, configuration, contacts mappings, tokens, and member logins are deleted immediately. Residual copies in encrypted backups expire within 30 days. You may also request deletion of any data at any time by contacting us.

Your choices

Team members connect their own accounts and can disconnect at any time — by asking their administrator to revoke their seat (which removes the contacts we created and discards our access), or by revoking YelloWho's access themselves: in Microsoft account settings (Apps and services you've given access to) or in Google Account settings (Third-party apps & services). Administrators control which drivers and contacts sync to whom, and can disconnect the fleet platform or phone system integrations at any time in Settings.

Contact

Questions or requests: invites@yellowho.com

We may update this policy as the service evolves; material changes will be reflected on this page with an updated date.