Trust & Data Handling
Security and data handling at Plavidian
Campaigns, government offices, and commercial mailers hand us voter files, constituent data, and customer lists. This page states plainly how that data is handled. Every claim here describes practice that exists today; where we have not verified something, we say nothing rather than round up.
Accounts & Access
Individual accounts, separated roles
Authenticated accounts
Access to Plavidian Connect requires an individual authenticated account. Passwords are stored as salted hashes, never in plain text, and there are no shared logins in the application design.
Role separation
Customer accounts and administrative accounts are separate roles. Customer users cannot reach administrative functions, and each customer account sees its own jobs and files.
Login activity is logged
Sign-ins to customer accounts are recorded, giving each account an activity record its owner can rely on.
No card data stored
Plavidian Connect does not store payment card data. Invoicing runs through Xero, and card details never enter our application.
Encryption
Encrypted in transit and at rest
Traffic to Plavidian Connect is encrypted in transit (TLS 1.2 or higher), and customer files and database records are encrypted at rest on Microsoft Azure.
Chain of Custody
Documented from data receipt to USPS induction
Most security pages describe intentions. Ours points at an artifact. The Campaign Mail Assurance™ Report documents what was produced on a job and how the run reconciled to the customer's list, which is chain of custody a customer can hold in their hands rather than a policy they have to take on faith. When camera verification runs on a job, every piece read is part of that record.
AI Features
Exactly what our AI does and does not see
The Plavidian Mail Expert answers USPS questions from a curated knowledge base we maintain. Retrieval runs on our own systems: the relevant USPS reference material is looked up locally and sent to the Anthropic API together with the question you typed. That is the whole payload. Customer mailing lists, job files, and artwork are never sent to any AI service, and under Anthropic's API terms, API inputs and outputs are not used to train models. We can be specific here because we built the data path and read it before writing this paragraph.
Campaign Confidentiality
Your list produces your mailing
Customer files are scoped to the customer's own account in Plavidian Connect: your proofs, artwork, and lists are visible to your account and to the production staff working your job. Questions about how a specific data set will be handled are welcome before you send it: orders@plavidian.com.
Data Retention
Kept while it is useful, then removed
Portal data tied to a job - uploaded files, mailing lists, and the per-piece camera scan records from a run - is retained for five years from the date the job is completed, then deleted. The job's own record, including postal and billing history, is kept longer where accounting and tax rules require it. This means your mailing list and scan data do not sit in the portal indefinitely: once a job has been done for five years, the working data behind it is removed.
What You Will Not Find Here
No badges we have not earned
We do not claim certifications we do not hold, and we avoid words like comprehensive and military-grade on principle. If your organization runs vendor security questionnaires, send one: orders@plavidian.com. Our privacy practices and data compliance commitments are published at Privacy and Data Compliance.
Questions before you send a file?
orders@plavidian.com · 760-666-3130 · 2210 E Vista Way Ste 6, Vista, CA 92084