How we protect your data and your customers' data.
All traffic to and from Cosmobill is encrypted in transit via TLS, provided by Cloudflare's edge network. Passwords are never stored in plain text - they're hashed with PBKDF2 (SHA-256, 100,000 iterations) and a unique random salt per account, using the Web Crypto API built into the Cloudflare Workers runtime.
Cosmobill never touches card numbers, bank login credentials, or PayPal passwords. When a customer pays by PayPal, card, Venmo, or Pay-in-4, the transaction is created through the PayPal Orders API and we only see the payment status and metadata PayPal returns to confirm an order completed - PayPal handles the sensitive parts entirely on its own systems. If a seller offers bank transfer, there's no automated processor involved: the customer self-reports that they sent the transfer, and the invoice only moves to "paid" once the seller personally confirms the funds arrived in their own bank account. Cosmobill is never a party to, and has no visibility into, that transfer.
Seller accounts and platform admin accounts use entirely separate login systems and session cookies, so an admin login can never grant seller-dashboard access (or vice versa). Session cookies are httpOnly, Secure, and SameSite=Lax, so they're inaccessible to page scripts and never sent cross-site. Seller sessions expire after 30 days of inactivity; admin sessions expire after 12 hours.
Cosmobill runs entirely on Cloudflare's global edge network (Workers) with data stored in Cloudflare D1, a distributed SQL database. There's no separate application server to patch or secure - the same platform that serves the site enforces our access rules.
Found a vulnerability? Open a support ticket and we'll take a look.