Legal
Security
Effective date: September 21, 2026
This page provides a general overview of how Solle Prosequi, LLC approaches security for the SolPros service. It is an informational summary, not a contract. The Terms of Service, Privacy Policy, and any signed Data Processing Addendum govern the parties' rights and obligations.
This page is intended to give prosecutor offices and other legal professionals a candid view of what SolPros does well, where the line of responsibility sits, and what SolPros is not designed to do.
1. Summary
- Logical separation. Each Customer Organization has its own workspace with role-based access controls.
- Encryption in transit and at rest is provided through our infrastructure providers.
- Authentication uses email/password with hashed credentials and supports session management. Multi-factor authentication is available as an opt-in account setting.
- Access controls limit personnel access to customer content to a small administrative support account used only for support, security, and operations.
- Backups, monitoring, and logging are in place for service continuity and incident detection.
- SolPros is not CJIS-compliant, is not a HIPAA Business Associate, is not FedRAMP authorized, and is not SOC 2 certified. Customers must not upload data that requires those compliance regimes.
2. Infrastructure and Sub-processors
SolPros is a cloud-hosted application that runs on commercial cloud infrastructure based in the United States. SolPros relies on its providers for baseline controls such as data-center physical security, encryption at rest, network protections, patching, and redundancy. The current list of principal sub-processors is published on the SolPros website.
The Customer Organization's contract is with SolPros; SolPros's contracts with its sub-processors are not directly assignable to customers.
3. Encryption
- In transit: All connections to the Service use HTTPS/TLS.
- At rest: Customer Data stored in our database and object storage is encrypted at rest by our infrastructure providers using industry-standard encryption.
- Backups: Backups inherit encryption-at-rest from the underlying infrastructure provider.
SolPros does not currently offer customer-managed encryption keys.
4. Authentication and Access
4.1 Customer authentication
- Account passwords are stored as salted hashes by the authentication provider.
- Multi-factor authentication (MFA) is available as an opt-in account setting.
- Session tokens are scoped to the user and Customer Organization.
- Invitations to a Customer Organization require email verification.
- Password reset flows use time-limited single-use tokens.
4.2 Authorization
- Each Customer Organization workspace is logically separated.
- Database queries are scoped by Customer Organization identifiers and enforced at the application layer; row-level security policies provide a defense-in-depth control where applicable.
- Roles (owner, admin, member) determine which actions a user can take within a workspace.
4.3 SolPros personnel access
- SolPros maintains a small administrative support account that has the technical ability to access workspace content for support, security, and operational purposes.
- Personnel access is limited to authorized SolPros operators with a legitimate business need.
- Access is auditable through application logs.
- Personnel access for routine support is not used to view content beyond what is needed to resolve an issue.
- Personnel access in response to suspected violations of the Terms and to legal process is governed by the Privacy Policy.
5. Audit Logs
The Service records security-relevant events (logins, permission changes, share-link creation, share-link access, deletions, administrative actions). Audit logs are accessible to Customer Organization owners and admins through the in-app audit log view. Backend application logs and security telemetry are retained on the operator side for a period reasonably necessary for security, fraud prevention, and incident response.
6. Sharing and External Recipients
Discovery sharing is implemented through tokenized links that are scoped to specific content and revocable by the Customer Organization. Share metadata (recipient identifiers, access timestamps, IPs of accessing devices) is recorded for audit purposes. Recipients are bound by the recipient terms displayed at the share landing page.
Once a recipient downloads content, SolPros cannot recall it; revoking a share link only prevents future access.
7. AI Feature Security
The AI Help chat sends user prompts and limited contextual metadata to Anthropic, the AI provider for AI Help, for the sole purpose of generating a response. Under the contract in effect with that provider, prompts are not used to train generally available models. AI Help is rate-limited and subject to a monthly spending cap to limit abuse and runaway cost. AI Help is not designed for, and you should not submit through it, case content or any other prohibited content listed in the Acceptable Use Policy.
Solly Summaries and Transcription work differently. They run open-source models that SolPros selected (Whisper for speech-to-text; pyannote for telling one voice from another in a recording; Qwen for summaries and for translating Spanish lines; Tesseract text recognition for scanned pages) on the SolPros AI server — on-demand graphics servers in the United States operated for SolPros by Modal Labs, Inc., a sub-processor. The controls are:
- One locked door. Only the SolPros application can start a job; the AI server's entry point refuses any request without SolPros's access key, and it cannot read SolPros's database or storage.
- A short-lived link, not a copy. For each job SolPros gives the server a time-limited, encrypted download link to the one file involved (two hours for files in SolPros storage; for a file linked from an evidence vendor, the vendor's own temporary link). A summary of a recording that has already been transcribed sends the text of the saved transcript instead of a link. Labelling the speakers of a recording that already has a transcript sends the link again with the start and end times of the transcript's lines — never their words. The server works from temporary storage that is discarded when the job ends and does not keep the file.
- A one-time secret per job. Results come back to SolPros over HTTPS and are accepted only with a secret created for that job, of which SolPros stores only a hash. Only the finished summary, transcript or speaker numbers are returned; they are stored under the same Customer Organization access controls as other Customer Data.
- What the provider retains. Modal retains the inputs and outputs of the server's processing steps for up to 7 days and then deletes them. Those are the request that started the job (normally the link and the one-time secret, not the file — by then the link has long expired and the secret is useless; for a summary of a recording that has already been transcribed, the request also contains the text of the saved transcript) and the text handed from one step to the next: the text read from a document or saved transcript being summarized, the finished summary, the Spanish lines of a recording with their translations, and, for speaker labels, the times of the transcript's lines and the speaker number given to each (no words). Modal encrypts this data at rest and states that it does not access it. The file itself is not retained, and the server's logs do not contain document or transcript text.
- Voices, not identities. The speaker model separates voices by their sound and returns numbers only. It does not identify anyone and holds no voiceprints of known people; its weights are copied once into SolPros's own model storage, the server runs it without contacting its maker, and its usage reporting is switched off. A name shown for a voice is typed by a member of your Customer Organization.
- Cost and abuse limits. Starts are rate-limited per user, the number of running jobs per organization is capped, and a monthly spending cap applies.
Under Modal's terms, customer data is not used to train AI models.
8. Vulnerability Management and Change Management
- Dependencies are tracked and patched on a routine cadence.
- Code changes are reviewed before release.
- Errors are monitored through a third-party error-monitoring service and acted on based on severity.
- Customers may report vulnerabilities to support@solpros.app. See the Terms for the responsible-disclosure expectations.
9. Backups and Continuity
- The managed database provider supports point-in-time recovery within a rolling window.
- Object storage redundancy is provided by the storage provider.
- These backups are intended for service continuity, not for legal-hold or records-retention compliance — Customer Organizations are responsible for their own evidentiary and records-retention obligations.
10. Incident Response
If we become aware of a confirmed security incident affecting Customer Data, we will investigate, contain, and remediate the incident; notify affected Customer Organizations without undue delay, consistent with applicable law and any signed DPA; provide information reasonably available about what happened, the data involved, and what we are doing in response; and cooperate with affected Customer Organizations on their own notification obligations.
11. What SolPros Is Not
SolPros is committed to candor about what it is not designed to do today. Customers should not rely on SolPros for the following without independent verification:
- CJIS-compliant storage or transit. Do not upload NCIC/III data, criminal history records subject to CJIS Security Policy, or other CJIS-restricted information.
- HIPAA Business Associate. SolPros is not a HIPAA business associate and does not sign Business Associate Agreements at this time. Customer Organizations that are HIPAA covered entities or business associates should not upload PHI in that capacity.
- FedRAMP-authorized environment. SolPros is not FedRAMP authorized.
- SOC 2 certified. SolPros has not undergone a SOC 2 audit.
- Court-of-record / records custodian. SolPros's backups are operational, not authoritative records. Customers remain the records custodian.
- Forensic chain-of-custody system. While the Service preserves upload timestamps and audit metadata, SolPros does not represent that its environment satisfies any specific chain-of-custody standard.
12. Customer Responsibilities
Customers also have a security role:
- Use strong, unique passwords and, when appropriate, the available MFA option.
- Manage role assignments carefully and revoke access when a member leaves or no longer needs access.
- Review what is being uploaded against the Acceptable Use Policy, including the prohibition on CSAM and CJIS data.
- Review share-link recipients before sending and revoke links promptly when no longer needed.
- Notify SolPros at support@solpros.app of any suspected unauthorized access or other security issue.
13. Contact
Solle Prosequi, LLC
Email: support@solpros.app