Privacy policy

Your recordings, projects, and exports are saved on your Mac or storage you choose. Demo Maker does not upload this content to its licensing service. Internet access is used for subscription checks, billing and account access, software updates, and optional downloads. Apple speech processing in older app releases is explained below.

When you choose to use the related features, Demo Maker processes screen or window imagery, system audio, microphone audio, camera video, cursor movement, clicks, key captions, project media, edits, generated captions, and exports. These files remain under your control on your Mac or storage locations you select.

Optional speech and noise-reduction models are downloaded from fixed HTTPS sources and verified against a pinned revision, expected byte count, and SHA-256 digest before use.

Captions and generated voice are processed by local models. Some models must be downloaded before first use. Model and runtime downloads use Hugging Face, GitHub, or the sources identified in the app’s notices; those providers receive ordinary request data such as your IP address. Your recording or script is not sent as part of a model download.

The voice-following teleprompter uses Apple’s Speech framework. In Demo Maker 1.0 builds 1 and 2, Apple speech recognition may use a network service when local recognition is unavailable. Later on-device-only releases refuse that network fallback. Check release notes and your installed build before relying on local-only teleprompter processing.

Importing a Google Font contacts Google Fonts to download the font you choose. Checking for app updates contacts Demo Maker’s update host; downloading an update transfers a signed app package. These requests do not include your project media.

To verify access, Demo Maker sends the app bundle identifier, Apple team identifier, app version and build, a random Secure Enclave-backed public key, a fingerprint derived from that key, the Mac name shown to you, and one-use challenge signatures. The private device key does not leave the Secure Enclave.

Our licensing service stores Stripe customer, subscription, Checkout Session, invoice, charge, refund, and dispute references when needed; normalized subscription state; approved app builds; hashed identifiers; active-device records; provider-event metadata; restore-token hashes; rate-limit state; reconciliation results; and security audit events. It does not store full payment-card details, hardware serial numbers, MAC addresses, private device keys, plaintext restore tokens, or your recording and project content.

Stripe hosts checkout, processes payment information, collects the billing address, supports tax calculation, sends receipts, detects fraud, handles payment disputes, and operates the customer billing portal under Stripe’s privacy policy. Demo Maker receives only the provider references, billing-country result, and status needed to administer billing and decide whether the subscription is entitled. We remain responsible for applicable tax registration, collection, filing, and remittance obligations.

Demo Maker is sold worldwide where Stripe can process payment. Cloudflare provides the request country at the network edge and Stripe provides the billing country entered in Checkout. We use those values for payment and tax availability, fraud and sanctions screening, compliance records, support, and subscription security. Missing or invalid country evidence fails closed; a difference between network and billing country does not by itself revoke a valid subscription. We do not use country information for advertising or behavioral profiling.

When you request purchase restore, the email you enter is used transiently to locate an eligible Stripe customer and subscription and send a one-use confirmation link through Cloudflare Email Service. The plaintext email is not persisted in our D1 database. A keyed one-way hash of the email supports subscription lookup, purchase restore, and abuse prevention. A hash associated with your subscription follows the entitlement-record retention period below; temporary abuse-prevention records follow their separate retention limits. Links expire after 15 minutes and are deleted after expiration or use.

Web sign-in uses the checkout email and an expiring confirmation link. After verification, an essential, secure, HTTP-only cookie keeps this browser signed in for up to the configured session lifetime (currently 12 hours). The server stores a hash of the session token. Signing out clears the browser cookie and requests session revocation. If the service is unavailable, the page explains that immediate server revocation could not be confirmed.

Cloudflare, which protects this website from automated abuse, sets a strictly necessary security cookie named cf_clearance after a brief automatic check in your browser, and may also set one named __cf_bm. These cookies hold only an encrypted security result that Cloudflare reads and are never used for advertising or tracking. Cloudflare treats them as valid for about 30 minutes, although your browser may keep cf_clearance for up to a year.

After checkout, an essential, secure, HTTP-only cookie named __Host-dm_checkout holds the checkout reference for up to 30 minutes so you can refresh the confirmation page. The server verifies the checkout before showing purchase details. The website also uses browser storage to keep account tabs in sync. The tab-sync entry is non-identifying and stays until you clear this site’s data. We do not use these for advertising or behavioral profiling. Personalized account data and purchase-confirmation API responses are not publicly cached.

• Perform the subscription agreement and provide requested product features.
• Protect subscriptions, devices, distributed builds, and services against misuse.
• Meet tax, accounting, fraud-prevention, and legal obligations.
• Diagnose failures, answer support requests, and operate Demo Maker.
• Understand, in aggregate, which pages and links bring visitors to the website.

Depending on your location, we rely on performance of a contract, legitimate interests in service security, reliability and understanding aggregate website use, compliance with law, and consent where required.

The homepage purchase counter uses completed one-time purchases. The current checkout does not request a public display name. We display a name only when the buyer previously gave explicit consent; we never publish buyer emails. Contact support to remove a previously displayed name. Checkout reservations and completed-purchase records support correct price allocations, payment verification, refunds and disputes; completed allocations remain part of the historical launch counter after a refund.

We use Stripe for one-time payments and existing subscription billing, Cloudflare for DNS, hosting, database, queues, email delivery, network protection, and signed-license issuance, and Apple for Developer ID signing and notarization. These providers may process data in countries other than yours under their contractual and legal transfer mechanisms.

We use Profound to measure automated crawler access to our public website pages. For requests identified as crawlers, we send the request time, public page path, IP address, user agent, response status and estimated response size. We exclude account, checkout and download requests, URL query values, referrers, cookies and request bodies. This measurement does not add browser tracking scripts or cookies.

We count visits to our public website pages, checkout starts and downloads with Cloudflare Workers Analytics Engine. Each count records the page path, the referring website’s domain name, a campaign tag taken only from a link’s utm_source or ref value, the country Cloudflare reports for the request, and whether the request appears to come from an automated crawler. It does not record IP addresses, user agents, cookies, other URL query values or any identifier, so a count cannot be connected to a person or to a later visit. This measurement adds no browser script, cookie or local storage.

• Device challenges and restore tokens: until expiration or use, then scheduled deletion.
• Download attribution records: up to 13 months. Pseudonymous download network and browser events: up to 90 days.
• Rate-limit buckets: no more than 48 hours after the related window.
• Aggregate website traffic counts: up to 3 months.
• Completed or failed activation requests: up to 30 days.
• Processed provider events, reconciliation records, and pseudonymous security audit events: up to 13 months.
• Entitlement and device records: while the subscription is active and up to 24 months after revocation or closure for restore, fraud, dispute, and support needs.
• Stripe payment, tax-support, dispute, and accounting records: according to Stripe’s and applicable legal retention requirements.

Cloudflare D1 point-in-time recovery may retain database history for up to 30 days. Scheduled deletion from the active database does not immediately remove earlier copies in this recovery history; those copies age out with the recovery window.

You can deactivate Macs through your account or deactivate the current Mac inside Demo Maker, cancel renewal in the billing portal, and ask us to access, correct, export, restrict, object to, or delete personal information where applicable. Some billing, fraud-prevention, tax, dispute, and security records may be retained where law permits or requires. You may also complain to your local data-protection authority.

Demo Maker is not directed to children under 16. We do not knowingly collect children’s personal information.

Private download links and signed package receipts are tied to a license. We retain download IDs, subscription references, release information, and pseudonymous network and browser hashes to investigate shared links and enforce license suspensions. Receipts contain no email address, license key, or sign-in credential.

We use TLS, server-authoritative subscription decisions, signed short-lived offline grants, device-bound Secure Enclave keys, one-use challenges and restore links, least-privilege service bindings, redacted logs, monotonic event handling, and Apple Developer ID signing and notarization. No security program eliminates every risk.

We will update the effective date and provide legally required notice before a material change takes effect.