RidgeVia

Crestcamp

Effective October 6, 2026

This policy covers the Crestcamp web portal (including "Sign in with Google" and the optional Google Drive, Gmail, and Calendar connection a practice can enable in Settings) and the Crestcamp Companion browser extension. Sections are labeled so you can find the one that applies to how you use the product.

At a glance: what we collect

A quick summary of every category of data Crestcamp handles. The sections below spell out the details for each one.

Data	Why we collect it	Who it's shared with
Account credentials Username, password (stored as a salted hash, never in plain text), linked Google identity if used	Sign you into your practice's Crestcamp account	Not shared with anyone
Patient health information Patient messages, AI triage results, health-agent chat content	Triage inbound patient messages and power the AI assistant your practice uses	Your practice's own staff; a small number of RidgeVia personnel when needed to support or secure the service (every access is logged); AI processing under signed HIPAA Business Associate Agreements (AWS Bedrock, OpenAI)
Google Drive, Gmail & Calendar content (optional, per practice) Files the assistant creates or a staff member selects through Google's picker; Gmail messages the assistant reads or drafts; calendar events it reads	Let the AI assistant look up or save files, read or draft email, and read the calendar when a staff member asks	Google, to service the request. Crestcamp never sends email or changes the calendar
Sign-in and security records Sign-in time, IP address, approximate location derived from the IP address, browser	Detect and investigate suspicious sign-ins; the security audit trail	IPinfo, which looks up the approximate location of an IP address
Billing details (practices on a paid plan) Billing contact and address; card brand, last four digits, and expiry (the full card number goes straight to Stripe and never reaches Crestcamp)	Charge the subscription, calculate tax, send receipts	Stripe, our payment processor
Session data Session token, "remember this browser" MFA token	Keep you signed in without re-entering credentials on every request	Stored only in your browser; not shared with any third party
Audit and activity logs Who accessed what, and when	Security, the HIPAA audit trail, troubleshooting	Not shared; kept per your practice's own data retention policy

Nothing here is ever sold or used for advertising. See "Who we share it with" below for the full list of service providers involved in running Crestcamp itself.

What Crestcamp is

Crestcamp is an admin portal and AI assistant, built by RidgeVia, for staff at direct primary care practices. It helps a practice triage patient messages and gives staff a chat assistant that can answer questions about their own patients and practice data. Crestcamp Companion is a companion browser extension that puts the same assistant one click away without leaving another tab. Both are operated by RidgeVia for the practices it serves; neither is offered to the general public.

Accounts and sign-in

Staff sign in with a username and password issued by their practice's Crestcamp administrator, or with Sign in with Google. Signing in with Google shares your name, email address, and profile photo (Google's basic openid, email, and profile scopes only) so Crestcamp can match you to your existing staff account by email. It does not create a new account on its own, and it never receives or sees your Google password. We link your account to that Google identity ("account linking") so future sign-ins are one click; you can only sign in this way if your email already matches a staff account your practice has provisioned and Google has verified that email address.

Patient information

A practice's message history, AI triage results, and chat conversations with the assistant may reference patients and their health information. This data is encrypted at rest, isolated per practice at the database level so no query can reach another practice's data, and processed only by AI models running under a signed HIPAA Business Associate Agreement (AWS Bedrock, and the OpenAI API). It is never sent to a general-purpose consumer AI product, and never used to train AI models. Access is limited to that practice's own staff and to a small number of RidgeVia personnel who need it to support, maintain, or secure the service under our Business Associate Agreement with the practice. Every access is logged for audit purposes. When the assistant would act outside the chat (post an internal note, save a file, or draft an email), it shows the staff member exactly what it will do and waits for them to confirm.

If you are a patient of a practice that uses Crestcamp, your practice controls your health information, and its own notice of privacy practices applies. Please contact your practice to see, correct, or ask questions about your information; we help practices answer those requests.

Google Drive, Gmail, and Calendar connection (optional, per practice)

A practice administrator can optionally connect a Google account in Settings so the AI assistant can look up or save Drive files, read or draft Gmail messages, and read calendar events when a staff member asks it to. This is off unless a practice's admin turns it on, and only one Google account is connected per practice, not per staff member.

When connected, Crestcamp requests:

Drive access limited to files the app touches (drive.file scope): Crestcamp can only see files it created itself or that a staff member explicitly selected through Google's file picker. It cannot browse, list, or read the rest of that Google account's Drive.
Gmail read access (gmail.readonly): lets the assistant search and read messages in the connected mailbox when asked.
Gmail draft access (gmail.compose): lets the assistant create drafts in the connected mailbox. Crestcamp never sends email on your behalf. Every message the assistant prepares is saved as a draft; a staff member must open Gmail themselves and click Send.
Calendar read access (calendar.readonly): lets the assistant and the Calendar tab read events on the connected account's calendar. Crestcamp never creates, changes, or deletes events.
Your email address (userinfo.email): so Settings can show which Google account is connected.

Your practice is responsible for having a HIPAA Business Associate Agreement with Google (Google Workspace) before connecting an account that will hold patient information; Crestcamp asks the administrator to confirm this when connecting.

The connection is stored as an encrypted refresh token tied to that practice. Any staff member can disconnect it at any time from Settings, which revokes Crestcamp's access to that Google account immediately.

Crestcamp Companion (browser extension)

What this extension is

Crestcamp Companion is a Chrome extension that adds a side panel for asking Crestcamp's AI assistant questions about a patient without leaving the current tab. It is distributed privately to staff of the practices RidgeVia operates Crestcamp for.

The extension has exactly one purpose: let a signed-in staff member send chat messages to their practice's own Crestcamp account and read the assistant's replies. It does not read, modify, or inject anything into the content of any website, including Spruce or any other page open in your browser.

Information the extension handles

Account credentials. The username and password you enter on the extension's login screen are sent directly, over HTTPS, to your practice's Crestcamp server to sign you in. The extension itself does not store your password: only the short-lived session token Crestcamp issues in return is saved, in Chrome's extension-private local storage (chrome.storage.local), which no website, including Spruce, can read.

Session token. Used to authenticate each request the extension makes to Crestcamp. It expires automatically (Crestcamp's standard session length) or is cleared immediately if you log out or if Crestcamp reports the session invalid.

Messages you send to the assistant. Text you type into the chat, which may reference a patient and their health information, is sent to your practice's own Crestcamp server to generate a response. The extension does not retain this text after the panel is closed; any server-side storage of it follows the same practices described under "Patient information" above.

What the extension doesn't collect

The extension has no access to the content of any web page, including Spruce. It never reads your browsing history, location, or any other site's data.

The current tab's address, only when you ask. When you press one of the suggestion buttons (such as "Check tone"), the extension reads the web address of the tab you're on (not the page itself) to see whether it is a Spruce conversation, so the assistant knows which conversation you mean without you typing a name. It reads nothing when you don't press a button, and the address is used only for that request.

Permissions it requests: access to your Crestcamp server's address (to sign in and chat); storage (to keep your session token in extension-private storage); sidePanel (to show the panel); identity (for Sign in with Google); and activeTab (to read the current tab's address as described above, only after you press a button).

How this information is used

Solely to authenticate you, run your practice's triage and chat features, and, if connected, act on the Drive/Gmail requests a staff member makes through the assistant. Nothing you enter is used for advertising, analytics unrelated to the product, or to train any model outside the AI pathway your Crestcamp deployment already uses.

Who we share it with

Data is never sold and never shared with advertisers. We use the service providers below to run Crestcamp, and no one else.

Providers that may handle patient information, each under a signed HIPAA Business Associate Agreement: Amazon Web Services (hosting, database, and AI processing through Amazon Bedrock) and OpenAI (AI processing through the OpenAI API).

Services your practice connects, under the practice's own agreements with them: its patient messaging service (Spruce) and, if connected, its Google account.

Providers that never receive patient information: Stripe (payments and tax), Resend (account emails such as setup links and billing notices), IPinfo (approximate location of sign-in IP addresses), Have I Been Pwned (when you choose a password, only the first five characters of its SHA-1 hash are sent, to check it against known data breaches), Render (hosts the public website and the portal's code), and Google Fonts (your browser loads the site's fonts from Google).

Security and retention

All traffic is encrypted in transit (HTTPS). Patient information and any stored Google refresh token are encrypted at rest. Session tokens live only in your browser's storage and are removed on logout, on expiry, or if you remove the extension; changing your password or choosing "Sign out everywhere" ends every session on every device. Patient information is kept according to the retention schedule we provide to your practice, and returned or destroyed when the practice stops using Crestcamp, as our Business Associate Agreement requires.

Your choices

You can end your session at any time, disconnect a linked Google account or the Drive/Gmail connection from Settings, or remove the extension entirely from chrome://extensions, which deletes its locally stored session token immediately.

Children's privacy

Crestcamp and Crestcamp Companion are workplace tools for verified practice staff accounts and are not directed at, or knowingly used by, children.

Changes to this policy

If this policy changes, the effective date above will be updated. For a material change we'll give notice before it takes effect, and Crestcamp will ask staff to review it.

Contact us

Questions about this policy, or requests regarding your data, can be sent to ridgeviallc@gmail.com.