Data Security

Pluraprint is built to keep the files and data your organization entrusts to it safe. This page gives a plain-language overview of how your data is protected. It’s useful when your team or your security reviewers want to understand where things stand.

Where your files live#

When your users submit prints, Pluraprint stores the design and sliced files they upload, along with generated thumbnails and printer camera snapshots, in secure object storage. Hosted deployments can use managed storage, where Pluraprint operates the storage connection and keeps provider credentials outside your deployment. Each deployment has its own isolated file assignment. On-premises and air-gapped deployments retain direct access to the object storage your administrators configure. Your deployment’s storage arrangement determines where files live. For managed storage, permitted regions are checked separately for new read links and uploads, including uploads already in progress. Your administrator can ask Pluraprint to confirm the assigned storage region and any residency requirements.

Managed storage limits new uploads when its capacity is full. Existing files remain available under the deployment’s read policy. If the managed service is temporarily unavailable, files already cached locally may still work; opening an uncached file or uploading a new one may need to wait for recovery. Your administrator can contact Pluraprint to review capacity or service availability.

Encryption at rest#

Production storage requires encryption at rest. Direct deployments verify their storage policy at startup. For managed storage, Pluraprint verifies the provider’s encryption policy before issuing new upload access, and the deployment checks signed policy evidence at startup.

Encryption in transit#

Data moving between the web app, services, on-site agents, and storage travels over encrypted TLS connections. Files are transferred using short-lived, links scoped to one file and operation rather than long-standing public URLs. Managed read links normally expire after five minutes; printer and large-download flows can receive up to one hour. A link can be reused until it expires, so treat it as private. Changing access policy stops new links; previously issued links may continue to work until expiry.

Stored credentials#

Sensitive credentials that Pluraprint holds on your behalf, such as single sign-on tokens and printer access codes, are individually encrypted before they’re stored, so they’re never kept in plain text. API keys are shown once at creation and stored only in a form that can’t be reversed.

Account access#

Pluraprint accounts are created by your administrators or through your single sign-on provider: open, public sign-up is off by default. If your organization chooses to enable self-service registration, new users must verify their email address before they can sign in, so an account can’t be activated without proving ownership of the address. See Signing In for the sign-in and registration experience, and Roles & Permissions for how access is scoped once someone is in.

Questions and compliance#

If your security or compliance team needs more detail for a vendor review, a data-processing agreement, or an on-premises deployment, reach out to your Pluraprint contact and we’ll work with them directly.