Your code never leaves your machine.

What we collect

Bounded by design, listed in full.

Profiles

Name, email, avatar, GitHub username, handle, and onboarding preferences.

CLI and private work

When you submit a bundle from the CLI, our servers receive bounded metadata only: commit counts and time histograms, file extensions with shares, category churn, detected skill slugs with counts and dates, ownership ratio, signed-commit stats, AI-workflow counts, an authorization attestation, and opaque fingerprints. The full field list is the public schema (bundle.v1.json).

Source code, diffs, commit messages, and file paths never reach our servers from the CLI.

Defenses

Live defenses record audio (and optional camera video). We store the recording, a transcript, and the evaluation results.

Opt-ins

Evidence clips on your public profile are visible by default; you can turn audio and video visibility off at any time. Only you can change your own toggles.

Partners

When a hiring partner requests a verification through our API, we store the candidate's email and name they provide, scoped to that partner.

GitHub tokens

We store GitHub App tokens in order to read the repositories you explicitly authorize. They live in a deny-by-default table no client can read.

Payments

Payments are processed by Stripe; we store subscription status and identifiers, never card numbers.

Code never reaches us

The CLI is open source, and its scan makes zero network calls.

The CLI is open source (Apache-2.0); its scan makes zero network calls, and you review the bundle before anything is submitted.

See the code yourself: the public redential-cli repository, the bundle.v1.json schema that defines every field we can receive, our privacy principles, and the privacy tests that enforce them.

Your machine

Open-source CLI. Code stays local.

Bounded metadata

Public schema.

Redential platform

Where it lives

Infrastructure and encryption.

Hosting

Supabase (AWS us-east-1, N. Virginia, USA) hosts the database, file storage, and authentication.

Application

The application runs on Vercel, served over HTTPS with HSTS.

Encryption

Data is encrypted in transit (TLS) and at rest by our infrastructure provider (AES-256, per Supabase's documented standard).

Who can access it

Deny-by-default, server-only, small team.

Row-level security (RLS) is enabled on every table; sensitive tables are deny-by-default and readable only from the server.
The service role key is server-only and never reaches the browser.
Production access is limited to the founder. Small team by design.
Production accounts (GitHub, Supabase, Vercel, Stripe) are protected with two-factor authentication.
Webhooks verify signatures (Stripe and GitHub, HMAC constant-time) before we trust any payload.
Secrets live in environment configuration, never in the repository.

Subprocessors

Every service, and exactly what it receives.

Service	What it receives
Vercel	Hosts the application; processes web traffic.
Supabase (AWS)	Database, file storage (defense recordings), authentication.
OpenAI	Audio of live defenses, for speech-to-text.
Anthropic	For connected GitHub repos: file contents, to detect and judge capabilities. For CLI bundles: bounded metadata only, never code. Also defense transcripts.
Resend	Transactional email: recipient address, name, profile handle.
Stripe	Payment processing: billing identity and subscription state.
PostHog	Product analytics: user id, email, onboarding intent, usage events.
Sigstore/Rekor	A public transparency log receives only an opaque, irreversible fingerprint of submitted work history. Entries cannot be deleted from that log.
GitHub	Reads repositories you explicitly authorize via the GitHub App.
cal.com	Scheduling for sales calls.

Retention and deletion

You can take it all back.

Account deletion

Deleting your account removes your profile, repositories, verifications, submissions, installation, and login immediately.

On request

Defense recordings, transcripts, and billing records are deleted on request: email juan@redential.com. We respond within 30 days.

Transparency log

Fingerprints already written to the public transparency log cannot be deleted from that log, by design.

Everything else

We do not sell personal data.

We retain data for as long as your account is active. Backups follow our provider's standard cycle.

If something goes wrong · Compliance (UK GDPR)

Incident response and UK GDPR.

Incident notice

If a security incident affects your data, we notify you at your account email without undue delay.

Legal basis, developers

For developers, our legal basis for processing is performance of a contract (Art. 6(1)(b)).

Legal basis, candidates

For candidates referred by a hiring partner, the partner is the data controller and Redential acts as processor under their instructions. The candidate always initiates the process explicitly, by opening their link and authorizing it.

International transfers

International transfers: our infrastructure providers rely on recognized transfer mechanisms documented in their own terms (AWS participates in the UK Extension to the EU-US Data Privacy Framework; provider agreements include Standard Contractual Clauses). Transfers are further covered in our Data Processing Agreement, available on request.

Data processing agreement

A Data Processing Agreement is available on request.

SOC 2 / ISO 27001

SOC 2 / ISO 27001: on our roadmap as we grow with enterprise customers.

Security contact: juan@redential.com

Open source

Don't trust us. Read the code.

The CLI is open source (Apache-2.0); its scan makes zero network calls, and you review the bundle before anything is submitted.

$ npx redential scan

View on GitHub →

Security contact

Questions about security?

Enterprise reviews, DPAs, and vulnerability reports. We're happy to go deep.

juan@redential.com Book a call