PILLAR Security

Security at PILLAR

PILLAR is purpose-built for revenue teams in regulated industries. Your data stays in your control, encrypted at rest and in transit, isolated per organization, and never used for model training or shared with third parties.

Architecture overview

Multi-Tenant Isolation

Every database query is scoped by organization ID through PostgreSQL Row-Level Security (RLS). Customer A cannot access Customer B's data at the database level, regardless of application logic. This is enforced by the database engine itself, not by application code.

No AI Inference in the Data Path

PILLAR's scoring engine is deterministic mathematics, not LLM-based inference. Your data never flows through OpenAI, Anthropic, or any third-party AI model endpoint. Scores are computed via weighted formulas on your PostgreSQL database. No data leaves the database boundary except to write scores back to your own CRM.

Encryption

At rest: AES-256 encryption on all database storage (managed by Supabase/AWS). API keys and OAuth tokens are additionally encrypted at the application layer before storage.

In transit: TLS 1.2+ on all connections. HSTS enforced. No plaintext endpoints.

Authentication & Access

User authentication via Supabase Auth (bcrypt-hashed passwords, session tokens). OAuth 2.0 for CRM and third-party integrations. API keys for MCP server access are stored as SHA-256 hashes. Role-based access controls limit what each user role can see and do.

Infrastructure partners

PILLAR runs on enterprise-grade infrastructure from partners who maintain their own compliance certifications.

Provider	Purpose	Region	Certifications
Supabase (AWS)	Database, authentication, RLS	US East (Virginia)	SOC 2 Type IIHIPAA eligible
Vercel	Application hosting, edge network	US (multi-region)	SOC 2 Type II
Cloudflare	Marketing site hosting, CDN, DDoS protection	Global	SOC 2 Type IIISO 27001
GitHub	Source code repository (private)	US	SOC 2 Type II

For a complete list of sub-processors, see the Sub-Processor List.

Data handling

What PILLAR processes

Revenue operations metadata: Account names, contract values, renewal dates, opportunity stages, territory assignments
Business contact information: Names, titles, email addresses, and phone numbers of administrators, sales contacts, and stakeholders (not students or end users)
Engagement metrics: Email/calendar activity summaries, support ticket metadata, NPS survey scores, product usage aggregates
Computed intelligence: Health scores, risk scores, priority scores, signals, and plays generated by PILLAR's scoring engine

What PILLAR does not process

Student educational records or personally identifiable student information
Full email or message bodies (only headers, timestamps, and participation metadata)
Payment card data or banking information
Protected health information (PHI)

FERPA Position

PILLAR processes revenue operations metadata about education organizations (district names, contract values, administrator contact information). PILLAR does not store, process, or have access to student educational records as defined under the Family Educational Rights and Privacy Act (FERPA). PILLAR is a revenue operations tool used by the vendor's sales and customer success teams, not by educators or students.

Data Retention

Active customers: Data retained for the duration of the service agreement plus 90 days after termination to allow for data export
Post-termination: All customer data deleted within 90 days of contract termination, or earlier upon written request
Backups: Automated daily backups retained for 30 days, encrypted, same region as primary database
Logs: Application logs retained for 30 days. Error monitoring data retained for 90 days.

Data Portability

Customers can export all of their data at any time via the PILLAR dashboard or MCP API. Upon termination, PILLAR provides a complete data export in standard formats (CSV, JSON) within 5 business days of request.

Operational security

Incident Response

PILLAR maintains an incident response process. In the event of a confirmed data breach affecting customer data, PILLAR will notify affected customers within 72 hours of confirmation, consistent with GDPR Article 33 timelines. Notification includes: nature of the incident, data affected, remediation steps taken, and point of contact for questions.

Vulnerability Management

Dependencies monitored for known vulnerabilities via automated scanning
Security patches applied within 7 days for critical vulnerabilities, 30 days for non-critical
Production deployments require passing build checks before promotion

Access Controls

Production database access restricted to service role keys, never exposed to client-side code
Employee access to customer data limited to support and debugging purposes, logged, and reviewed
OAuth tokens and API keys encrypted at the application layer before database storage

Compliance documentation

The following documents are available upon request or during procurement:

Data Processing Agreement (DPA) - standard DPA covering data processing terms, sub-processors, and data subject rights. Available for execution with any customer agreement.
Sub-Processor List - published at pillargtm.com/legal/sub-processors
FERPA Compliance Statement - available upon request
Security Questionnaire - PILLAR can complete SIG Lite, CAIQ, HECVAT, or custom security questionnaires. Contact security@pillargtm.com

Last updated: April 2026. For security inquiries, contact security@pillargtm.com