Privacy

Keep the public site
deliberately narrow.

BitTwelve is currently in private development. The operational service is disabled. Product screens remain publicly visible as non-operational previews, but the live site does not accept twelve-word codes, create or recover hosted maps, sell memberships, or collect membership information through those workflows.

01

No recovery-word entry.

The public site shows disabled twelve-word and creation interfaces so the product can be evaluated, but they do not accept input or generate codes. Creation, recovery, update, membership, email, and billing APIs remain disabled at the server.

02

No live membership checkout.

BitTwelve is not currently accepting new subscription payments. Stripe integration remains part of the private product code. The membership screen is visible as a product preview, but checkout and billing actions are disabled while the project is paused.

03

Contact happens through email.

If you choose to email hello@davisvillelabs.com, your email provider and the receiving mail service will process the information you send. Do not send wallet seeds, private keys, passwords, authentication codes, or other sensitive access credentials by email.

04

Measure the site, not the person.

BitTwelve uses Cloudflare Web Analytics for privacy-focused traffic, referral, page-use, and performance measurement. Cloudflare states that its RUM beacon does not use browser cookies, localStorage, sessionStorage, or IndexedDB for measurement. BitTwelve does not intentionally use Google Analytics, advertising pixels, social widgets, or behavioral advertising cookies.

05

Ordinary delivery still creates metadata.

Cloudflare and ordinary internet infrastructure may process IP addresses, timestamps, device details, requests, abuse-prevention signals, and logs needed to deliver and secure the website. BitTwelve does not promise network anonymity.

06

The product design still favors separation.

The private product architecture was designed so readable recovery-map content is encrypted in the browser and membership identity remains separate from the encrypted recovery package. Those design details remain documented on the Security page, but operational use is currently disabled.

The current privacy boundary

There is no live recovery workflow to send a map or twelve-word code to BitTwelve.

Questions

Contact Davisville Labs.

Email hello@davisvillelabs.com