PrintCrate
How it works Templates Pricing
Nonprofit & donor mailingsNPSP admins Small business & membershipOps & admin teams
All guides Setup guide FAQ
Guides
About Security Pricing FAQ
Join the waitlist
Product
How it works Templates Pricing
Solutions
Nonprofit & donor mailings Small business & membership
Guides & resources
All guides Setup guide FAQ
Company
About Security Terms Privacy
Join the waitlist
Security

Your record data never leaves your Salesforce org.

PrintCrate runs entirely as Apex and Lightning components inside your own org. There's no external server, no separate database, and no third-party service in the data path.

Fully native

Record selection, field mapping, and PDF generation (via Apex's Blob.toPdf()) all run inside your Salesforce org. No external backend exists for PrintCrate to call.

Standard field-level security

The field picker only ever shows fields the running user can already see — verified directly with a restrictive, minimum-access test profile, not just an admin account.

No data retention outside the PDF

Generated PDFs are handed back to your browser for download. PrintCrate doesn't store a copy, log the contents, or retain generated files anywhere.

What PrintCrate can access

Scoped to exactly what a mailing needs.

Permission set grants
  • Read-only access to Contact, Lead, and Account (the objects with a one-click list-view button)
  • Full access to PrintCrate's own usage-tracking and saved-preset objects
  • Access to the Apex classes and Visualforce page that generate the PDF
What it never touches
  • No org-wide "View All Data" or elevated access of any kind
  • No write access to your Contact, Lead, or Account records
  • No outbound integration or external API call in the label-generation path
Billing is the one external call. Upgrading to the paid tier talks to Stripe directly from your browser session to open a real checkout — that's the only place PrintCrate makes an external request at all, and it carries no record data, only the checkout itself.