Skip to content
Pulsor Suite

Security

Data protection

How Pulsor protects customer data — in transit, at rest, between tenants and inside your own infrastructure.

Controls

Where your data goes

To answer a question, the AI model receives the question and the most relevant excerpts the person may read — not your document base. What leaves your installation, and to whom, depends on the deployment you choose.

  • Files stay in your company's space: on our servers in the cloud, on yours in a private or on-premise installationAvailable
  • With Pulsor Agent and Pulsor Cloud, your files stay on your server: the agent sends Pulsor the text of the folders you assign, over HTTPS, not the files. That text is indexed on Pulsor Cloud servers. Scans without text are sent once for character recognition, then deletedAvailable
  • Text and scanned images are read on the Pulsor server (character recognition), with no external serviceAvailable
  • The search index is computed by a model installed on the server, or by the service of the AI provider you choosePer deployment
  • To answer, the question and excerpts the person may read are sent to the AI model. A short document, or one a user attaches on purpose, can be sent in fullAvailable
  • Administrators choose what the AI provider receives: a strict profile limits each question to 8 excerpts and 8,000 characters, at most 3 excerpts per documentAvailable
  • Your data is not used to train Pulsor models; AI providers' own terms apply to the excerpts they receivePer deployment
  • Figures (Operations add-on) are computed by an engine on the server; the AI only sees column names and two sample rows to write the queryIn progress
  • Meetings (Operations add-on) are transcribed on the server; the audio is deleted as soon as it is transcribedIn progress
  • On-premise or isolated installation with a local AI model: nothing leaves your serversPer deployment

Data protection

Protecting customer data in transit, at rest and between tenants.

  • Encryption in transit (when served over HTTPS/TLS)Available
  • Encryption at rest (depends on deployment infrastructure)Per deployment
  • AI keys and connector credentials encrypted in the databaseAvailable
  • Tenant isolation (logical, multi-tenant)Available
  • Pulsor Cloud: database, documents and cache encrypted at rest (LUKS2, AES); the unlock passphrase is never stored on the serverAvailable
  • History retention set by each company: until deleted, 24 hours, 30 or 90 days, with hourly purgeAvailable
  • “Delete all history” for administrators; at termination, the company's stored files are erased tooAvailable
  • Exclusion patterns (for example “Payroll” or “*.pst”) keep matching files out of PulsorAvailable
  • Technical logs never contain the text of questions, answers or excerptsAvailable

Backup & recovery

Backup and disaster-recovery objectives for managed environments.

  • Backups (depend on the deployment model)Per deployment
  • Pulsor Cloud: encrypted backups (AES-256); deleted data remains in them for 14 daysAvailable
  • Recovery objectives (RPO/RTO)To confirm

Private deployment

Private Cloud, On-Premise and Sovereign deployments for maximum control.

  • Private CloudCustom
  • On-PremiseCustom
  • SovereignCustom

FAQ

Frequently asked questions

See Pulsor on your own use cases.

A demo shaped around your sources, your security requirements and your deployment model.