Privacy Policy
The data the Balt service processes, the purposes of that processing, who receives it, and how long it is kept.
This Privacy Policy describes how SKILLFORGE APP, a French simplified joint stock company (société par actions simplifiée) with a share capital of EUR 1,000, registered under SIREN 993 554 203, with registered office at 2 Rue des Commères, 78310 Coignières, France (the « Provider », « Balt », « we », « us »), processes personal data in connection with the Balt service, its website, and its communications.
It forms an integral part of the Agreement and applies together with the Data Processing Agreement, which governs the processing we carry out on Customer’s behalf as a processor. In the event of conflict between this policy and the DPA with respect to such processing, the DPA prevails. Capitalized terms have the meanings given in the Definitions.
1. Scope
This policy covers:
- (a) the Service, meaning the Balt Application, which takes part in conversations in connected Slack and Microsoft Teams workspaces and Discord servers, and in conversations held with it in the console;
- (b) the administration console, where Customer manages its organization, users, integrations, and billing;
- (c) the hire-balt.com website and its forms;
- (d) the communications we send to Authorized Users and to prospects.
It does not apply to processing that Connected Platforms (Slack, Microsoft Teams, Discord, Google Workspace, or others) carry out on their own behalf, which is governed by their own privacy policies.
2. Our two roles
Depending on the processing concerned, we act as a processor or as a controller.
2.1 Processor, for data processed through the Service
Customer Data, including conversation content, documents, Outputs, and content retrieved from Connected Platforms, is processed on Customer’s behalf and on its instructions. Customer is the controller; we act as a processor within the meaning of Article 28 GDPR, under the Data Processing Agreement.
Requests from data subjects concerning that data are addressed to Customer. Any request we receive directly is forwarded to Customer within the timeframes set out in Section 9 of the DPA.
On Customer’s instruction, we produce aggregated and anonymized statistics from the metadata of use of the Service alone, never from the content of conversations or documents (Section 2.3 of the General Terms). Once anonymized, they are no longer personal data.
2.2 Controller, for our own processing
We are the controller for account and customer relationship management, billing, security and abuse prevention, audience measurement on our website and console, and our commercial communications. That processing is described in Sections 5, 12, and 14.
3. The data we process
| Category | Data |
|---|---|
| Account and identity | Name, business email address, sign-in identifier, role, and organization of Authorized Users. Authentication is handled by our identity provider; we store no password and no third-party identity provider subject, and we mint no session of our own. |
| Workspace | Identifier and name of the connected Slack or Microsoft Teams workspace or Discord server, the conversations Balt has been added to, and the identifier, display name, and where applicable email address of participants. |
| Conversation content | Message text, author, timestamp, and thread, together with files and documents submitted to Balt (Section 4). |
| Console conversations | Messages exchanged with Balt in the console, with their title, author, and archiving date. Attached files are kept for thirty (30) days. |
| Balt’s memory | A workspace memory and skill documents, written by Balt from conversations without attribution to any person, and one private note per person, which runs started by other people cannot read. |
| Integration credentials | OAuth tokens and other credentials provided to connect a Connected Platform, protected by envelope encryption. |
| Technical logs | The log of events received from the platforms, access and execution logs, performance metrics, and incidents. Telemetry sent to our observability providers contains metadata and timings only. |
| Phone | The phone number an Authorized User has added in the console. Sending and receiving text messages is currently turned off. |
| Billing | Corporate name, billing address, VAT number, subscribed plan, Credit consumption, and invoices. Payment data is handled by our payment provider and does not pass through our systems. |
| Meetings | Where Customer has Balt join an online meeting: the audio or video recording, the transcript, and the meeting metadata. |
| Website and communications | Data entered in the website’s forms and when booking a call, audience measurement (Section 14), and deliverability data for our emails. |
A conversation held in the console is accessible only to the person who opened it, including within their organization. Where that person has consented to audience measurement, the session recording described in Section 14 may show it, unless their organization has connected a Google account.
Having Balt join a meeting is a High-Risk Action within the meaning of Section 3.3 of the Product Terms: it always requires explicit human approval and cannot be pre-authorized. Informing participants and obtaining their consent is Customer’s responsibility, under Section 2 of the Acceptable Use Policy.
4. What Balt reads in a conversation
Balt receives every message posted in the conversations it has been added to, including those not addressed to it. It responds to and acts on only the messages addressed to it; the others are recorded without being submitted to the model.
On joining a conversation, Balt reads the preceding ninety (90) days of its history once. Balt states this boundary rather than answering a question that goes beyond it.
Messages are stored as written, without filtering. Customer remains responsible for the data it submits to the Service, in particular under Section 3 of the Acceptable Use Policy.
5. Purposes and legal bases
For the processing for which we are the controller within the meaning of Section 2.2:
| Purpose | Legal basis |
|---|---|
| Providing and operating the Service, managing accounts, access, and support | Performance of the contract with Customer; legitimate interest as regards Authorized Users who are not parties to it |
| Billing, collecting amounts due, and keeping accounts | Performance of the contract; legal and tax obligations |
| Securing the Service and preventing fraud, abuse, and incidents | Legitimate interest in protecting the Service, its customers, and their data |
| Measuring audience in the console (Section 14) | Consent |
| Sending communications about the Service | Performance of the contract for service communications; consent or legitimate interest for prospecting, with a right to object at any time |
| Responding to requests from authorities and asserting our rights in legal proceedings | Legal obligations; legitimate interest |
No decision based solely on automated processing that produces legal or similarly significant effects concerning a person is taken in the course of this processing. Providing account data is necessary to enter into and perform the Agreement; without it, the Service cannot be provided.
For processing carried out on Customer’s behalf, the purpose is the provision of the Service as described in Annex I to the DPA, and the legal basis is the one Customer has determined as controller.
6. Artificial intelligence and model training
We do not train any model, ours or a third party’s, on Customer Data. Our contractual arrangements with each AI Subprocessor prohibit the use of Customer Data to train general-purpose AI models or for advertising purposes.
The content of a conversation is sent to the model provider only to produce Balt’s response. The model providers are those in the first row of the table in Section 7.1. None of them uses that content to train its models; each may retain it for at most thirty (30) days, solely to detect abuse.
If we become aware that a change to an AI Subprocessor’s terms materially reduces the level of protection of Customer Data, we will inform Customer through the process set out in Section 8 of the DPA.
6.1 Data received from the Google APIs
Balt’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements:
- that information is used only to provide and improve user-facing features prominent in the requesting Authorized User’s experience, such as answering a question about an email or placing an appointment in a calendar;
- it is neither used nor transferred to train, improve, or feed any generalized artificial intelligence model, nor for advertising purposes;
- it is transferred only to the subprocessors strictly necessary for those features, listed in Section 7, including the model provider that produces the requested answer;
- no individual at Balt reads it, except with the express prior agreement of the person concerned as to the specific items, where necessary for security purposes such as investigating a bug or abuse, where required by law, or where the data is aggregated and anonymized for internal operations. A session recording (Section 14) of an organization that has connected a Google account shows no text, only clicks and the layout of the screen, and a Balt administrator signs in as a person only for those purposes, each such sign-in being recorded;
- Customer may revoke access at any time from the Service settings or from its Google account, which deletes the associated tokens under Section 5.4 of the Product Terms.
What Balt accesses. With Gmail, the messages, labels and drafts of the mailbox a person connects. With Google Calendar, the events of the calendar they connect. Balt reads them to answer that person or to run a routine they turned on, and does not copy the content of a mailbox or a calendar.
What Balt does with it. A message is sent and a draft created only after the person approves it on a confirmation card. A routine the person turned on may apply a label to a message.
Where it is kept, and for how long. What Balt reads for a conversation or a routine run stays with that conversation or run, in the Service’s database, hosted in the European Union and encrypted at rest (Sections 8 and 11); Section 7 says where each subprocessor processes it. It is kept as Section 9 sets out for conversation content. Disconnecting an account deletes its access tokens and does not delete what a conversation already holds.
How to have it deleted. A person, or their organization, can ask at any time for what Balt holds from their Google account to be deleted. Section 10 says what is deleted; requests go to the organization’s administrator or to legal@cobalt-ia.com.
6.2 Data received from Slack, Microsoft Teams and Discord
Data obtained through the Slack, Microsoft Teams and Discord APIs is not used to develop, train, or improve any generalized machine learning model, nor for advertising or targeted advertising purposes. It is used solely to operate Balt in the workspace that installed it, and is disclosed neither to other customers nor to third parties other than the subprocessors listed in Section 7.
7. Subprocessors
The list below is the list of authorized subprocessors within the meaning of Section 8 of the DPA. The DPA and the Product Terms refer to it. Section 7.3 states, for each, the contracting entity, its contact details, and the safeguard covering any transfer outside the European Union.
Slack, Microsoft Teams, Discord, and the other Connected Platforms are not subprocessors (Section 8.4 of the DPA): the conversation is theirs, under the contract between them and Customer, and Balt takes part in it. A conversation held in the console has no holder other than us and is disclosed to none of them.
7.1 Subprocessors that process message content
| Subprocessor | Purpose | Data received | Location |
|---|---|---|---|
| Microsoft Azure AI Foundry, Amazon Bedrock, Google Cloud Vertex AI | Language models producing Balt’s responses | The content of the conversation Balt is answering | European Union |
| Modal | Hosting and running the Service | Message content, on every run; each organization’s workspace: a copy of its memory, skills, and documents, and the files Balt produces there | Execution in the European Union (Ireland). Stored in the United States: each organization’s workspace, execution logs, deployment secrets, and call payloads over 2 MiB |
| Vercel | Hosting the website and the console; relaying requests to the Service, without caching | Message content in transit: platform events and console requests | Point of presence nearest to the sender: Paris for users in the European Union; notifications sent by Slack or Microsoft from the United States pass through the United States, without storage |
| Recall.ai | Joining, recording, and transcribing online meetings | Audio, video, transcript, and participant list | European Union (Germany) |
| ElevenLabs | Speech transcription: voice messages, the console microphone, and recorded meetings. Optional: involved only when those features are used. Where the Order Form so provides, transcription is performed by Microsoft Azure in the European Union and ElevenLabs receives no Customer data | The audio excerpts to transcribe | United States |
| Linkup | Web search and reading public pages | Search terms and the addresses of pages to read, which may carry what was said in the conversation | Company established in France; a request may be processed in the European Union, the United States, Canada, or Asia-Pacific, depending on Linkup’s load balancing |
| Mintlify | Hosting the help centre and searching its pages to answer questions about the Service | Search terms, which may carry what was said in the conversation; for visitors to the help centre, the pages they view and the questions they ask its assistant | United States |
| FullEnrich | Finding a person’s business contact details, and people or companies matching professional criteria. Can be turned off for an organization on request | The name and employer of the person searched for, their LinkedIn profile where provided, and the search criteria | United States |
| Nango | Connecting to Connected Platforms: holding OAuth credentials and relaying calls | OAuth credentials; the request and response of relayed calls; change notices sent by Connected Platforms, without their content; for a calendar, the identifier and times of each occurrence | United States |
| Resend | Sending transactional emails, including invitations. Receiving and sending emails exchanged with Balt, where a person writes to Balt by email or a routine answers by email; this use is optional | The content and addresses of emails exchanged with Balt and of transactional emails | United States |
| Twilio | Sending and receiving text messages, only if a person adds their phone number | The content of text messages and the phone numbers of the person and of Balt | Ireland (European Union) |
| PostHog | Audience measurement in the console, with the user’s consent, and on the public website, without cookies (Section 14) | The console's screens as displayed, conversations included, clicks, and navigation; for the public website, the pages visited, where the visit came from, and clicks on the sign-up and booking buttons | European Union |
7.2 Other subprocessors
| Subprocessor | Purpose | Data received | Location |
|---|---|---|---|
| Neon | The Service’s database, encrypted at rest | All of the Service's data, at rest | Germany (Frankfurt) |
| Scaleway | Storage of files and meeting recordings; encryption key management | Shared files and meeting recordings, at rest | France (Paris) |
| Convex | Hosting Spaces, for organizations that use them | Each Space's data and the accounts of the people who sign in to it | Ireland (Dublin) |
| Restate | Orchestration of runs | Workspace, conversation, and event identifiers | European Union |
| Google Cloud (Pub/Sub) | Notice that a message has arrived in a connected Gmail mailbox | The address of the connected mailbox and a position in its history, never the message | European Union (Belgium) |
| Upstash | Outbound message queue | Thread, command, and event identifiers | Germany (Frankfurt) |
| Clerk | Console sign-in | Name, email address, and sign-in identifier of Authorized Users | United States |
| Dash0 | Platform telemetry | Metadata and timings, no content | European Union (Netherlands) |
| Sumble | Public information about companies: group structure, hiring, technologies. Can be turned off for an organization on request | A company's name, domain, or identifier and search criteria; no personal data | United States |
| Cal.com | Booking calls from the website | What the person booking enters, including their name and email address | United States |
| Autumn, Stripe | Subscriptions, payments, and invoicing | The organization's billing and payment data | United States |
7.3 Identity, contact details, and transfer safeguard
| Subprocessor | Contracting entity and address | Contact | Transfer safeguard (Section 8) |
|---|---|---|---|
| Microsoft (Azure AI Foundry) | Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, D18 P521, Ireland; Microsoft Corporation, One Microsoft Way, Redmond, WA 98052, United States | Microsoft Ireland Operations Limited, Attn: Data Protection, at the address opposite | Adequacy (EU-US Data Privacy Framework); SCC |
| Amazon Web Services (Amazon Bedrock) | Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg | aws-EU-privacy@amazon.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Google Cloud (Vertex AI) | Google Cloud France SARL, 8 rue de Londres, 75009 Paris, France, RCS Paris 881 721 583 | support.google.com/cloud/contact/dpo | Adequacy (EU-US Data Privacy Framework); SCC |
| Modal | Modal Labs, Inc., 233 Spring Street, East Floor 11, New York, NY 10013, United States | security@modal.com | SCC |
| Vercel | Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, United States | privacy@vercel.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Recall.ai | Hyperdoc Inc., 2261 Market Street #4339, San Francisco, CA 94114, United States | hello@recall.ai | SCC |
| ElevenLabs | Eleven Labs Inc., 169 Madison Avenue #2484, New York, NY 10016, United States | dpo@elevenlabs.io | Adequacy (EU-US Data Privacy Framework); SCC |
| Linkup | Linkup Technologies SAS, 28 avenue des Pépinières, 94260 Fresnes, France, RCS Créteil 930 910 740 | privacy@linkup.so | SCC, for requests processed outside the European Union |
| Mintlify | Mintlify, Inc., 1 Post Street, Suite 1800, San Francisco, CA 94104, United States | security@mintlify.com | SCC |
| FullEnrich | FullEnrich Corp, 28 Geary Street, Suite 650 #346, San Francisco, CA 94108, United States | support@fullenrich.com | SCC |
| Nango | Nango Inc., 2093 Philadelphia Pike #2885, Claymont, DE 19703, United States | hello@nango.dev | Adequacy (EU-US Data Privacy Framework); SCC |
| Resend | Plus Five Five, Inc., 2261 Market Street #5039, San Francisco, CA 94114, United States | privacy@resend.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Twilio | Twilio Ireland Limited, 70 Sir John Rogerson’s Quay, Dublin 2, D02 R296, Ireland; Twilio Inc., United States | privacy@twilio.com | Adequacy (EU-US Data Privacy Framework); SCC |
| PostHog | PostHog, Inc., 2261 Market Street #4008, San Francisco, CA 94114, United States | privacy@posthog.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Neon | Databricks, Inc., for Neon, LLC, 160 Spear Street, Suite 1300, San Francisco, CA 94105, United States | privacy@databricks.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Scaleway | Scaleway SAS, 8 rue de la Ville l’Évêque, 75008 Paris, France | privacy@scaleway.com | None required: European Union entity |
| Convex | Convex, Inc., 444 De Haro Street, Suite 218, San Francisco, CA 94107, United States | privacy@convex.dev | SCC |
| Restate | Restate GmbH, Knaackstraße 92, 10435 Berlin, Germany, HRB 240580 B (Charlottenburg Local Court) | dataprotection@restate.dev | None required: European Union entity |
| Upstash | Upstash, Inc., 6202 Vía De Adrianna, San Jose, CA 95120, United States | privacy@upstash.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Clerk | Clerk, Inc., 660 King Street, Unit 345, San Francisco, CA 94107, United States | privacy@clerk.dev | Adequacy (EU-US Data Privacy Framework); SCC |
| Dash0 | Dash0 Inc., 169 Madison Avenue STE 38218, New York, NY 10016, United States | privacy@dash0.com | SCC |
| Sumble | Sumble, Inc., Delaware corporation no. 6927348, registered office: 3500 S DuPont Highway, Dover, DE 19901, United States | support@sumble.com | SCC |
| Cal.com | Cal.com, Inc., 2261 Market Street #4382, San Francisco, CA 94114, United States | privacy@cal.com | Adequacy (EU-US Data Privacy Framework); SCC |
| Autumn | Rebase, Inc. (Autumn), Delaware corporation no. 5598287, registered office: 251 Little Falls Drive, Wilmington, DE 19808, United States | security@useautumn.com | SCC |
| Stripe | Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02 FX04, Ireland; Stripe, LLC, United States | dpo@stripe.com | Adequacy (EU-US Data Privacy Framework); SCC |
Each subprocessor is bound by contract to data protection obligations at least equivalent to ours. Customer may object to the addition of a new subprocessor on the terms and within the period set out in Section 8 of the DPA.
We do not sell personal data and do not disclose it to third parties for targeted advertising. We may disclose it where required by law or ordered by a competent authority, and in connection with a merger, acquisition, or asset sale, in which case this policy continues to apply until Customer is informed of any change.
8. Transfers outside the European Union
The Service’s database and its backups, shared files, and meeting recordings are hosted in the European Union, and prompts sent to the language models are processed there. Balt’s workspace for each organization, which holds a copy of its memory, skills, and documents and the files Balt produces there, is stored by Modal in the United States, as are execution logs.
Some subprocessors are established outside the European Union, mainly in the United States, or may access from a third country the data they process in the Union, or process a request there. They receive only the data necessary for their purpose, and each transfer relies on one of the following safeguards, stated for each in Section 7.3:
- Adequacy decision (Article 45 GDPR): for a recipient certified under the EU-US Data Privacy Framework, Commission Implementing Decision (EU) 2023/1795. Its certification is checked on the official list before relying on it, and every year thereafter;
- Standard Contractual Clauses or SCC (Article 46(2)(c) GDPR): the clauses adopted by Commission Implementing Decision (EU) 2021/914, supplemented by a transfer impact assessment and, where necessary, by supplementary measures.
Should the adequacy decision on which a transfer relies cease to apply, the Standard Contractual Clauses replace it or the transfer ends. A copy of the applicable safeguards, the transfer mapping, and the transfer impact assessments can be obtained at legal@cobalt-ia.com, on the terms of Section 11 of the DPA.
9. Retention periods
A workspace’s data is kept while that workspace is connected to the Service, and deleted when it is no longer connected or on request. No data is deleted because of its age.
| Data | Retention |
|---|---|
| Conversation content and event log | Until the install it was received through is removed, the Agreement is terminated, or deletion is requested |
| Memory, skills, and derived documents | Until the Agreement is terminated or deletion is requested; removing a chat app does not delete them |
| Data of a Slack or Microsoft Teams workspace or a Discord server | Deleted within fourteen (14) business days of the app being uninstalled, with no request needed |
| Integration credentials | Until the Connected Platform is disconnected; disconnection does not by itself delete Customer Data already collected |
| Meeting recordings and transcripts | Until deleted by Customer, and at the latest as conversation content is |
| Account data | The Subscription Term, then thirty (30) days |
| Phone number | Until the person removes it, and at the latest as account data is |
| Technical logs and telemetry | Twelve (12) months at most |
| Console session recordings (Section 14) | Thirty (30) days |
| Console audience measurement events (Section 14) | Twenty-five (25) months after the person’s last activity; their deletion is requested no later than the day after the person’s account is deleted |
| Accounting records and invoices | Ten (10) years (article L. 123-22 of the French Commercial Code) |
| Prospects and business contacts | Three (3) years from the last contact |
On expiry of the Agreement, deletion of Customer Data is governed by Section 13 of the DPA. Customer Data that does not constitute personal data is retained for thirty (30) days following termination and then deleted or anonymized, under Section 11.8 of the General Terms.
10. Deletion and the right to erasure
A person’s messages. On request, all of a person’s messages are deleted, including from the event log. Conversations remain coherent for the other participants.
Derived content. Because the workspace memory and the skill documents do not identify the author of each item, they are deleted in full, after the messages they were derived from. A person’s private note is deleted with their data.
Exception. Integration documents installed by Balt, which contain no data from conversations, are kept.
11. Security
We maintain an information security program proportionate to the nature of the Service and the risks involved. The technical and organizational measures are described in Section 6 of the Product Terms and detailed in Annex II to the DPA: encryption of data in transit and at rest, envelope encryption of integration credentials, access control and least privilege, hosting in the European Union, logging and continuous monitoring, regular encrypted backups, and staff awareness training.
In the event of a personal data breach affecting Customer Data, we notify Customer without undue delay under Section 10 of the DPA. No system being immune, these measures reduce risk without eliminating it.
12. Your rights
Every data subject has, under Articles 15 to 22 GDPR, the rights of access, rectification, erasure, restriction, objection, and portability, the right to give directions as to the fate of their data after death, and the right to withdraw consent at any time where processing rests on it.
For data processed through the Service, requests are addressed to Customer as controller; we forward any request received directly and assist Customer under Section 9 of the DPA. For processing for which we are the controller, requests are addressed to legal@cobalt-ia.com.
We respond within one (1) month of receiving the request, extendable by two (2) months having regard to its complexity or to the number of requests. Proof of identity may be requested where there is reasonable doubt as to the identity of the requester.
Every data subject may lodge a complaint with the Commission nationale de l’informatique et des libertés (CNIL), 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, or with the supervisory authority of their place of residence.
13. Minors
The Service is intended for professional use and is not designed for minors. Customer shall not submit to the Service data relating to persons under fifteen (15) years of age, the age of digital consent in France, under Section 3 of the Acceptable Use Policy. If we learn that such data has been submitted, we delete it without delay.
15. Changes
This policy carries a version number and an effective date, available in the version history. Material changes are notified to Customer’s administrator before they take effect, under Section 16 of the General Terms. We review this policy at least once a year.
16. Contact us
For any question about this policy, about exercising your rights, or about data protection: legal@cobalt-ia.com, or by post to SKILLFORGE APP, Legal Department, 2 Rue des Commères, 78310 Coignières, France.
The other documents of the agreement
- Definitions : The defined terms used across the Balt contractual documents.
- General Terms : The core contractual terms governing access to and use of the Balt service.
- Acceptable Use Policy : The rules for acceptable and prohibited use of the Balt service, and prohibited data.
- Product Terms : Service description, AI functionality, autonomous actions, connected platforms and security.
- Usage Terms : How Credits, allocations, top-ups and accounts work.
- License Terms : The license granted to use the Balt service, and its restrictions.
- Data Processing Agreement : The Article 28 GDPR agreement, Standard Contractual Clauses included, counter-signed on request.
- Legal Notice : The website publisher, its publication director and its hosting providers.
For any question about this policy, contact us at: legal@cobalt-ia.com
