Security and trust

Sliick Docs is built to a Salesforce-first security model and has passed the AppExchange security review. This page is the short version for a security or compliance reviewer.

• Your data never leaves Salesforce on the standard path. PDF and Word documents are generated natively, inside your org. No external rendering service, no third-party endpoint, no Remote Site or Trusted Site is required. The same is true of native e-signature. The two premium capabilities that do use an external service, high-volume rendering and the cryptographic signature seal, are opt-in, provisioned per organisation, and described as such where they appear in this documentation.
• Your existing Salesforce permissions are enforced everywhere. Every read and write Sliick Docs performs runs with the user’s own sharing, profile and field-level security. Two users see only the data they are already entitled to see, in the editor and in the generated documents.
• Published releases are frozen snapshots. Each Publish action creates an immutable release that the package treats as read-only, and edits and deletes are refused through every Sliick path. A document generated today will look identical a year from now, even if the underlying template has been rewritten.
• Every generation is fully audited. Each file, single or bulk, is logged as a generation with who ran it, when, in which format, against which record, with which template release, the resulting file, and, when auto-email is on, every recipient address.
• Fingerprinted audit log for regulated industries. When per-template audit is enabled, every successful generation captures a fingerprint of the resolved merge values for integrity verification, written through a protected path so users cannot suppress or forge entries. The fingerprint defends against accidental corruption and tampering by non-administrators; as with any in-org integrity scheme, a Salesforce System Administrator retains the platform-level ability to edit their own org’s data, so layer Field History Tracking on the audit records if regulator-grade tamper evidence is a requirement.
• Retention policies are enforceable. Per-template auto-delete windows are honoured by a nightly sweep, and the generation row survives as audit trail even after the file is gone.
• Least-privilege permission sets out of the box. End users only get the ability to generate, automation accounts only get what they need to run, and admin rights stay with a small group of template authors. See Install and permission sets.
• Reviewed by Salesforce, not by us. Sliick Docs is listed on the AppExchange, which means an independent Salesforce security review has examined the package against the AppExchange Security Requirements before it was made available.

Detailed technical guarantees are available on request for security-review processes. Get in touch.