Privacy

Know less.
Store less.

BitTwelve is built around data minimization twice over: the service asks for no account, and users are encouraged to store only a recovery roadmap rather than the sensitive credentials or documents themselves.

01

No account required.

BitTwelve does not require a profile, beneficiary record, social login, phone number, or email address to create or open a recovery map.

02

Keep sensitive originals out.

Do not enter wallet seeds, private keys, passwords, authentication codes, legal originals, identity documents, financial account credentials, or other information whose disclosure alone could create access or control. A useful BitTwelve should contain directions to those materials, not copies of them.

03

Readable roadmap text stays local before storage.

Creation and decryption are designed to happen in your browser. The hosted service stores an encrypted package rather than the readable roadmap. The twelve-word code is not intentionally transmitted during normal creation or recovery.

04

No advertising profile.

BitTwelve is designed without advertising pixels, social widgets, analytics cookies, or third-party runtime fonts. It does not intentionally build a behavioral advertising profile around visitors.

05

Hosted use still creates metadata.

Cloudflare, internet providers, browsers, and other network infrastructure may process technical information such as IP addresses, timestamps, device details, and requests required to deliver the site. BitTwelve does not promise network anonymity.

06

Encrypted does not mean risk-free.

No browser-based software is risk-free. Keep an independent offline recovery path, minimize what you place in the map, and never make BitTwelve the only route to important information.

The privacy boundary

The safest data to protect is data the service never needs to receive.

Private by design

No account.
No credential vault.
Just a map.

Read the security model