Informativa sulla privacy

Come raccogliamo, trattiamo e proteggiamo i tuoi dati.

Ultimo aggiornamento: 31 ottobre 2026

Mostriamo la versione inglese finché la traduzione non è pronta.

This Privacy Policy explains how NEXT BP processes personal data when you visit blast-audit.com or use Blast Audit: the Excel add-in, the web dashboard, the connectors to cloud storage, the MCP server, the engagement agent, the financial statement review, the PBC request lists, analysis projects and the Blast Audit Academy (the "Software"). It is the information required by Articles 13 and 14 of the General Data Protection Regulation (GDPR).

This policy is for information; it does not form part of the contract concluded with your organisation. The commitments that NEXT BP makes as processor are set out in the Data Processing Agreement (DPA).

1. Who We Are

The controller is NEXT BP, a French simplified joint-stock company (SAS) with a share capital of €100, registered with the Paris Trade and Companies Register under number 920 753 233, whose registered office is at 127 rue de la Tour, 75016 Paris, France.

For any question about your personal data or to exercise your rights, write to privacy [at] blast-audit.com. NEXT BP has not appointed a data protection officer; this address reaches the person in charge of data protection at NEXT BP.

The Software is intended for professionals. It is not intended for children.

2. Controller or Processor

NEXT BP processes personal data in two capacities.

As controller, for the data it needs to run its own business: visitors to the website, accounts and authentication of users, billing, support, security, product analytics, prospecting and sales relations. This Policy describes these processing operations.
As processor, for the documents and content that audit and accounting firms submit to the Software (for example bank statements, invoices, contracts or payroll records) and the personal data they contain. The firm that uses Blast Audit is the controller of these data and decides what it submits. NEXT BP processes them only on that firm's instructions, under the DPA.
As processor, also, for the consultation of usage per member when your organisation turns on the setting described in Section 12. Your organisation is the controller of that consultation. NEXT BP presents and exports the indicators on that instruction (Section 2.5 of the DPA). That consultation is not the product analytics for which NEXT BP is controller.

If your data appear in a document that a firm has submitted to Blast Audit, or in a file sent to a firm through a PBC request list, contact that firm to exercise your rights. If you write to us, we forward your request to the firm concerned.

If a firm has sent you requests for documents through a PBC request list, that firm is the controller of the requests, your e-mail address, your language, your messages, the reasons you give, your files, the results of the AI checks on them and the record of your actions on the list. Contact it to exercise your rights. If you write to us, we forward your request to it. NEXT BP is the controller of the record that NEXT BP itself keeps to limit abuse of the link, and of its technical logs (Section 4).

3. Data We Collect and Where It Comes From

Identity and account data: name, e-mail address, organisation, role, language, identifiers from your identity provider when your organisation uses single sign-on, sign-in dates.
Billing data: name of the billing contact, company details, address, VAT number, subscription, invoices and payment status. Card details are entered on Stripe's pages; we do not keep the full card number.
Usage data: features used, number of pages processed, AI credits consumed, technical identifiers, browser and device data, IP address, pages viewed. Per-member detail (name, e-mail address, role, indicators of the view) is described in Section 12. It is not sent to the analytics tool.
Support and communications: messages, e-mails and attachments you send us, and the e-mails we send you.
Prospecting data: what you enter in our contact and demo forms (name, professional e-mail address, phone number, company, job title, team size, message).
Connector data: when you connect Google Drive or Microsoft 365, the access tokens and the account identifier that the provider returns.
Content submitted to the Software: documents, extracted values, instructions, voice input. NEXT BP processes this content as processor (Section 2).

Most of these data come from you. Some come from other sources:

your organisation's administrator, who invites you and assigns your role;
your organisation's identity provider, through WorkOS, when single sign-on is used;
Stripe, for the status of payments;
Google or Microsoft, when you connect a connector.

4. Purposes, Legal Bases and Retention

The durations below are maximum durations; if a deletion fails, Section 7 applies.

Purpose	Data	Legal basis	Retention
Create and manage your account, authenticate you, manage your organisation's users	Identity and account data	Performance of the contract with your organisation (Art. 6(1)(b)); for users invited by their organisation, our legitimate interest and that of the organisation in giving them access to the service (Art. 6(1)(f))	For the life of the account, then deleted no later than 30 days after it is closed
Provide the features of the Software, apply quotas and meter usage	Usage data, connector data	Performance of the contract (Art. 6(1)(b))	Raw usage events and daily aggregates per user: 13 months, plus one day of technical margin, then deletion. Entries for AI credits and OCR pages, and records of the execution of the artificial-intelligence features: the user's identifier is removed from them 13 months, plus one day, after the entry; a record still open on that date is detached when it closes. The lines and their amounts stay attached to the organisation, for billing. Organisation totals without a personal identifier: for the life of the account. At the end of the organisation's contract, the raw usage events, daily aggregates per user, records of the execution of the artificial-intelligence features and organisation totals that remain, whatever their age, are deleted with the organisation's data (Section 7.3 of the DPA); entries for AI credits and OCR pages are kept for billing, without the user's identifier. Connector tokens: until disconnection. Per-user export files: 30 days, then deletion.
Invoice, collect payments, keep accounting records	Billing data	Performance of the contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) for accounting records	For the life of the subscription; invoices and accounting records: 10 years (Article L. 123-22 of the French Commercial Code)
Answer support requests, including the suggestions and bug reports you send through the support chat or by e-mail, and take them into account to improve the product. When it is active, Moulinet, an artificial intelligence assistant, receives these requests first and answers them or hands them to the team, which also takes over the conversation at your request (article 12)	Support and communications, identity data	Performance of the contract for customers; legitimate interest in answering visitors and prospects (Art. 6(1)(f)); legitimate interest in having requests handled first by Moulinet, for customers and visitors alike (Art. 6(1)(f)); legitimate interest in improving the product, for suggestions and bug reports (Art. 6(1)(f))	Conversations: 24 months after the last message, then deletion; 90 days for conversations of visitors who are not signed in that our team never replied to, even if Moulinet did. Moulinet's replies, the summary of the hand-over to the team and the log of its work are deleted with the conversation. Support administration logs: 24 months. You can ask for earlier deletion (Section 8)
Send service e-mails: invitations, onboarding, trial and billing reminders	Identity data, language, organisation, plan, subscription events	Performance of the contract (Art. 6(1)(b)); for onboarding advice, our legitimate interest in helping customers use the service (Art. 6(1)(f))	For the life of the account
Secure the service, prevent fraud and abuse, detect errors	IP address, technical logs, error reports	Legitimate interest in protecting the service and its users (Art. 6(1)(f))	Logs: 30 days; error reports: 90 days
Product analytics in the Excel add-in and the administration console	User identifier, e-mail address, organisation; usage events: actions in the product, ratings of the assistant's answers, errors, response times, language, add-in version and Excel environment, pages viewed and console calls. These events are designed to contain neither the content nor the name of documents	Legitimate interest in understanding how the product is used and improving it (Art. 6(1)(f)). This measurement does not collect consent; it is designed to store nothing on your device	25 months
Audience measurement without cookies on the website and the dashboard, not linked to an account, without consent	Pages viewed, interactions, IP address and browser user agent, which PostHog turns into a hash with a salt that changes every day; according to PostHog's documentation, the IP address is not stored	Legitimate interest in measuring the audience of the website and the dashboard (Art. 6(1)(f))	25 months
Audience measurement and session recording on the website, and product analytics in the dashboard, with your consent	Browser identifier, pages viewed, interactions, survey responses; session recording of visitors who are not signed in, designed to stop at sign-in, whose text masking is not guaranteed; when you are signed in, user identifier, e-mail address and organisation; according to PostHog's documentation, the IP address is used to look up the country and filter out bots, and is not stored	Consent (Art. 6(1)(a)), given in the cookie banner	Events: 25 months; recordings: 90 days
Product analytics and billing tracking through events that our servers send to the analytics tool. These events do not depend on the cookie choice, which concerns only the browser	Account and organisation identifiers; sign-up; billing and subscription events; metrics of service e-mails (delivered, opened, clicked, bounced, marked as spam, unsubscribed); metadata of calls to AI models, operated by Microsoft (Azure OpenAI service) or by a provider chosen by your organisation, and of OCR and document-agent processing (feature, provider, tokens, duration, status, estimated cost), without document content; denied access to AI chat and trial limits reached; feature-flag evaluations, with the e-mail address for some flags. Per-member detail and the usage events recorded for the firm are not sent	Legitimate interest in measuring product use (Art. 6(1)(f)). For billing events, performance of the contract (Art. 6(1)(b))	25 months at the analytics tool. Billing follows the corresponding row
Usage statistics of the Excel add-in	Session and visitor identifiers, page, referrer, country and city derived from the IP address, which is kept only in hashed form	Legitimate interest in measuring the use of the add-in (Art. 6(1)(f))	25 months
Keep evidence that an owner or administrator accepted the Terms and Conditions, the EULA or the Data Processing Agreement for their organisation, and that you were informed of this Privacy Policy	Account identifier, e-mail address and role of the person who accepts, organisation, text, version, date, surface and language shown	Performance of the contract (Art. 6(1)(b)); legitimate interest in being able to prove the contract (Art. 6(1)(f))	Acceptances: for the life of the contract, then 5 years; information about this policy: as long as your account exists
Limit the requests made through the link of a PBC request list	Hash (not the value itself) of the IP address, of the link token or of the recipient, depending on the action, with a request counter	Legitimate interest in protecting the service, the firms and their clients against abuse (Art. 6(1)(f))	2 days
Prospecting and sales relations with professionals	Prospecting data	Legitimate interest in presenting our services to professionals (Art. 6(1)(f))	3 years after the last contact from the prospect
Comply with legal obligations, establish or defend legal claims	The data concerned	Legal obligation (Art. 6(1)(c)); legitimate interest (Art. 6(1)(f))	Statutory limitation periods (5 years in commercial matters)

Where we rely on our legitimate interest, you can object at any time (Section 8).

5. Recipients

Personal data are accessible only to the NEXT BP personnel who need them. We share them with the following service providers, which act on our instructions:

Microsoft (Microsoft Ireland Operations Limited): hosting on Microsoft Azure in France; Azure OpenAI (EU Data Zone) for the artificial-intelligence features; Azure AI Content Understanding for document analysis and the advanced reading of scanned pages (some scanned pages may be read by NEXT BP's reader, which we operate ourselves within our Microsoft Azure hosting; except when your organisation uses its own Azure key, Azure reads each scanned page for which the result you receive does not come from this reader, including pages re-read, and may also read pages that this reader reads; to measure and maintain the quality of the reading provided to you, this reader may re-read a page already read by Azure, and we keep from that re-reading only figures without document content); the Azure AI service in the EU Data Zone, which checks the engagement agent's and the Excel agent's results tables and checks Moulinet's replies before they are sent (Moulinet is the artificial intelligence assistant of our support, article 12); Azure AI Speech for voice input; Azure Communication Services for transactional e-mail, including our support replies;
Cloudflare: hosting of the website and the dashboard, receipt of support e-mail;
Google (Google Workspace): NEXT BP's e-mail, including e-mail sent to support [at] blast-audit.com;
WorkOS: authentication and single sign-on;
Stripe: payment and invoicing;
PostHog: product analytics and audience measurement (Section 4). It does not receive per-member detail;
Sentry: error monitoring;
Customer.io: service e-mails linked to the account and the subscription, whose opening and clicks are measured by a pixel and by redirected links;
Exa: web search offered by the Excel agent, when you approve the search query.

When your organisation uses its own Azure key, every scanned page is read by the advanced reading, with that key. For those reads, Microsoft acts under your organisation's Azure contract and on its instructions, not ours (Section 5.7 of the DPA).

The location of each provider and the safeguards applicable to transfers are listed in Annex 3 of the DPA, which is our dated sub-processor list.

We may also disclose data to public authorities when the law requires it, to our professional advisers (lawyers, auditors) bound by confidentiality, and to an acquirer in the event of a merger or sale of the business, after informing you.

We do not sell personal data.

6. Transfers Outside the European Economic Area

We host our databases and files in the European Union. Some providers are established in the United States or may access data from there: Cloudflare, Google, Stripe, WorkOS, Sentry, Customer.io, PostHog and Exa. These transfers rely on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework when the recipient is certified (at the date of this policy: Cloudflare, Google, Stripe, PostHog, Sentry and Customer.io), and on the Standard Contractual Clauses adopted by the Commission (Decision (EU) 2021/914) in the other cases (WorkOS and Exa) or in addition. Microsoft providers (Azure hosting, Azure OpenAI, the Azure AI service in the EU Data Zone that checks the engagement agent's and the Excel agent's results tables and checks Moulinet's replies before they are sent, Azure AI Content Understanding, Azure AI Speech and Azure Communication Services) process data in the European Union. Microsoft personnel located outside the EU Data Boundary may access that data remotely, as necessary to operate, troubleshoot, support and secure the services: this transfer relies on the 2021 Standard Contractual Clauses (Decision (EU) 2021/914, Module 3, processor to processor) between Microsoft Ireland Operations Limited and Microsoft Corporation, and on the EU-U.S. Data Privacy Framework, under which Microsoft Corporation is certified. The review, by Microsoft employees, of data that triggered its abuse-monitoring systems (article 10) may also take place outside the European Economic Area: Microsoft's contract places those employees in the European Economic Area only for a deployment within the EU Data Boundary, and Microsoft makes no EU Data Boundary commitment for the preview on which the Azure AI service in the EU Data Zone runs. The Microsoft employees who review this service's data, including the support messages it receives to check Moulinet's replies, are therefore not necessarily located in the European Economic Area. Microsoft's contract governs its transfers outside the European Economic Area by the 2021 Standard Contractual Clauses, subject, for a preview, to the lesser or different privacy and security measures Microsoft may apply (article 10). You can obtain a copy of these safeguards by writing to privacy [at] blast-audit.com.

7. Data Retention

The retention period of each category of data for which NEXT BP is the controller is given in the table in Section 4. At the end of the period, data are deleted or anonymised. If a deletion fails, it is retried and takes place as soon as possible. Database backups, and files deleted from an engagement, a financial statement review, a PBC request list or an analysis project, remain recoverable for at most 7 days after deletion.

For the content that NEXT BP processes as processor, the periods are set in Annex 1 to the DPA. In short:

content submitted for OCR or document analysis is deleted, in the copies that NEXT BP controls, at most 24 hours after upload; the copies that Microsoft temporarily stores for abuse monitoring are not covered (Section 10);
for the Excel agent, the add-in sends our servers, for each conversation, the name of each document saved in your workbook and the text that OCR read in it, so that the agent can list those documents, search them and read their pages, even when the request does not concern them; it does not send the files themselves for this; the content of an Excel agent conversation, including that text, is deleted from NEXT BP's systems at most 24 hours after it reaches them, and database backups keep it up to 7 more days; the copies that Microsoft temporarily stores for abuse monitoring are not covered (Section 10);
the content of an engagement of the engagement agent, of a financial statement review, of a PBC request list or of an analysis project is kept while it is open, then deleted from NEXT BP's systems no later than 30 days after it is closed; after a long period without activity, it may be closed, under the rules of Annex 1 to the DPA; the copies that Microsoft temporarily stores for abuse monitoring are not covered (Section 10);
the files of a PBC request list copied into an engagement follow that engagement's retention, and those imported into a workbook stay in that workbook;
operational logs, designed to contain no document content, are kept 30 days.

8. Your Rights

You have the right of access, rectification and erasure, the right to restrict processing, the right to data portability, and the right to object to processing based on our legitimate interest, including prospecting, which you can stop at any time without giving a reason. Where processing is based on your consent, you can withdraw it at any time; for cookies, use the Cookie settings link at the bottom of every page. Under French law, you can also give instructions on what happens to your data after your death.

To exercise these rights, write to privacy [at] blast-audit.com. We answer within one month; this period may be extended by two months for complex requests, in which case we tell you. We may ask for information to confirm your identity.

You can lodge a complaint with the French data protection authority, the CNIL (3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, www.cnil.fr), or with the authority of the Member State where you live or work.

9. Mandatory and Optional Data

Your name, e-mail address and organisation are required to create an account; without them, we cannot give you access to the Software. Billing data are required to take out a paid subscription. In our forms, required fields are marked; the other fields are optional. Accepting audience measurement cookies is optional and has no effect on access to the website. The cookieless audience measurement of the website and the dashboard, described in Section 4, takes place before that choice and if you refuse; it is not linked to your account.

10. Artificial Intelligence and Automated Decisions

We do not use your data or the content you submit to train or fine-tune artificial intelligence models. Under its contract, our AI provider, Microsoft, does not use that content to train generative AI foundation models without our documented instructions, and we give no such instructions.
If your organisation saves its own API key for another AI or OCR provider, the requests concerned are sent to that provider under the contract your organisation has with it; that provider is not our processor (Section 5.7 of the DPA).
We configure the Azure OpenAI service so that it does not keep requests or responses for later retrieval, subject to the abuse monitoring described below.
Microsoft temporarily stores all requests sent to Azure OpenAI and all responses, to monitor for and prevent abusive or harmful uses or outputs of the service (abuse monitoring). Microsoft's contract sets no duration for this storage. Only data that has triggered its automated systems may be reviewed by authorised Microsoft employees; for EU Data Boundary deployments, those employees are located in the European Economic Area. Microsoft's terms (Privacy & Security Terms) also allow its personnel located outside the EU Data Boundary to access data processing systems inside it remotely, as necessary to operate, troubleshoot, support and secure its services. Microsoft has not granted NEXT BP an exemption from this monitoring: this storage therefore takes place. Microsoft may also temporarily store, for abuse monitoring, the requests sent to the Azure AI service in the EU Data Zone that checks results tables and checks Moulinet's replies before they are sent, and that service's responses; Microsoft has given NEXT BP no commitment on how long it keeps them. For this service too, only data that triggered Microsoft's automated systems may be reviewed by authorized Microsoft employees, located in the European Economic Area for a deployment within the EU Data Boundary, and Microsoft does not use this content to train generative AI foundation models without our documented instructions, which we do not give. This service runs on a model version that Microsoft offers as a preview: Microsoft's terms for Azure previews apply to it, and Microsoft may apply to previews privacy and security measures that are lesser than or different from those described here, including other abuse-monitoring practices. Microsoft makes no EU Data Boundary commitment for previews: the Microsoft employees who review this service's data are therefore not necessarily located in the European Economic Area. For either service, Microsoft's contract only sets a latest deletion: after our Azure subscription ends, Microsoft keeps this data for ninety (90) days in a limited-function account, then deletes it within the following ninety (90) days. That subscription is ours: the end of your organisation's contract does not end it.
The Software makes no decision based solely on automated processing that produces legal effects concerning you or similarly significantly affects you. Its results are suggestions that the user checks. Moulinet's replies to support requests are sent without prior review by the team; each one says it is written by an AI, and they decide nothing about you. A button in the chat hands the conversation to the team at any time; a reply to its e-mail does too, except a reply to a question Moulinet asked to clarify the request (article 12).

11. Cookies

The cookies and browser storage used by the website and the dashboard, their purpose, duration and how to change your choice are described in our Cookie Notice.

12. Specific Features

When a function below processes data on behalf of your organisation, its retention periods are set in Annex 1 to the DPA and summarised in Section 7.

Voice input. When voice input is enabled, the add-in records your voice while you dictate and sends the audio to our servers, which have it transcribed by Azure AI Speech, in the EU Data Zone. According to Microsoft's documentation, this service does not keep the audio. NEXT BP does not keep it beyond the transcription, which is returned to you. This processing is carried out on behalf of your organisation, under the DPA.

Cloud storage connections (Google Drive, Microsoft 365). If you connect a Google Drive or Microsoft 365 account, Blast Audit reads your files so that you can choose and import documents from Excel. For Microsoft 365, we request the right to read your files and, for a work account, the list of SharePoint sites you have access to. The Software is designed not to create, modify, share or delete any file in your cloud storage. The access tokens are encrypted and stored for your account, and deleted when you disconnect the account from the Blast Audit dashboard. Disconnecting does not withdraw the authorisation on the provider's side: you can also revoke it from the permissions page of your Google or Microsoft account. Imported files are passed to your browser; the Software is designed not to keep them on our servers. If you submit them for processing, the retention rules in Section 7 apply.

SharePoint search (Microsoft 365 Copilot). An administrator who has connected their work Microsoft 365 account can search their organisation's SharePoint from the dashboard. Their query is sent, with their connection, to the Microsoft 365 Copilot retrieval service (Microsoft Graph), which Microsoft operates under your organisation's Microsoft 365 contract. The dashboard displays extracts, with their title and author. The Software is designed to keep neither the query nor the extracts; our logs keep only the number of results.

Google user data. Blast Audit's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We request the scope https://www.googleapis.com/auth/drive.file, which gives Blast Audit access only to the files you choose in the Google Drive picker. We use it only to download the file you select so that it can be displayed and linked to cells inside your own Excel workbook. We do not use Google user data for advertising, we do not sell it, we do not use it to train artificial intelligence or machine learning models, and we do not transfer it to third parties except as necessary to provide the feature (our hosting provider Microsoft Azure) or as required by law.

MCP server. If you connect an AI assistant of your choice (for example Claude or ChatGPT) to Blast Audit through the MCP server, you authorise it with your Blast Audit account through WorkOS. The assistant's requests and the results returned by your add-in pass through our servers: their content is masked, and the record deleted, no later than 30 days after the request. So that the assistant can find your workbooks, the add-in reports to our servers the name and identifier of the workbooks that are open; this report is deleted no later than 90 days after the last report. The assistant you connect is operated by its own provider, under that provider's terms; it is not a NEXT BP sub-processor. We keep the list of connected assistants (name, date of last use) so that you can see and disconnect them.

Engagement agent. If your organisation uses the engagement agent, the documents imported into an engagement, the task log and the workpapers are kept on our servers while the engagement is open, so that the agent can work without Excel open, then deleted under Section 7.

Financial statement review. If your organisation uses the financial statement review, our servers keep the content of each review while it is open, so that all its members find the same work: the documents imported and the text that OCR reads from them, the annotations, the comments and their replies, the checklists, the AI's answers with the passages they cite, the reviewers' verdicts and their notes, the analysis settings and the findings sent to Excel. The review keeps the list of its members and their access, and, with the date, the member behind each act. The comments, the replies and the verdicts show the name or e-mail address of their author, which the checklist sheets sent to Excel repeat. When the AI answers a checklist, our servers send the checklist's questions and the text of the statements' pages to the Azure OpenAI service; the copies that Microsoft keeps for abuse monitoring (Section 10) are not deleted with the review. A closed review is deleted under Section 7.

PBC request lists. If your organisation uses PBC request lists, its members send requests for documents by e-mail to people at their clients or elsewhere. Each recipient opens a personal link, without an account. They can send or withdraw files, write messages, say that they have nothing to send and why, choose their language, and hand a request to a colleague, who then becomes a recipient. The requests, the recipients' e-mail addresses and languages, the record of their actions with the date, their messages, the reasons they give, their files, the results of the AI checks where the organisation has set questions, and the member who sent each request are kept on our servers while the list is open. Closing a list ends every recipient's access; the list is then deleted under Section 7. The firm is the controller of these data (Section 2). The page a recipient opens through the link has no audience measurement and no product analytics. To limit abuse, NEXT BP keeps, as controller, a hash (not the value itself) of the IP address, of the link token or of the recipient, depending on the action, with a request counter, for 2 days at most (Section 4).

Analysis projects. If your organisation uses analysis projects, the data sources imported into a project, the datasets built from them, the cell ranges sent from Excel, the analysis journal and the scripts that ran, the results and the conversations with the project's assistant are kept on our servers, in the European Union, while the project is open, then deleted under Section 7. The analysis journal names the member who ran each step or approved a run proposed by the assistant. The assistant receives from the project limited items (names and columns of sources and datasets, row counts, totals and a few sample rows), as well as the members' messages and the history of its conversation, which may repeat those items. The Software is designed to run what the assistant proposes only with the approval of a member with full access to the project.

Procedures and conventions of the agent. The procedures that your organisation writes for the engagement agent, their versions and the conversations used to write them are kept until the procedure is withdrawn; a version cited by an engagement task is kept until the last engagement that cites it is deleted. Where your organisation turns on conventions, the agent can retain, at your request, a way of working; a convention is kept until you or an administrator delete it, or until you leave the organisation, which deletes it.

Blast Audit Academy. If you follow the Blast Audit Academy, we record the lessons and paths you complete, with their date, and your answers to exercises and quizzes, with their score. The owners and administrators of your organisation see your progress and your best score on each quiz. These data are processed on behalf of your organisation and deleted after you leave the organisation.

Usage per member. For each user, the Software records indicators of use: the date (the day, without the time) of the last activity, the number of active days, documents imported, snips, matching runs, OCR pages, runs of the artificial-intelligence features and credits consumed. Together with your name, e-mail address, role and member status, these indicators can be shown to the owners and administrators of your organisation, and exported by them, when one of them turns this view on. The usage of people who have left the organisation is added up on a single "former members" line, with no name; when only one person has left the organisation, that line shows that person's totals.

The view does not contain the content or the name of documents. It contains no timeline, no score, no ranking and no measurement of working time.

For this consultation, your organisation is the controller. NEXT BP is its processor (Section 2.5 of the DPA). The retention periods of usage data are given in Section 4.

This Policy is not the information your organisation must give you before turning the view on, and it is not the consultation of your representatives. To exercise your rights in relation to this consultation, contact your organisation. If you write to us, we forward your request to it. Per-member detail is not sent to the analytics tool.

Support. You can contact us through the support chat or by e-mail. Conversations and their attachments are stored on our servers, on Microsoft Azure in the European Union. When you have not read a reply from our team or from Moulinet, we send it to you by e-mail through Azure Communication Services. Support e-mails, including those sent to support [at] blast-audit.com, are received by Google Workspace, our e-mail provider, or by Cloudflare's e-mail service, and then passed to our servers.

Moulinet, the support's artificial intelligence assistant. When it is active, Moulinet, an artificial intelligence (AI) assistant, receives messages sent to support first, in the chat and by e-mail, including those of visitors who are not signed in. It answers from our public documentation (help center, release notes, the site's product pages, its security page) and from notes written by our team; each of its messages says it is written by an AI. Its replies are checked automatically before they are sent, by Azure OpenAI and, where applicable, by the Azure AI service in the EU Data Zone (articles 5, 6 and 10); this check does not guarantee that they are accurate. These services receive the text of the messages, after every e-mail address and the phone numbers our tool recognises are replaced, the language of the conversation, the extracts of our documentation used to answer and the proposed reply. They receive no data from your account (name, e-mail address, organisation) and no attachment, not even its name. However, a name, a company or a number our tool does not recognise may be sent to them if it is written in a message. You can ask to talk to the team at any time: a button in the chat hands the conversation to the team; a reply to its e-mail does the same, except a reply to a question Moulinet asked to clarify the request.

13. Security

We protect personal data with technical and organisational measures appropriate to the risk, in particular hosting in the European Union, encryption in transit (TLS) and at rest, separation of each organisation's data, restricted access and automatic deletion of document content. These measures are described in Annex 2 to the DPA. To report a vulnerability, see our security page.

14. Changes to this Policy

We may update this Policy to reflect a change in our processing or in the law. The date at the top shows the version in force. A version takes effect on publication; we inform users of any material change by e-mail or in the Software no later than that date.

15. Contact

privacy [at] blast-audit.com
NEXT BP, 127 rue de la Tour, 75016 Paris, France