Drafts on this device
In local mode, demo metadata and screenshots are saved in the browser’s IndexedDB. The selected light or dark mode is stored in localStorage. These are device-side storage mechanisms; local drafts are not automatically uploaded into a cloud workspace.
Clearing site data, changing browser profiles, or using another device can make those drafts unavailable. A JSON download gives you a portable copy. Local previews can display locally saved content, so the same URL may not work for another person.
Public GitHub repository imports
The importer sends your selected repository URL and branch to DemoSynth’s analysis endpoint. It requests public metadata, a file tree, and selected source files from GitHub’s REST API. Source excerpts are used to build a mock interface and can be held in a short-lived server-memory cache.
Generated demos include source attribution such as the repository URL, branch, commit, and selected file paths. Imported source files are not executed. A public repository may still contain material you do not want in a presentation, so review the generated text and screens.
Optional GitHub and AI keys
A GitHub token and an OpenAI or Gemini key are optional inputs. When supplied, the key is sent with the generation request and used to call the selected provider. These input keys are not written into the saved demo metadata or screenshot exports.
The default source-derived generator does not use an AI provider. When AI refinement is selected, relevant source excerpts and screen descriptions are sent to that provider to refine the tour’s copy. Provider handling and billing follow that service’s own terms.
Chrome extension data handling
The extension’s single purpose is to capture the website flow you choose and turn its screenshots and clicked targets into an editable product tour. Capture starts only when you select Start Capture. It reads visible page content and clicked element labels, target coordinates, viewport dimensions, capture timestamps, and the current site origin. It does not read your browser history database, cookies, or saved passwords. Screenshots and labels can still include information visible on the selected page.
The activeTab permission grants temporary access to the page you choose. Scripting inserts the capture and blur controls into that page, and storage retains settings and local screenshots. Captures are stored in extension IndexedDB until a new capture replaces them or you clear extension data. The website keeps imported drafts in its own browser storage until you delete them or clear site data. Keep an exported backup if you need longer retention.
On Finish, a temporary connection moves screenshots to your exact Studio tab, where they remain local for review. The connection expires after 15 minutes. Optional direct cloud capture sends screenshots to your configured image storage and tour metadata to your configured Studio API over HTTPS; its optional access token is held in Chrome session storage. The current hosted service keeps cloud publishing disabled.
Captured data is used to create, edit, export, and, when enabled and explicitly chosen, publish your tours. This capture workflow does not sell screenshots, use them for advertising, or send them to an AI provider. Optional AI refinement elsewhere in the app requires a separate user action. Anyone you share an export or published tour with can see its included content. Review and redact before sharing.
Our use of information received through Chrome APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Captured data is not used to determine creditworthiness or for lending purposes.
Screenshots and downloaded files
Screenshots can contain personal, account, or customer information. The extension has blur tools, and Studio lets you apply solid covers to screenshots after capture. Automatic detection is not a complete privacy review. Review screenshots and captions before exporting or publishing them. Applied covers replace pixels in the updated image; originals remain in undo history and previously saved, captured, exported, or hosted copies.
Downloaded JSON can include embedded screenshots; a written guide can include screenshot links. A README cover is intended to be committed into your repository. Treat each exported file according to the information it contains.
Connected cloud services
The website is hosted on Cloudflare. Hosting providers can process ordinary connection and operational information to deliver the service. GitHub processes repository requests, and optional AI providers process the requests you choose to send to them.
Cloud publishing is currently disabled in this deployment. When configured and enabled, authentication and demo metadata use the connected backend, and screenshots are uploaded to configured storage. A published tour and its image URLs are intended for readers outside your editing session.
The player’s optional analytics design records randomly identified tour sessions and step/completion events. Those events represent visits, not verified unique people. Analytics storage requires a configured backend; it is not evidence of traffic when that backend is unavailable.
Your practical controls
Export a backup before clearing browser data. Remove a local draft from the workspace when you no longer need it. If cloud publishing is enabled later, review its deletion and storage behavior separately: deleting demo metadata does not necessarily delete every hosted image object.
Keep passwords, access tokens, private URLs, and unredacted personal information out of screenshots and public README files. This page will need updating when the app’s data paths or configured services change.