ZippleeZipplee
Trust & Security

How we protect your data

Zipplee (and our benefits-communication product, Zipplee) is operated by Custom Ai Apps LLC. We hold employee and HR-adjacent content for the companies we serve, and we take that responsibility seriously. This page explains — honestly — how that data is secured, where it lives, who processes it, and where we are on our compliance roadmap.

Encryption

All data is encrypted in transit and at rest.

Tenant isolation

Every customer ("tenant") is logically separated from every other customer at the database level. We enforce this with PostgreSQL Row-Level Security (RLS).

In plain language: each row of data in our database is tagged with the company it belongs to. Row-Level Security is a rule, enforced by the database itself, that checks the identity of whoever is asking before any data is returned — and only ever hands back rows that belong to that requester's company. There is no code path a customer can take to read another customer's data, because the database refuses the request, not just the application. This isolation is applied to every customer-facing table.

Authentication

Access to your workspace is protected by JWT-based authentication. When a user signs in, they receive a short-lived, signed token (a JSON Web Token) that the system verifies on every request. That token also carries the user's identity into the Row-Level Security checks described above, so authentication and data isolation work together rather than as separate, optional layers.

We practice least-data collection — we ask for and store only the information needed to run the product, and we do not collect employee data we have no use for.

Where your data is hosted

Application & data

Supabase (managed PostgreSQL database, authentication, file storage, and edge functions), running on Amazon Web Services in a United States region.

Website & content delivery

Netlify provides static hosting, a global CDN, and TLS certificates for the pages and published content we serve.

Document rendering (turning content into PDFs) runs on a dedicated Railway worker. It receives document content only for the duration of a render and does not serve as a system of record.

Our sub-processors

We use a small, deliberate set of established sub-processors to operate the product. Each one handles a specific function:

ProviderPurpose
SupabaseDatabase, authentication, storage, and edge functions — the core application data layer.
Amazon Web ServicesUnderlying cloud infrastructure that Supabase runs on (US region).
NetlifyStatic website hosting, global CDN, and TLS.
RailwayPDF / document rendering worker.
OpenAIAI text generation for content-drafting features.
AnthropicAI text generation for content-drafting features.
TwilioSMS notifications and alerts.

The full, current list — including the specific data each provider processes and its location — is maintained on our sub-processors page. We do not sell customer data, and we do not permit our AI providers to train their models on your content.

Compliance posture

We want to be precise here, because security pages too often imply certifications that don't exist. Here is the honest picture:

Reliability & backups

Security contact

If you have a security question, a concern, or wish to report a vulnerability, contact us at security@zipplee.io. We read and respond to every report.