How to read this list: anything marked Being built is not yet in the product; everything else describes what is in place today.
1. Purpose and change notification
Valutare, Inc. ("Valutare") engages a limited set of third-party service providers ("subprocessors") to deliver the Valutare performance-management platform. This register lists each subprocessor, the service it provides, the categories of customer personal data it may process, its processing location, and the transfer mechanism relied upon. It is incorporated by reference into the Valutare Data Processing Agreement ("DPA") as Annex III.
Subprocessors fall into two classes:
- Infrastructure subprocessors (Section 2) — engaged for all customers as part of operating the platform.
- Integration subprocessors (Section 3) — engaged only when a customer administrator or individual user connects the corresponding integration.
Change notification. Valutare will give at least 30 days' advance notice (by email to the customer's designated contact) before engaging a new subprocessor or materially expanding the scope of an existing one. During the notice period, customers may object as provided in the DPA. Removals and non-material updates (e.g., a vendor name change) may be reflected without advance notice.
2. Infrastructure subprocessors
| Subprocessor | Service provided | Data categories processed | Processing location | Transfer mechanism |
|---|---|---|---|---|
| Google Cloud Platform (Cloud Run, Cloud SQL for PostgreSQL, Memorystore for Redis, Secret Manager, Cloud Storage) | Application hosting, managed database, cache, secrets management, file storage | All customer data processed by the platform, including personal data of customer personnel (profiles, goals, feedback, review content). Personal-data fields carry AES-256-GCM field-level encryption at rest, in addition to provider disk encryption. | United States | Standard Contractual Clauses, and/or other safeguards under Chapter V of the GDPR, as applicable |
| Google (Gemini API) | AI-assisted features (coaching, drafting, summaries), translation, and the wellbeing check that decides whether to show a support message. Today it handles every AI request | Prompts derived from customer data. Before any prompt leaves the platform, Valutare's AI gateway automatically detects personal names and replaces them with placeholders. No individual's recorded protected characteristics are sent. | Google's Gemini API (Google-operated locations). Being built (before our first customer goes live): moving to Google Cloud Vertex AI in the United States | Google Cloud Data Processing Addendum (incorporates Standard Contractual Clauses) |
| Anthropic (Claude) | AI-assisted features; which provider handles a request depends on the feature and the language. Not used in production today | Prompts derived from customer data, with names replaced by the gateway as above | United States | Data-processing terms (incl. SCCs) — execution in progress |
| Mistral AI | AI-assisted features for some European languages. Not used in production today | Prompts derived from customer data, with names replaced by the gateway as above | European Union | Data-processing terms (incl. SCCs for any third-country transfer) — execution in progress |
| Resend | Transactional email delivery (notifications, data-export delivery links) and trust center email | Recipient names, email addresses, notification content | USA | Data-processing terms (incl. SCCs) — execution in progress |
| Cloudflare (R2 object storage) | Temporary storage of GDPR data-subject export archives, delivered to the requesting user via time-limited links | Export archives, which contain the requesting user's personal data held by the platform | Global (Cloudflare network) | Data-processing terms (incl. SCCs) — execution in progress |
| Sentry (Functional Software, Inc.) | Application error monitoring | Error and performance-monitoring events. Before an error event leaves the platform, personal data is scrubbed from it. | USA | Data-processing terms (incl. SCCs) — execution in progress |
| PagerDuty | Operational incident alerting (critical security alerts) | Alert metadata, which may include user and tenant identifiers of customer personnel and technical details of the request that raised the alert | USA | Data-processing terms (incl. SCCs) — execution in progress |
| Slack (Salesforce, Inc.) | Operational security alerting — critical and high-severity security alerts are posted to Valutare's own internal Slack workspace via an incoming webhook | Alert metadata, which may include user and tenant identifiers of customer personnel and technical details of the request that raised the alert | USA | Data-processing terms (incl. SCCs) — execution in progress |
How long AI providers keep requests. Providers may keep requests for a limited period to monitor abuse. None may use them for training. Periods are from each provider's published terms (checked October 14, 2026).
| AI provider | Retention of requests and responses |
|---|---|
| Google (Gemini API) | Kept for a limited period to detect abuse, under Google's terms for paid Gemini API services; Google does not use them to improve its products. Being built (before our first customer goes live): on Google Cloud Vertex AI in the United States, cached for up to 24 hours to serve requests, then deleted; Google may also log requests to detect abuse, as its Cloud terms allow |
| Anthropic (Claude) | Deleted within 30 days; kept up to 2 years only if Anthropic's safety systems flag a request as breaking its usage policy |
| Mistral AI | Kept for 30 rolling days to monitor abuse, then deleted; none if zero data retention is active on our account |
Note on Slack. The Slack row above covers Valutare's own operational alerting channel — it applies to all customers and is unrelated to the customer-optional Slack integration listed in Section 3, which processes customer workspace data only if a customer connects it.
Customer data is hosted in the United States. EU hosting will be offered to EU customers once EU data storage, AI processing in the EU and an EU data protection officer are in place. Being built: a separate instance (its own service and database) for each customer. Today, Google's Gemini API handles every AI request; once Anthropic and Mistral AI are in use, which AI provider handles a request depends on the feature and the language. Every AI provider is engaged under terms that bar training on customer data. Where customer personal data crosses a border to a subprocessor, transfers are governed by the mechanism recorded per vendor above. Google Cloud Platform and Google's AI services operate under Google's published Cloud Data Processing Addendum (which incorporates Standard Contractual Clauses); for vendors marked "execution in progress," the data-processing terms — which will incorporate SCCs — are being finalized.
3. Integration subprocessors (active only on customer connection)
The providers below process customer data only if a customer connects the corresponding integration. Each user connects their own work account (the customer's IT administrator may need to approve Valutare first); once Slack approves Valutare, Slack is installed once by the customer's Slack administrator and each user then links their account. Access is read-only metadata: who, when and with whom. Valutare never stores or uses email bodies, message text, file contents, recordings or transcripts; where a provider includes message text with the details Valutare uses, Valutare discards it on receipt. Valutare never sends email or messages as a user, and posts its own notifications only where the customer's administrator sets it up. Disconnecting an integration stops collection and deletes its stored data within 30 days. Being built: deletion of all Slack data within 14 business days after Valutare is removed from a Slack workspace.
| Provider | Integration(s) | Connected by | Data in scope when connected | Processing location | Transfer mechanism | Status |
|---|---|---|---|---|---|---|
| Google (Google Workspace) | Google Calendar; Gmail; Google Drive; Google Meet | Individual user | Calendar: meeting times, organizer, invitees and responses (titles only if the customer turns them on; never invitation text). Gmail: sender, recipients, time and thread of each message (subject lines only if the customer turns them on; never bodies). Drive: file names, owners, when the user last edited a file, and who it is shared with (never contents). Meet: attendance for meetings the user organized (never recordings or transcripts). | Provider-operated regions (per provider terms) | Standard Contractual Clauses, and/or other safeguards under Chapter V of the GDPR, as applicable | Available |
| Microsoft (Microsoft 365) | Outlook calendar and mail; OneDrive; Microsoft Teams | Individual user | Calendar and mail: as for Google. OneDrive: file metadata as for Drive. Teams: who sent a chat message and when; attendance for meetings the user organized. Being built: in teams that add the Valutare Teams app, who posted in channels and when, and Valutare's own notifications through the Valutare Teams app or a webhook the customer creates. | Provider-operated regions (per provider terms) | Standard Contractual Clauses, and/or other safeguards under Chapter V of the GDPR, as applicable | Available (channel activity being built) |
| Slack | Slack (workspace app) | Customer's Slack administrator installs; each user links | Valutare posts its own notifications to channels the administrator chooses. Being built: who posted in channels the Valutare app was invited to, and when. Never direct messages or a person's message history. | Provider-operated regions (per provider terms) | Standard Contractual Clauses, and/or other safeguards under Chapter V of the GDPR, as applicable | Built; offered once Slack approves Valutare |
| Zoom | Zoom | Individual user | Attendance for meetings the user hosted; never recordings, transcripts or chat. | Provider-operated regions (per provider terms) | Standard Contractual Clauses, and/or other safeguards under Chapter V of the GDPR, as applicable | Built; offered once Zoom approves Valutare |
HR, payroll and equity systems (connected by the customer's administrator):
| Provider | Data in scope when connected | Processing location | Status |
|---|---|---|---|
| BambooHR | Employee profile and work details (name, work email, job title, department, manager, location, start date, employment status); pay details where the customer uses compensation features | Provider-operated regions (per provider terms) | Built; offered once BambooHR approves Valutare |
| Rippling | As for BambooHR | Provider-operated regions (per provider terms) | Built; offered once Rippling approves Valutare |
| Workday | As for BambooHR | Customer's Workday tenant | Built; set up with the customer's Workday team during onboarding |
| HiBob, Gusto | As for BambooHR | Provider-operated regions (per provider terms) | Coming next |
| Carta | Equity grants and vesting, where the customer uses compensation features | Provider-operated regions (per provider terms) | Coming next |
| ADP | As for BambooHR | Provider-operated regions (per provider terms) | On our roadmap |
Instead of connecting an HR system, a customer can upload a spreadsheet of its people.
Planned connections (not active; no data flows to them today). "Coming next" means built and waiting for the provider's approval, or next in line to build; "On our roadmap" means intended but further out. Each follows the rules in Section 3 and the privacy policy from the day it is offered. Customers are told under Section 1 before any of them handles customer data.
| Type | Coming next | On our roadmap | Data in scope when connected |
|---|---|---|---|
| Project and task tools | Jira (Atlassian), Asana, Microsoft Planner, Google Tasks | monday.com, Notion, Linear, Trello, ClickUp, Smartsheet | For items assigned to or created by the user: type, status changes, due and completion dates; titles only if the customer turns them on. Never comments, descriptions or attachments |
| Code tools | GitHub | GitLab, Bitbucket, Azure DevOps | For changes the user opens or reviews: when opened, reviewed and merged, and by whom; titles only if the customer turns them on. Never code or review comments |
| Sales and support tools | — | Salesforce, HubSpot (as the customer's own system), Zendesk, Freshdesk, ServiceNow | For records the user owns or works on: stage or status changes, dates and outcome; record names and amounts only if the customer turns them on. Never email, call, note or ticket content |
Single sign-on. Customers can sign in to Valutare through OpenID Connect with Okta, Microsoft Entra ID or Google. These sign-in services are the customer's own, not Valutare subprocessors.
Company-wide connection by a customer's IT administrator, where a provider approves it, may be offered later; customers will be told under Section 1 before it is available.
4. Website and sales vendors (no customer data)
These vendors run our public website (www.valutare.ai), our trust center and our sales contacts. They receive information about website visitors and people who contact us, never the employee data customers put in the Service. They are listed here because our privacy policy points to this page.
| Vendor | Service | Data | Location |
|---|---|---|---|
| Vercel | Website hosting | Visitor IP address and request details | United States |
| Google Analytics | Website usage statistics (loads for European visitors only after they accept cookies) | Pages visited, approximate location, device and browser details, cookie identifiers | United States |
| HubSpot | Website forms, sales contacts and the events mailing list | Name, work email, company, role and messages people send us | European Union (HubSpot EU data center) |
| Calendly | Demo booking calendar | Name, work email, booking time, answers to booking questions, and the link's campaign tags | United States |
| Cloudflare (Turnstile) | Security check on website forms | Visitor IP address and browser signals | Global (Cloudflare network) |
| Supabase | Website assessment and survey answers; trust center accounts, NDA acceptance records and document access logs | Name, work email, company, answers, IP address | United States (to be confirmed) |
| Postmark | Email for website assessment results and event sign-ups | Recipient name and email, message content | United States |
5. Vendors that are NOT active subprocessors
For transparency: the following vendors appear in Valutare's technology stack but are not subprocessors — no customer data is transmitted to them today.
| Vendor | Status |
|---|---|
| Twilio | Not used; no customer data is sent to it |
| OpenAI | Approved AI provider; not used for customer data. If that changes, customers will be notified under Section 1 first, and processing will be in the United States |
If any of these services is activated in the future, customers will be notified under Section 1 before it processes customer data.
Two further clarifications privacy reviewers commonly ask about:
- Virus scanning of uploaded files runs on software self-hosted within Valutare's own infrastructure; no third party is involved.
- Valutare uses no payment processor and no third-party product-analytics vendor that processes customer data.
- Services that receive no customer content: Have I Been Pwned (checks a new password against known breaches using only the first 5 characters of a one-way hash of it), the push-notification services of users' browsers (notifications are encrypted and carry only a generic notice; the content is shown in Valutare after the user signs in), and public domain-registration lookups.