Trust Center
Last updated: August 2026
Votexia operates under a Zero-Trust model. This page summarizes how we protect your data and isolate every customer. For the data-privacy foundation, start with Metadata-First Architecture.
Metadata-First Architecture
Most compliance tools ask you to upload screenshots, connect databases, or grant broad access. Votexia is built the opposite way. We monitor your compliance posture from infrastructure configuration metadata only — designed to avoid reading or storing patient records. This is the foundation of the product, not a setting you turn on.
| Votexia reads | Votexia never reads |
|---|---|
| Encryption status, port config, IAM policy, logging state | Database rows, storage object contents, patient records |
| Resource tags, region, retention settings | PII / PHI payloads, application data |
HIPAA Compliance
Important: HIPAA does not offer a “certification.” No product can be “HIPAA Certified.” Beware any vendor that claims it. This page describes how Votexia is designed to support your HIPAA compliance — accurately, without overclaiming.
Votexia provides automated technical control monitoring mapped to the HIPAA Security Rule (45 CFR §164.308–312). It automates the collection of evidence that your cloud controls are in place and operating — encryption at rest, transmission security, access controls, audit logging, and more — and preserves that evidence in a tamper-evident ledger for your auditors.
Infrastructure Security
| Subprocessor | Purpose | Data handled |
|---|---|---|
| Application hosting | Serving the app & API | Ephemeral request data |
| Managed PostgreSQL | Primary database | Encrypted evidence, user IDs, hashed passwords |
| Redis (rate limiting) | Abuse protection | IP addresses, user IDs (transient, TTL-expired) |
| Immutable ledger | Tamper-evident audit log | Evidence hashes, action metadata |
| Lemon Squeezy | Billing (Merchant of Record) | Billing email, org ID (no card data touches Votexia) |
| Email delivery | Transactional email | Recipient address, message content |
All stored credentials and integration secrets are encrypted at rest (AES-256-GCM, KMS-managed). Data in transit uses TLS 1.3.
Data Retention & Deletion
Upon termination, all organizational metadata, historical compliance reports, and encrypted integration credentials are permanently, cryptographically shredded within 60 days (subject to any regulatory retention obligation, which applies only to non-PHI metadata and evidence hashes). We do not retain customer metadata beyond our standard disaster-recovery window.
Responsible Disclosure
Votexia takes security seriously and welcomes the security community’s help in keeping our platform safe. If you believe you’ve found a vulnerability, please report it to us privately using the process below.
If you conduct security research and report vulnerabilities in accordance with this policy, we consider your actions authorized. We will not pursue or support legal action against you, and we’ll work with you to understand and resolve the issue quickly.
How to report
Email security@votexia.com with:
- A clear description of the vulnerability
- Steps to reproduce
- A proof of concept, if available
- The impact you believe it has
We aim to acknowledge reports promptly and will keep you updated as we investigate and remediate.
Scope
In scope: Votexia’s public application and API (votexia.com, app.votexia.com). Out of scope: our customers’ cloud environments (test only your own), third-party services we use, and social-engineering of Votexia staff.
Votexia does not currently operate a paid bug-bounty program. Reports are accepted on a good-faith, unpaid basis — and we’re grateful for them.
| Reason | Contact |
|---|---|
| Report a vulnerability | security@votexia.com |
| Security questionnaire / due diligence | contact@votexia.com (we’ll route to security) |
| Request a BAA | contact@votexia.com |
| Pentest summary (enterprise, under NDA) | contact@votexia.com |
| Report a suspected incident affecting your account | security@votexia.com |
What to include in a security report
- A clear description and the impact you believe it has
- Steps to reproduce and a proof of concept, if available
- Your contact details so we can follow up
We aim to acknowledge security reports promptly. Please report privately and do not disclose publicly until we’ve remediated and authorized disclosure.