MailScope · Visual Dev Studio

Privacy policy

What stays on your Mac, what reaches the store, and what this website measures.

Last reviewed:

Who and what this covers

This policy covers the MailScope website at mailscope.app, purchases through Stripe Payment Links, the Visual Dev Studio store at store.visualdevstudio.com, and the MailScope Mac app.

MailScope is offered by ProductizeHQ LLP under the Visual Dev Studio brand. For privacy questions, contact [email protected].

Your captured mail

MailScope captures development email on your Mac and never relays it to real recipients. Messages, addresses, headers, bodies, attachments and saved analysis are stored in the app’s macOS sandbox. Core capture, inspection and local checks work without an API key or an internet connection.

Delete and Delete All remove messages and their associated data. Interrupted file cleanup is retried at launch. Automatic backups made before a database upgrade keep the three newest copies; those backups can still contain mail you have since deleted. Your own backups and exported files are separate copies.

Remote preview resources are blocked until you allow them for a message. Loading remote content, opening browser links or attachments, and explicitly checking selected links or images can contact external servers. Link/image checks send HEAD requests without cookies or stored credentials and report redirects without following them. URLs, including their query strings, reach the servers you choose to check.

Assistant access is opt-in

MCP is a separate, optional local connection. An assistant with its access token can read captured mail, and content returned to that assistant may be sent to its model provider. Disable MCP to close connections, or replace its access token to revoke old configurations. The token is stored in macOS Keychain.

The built-in AI Debug interface is currently hidden. Existing saved analysis and API keys are retained; API keys are stored in Keychain. The app does not send analytics or telemetry.

Licence and update requests

Activation, refresh, validation, deactivation and update checks contact store.visualdevstudio.com over HTTPS. Each sends your licence key and a stable Mac identifier: a one-way SHA-256 hash of the hardware UUID combined with the product name. The raw hardware UUID and serial number are never sent. This identifier is linked to your licence; it is not an anonymous website visit.

  • Activation also sends your computer name, up to 64 characters, so you can recognise the Mac in your account.
  • Validation also sends the app version and build.
  • Update checks send the same licence key and Mac identifier to find releases your licence covers.

The store sees the request’s IP address and User-Agent. Activation usage records keep the device identifier, name and activation state/times, and do not store IP or User-Agent in those rows. The store also keeps licence and operational activity records to support activation, recovery and troubleshooting. This is separate from website analytics.

No captured email, address, header, attachment or MCP content is sent to the store. The licence key and signed licence evidence are stored in Keychain. Launch verifies saved evidence locally and never waits for the store. Trial copies make no store requests.

Activated Macs check for updates about weekly and validate once after an app update. Turn off Check for updates automatically in Settings → Updates to stop background store requests. Actions you choose, such as Activate, Refresh License, Verify Again, Deactivate This Mac and Check for Updates, still contact the store.

Included in-app updates use temporary signed store feed/download URLs, followed by a five-minute Cloudflare R2 download link. The R2 link carries no licence key or device identifier. The store records licensed portal and in-app update downloads against the customer, licence and release; in-app update records also identify the Mac’s activation. These download records do not include the licence key, IP or User-Agent.

Purchases and your store account

Purchases happen in your browser through Stripe Payment Links, outside the app. Stripe handles your email, payment details and billing information, including billing country where collected for tax or invoicing. See Stripe’s privacy policy.

The store keeps your purchase email, customer name when supplied, amount, currency, payment/refund status, Stripe references, purchased licence terms and licence record. It also retains redacted Stripe event payloads for payment processing and recovery. The app never sends payment data.

Purchase emails include a PDF containing your licence key and a link to your account. Treat the email and PDF as private credentials. The store records delivery status; opening the PDF is not logged by the store.

Your account uses email sign-in links or optional passkeys. The store keeps sign-in token hashes, expiry/consumption records and any passkey credentials you register. Its browser session uses cookies for account access and request security. The default database session storage can retain IP and User-Agent; sign-in and API rate limiting also use IP addresses. Account sessions are separate from the app’s activation records.

Website analytics and hosting

This website uses self-hosted Umami at stat.visualdevstudio.com for page views on mailscope.app and anonymous counts of public-download and checkout-link clicks where those links are available. Click-event properties contain only the link’s placement or displayed price tier; they do not include personal data, query strings, session IDs or email addresses. A checkout-link click is not a completed purchase.

Umami also sends the page URL (including query string and fragment), page title, referrer, browser language and screen size. The analytics server receives ordinary request information such as IP address and User-Agent. Cloudflare hosts the website and public download delivery. Requests to the website, store and download hosts reach the servers providing those services.

The landing-page analytics do not set tracking cookies. The current Umami script reads an optional local umami.disabled opt-out setting and does not write a visitor identifier to browser storage. This does not describe Stripe’s or the store’s essential cookies. The store source reviewed for this policy has no equivalent page-view tracker.

We will update this policy if the analytics tools or the data they collect change.

Questions and data requests

For purchase or licence recovery, sign in at your store account. For privacy questions or requests concerning store records, email ProductizeHQ LLP at [email protected].

Store order and licence history is retained for recovery and payment reconciliation. Deleting mail in the app does not delete store purchase or licence records. Contact us about access, correction or deletion of your store information.