The path a capture takes, stage by stage, with the boundaries stated plainly, written so a security reviewer can check every claim against our documentation and against an exported file.
Demo Maker Pro captures a browser workflow inside your own Chrome or Edge, in the session you are already signed into. Each click produces a step, and steps are stored in the extension's own storage and sent to the desktop application on the same computer, over a loopback connection to 127.0.0.1 that does not leave your machine. The extension does not send captured content to us or to any third party.
Editing, previewing and export all happen locally. The project is a .dmp file on your computer, in a location you choose, and Publish > Export HTML writes a single self-contained HTML file that does not contact our servers.
The desktop application communicates with our servers in only two situations: to verify your licence, and when you publish a demo. Publishing is a deliberate, separate action, and it is the point at which demo content leaves your machine. Everything below is traceable to the privacy policy and the documentation; where those are silent, so is this page.
Not in a footnote, these are what a reviewer needs first.
A published demo should be treated as public. Publishing uploads the demo to our hosting at demos.demomakerpro.com. Published demos are not indexed or listed publicly and the link contains a random identifier that cannot be guessed, but it is not password protected, and anyone who has it can view the demo.
Licence activation requires periodic connectivity. Once activated, the application keeps working for three days without an internet connection; connecting once resets the three days. Verification sends your licence key and a device identifier to LicenseSeat, our licensing provider, and receives back whether the licence is valid. That identifier is a generated value used to enforce how many devices a licence may be used on, not a hardware serial number.
A capture contains whatever was on screen. A step is a faithful copy of what the application displayed, including any real customer data, account names or personal information that was visible. Record with a demo or test account, and review a demo before you share it.
You open your product in Chrome or Edge, sign in as normal, click the extension icon and press Start Recording. Recording is deliberate: nothing is captured while recording is stopped, visiting a site with the extension installed captures nothing, and clicks are ignored until you start. The extension records only while the desktop application is open and licensed, and steps stream into the editor in real time.
Each click captures a step. Per the privacy policy, a step contains:
That is the whole list: a copy of a rendered page plus the coordinates of a click. Not a keystroke log, not a session recording.
Steps are stored in the extension's own storage and sent to the desktop application on the same computer, over a loopback connection to 127.0.0.1 that does not leave the machine. They stay there until you use Clear steps, or remove the extension, removing it deletes them.
Projects are stored on your computer as files you choose the location of, and editing and previewing happen locally. File > Save Demo (.dmp) writes the editable project, containing every captured step, to your disk. We hold no copy.
Publish > Export HTML writes a single self-contained HTML file. Everything the demo needs is inside it, so you can host it anywhere, embed it, or email it. It keeps working regardless of your subscription, and does not contact our servers. It also carries no measurement: analytics are added by our server at the moment you publish, so an exported file contains no analytics code at all and sends us nothing, ever.
Publish > Publish to DemoMakerPro uploads the demo to our hosting and returns a shareable link. At that point the demo's contents are stored on our servers and served to anyone who has the link. Delete one at any time from File > My Demos > My Cloud Published Demos; deleting removes the files from our servers and the link stops working immediately.
A reviewer watching network traffic will see it, so it should be stated. To make a finished demo work offline, the extension downloads the stylesheets, fonts and images the recorded page refers to, from wherever that page hosts them. Those requests are made without your cookies or sign-in details, and what comes back is embedded in your local recording. The extension fetches from origins the page already points at, while sending the capture nowhere. That is how a self-contained file ends up self-contained.
Desktop Capture is a separate path for programs that are not web pages, and does not involve the extension. Each press of the capture key records an image of one window, plus that window's title, the program name, and its size. Nothing else on your computer is read: not your other windows, not your files, not your clipboard, and not what you type. Those captures stay in the project on your computer and reach us only if you publish.
| Action | Does demo content reach our servers? | What does travel |
|---|---|---|
| Browsing with the extension installed, not recording | No, nothing is captured at all | Nothing |
| Recording in Chrome or Edge | No | Steps to the desktop app over 127.0.0.1; asset fetches to the recorded page's own hosts, without your cookies |
Desktop Capture, editing, saving a .dmp |
No | Nothing |
| Export HTML | No, the exported file does not contact our servers | Nothing |
| Licence verification | No demo content | Licence key and a generated device identifier, to our licensing provider |
| Publish to DemoMakerPro | Yes, this is the upload | The demo, stored on our servers and served to anyone with the link |
Because the recording happens inside your own already-logged-in Chrome or Edge, the application sees an ordinary session from an ordinary browser on an approved device. There is no cloud renderer to authorise, no service account to provision, no credentials to hand a vendor and no address to allowlist. Whatever your organisation already decided about who may open that application from that laptop governs the capture.
The usual worry about a recording tool is not that it does something visible, but that content ends up somewhere by default. Here the upload is a menu item someone chooses.
An exported demo is one HTML file. A reviewer can read it, open it with the network tab recording, and observe the requests it makes, rather than taking a vendor's word about infrastructure they cannot see, a claim the person signing it off can falsify. The same property makes the file yours to host, and it exists because the capture is real HTML and CSS rather than a video.
A local-first architecture creates an obvious support problem: if we never see your recording, how do we fix a capture that went wrong? The documented answer is that you send us the capture file. As the docs put it, that means we can diagnose the problem without ever needing access to your system or an account on it.
Both halves of that trade are worth stating. You decide what to send and when, rather than granting a screen-share into production. In exchange, a file you send is a file a person reads: the privacy policy states that no person reads your captured content except where you send it to us for support, or where we are required to act for security or legal reasons.
There is no value in an architecture article a reviewer cannot check, so this page states nothing our privacy policy and documentation do not. One limitation belongs with the three at the top: local-first does not make you independent of us for authoring. Recording requires the desktop application to be open and licensed, and when a paid plan ends you can no longer record, edit, export or publish. Demos already exported keep working; that part is unconditional.
If your review needs something this page does not answer, email support@demomakerpro.com. More articles are in resources.
Record a workflow, export the HTML, and open it with the network tab recording. The trial is the right place to verify this rather than take it on trust.
Start your free 7-day trial