Skip to content

Data & security

How data is
handled today

This page describes how the Jenny app and this website handle data as they work today. It is factual, not a certification: we do not claim ISO 27001, SOC 2 or any other security certification.

Last reviewed: 21 October 2026

Where Jenny runs

The Jenny app (jennyos.com) runs on Vercel. Workspace records are kept in private Vercel Blob storage that is not publicly readable.

The app’s server functions run on Vercel in its US East region, and workspace records and files are stored in the United States, so we don’t describe Jenny as EU-hosted. Background work, notifications, saved searches and usage limits use a PostgreSQL database hosted by Supabase in the EU (Ireland). The application connects with a restricted database role, and database policies keep each workspace’s rows separate.

Who can get in

Access today uses a workspace access code; a named administrator login with e-mail and password, limited to an approved list of addresses, is deployed but not yet in use. Client trials use a personal access code per named person. Sessions are signed and expire.

Each workspace only sees its own records.

AI processing

Jenny uses Anthropic’s Claude models through Anthropic’s API to read CVs and job descriptions, draft messages and run the assistant. Under Anthropic’s commercial terms, data sent through the API is not used to train their models.

Fit scores are calculated by fixed rules from recorded evidence. AI can propose quoted evidence but never changes a score by itself. Protected characteristics such as age, gender, nationality or health are not ranking criteria.

CVs are generated from recorded facts by fixed rules, not written by AI, and need a “facts checked” confirmation.

Control over outgoing work

Sending requires approval by default; switching that off is an administrator setting (everyone using the shared workspace code is an administrator today). A workspace-wide stop switch pauses all sending. Do-not-contact flags, unsubscribes, suppression lists and daily limits apply to every send.

Actions the assistant proposes with consequences — sending, importing, moving candidates — wait for a single-use confirmation from you.

E-mail delivery is only reported as sent when a real sending provider confirms it. Until a provider is connected for a workspace, Jenny records sends as simulated.

Limits on usage and cost

Each workspace has daily limits on AI work, discovery and LinkedIn searches. Trials have their own spending limit.

This website (jennyhires.com)

CVs and job descriptions uploaded to the public demos are processed in memory to show you a result and are not stored. They are sent to Anthropic for processing; only job titles and a location are sent to LinkedIn’s public job search.

Form submissions (free-trial applications, founding access, integration requests) are stored in a Supabase database in the United States region and used only to reply to you.

Abuse limits use a salted one-way hash of your IP address, kept for 7 days. Analytics are anonymous and cookieless (Vercel Web Analytics).

Not in place yet

Self-service data export and erasure in the workspace, a mailbox connection and calendar integration are not available in production yet. Requests to access, correct or delete personal data can be sent to hello@forti8.io.

Website privacy noticeSecurity questions or a vulnerability to report: hello@forti8.io.