privacy
Most of a privacy policy is about what a company promises to do with your data. The interesting half here is what the product is structurally unable to receive in the first place.
the data model
Nothing about an individual customer of yours reaches us at all. There is no snippet in your app, no SDK, and no endpoint for your backend to report to. 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 narrower promise. Your site reported signups to us through a write-only key, using an opaque id you chose — never a name or an email, but a row per customer nonetheless. Those endpoints are gone and so are the tables behind them. The guarantee is now structural: there is no column anywhere in the product that could hold a customer of yours, so everything is a count against a denominator.
The cost is stated rather than hidden. Because nothing joins a visit to a payment, Madruga will tell you how many people a community sent and what a product earned, and will not claim to know which community produced a given customer.
The Stripe and Simple Analytics connections are read-only keys you supply, held encrypted, and used to read subscriptions and traffic for the domains and price ids you declare. 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. There is no third-party tracker anywhere in the product.
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.
Two. Stripe processes payments, and Resend delivers transactional email. Each holds only what its job needs, under its own terms.
One session cookie, so you stay signed in. That is the whole list. Our own site analytics are cookieless and respect Do Not Track, which is why there is no consent banner on this page. The madruga_cell cookie the attribution snippet sets is a first-party cookie on your domain, not ours, and it holds a community slug rather than anything about the person.
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 16 August 2026.
