Security by design
Permissions, identity and audit are part of the platform foundation, shared by every module.
- Shared permission model across modulesAvailable
- Least-privilege defaultsTo confirm
Security
Security that starts with who may see what.
Pulsor is built on one principle: AI only sees what the user is authorized to see. This page describes our security approach. Controls marked “To confirm” are being verified and will be published on the Trust Center.
Security
AI only sees what the user is authorized to see.
Permissions are enforced before retrieval, not after generation. Two people can ask the same question and receive different, correct answers.
Same questionWhat is the status of Project Atlas?
Project member
3 sources usedAtlas is on schedule for phase 2. Budget consumption is 64% [1]; the vendor review closes on the 18th [2].
[1][2][3]
External contractor
1 source usedI can share the public project brief [1]. Budget and vendor details are outside your access.
[1]restrictedrestricted
Controls by domain
Identity & access management
Federated identity and role-based access control.
- RBAC — roles and application permissionsAvailable
- SSOIn progress
- OIDC (supported in the architecture)In progress
- SAML (being hardened)In progress
- Second factor: personal PIN after the password (company policy)Available
- Authenticator-app (TOTP) MFA for every userPlanned
Permission-aware AI
Retrieval is filtered by the requesting user's rights before any content reaches the model.
- Pre-retrieval permission filteringAvailable
- Restricted items never disclosed in resultsAvailable
- Windows file rights read by Pulsor Agent and applied before the AI, never wider than WindowsIn progress
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
Auditability
Visibility into access and administrative actions.
- Audit logsAvailable
- Access visibility — sessions, questions, documents opened and exports per employeeAvailable
- Administrative action historyAvailable
Application security
Secure development practices across the platform.
- Secure APIsTo confirm
- Input validationAvailable
- Rate limiting (AI requests, PIN, sign-in, agent pairing)Available
- Dependency security — known-vulnerability audit on every changeAvailable
- Upload security (to be audited before production)Partial
Infrastructure
Hardening and operations of the environments Pulsor runs.
- Hosting provider and regionsTo confirm
- Network segmentationTo confirm
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
Incident management
How security incidents are detected, handled and communicated.
- Incident response process (to be formalized)Planned
- Customer notification commitmentsTo confirm
AI security
Controls specific to AI models, prompts and agents.
- Prompt-injection mitigations (policy in every prompt; ongoing work)Partial
- Agent approval workflowsAvailable
- Model and external-source policiesTo confirm
- Multi-model architecture — cloud and private AI modelsAvailable
- Local AI modelsPer deployment
Private deployment
Private Cloud, On-Premise and Sovereign deployments for maximum control.
- Private CloudCustom
- On-PremiseCustom
- SovereignCustom
Compliance
- ISO/IEC 27001Information security managementPlanned
- ISO/IEC 27701Privacy information managementPlanned
- ISO 22301Business continuityPlanned
- SOC 2Service organization controlsPlanned
- GDPRGDPR alignment — documentation in preparationIn progress
- OWASPSecure development practicesAligned
See Pulsor on your own use cases.
A demo shaped around your sources, your security requirements and your deployment model.