Privacy notice

Who we are

DC Blueprint, Geneva, Switzerland, publishes dcblueprint.com and is responsible for your data (the controller). DC Blueprint is a Swiss company: our data protection law is the Swiss Federal Act on Data Protection (FADP), and we also apply the GDPR where it covers readers in the EU and the UK. We have not appointed a representative in the EU. Contact: [email protected].

This notice covers dcblueprint.com, its account pages and its AI connector.

Cloudflare

Every request to dcblueprint.com passes through Cloudflare, which protects the site against attacks and delivers its pages. To do that Cloudflare handles your IP address, your browser's user agent and the address you asked for, and keeps security records, such as requests it blocked, under its own privacy policy. If Cloudflare challenges a request it believes is automated, it may set a cookie of its own, such as cf_clearance, to remember that the challenge passed. We rely on our legitimate interest in keeping a public site safe and available.

Our server

The site and its database run on a server we rent in the European Union. The server writes no access log, so the pages you read are not stored there. The app keeps a system journal of service events, such as a restart, a page that failed, the kind of an email sent (never its address or content) and the random identifiers of an erased account, so that an erasure can be applied again after a restore. Older entries are overwritten as the journal fills.

To limit abuse, sign-in attempts, emailed links and calls to the AI connector and runs of the member tools are counted against a keyed hash of your email address, your account or your network, never the address itself. Each counter runs for a minute, an hour or a day, and is deleted at the next daily clean-up. We rely on our legitimate interest in keeping accounts and the connector safe.

Cookies and browser storage

dcb_theme remembers whether you chose the light or the dark theme. It is set only when you press the theme button at the foot of a page, holds the word light or dark and lasts a year.

ss_noga is set only if you open a dcblueprint.com address ending in ?ss_noga=1. It tells the site to load no analytics in that browser for a year, and ?ss_noga=0 removes it. We use it to keep our own visits out of the figures, and you can use it the same way.

The account pages set four more cookies of ours, all limited to dcblueprint.com and unreadable by scripts. __Host-dcb_session keeps you signed in for 24 hours from the moment you sign in; it holds a random token, and our database keeps only a hash of it. __Host-dcb_csrf protects the account forms and ends when you close the browser. __Host-dcb_b ties an emailed sign-in link or a Google sign-in to the browser that asked for it, for 15 minutes. __Host-dcb_rp holds a password reset for its 30 minutes, so the reset link leaves the address bar.

The Build and Operate steps can save your figures in your own browser's local storage, and the Plan reads them back there. They are never sent to us, and clearing your browser data removes them. A Plan you share lives in its link.

These cookies record a choice you made or keep a service you asked for working, and are used for nothing else. We set no other cookie, and the site shows no advertising.

Analytics

DC Blueprint uses Google Analytics 4 in a property of its own, not shared with any other site. It counts page views, scrolling, clicks on links to other sites and a few events of ours: a step of the Plan opened, a market chosen, a figure edited in place (which field, not the figure), a link shared or printed, a tool run, a block saved, an account created (sign_up) and a sign-in (account_signin). These events carry a step, a market, a tool or the sign-in method, never your figures, your email address or your account. Page views carry the page's address without the part after #, where a shared Plan keeps its figures.

Visitors in the EU, the EEA, the UK and Switzerland send Google only measurements without cookies, which do not identify your browser. We show no consent banner, so no analytics cookie is set for them. Elsewhere Google Analytics sets its own cookies on dcblueprint.com (_ga and _ga_ followed by the property id, kept for two years) to recognise a returning browser. Google Analytics 4 does not log or store IP addresses: Google uses the address to work out an approximate location and then discards it. Google signals are off, ad data redaction is on, and the property is linked to no advertising account. We read only aggregated reports and Google keeps the event data for two months, the shortest period it offers. Browsers that report automation, and any browser with ss_noga, load no analytics at all. We rely on our legitimate interest in knowing which pages and tools are useful.

Accounts

An account keeps your email address in lower case, whether and when it was confirmed, when you signed up and last signed in, your organisation and your role in it, and, if you set a password, only a hash of it. You can sign in with a password, with a link we email you or, where the sign-in page offers it, with Google. Google then confirms your email address and gives us a stable account identifier, which we keep to recognise you next time. We ask Google for nothing else, such as your name or picture, and keep no Google password or token. A sign-up with a password whose address is never confirmed is deleted after 30 days.

Every account here is created here: we import no account, password or project from another site. A free account keeps one project; a licence keeps more. We use your projects only to show your work to you, and we never sell them, share them or use them in any dataset or publication of ours.

Delete my account, on your account page, erases your account, your sign-in links and sessions, and every organisation you are alone in with its projects, licence record and connector key. A paid plan has to be cancelled first, so no subscription keeps billing after the account is gone. We keep one salted hash of your address so the same address cannot start a second free trial, and a record of the erasure that holds only random identifiers. We process account data to provide the service you signed up for (the contract with you).

Licence and payments

A licence starts with a 7-day trial without a card. Licences are sold through Stripe Managed Payments, under which Stripe is the merchant of record: Stripe sells the subscription to you, takes the payment, charges the tax, sends receipts, handles refunds and disputes and keeps your card and billing details under its own privacy policy. We never see your card. When you buy, we send Stripe your email address and our identifiers for your account and organisation. From Stripe we keep your customer and subscription identifiers, the prices, seats and site packs you chose, the status of the subscription and when it renews or ends, and the time you asked for access to start at once with the version of the terms you accepted. We keep Stripe's event identifiers for 30 days so a message from Stripe is applied once, and a note of any billing problem, such as a refund or a payment with no account, by Stripe identifier only. As merchant of record, Stripe keeps the purchase and invoice records; ours go with your account. We process licence and payment data to perform the contract with you.

When a licence lapses, the projects beyond the one a free account keeps stay readable for 90 days. We email you on day 80, and on day 90 those projects are hidden from every view and marked erased; they are removed for good with your account. For the board we count licence events, such as a trial started or a plan paid, under a short hash that names nobody.

AI connector

The AI connector lets an assistant you use ask DC Blueprint for figures. If you make a personal key on your account page, we keep its public prefix, a hash of the secret (the key itself is shown to you once and never stored), when it was made, last used and revoked, and how many runs and calls your account used each month and day. Your assistant sends us its question, such as a market and a tier, which we use to answer and do not store: one hash of the tool, market, tier and day prevents counting a repeat twice, and is deleted after the following month.

For every call, with or without a key, we count the day, the tool and the name the assistant gives for itself, with no address, key, account or question, and keep the counts for 400 days. We process connector data to provide the service you asked for and, for the counts, on our legitimate interest in knowing how the connector is used.

Emails we send

Account emails come from send.dcblueprint.com through Resend, which receives your address and the message to deliver it: a sign-in link, a confirmation, a password reset, a notice that an address already has an account, a change of sign-in email (to both addresses), the trial emails when it starts and three days before it ends, a reminder before a card trial turns paid, a note when a licence ends, the day 80 warning and one confirmation after a purchase. These emails are part of running your account and your licence. We send no newsletter or advertising from dcblueprint.com.

How long we keep it

Sessions end after 24 hours and are deleted the next day. Emailed links work for 15 minutes (sign-in), 30 minutes (password reset), 24 hours (email change) or 48 hours (confirmation), and are deleted once used or expired. Account data stays until you delete the account. Each night we take an encrypted copy of the database, encrypted so that the server itself cannot read it, and keep it on the server for 14 days; encrypted copies we take off the server for recovery are removed when we decide. If we ever restore one, every erasure made since it was taken is applied again before the site reopens.

Writing to us

When you write to us, we keep your message and your address so we can answer you, and delete them when you ask. We rely on our legitimate interest in answering you.

Sharing

We share data only with the services named here: Cloudflare, our hosting provider, Google (analytics, Google sign-in and our mailbox, so it sees what you write to us), Stripe and Resend. Cloudflare, Google, Stripe and Resend may process data outside Switzerland and the EU under the EU standard contractual clauses and the Swiss and EU data privacy frameworks. We never sell personal data.

Your rights

You can ask to see, correct, delete or restrict the use of your data, receive a copy of it, or object to processing based on our legitimate interest, by writing to [email protected]. You can also contact the Swiss Federal Data Protection and Information Commissioner or your local data protection authority.

Changes

If this notice changes, we update this page and its date.