privacy
Most of a privacy policy is about what a company promises to do with your data. The more useful half here is what this product simply cannot receive in the first place.
the data model
Nothing about an individual customer of yours reaches us at all. There is nothing to add to your app, no library, and nowhere for your servers to send anything. Madruga reads two things: how many visits each community sent, from your own analytics, and what your products earned, from Stripe.
This used to be a smaller promise. Your site reported sign-ups to us using a code you chose — never a name or an email, but still one record per customer. That is all gone now, along with the tables behind it. The promise is now built into the product: there is no column anywhere that could hold one of your customers, so everything we store is a count.
We say what that costs you, rather than hiding it. Because nothing links a visit to a payment, Madruga will tell you how many people a community sent and what a product earned, and will never claim to know which community won you a particular customer.
The Stripe and Simple Analytics connections are read-only keys you supply, stored encrypted, and used only to read subscriptions and visits for the domains and price ids you tell us about. Madruga never writes to either account.
your own data
Your email address, for passwordless sign-in. Any profile name you provide. Billing metadata held by our payment processor. Product logs we use to operate and secure the Service. Our marketing site and the signed-in app both load Google Analytics, so Google receives the page addresses you visit here. It is never given anything about your customers: no name, no email, no id, no row. There is no path for it to be.
To authenticate you, provide the Service, process payments, and send the three transactional emails there are: a sign-in code, a team invitation, and your dated review. We do not sell your personal data, and we send no marketing email to your sign-in address.
Three. Stripe processes payments, Resend delivers transactional email, and Google Analytics measures which pages people read. Each holds only what its job needs, under its own terms.
Two kinds. One session cookie, so you stay signed in. And the cookies Google Analytics sets to count a visit as one visit, which last up to two years. Google Analytics is now the only measurement on this site, so every cookie above the session one is theirs. We used to run a second, cookieless tag beside it, and we used to describe a cookie set by an attribution snippet on your own site. Neither exists any more.
We show no cookie banner. Using this site is treated as your agreement to the measurement described here, and the Terms of Use say so. That means the Google Analytics cookies are set when the page loads, not after you are asked. If you would rather not be measured, block the tag in your browser or install Google's own opt-out add-on, and the rest of the site keeps working. Write to us and we will delete what is held about you.
For as long as your workspace exists. Delete the workspace and its data goes with it, immediately and permanently, apart from records our payment processor is required to keep for tax and accounting.
Export everything in your workspace as JSON, or delete the workspace and its data, at any time from Settings. Both stay available after a subscription lapses. For anything else, write to us.
Write to [email protected] and a person answers. The data controller is Binns Pte. Ltd., and the Terms of Use are a separate document.
Last updated 24 August 2026.