Local-first architecture

Know the actual privacy boundary.

Local execution, encrypted payloads and managed metadata have different protection boundaries. Preview availability is not production-security certification.

What stays on your computer

Connector credentials, browser sessions, documents, interview media, screenshots, transcripts, detailed automation evidence and local AI prompts remain local by default unless a feature asks to transmit data.

Selected payloads, not whole-database encryption

Selected private payloads are encrypted. The entire SQLite file is not encrypted. Interview company, role and link; workspace title, subtitle and reference; and activity summaries can remain readable local metadata. Device access controls and disk encryption remain important.

What Managed stores

Account and billing metadata, device state and delivery metadata are not the same as encrypted career-record envelopes. Tenant scope is server-derived and reinforced by row-level security. A client-submitted receipt is an assertion, not independently verified employer acceptance; a URL and digest alone are not proof.

Device identity and evaluation

The updated source exposes an installation identity in the desktop settings panel. The published preview, fresh-device pairing, signed ownership and phone-verification delivery still require integration evidence. Account identifier markers currently use normalized SHA-256 hashes; do not treat them as a secret-key HMAC or an absolute one-person/device guarantee.

CV and application evidence

The CV maker currently saves a blueprint. Its score measures populated-field completeness, not ATS quality, factual truth or a generated PDF. Research adapters and client-reported receipts are not proof that every advertised channel has a live, verified submission executor.

Payments and releases

Checkout is Web-only and explicit. Market/provider price matching is required before redirecting to payment. Cancellation is confirmed only by the account service/provider, and paid access uses the returned paid-through date. Native signing, notarization and clean-device validation remain release gates.

Analytics

Third-party analytics and recording are disabled in this build. Re-enabling requires verified private-route lifecycle isolation, masking and consent withdrawal. Public account links use full-document navigation.

Responsible use

Automation and assistance require permission. Read the Acceptable Use Policy →.

Security contact

Report suspected vulnerabilities privately through Cariew Support. Do not include credentials or unrelated personal data.