CostCompass Privacy Policy
Effective Date: April 23, 2026 Last Updated: October 9, 2026
1. Introduction
CostCompass ("we", "us", or "our") is committed to protecting your privacy.
This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you access the CostCompass dashboard and associated services (collectively, the "Service").
By using the Service, you agree to this Privacy Policy.
2. Information We Collect
2.1 Information You Provide
Account Information: Name and email address.
Provider Credentials: API keys or OAuth tokens you connect so that CostCompass can retrieve usage data from third-party AI and compute providers on your behalf.
Support Communications: Messages, feedback, and other correspondence.
2.2 Information Collected from Third-Party Providers
When you connect a provider, CostCompass fetches:
- Token and request usage records
- Model names and request timestamps
- Cost metadata returned by the provider's API
We collect only the data necessary to display spend and usage insights. We do not fetch the content of your API requests or responses.
2.3 Information Collected Automatically
Usage Data: Interaction with features in the Service.
Log Data: IP address, browser type, device type, and timestamps.
2.4 Analytics and Cookies
Our public marketing and informational pages (for example, the landing, terms, and privacy pages) use Google Analytics, a web analytics service provided by Google LLC ("Google"). Google Analytics sets cookies and uses similar technologies to collect behavioral data about how visitors interact with these pages, which is transmitted to and stored by Google. This data may include:
- Pages viewed, time spent, and clicks
- Referring URLs and approximate geographic location (derived from IP address)
- Browser, device, and operating-system information
We use this information to understand site traffic and improve the Service. Google processes it in accordance with its own privacy policy (https://policies.google.com/privacy). You can opt out by installing Google's opt-out browser add-on (https://tools.google.com/dlpage/gaoptout), by blocking analytics cookies in your browser, or via a cookie-consent control where offered.
The signed-in CostCompass dashboard does not load Google Analytics. Analytics on the dashboard are limited to first-party instrumentation that does not load third-party scripts into the page that handles your provider credentials.
2.5 Crash & Error Diagnostics
Our native desktop clients (for example, the macOS menu-bar app) send crash and error diagnostics to Sentry, an error-monitoring service provided by Functional Software, Inc. ("Sentry"), so we can diagnose failures we would otherwise never see.
These reports are stripped of your credentials and usage data on your device before they are sent. What a report may include:
- Crash and error information, including stack traces
- Operating-system and app version
- A short trail of app-lifecycle events (for example, launch, quit, and refresh start/finish)
What a report excludes — removed client-side before transmission:
- Your provider API keys, vault password, and CostCompass API keys
- Any decrypted credentials or authentication tokens
- Your usage and cost data, and the network addresses your credentials are sent to
Sentry processes this diagnostic data in accordance with its own privacy policy (https://sentry.io/privacy/). This flow applies to the native clients only; the browser dashboard does not send this data.
2.6 Feedback Board
Our feedback board at feedback.costcompass.cc is run for us by Idle Signal, using its hosted feedback service, FNI. When you sign in to the board with your CostCompass account, we send Idle Signal an opaque account identifier, whether you are a CostCompass administrator, and a display name made from the part of your email address before the "@" (for example, jane.doe@example.com becomes "Jane Doe"). The board shows that display name next to the ideas and comments you post, so other people using the board can see it. We never send your full email address, and no usage, cost, or credential data. The ideas, comments, and votes you post there are stored by Idle Signal. If you have signed in to the board, we send that same identifier again when you export or delete your CostCompass account, so that Idle Signal can return or erase your board data. The board's typefaces are served by Google Fonts, so when a page of the board loads, your browser requests them from Google, which receives your IP address and standard request data (such as your browser type and the page that asked); no cookies are set and nothing you post is sent.
If you have signed in to the board and then delete your CostCompass account, we instruct Idle Signal to erase your identity on the board. If that request fails, we retry automatically and flag it on our service health monitoring for our team to resolve. Once erased, anything you posted there is no longer linked to you and is shown as coming from a deleted user. If you have signed in to the board, your feedback data is included when you export your account.
3. How We Use Your Information
We use collected information to:
- Fetch and display your usage and spend data from connected providers
- Aggregate and visualize cost trends across providers
- Provide account functionality
- Improve and maintain the Service
- Detect abuse and enforce our Terms
4. API Keys & Credential Storage
Your provider API keys are encrypted in your browser, with a vault password only you know, before they are sent to us for storage. We store only the encrypted result. We hold no key that can decrypt it, and your vault password is never sent to us.
When you refresh your usage, your browser decrypts the key and sends it to the provider through our broker, which holds it only for that one request. Credentials are never logged, and we share them only with the provider they belong to.
We use your credentials only to request read-only usage data from that provider. Our security page explains how this works in more detail.
5. Data Sharing
We may share information with:
Service Providers: Cloud hosting and infrastructure providers necessary to operate the Service, including Cloudflare, Inc. (network delivery and security).
Feedback Service Provider: Idle Signal operates our feedback board (FNI), as described in Section 2.6. It receives an opaque account identifier, your administrator status, and a display name made from the part of your email address before the "@", plus whatever you post on the board.
Analytics Providers: Behavioral and cookie data collected on our public pages is shared with Google (Google Analytics), as described in Section 2.4. This does not include your account credentials or provider data.
Diagnostics Providers: Crash and error diagnostics from our native clients are shared with Sentry (Functional Software, Inc.), as described in Section 2.5. This data is stripped of your credentials and usage data before it is sent.
Legal Compliance: If required by law or valid legal process.
Business Transfers: In connection with mergers, acquisitions, or asset sales.
Service Providers We Use
These providers process personal data on our behalf, only to operate the Service:
| Provider | Purpose | Data it receives |
|---|---|---|
| WorkOS, Inc. | Sign-in and account authentication | Name, email address, sign-in events |
| Cloudflare, Inc. | Network delivery and security | IP address and request data for traffic to our sites |
| Idle Signal | Our feedback board (FNI) (Section 2.6) | An opaque account identifier, administrator status, a display name from your email address, and what you post on the board |
| PostHog, Inc. | Product analytics in the signed-in dashboard | Page views and interaction events (credential fields are excluded) |
| Google LLC (Google Analytics) | Analytics on our public pages (Section 2.4) | Cookie identifiers, page views, device and browser data |
| Google LLC (Google Fonts) | Typefaces for our feedback board (Section 2.6) | IP address and request data when a board page loads its fonts |
| Functional Software, Inc. (Sentry) | Crash and error diagnostics from our native clients (Section 2.5) | Crash reports, OS and app version; credentials and usage data are removed first |
| Apple Inc. (Apple Push Notification service) | Push notifications to our native clients | Device push tokens and notification content |
We do not sell personal data.
6. Data Retention
Usage records and cost snapshots are:
- Stored until you disconnect the provider or delete your account
- Deleted when your account is deleted
Deleted data may remain in encrypted backups for up to six (6) months before permanent removal.
7. User Controls
You may:
- Disconnect any provider and remove its stored credentials at any time
- Export your stored usage data
- Delete your account and all associated data
Requests can also be sent to support@costcompass.cc.
8. Security
We use reasonable administrative, technical, and physical safeguards.
- All data transmission uses HTTPS encryption.
- Credentials are never included in API responses.
- Sign-in is handled by WorkOS AuthKit. A session lasts at most 90 days, and we re-check it with WorkOS every 15 minutes. Signing out ends the session on our server right away.
No system can guarantee absolute security. If personal data is exposed, we will tell affected users within 72 hours of confirming it.
9. International Transfers
Your data may be processed in the United States or other jurisdictions where our service providers operate.
By using the Service, you consent to these transfers.
10. Children's Privacy
The Service is not intended for children under 13. We do not knowingly collect data from children.
11. Third-Party Links
Our Service may contain links to third-party websites. We are not responsible for their privacy practices.
12. Changes to This Policy
We may update this Privacy Policy periodically. The "Last Updated" date reflects the most recent revision.
13. Contact Us
For privacy-related inquiries: