OPTION63

Share contacts on your terms.

option63 rewrites vCard data at the point where it leaves a trusted environment — before it reaches unvetted devices, untrusted clouds, or AI ingestion. Only what you allow ever crosses the line.

How it works

option63 rewrites each vCard at the boundary — sensitive fields are removed, masked, or relayed before the contact ever reaches an untrusted device, cloud, or AI agent.

Before Trusted device or cloud
BEGIN:VCARD
VERSION:4.0
FN:Jamie Morgan
ORG:Option63 Ltd.
TITLE:Account Manager
TEL;TYPE=cell:+1-555-0142
EMAIL:jmorgan@corp.example
NOTE:Calls contract renewal — $240k ARR, renewal 09/15
END:VCARD
Full name Org + title Real email Revenue note
option63
↓ filters, transforms
After Un-trusted device, cloud or agent
BEGIN:VCARD
VERSION:4.0
FN:J.M.
TEL;TYPE=cell:+1-555-0142
EMAIL:4deef0b60a8c@relay.option63.eu
END:VCARD
Initials only Relay email Org stripped Note stripped

Three ways to use option63

A Rust library for integration, a CLI for pipelines, and a CardDAV proxy — all RFC-compliant, memory-safe, and designed for privacy-critical workflows.

Rust crate

`o63` — parse and display vCard files. RFC-compliant, memory-safe, built for privacy-critical infrastructure.

cargo add o63

Command line

Validate, display, and filter vCard properties — build privacy-preserving export and ingestion pipelines.

o63 vcard --help
in progress

CardDAV proxy

Make your contacts (Google, Outlook, etc) available through a CardDAV server with filtering applied.

o63 carddav --help

Need this in your stack?

We build custom deployments and CardDAV or AI integrations, run your infrastructure, or handle it for you — on-premises or hosted, with ongoing support.