DRAFT for review. This page is authored ahead of counsel review and still contains placeholders — shown in brackets — that Uniqcli will finalize before it is published. It describes current practice in plain English and is not final legal text.
This is our trust center: a plain-English summary of the safeguards built into the Uniqcli platform. Our Privacy Policy at /legal/privacy covers what we collect and why; this page covers how we protect it. Uniqcli's website and services are directed to customers in the United States.
Protections built into the platform
These are enforced in the site's and backend's code, not just stated as policy:
Field-level encryption at rest. Sensitive fields — a business's federal EIN and any tax-exemption certificate number — are encrypted with AES-256-GCM before they are stored, and the EIN is displayed back only as its last four digits.
Deny-by-default, role-gated access. Portal requests are denied unless a signed-in identity's role explicitly allows them, so staff and buyers reach only what their role permits.
Audit logging. Sensitive administrative actions are recorded to an audit trail.
Email masking in logs. Email addresses are masked in operational logs rather than written in full.
Payment data isolation. Card and payment credentials are handled by our payment processors, Stripe and PayPal, and are never stored on Uniqcli's systems; our records hold at most a payment-method reference, the card brand, and the last four digits.
Fail-closed configuration. When a security-critical setting is missing, the affected path rejects the request rather than proceeding in an insecure state.
Signed unsubscribe links. The unsubscribe link in marketing email is HMAC-signed and verified in constant time, so an unsubscribe request cannot be forged.
Privacy-signal-gated analytics. When your browser sends Global Privacy Control or Do Not Track, our analytics scripts do not load at all and no analytics data is collected for that visit.
Operational practices
Alongside the platform controls above, Uniqcli maintains operational practices that are managed by people and process rather than enforced in code. Because these cannot be verified from the code alone, they are marked for confirmation before this page is published:
A designated data custodian is responsible for how customer data is handled. [Attestation — dee confirms before publication.] [Custodian role/name — dee confirms.]
Access to systems and data is reviewed on a regular cadence. [Attestation — dee confirms before publication.] [Access-review cadence — dee decision.]
Data is backed up and can be recovered. [Backup and recovery details — dee confirms.]
Related pages
For the full picture of what we collect, share, and retain, and your choices, see the Privacy Notice at /legal/privacy. For information that must not be submitted through public channels and how to request an approved channel, see /legal/controlled-information. For how to tell genuine Uniqcli email from impersonation and report a suspicious message, see /legal/report-phishing.
