1. Who this applies to
This policy covers the Data Maestro macOS app, the data-maestro-cli command-line tool, and this website, operated by Ricardo Burger Schalch Consultoria em Tecnologia da Informacao Ltda, doing business as RBSTech ("we", "us"), based in Brazil. It's written to satisfy both Brazil's LGPD and the EU's GDPR, since we have customers in both regions.
2. What never leaves your Mac
Data generation, PII anonymization, database seeding, quality-metric scoring, and the Fake API Generator's served data all run entirely inside the app's local Rust core. None of the datasets you build, import, anonymize, or push to a database are ever sent to us or to any third party — there is no "upload" step anywhere in the product.
3. What the app does send, and why
License activation. Entering a license key sends a hashed device identifier (not raw hardware identifiers) plus the license key to datamaestro.rbstech.app/api/activate, so we can enforce the per-seat limit your license type allows. This hash, the license tier, and an activation timestamp are stored in Vercel KV (our database provider) for as long as the license is active, so a later "Deactivate this Mac" call can free the seat again.
Update checks. The app periodically checks datamaestro.rbstech.app/appcast.xml (via the open-source Sparkle framework) for new versions. This is a simple file fetch — we don't enable Sparkle's optional system-profiling data collection, so no extra system information is deliberately transmitted, though any web request inherently exposes your IP address and app version to server logs.
Checkout, if you buy a license. Purchases are handled entirely by Paddle, our merchant of record — we never see or store your payment card details. Paddle passes us your email address and order details so we can generate and deliver your license.
License-key email. After a successful purchase, we send your license key to the email address from checkout using Resend, our transactional email provider.
4. Third-party processors
- Vercel — hosts this website, the activation API, and the KV store holding device-hash/seat records.
- Paddle — merchant of record for all purchases; handles payment details and tax collection.
- Resend — sends license-key delivery and license-related transactional emails.
- GitHub — hosts app release binaries and update packages downloaded by Sparkle.
None of these processors receive the data you generate, import, or anonymize inside the app — only the license/checkout metadata described in Section 3.
5. What we don't do
We don't run analytics or telemetry inside the app, don't sell or share your data with advertisers, and don't use the email address on your license for anything beyond license delivery and support unless you separately opt in to something else.
6. Your rights
Under LGPD and GDPR, you can request access to, correction of, or deletion of the license/activation data we hold about you (email address, device hash, order metadata). To exercise any of these, email [email protected]. Deleting your activation record will deactivate your license on that device.
7. Data retention
Device-hash and seat-activation records are kept for as long as your license is active, plus a reasonable period after expiry for support purposes. Checkout records are retained by Paddle per their own policy, typically for tax and accounting compliance.
8. Changes to this policy
If this policy changes materially, we'll update the effective date above and, for significant changes, note it in the app's release notes.