Privacy policy

Workspace content and device pairing

Dash processes the workspace information you choose to use, including tasks, instructions, results, activity, guest desktop previews, usage totals, and connected-device details. The workspace is managed on your own Mac and, when configured, your Mac mini and its guests. A paired iPhone or iPad receives workspace information over an encrypted connection. Madrina does not operate a cloud copy of your workspace as part of local pairing.

Phone workspace snapshots are held in app memory. Task histories and workspace files can remain on your Mac or guests. Pairing credentials are stored in the device’s Keychain; API and SSH keys are not included in the phone’s workspace snapshots. Pairing codes grant access to your workspace and should be kept private.

Where protected pairing is available and enabled, device approval and device authentication protect the connection. Apple handles Face ID, Touch ID, or passcode checks; Dash does not receive your biometric templates or device passcode. Connection availability is explained on our support page.

If you configure an AI provider and start a task, the Mac or mini sends task instructions and the context needed to carry it out, which can include guest screenshots, to the provider you selected, such as OpenAI or Anthropic. The provider processes that data under your account and its terms. Viewing the companion or a guest preview does not itself start an AI task. Websites and applications you use inside a guest handle information under their own privacy policies.

Your Madrina account

Firebase Authentication, operated by Google, verifies your email and password, sends account verification and password reset messages, and stores your authentication record. Our service passes passwords to Firebase over HTTPS and does not store them. Cloudflare hosts the account-to-license connection and protected session records. We store a random purchase customer identifier, account identifier, device public keys and labels, session dates, and encrypted authentication refresh credentials. We do not collect your Mac’s hardware serial number for licensing.

Browser sessions use a Secure, HttpOnly cookie. The apps keep their session and device signing key in Keychain. Purchases are checked with RevenueCat; a signed license can continue working offline for up to seven days before an online check is required. Account sessions expire after 30 days. Signing out other devices stops further online access, but an already verified offline license can last until its expiry.

You can delete your Madrina account from Account controls in the app or your website account. This removes the account mapping and active account sessions. Payment providers may retain transaction records for billing, refunds, fraud prevention, and legal obligations. Deleting an account does not request a refund or erase files on your Mac or guests. Contact support with your receipt if you need to reconnect a valid website license after account deletion.

Purchases and license verification

If Madrina issues you a complimentary or judge license number, you can enter it directly in Dash without creating an account. The app sends the number over HTTPS for validation and keeps it with the device signing key in Keychain so the license can be checked again. The licensing database stores the issued number’s one-way hash, not the number itself. Signed offline access lasts up to seven days. Keep the number private; it authorizes your devices.

You can optionally connect a number to one verified Madrina account on this website. That stores the license identifier, redemption date, and connected account identifier. After account deletion, we remove the connected account identifier and retain a revoked used-number record. Account sign-out does not remove a number independently saved on a device; use “Remove number from this device” in Dash. Complimentary access does not create a payment transaction.

Dash uses RevenueCat to verify access, restore purchases, connect a redeemed website purchase to the app, and report purchase performance. Through its SDK and purchase services, RevenueCat processes a customer identifier, purchase history, transaction or receipt information, and technical details such as app and operating-system versions and connection activity. These records can be associated with your purchase and redeemed license.

For a website purchase, RevenueCat and Stripe process your email, order information, and the payment and billing details needed for checkout, receipts, redemption, fraud prevention, and refunds. Apple processes App Store payments. Madrina can access purchase and customer records needed for licensing, purchase reporting, and support, but does not receive or store your full payment-card number.

Workspace content, guest screenshots, pairing secrets, and API keys are not sent to RevenueCat for license verification. The iOS integration disables RevenueCat’s automatic device-identifier collection and optional diagnostics and does not use an advertising identifier.

More information: RevenueCat privacy policy and Stripe privacy policy.

Permissions and your choices

• Local Network: lets your iPhone or iPad reach your paired Mac on the same network.
• Camera: scans your Mac’s pairing QR code. The scanner does not upload camera footage to Madrina. You can enter the pairing code manually instead.
• Device authentication: protects access to a connection that uses protected pairing, when configured.

You can change permissions in your device’s Settings, forget a connection in Dash, or disable and revoke phone access on the Mac. Revoking a necessary connection permission stops the related feature. Stop a running task and disconnect its provider in the Mac app to stop future task requests to that provider; this does not recall information already sent.

Website visits and the sample workspace

The landing page contains a sample workspace with simulated figures and tasks. Drafts you enter there stay in the page’s memory and are discarded when the page reloads or you leave it. The sample does not connect to your Mac, run real tasks, or send its drafts to an AI provider.

Our hosting and delivery providers, OpenAI Sites and Cloudflare, process normal web-request information, such as IP address, requested URL, browser information, timestamps, and security events, to serve and protect the site. Hosting or security features may use cookies or similar storage for those purposes. The site does not add advertising trackers. Opening checkout takes you to the purchase providers described above.

When you contact us

If you email us, Madrina and its email service process your email address, message, and any attachments you choose to send. We use them to answer you, investigate problems, help with purchases, and handle privacy requests. Send only the details needed for the issue. Please do not send passwords, pairing codes, API keys, card details, or private guest screenshots.

How information is shared and protected

We use service providers for hosting, payments, license verification, and support for the purposes described here. We require providers processing personal information for us to protect it consistently with this policy and applicable privacy requirements. Services you independently choose to connect also have their own terms and privacy policies. Providers may process information in countries other than your own.

We do not sell personal information or use it for cross-app or cross-site advertising tracking. Information may be disclosed when required by law or when necessary to address fraud, security incidents, or the protection of legal rights. Access is limited to the information needed for the relevant purpose.

Dash uses encrypted device connections and Keychain storage for pairing credentials. Keep your devices, pairing codes, and accounts secure. No transmission or storage system can guarantee absolute security.

Retention and deletion

• Workspace data: remains on your devices according to your use and deletion of local tasks and files. Phone snapshots are not a separate cloud archive. Forgetting a phone connection does not delete the Mac’s tasks or guest files.
• Pairing: use the app’s forget-connection option to remove the phone’s saved pairing. Revoke that pairing on the Mac to stop future access. Uninstalling alone should not be used as a substitute for revocation.
• License and payment records: are retained as needed to maintain and restore your license, handle refunds and fraud, and meet accounting or legal obligations. Purchase providers may need to retain transaction records after a deletion request.
• Support messages: are retained while needed to resolve the request, maintain relevant support records, or meet legal obligations. Hosting and security records follow the providers’ operational retention practices.
• Website drafts: last only for the current page session and are not saved to our server.

To request access, correction, deletion, or withdrawal of consent for personal information held by Madrina, email dan@madrinai.com with “Privacy request” in the subject. We may ask for limited information, such as an order identifier, to verify the request; we will not ask for your password or full payment-card number. We will explain any information that must be retained and coordinate applicable requests with providers that process it for us. Removing records needed to verify a license can affect restoration, which we will explain before processing such a request.

Local device pairing does not require a separate Madrina sign-in account. Depending on your location, you may also have rights to restrict or object to processing, receive a copy of your data, or contact a privacy regulator. Contact us to exercise the rights that apply to you.

Updates and contact

We will update this page and its date when the policy changes. If a change requires new permission or notice, we will provide it as applicable before that processing begins. For help using Dash, visit Support. For privacy requests, email dan@madrinai.com.