Anyone can claim “we take privacy seriously.” This page is about our principles — the choices we’ve made and the lines we won’t cross. For the technical details on encryption and infrastructure, see our security architecture.
BlushDesk exists because the people who built it watched friends in this industry get deplatformed by mainstream SaaS, doxxed by careless data handling, and squeezed by tools that were never designed with their safety in mind.
We’re not a side project for an investor pitch deck. We’re a small team that chose to build this on purpose, and we treat the responsibility like our own data was in the database — because it is. Giulia runs her own bookings on BlushDesk. If something is broken, slow, or unsafe, we feel it before anyone else does.
Most platforms in our industry either get sold and gutted, or get pressured by investors to “clean up” the user base. We took no VC money. There’s no board meeting where someone suggests we deplatform a category of users to look better on paper.
The only people we answer to are the providers using BlushDesk. That’s the structure by design — not a temporary phase before we “scale.”
You own your data. Not us, not our hosting provider, not anyone else. These aren't legal disclaimers — they're commitments you can hold us to, built directly into the product.
Export every client, booking, form submission, and note as JSON or CSV. Decrypted, machine-readable, take it anywhere.
Hit the button. Database rows, encrypted blobs, backups, audit trails — all wiped. No 90-day grace period. No "we keep it just in case."
Sign up with whatever name you choose. We don't ask for government ID, real names, or phone verification. We don't want it.
Our terms of service fit on one page and don't hide anything. No 40-page legalese. No "we may change this at any time" clauses.
A warrant canary is a public statement that says, “as of today, we have not been compelled to hand over user data.” If we ever are compelled — and gagged from telling you — the canary stops getting updated.
Updated monthly. Last updated: April 2026. If this section is removed or not updated for more than 60 days, assume the worst.
Curious about the technical side — encryption, hosting, jurisdiction? That's all on the security page.