Privacy and legal notice
Two kinds of data pass through DeployIt, and our role is not the same for each.
In force from November 17, 2026.
This translation is provided for information. The French version prevails.
Yours, as a customer
The names and emails of administrators and of people who sign up, their profile, billing, and the request and settings logs. For this data, Ysae SLU is the controller.
What we receive: the email address, the name, the company; for a plan, the billing information passed on by Paddle (never a card number); for each request, under the person's name: the question, the answer and its sources, the profile, the tool called, the status, the duration and the cost; technical logs for security and debugging.
What we do with it: provide the Service, answer support requests, bill, keep things secure and prevent abuse. Nothing is sold, nothing is used for advertising.
Your repositories' data
The code, the names and addresses of commit authors, and the statistics that follow from them. You are responsible for this data; we process it for you, on your instructions, under the data processing agreement below.
If you are a tracked developer
Your employer, or your client, uses DeployIt to track their team's work. Here is what that means for you.
- What is measured. Your merged commits: their date and time, their PR, their review, their tests, their ticket, their module; the defects DeployIt attributes to them, "to confirm" until an administrator or an automated investigation (a model that rereads the code, checked by two others) has confirmed them; a score of their code given by a language model. Also: your Git identities, the reviews you give, your share of each module, your working time, whether you are a contractor, and the absences your employer declares.
- What isn't. Not your screen, not your messages, not the time spent on a task. Only your commits, your PRs and your reviews appear, plus what your employer declares (absences, working time).
- Who reads it. The people your employer designates with the Leadership profile, the data tool it connects, and the company's administrators. With the Everyone profile, your name is removed from answers when DeployIt knows it.
- Your rights. You ask your employer for access to your data, its correction, its deletion, or to stop being tracked; they can export and delete everything DeployIt knows about you. We help them answer you within 7 business days. You can also write to us at [email protected]: we pass your request on to your employer.
How long
| Data | Kept |
|---|---|
| The code copy | While the repository is connected. Erased by a queued job, usually within hours of its removal from DeployIt. |
| The request and settings logs | 12 months by default; 3, 12 or 24 months, as the customer chooses. |
| Statistics | 24 months by default; 12 or 24 months, or for as long as the company exists, as the customer chooses. Those of a removed repository are deleted if the administrator asks; those of a person, on request. |
| Accounts and sign-ups | For as long as the company exists; a removed person keeps their line in the log, with no more access. |
| When the subscription ends | Nothing is erased at that moment: the company moves to the free plan, developer tracking stops, and the periods above keep applying. |
| When the company is deleted | Possible once the last paid period has ended. Access is cut at once; everything is erased by a queued job, usually within the following hours, except where the law requires keeping it (invoices, at Paddle). |
| Model usage | 25 months. |
| Alerts sent | 400 days. |
| Payment events | 90 days. |
| The daily database backups, at DigitalOcean | Seven days, according to DigitalOcean's documentation; they hold erased data until they rotate. |
What this site measures
No third-party analytics tool, no font loaded from another site: everything is served by deployit.ai, and page views are counted by our application, app.deployit.ai.
Two cookies set by deployit.ai and also read by app.deployit.ai: dit_vid, an anonymous visitor identifier kept for 12 months, and dit_attr, which remembers for 6 months where you arrived from (campaign parameters, referring site, landing page). They are used to count our visits and to learn which channel people find us through; if you create an account, they are attached to it.
A third cookie, i18n_redirected, remembers the language you chose.
A fourth cookie, __cf_bm, is not ours: Cloudflare, whose network our host DigitalOcean places in front of the site and the application, sets it to tell visitors from automated traffic. It expires after 30 minutes of inactivity and we never read it.
No IP address is kept in a database, no browser is recorded (at most a "bot" flag), and address parameters are cut before recording, except campaign parameters (utm, gclid, source); the address of the site you came from is kept whole, up to 300 characters. You can delete or block these cookies from your browser; the site works without them.
Messages you send us at [email protected] arrive in our inbox; we keep them for as long as it takes to reply.
Your rights
You can access your personal data, have it corrected or deleted, export it, object to some processing and withdraw your consent. Write to [email protected]. You can also complain to the data protection authority in your country.
Security: data encrypted in transit (HTTPS), access limited to what is strictly needed; model keys, secrets of your tool servers and the address of your database encrypted separately (AES-256-GCM). According to DigitalOcean's documentation, the database and the cache it manages also encrypt data at rest.
The Service is not intended for people under 18; we do not knowingly collect their data.
Where the data goes
Our servers are in London (United Kingdom), at DigitalOcean: the application, the database and the cache, which DigitalOcean manages. The code sent to the model (the content of the files to summarise, then what is needed to answer) is read by OpenAI, in the United States, except for the roles where you bring your own provider. Paddle handles billing; alwaysdata, a French company with servers in France, sends our service emails.
For the United Kingdom, these transfers outside the European Economic Area rely on the European Commission's adequacy decision. For a processor established elsewhere, the safeguard that covers the transfer is given to you on request.
We may change this policy; substantial changes are announced to administrators at least 30 days in advance.
Data processing
This agreement binds each customer, as controller, to Ysae SLU, as processor, for the data in its repositories and statistics. It is part of the terms of service. A signed copy is available on request from [email protected].
1. Parties
This agreement is made between the Customer (controller) and Ysae SLU, which operates DeployIt (processor), under Article 28 of the General Data Protection Regulation. Processor's address: Carrer de l'Aern, 12 atic, La Margineda, AD500 Andorra la Vella, Principat d'Andorra.
2. Subject and instructions
Ysae SLU processes the Customer's personal data (commit authors, members, per-person statistics, repository content) solely to provide the Service, and solely on the Customer's documented instructions, which include its Company settings.
3. Sub-processors
Hosting and infrastructure: DigitalOcean, in London (United Kingdom), for the application, the PostgreSQL database, and the cache and queues (Valkey), both managed by DigitalOcean. Language models: OpenAI; none if the Client brings its key for each role (agent, expert and mini). Payment: Paddle, reseller. Service emails: alwaysdata, in France. Sources: GitHub and GitLab, for the repositories the Client connects. Site audience measurement: no processor. We notify clients before adding a processor; a client can object by cancelling.
4. Security
Encryption in transit (HTTPS). According to DigitalOcean's documentation, the database and the cache it manages encrypt data at rest (LUKS) and in transit. Access to data limited to the people who need it, on the least-privilege principle. Model keys, tool server secrets and the address of the Client's database encrypted separately (AES-256-GCM). Log of requests and settings.
5. Data breaches
If there is a personal data breach, Ysae SLU notifies the Customer without undue delay, and no later than 72 hours after becoming aware of it.
6. Data subject rights
Ysae SLU helps the Customer respond to requests for access, rectification, erasure, restriction, portability and objection, within 7 business days, in particular through the export and deletion of a person's data.
7. No training
Ysae SLU never uses the Customer's data (source code, repository content, processed data) to train or fine-tune an AI model, whatever the plan.
8. End of processing
At the end of a plan, the Company moves to the free plan and processing continues within its limits, without developer tracking, with the chosen retention periods. The Client can delete its Company once the last paid period has ended. Ysae SLU then cuts access at once and erases all the data processed for it with a queued job, usually within the following hours, retried if it fails, except where the law requires keeping it; the daily database backups, which DigitalOcean keeps for seven days according to its documentation, hold it until they rotate. If the code copy is held in an unreachable database of the Client, Ysae SLU retries and then notifies the Client. While its plan or the trial runs, the Client can export the statistics with a Data tool key; the data of each tracked person can be exported from its workspace.
9. Audit
With reasonable notice and at most once a year, the Customer may request a compliance audit, carried out by an independent third party bound by confidentiality.
10. Contact
For any request about this agreement: [email protected] or [email protected].
Legal notice
- Publisher
- Ysae SLU · Carrer de l'Aern, 12 atic · La Margineda · AD500 Andorra la Vella · Principat d'Andorra
- Contact
- [email protected]
- Host
- DigitalOcean, LLC (United States) · London data centre (United Kingdom)
- Payment
- Paddle, reseller (Merchant of Record)