Privacy at a glance

We process account details and the content and activity needed to deliver the features you use. We do not sell personal data or use advertising trackers.
Your organization controls its content, publication settings, and learner records. Published content is available to the audience allowed by its sharing settings.
Using an AI feature sends the content needed for that request to OpenAI. You choose when to use these features.

Who is responsible

Demo-Creator is operated by ABIT Technology, Adrian Shajkofci, Rue des Champs du Bourg 28, 1920 Martigny, Switzerland. This notice covers our website, hosted application, recording tools, public demos, and training features. We are responsible for personal data used to administer accounts, billing, support, security, and our own communications. Swiss data protection law applies, together with the GDPR where applicable.

For personal data an organization includes in demos or training, that organization generally decides why the data is processed and who can access it. We process that content on its behalf to provide the service. If your employer or another organization invited you, its privacy notice also explains how it uses your information.

Personal data we process

The information we process depends on whether you visit the website, create content, view a demo, or take part in training.

Accounts and support: Name, email address, sign-in and verification details, organization membership and roles, preferences, and messages you send us. Passwords are stored as hashes.
Demos and recordings: Screenshots, recordings, uploaded images and audio, text, translations, quizzes, comments, and content revisions. Screenshots can contain personal data from the application you capture.
Viewing and technical activity: Player session identifiers, viewed steps, viewing time, completion and link clicks, browser and device category, language, referring hostname, and approximate country. Requests also involve an IP address and technical information needed to deliver and protect the service.
Training and quiz records: Learner name and email, assignments, progress, submitted answers, scores, review feedback, completion dates, and certificate details, including fields configured by the training organizer.
Payments and subscriptions: Plan, usage, customer and subscription identifiers, payment status, and invoice information. Payment card details are entered with Stripe; our application does not store full card numbers.

We receive data from you, your browser, your organization, and integrations you choose, such as Google sign-in or Stripe payments. An organizer can also provide your details when assigning training.

Purposes and legal bases

We use personal data to provide and maintain Demo-Creator, respond to requests, and meet legal obligations. We do not sell or rent personal data or use it for advertising profiles. Where the GDPR applies, the bases for our own processing are:

Providing the service: Performing our contract with you, or taking steps you request before a contract: account access, content processing, subscriptions, and support. Customer content is processed on the organization’s instructions.
Security and improvement: Our legitimate interests in preventing abuse, investigating errors, keeping the service reliable, and improving usability. Viewing reports help organizations understand how their demos are used.
Legal requirements: Compliance with applicable accounting, tax, and other legal duties, and handling lawful requests from authorities.
Product emails: Our legitimate interest in sending account holders tips, product news and occasional offers about Demo-Creator, which Swiss law permits for existing customers. You are told about this when you sign up, every email lets you unsubscribe, and newsletter subscriptions without an account require your confirmation.

Sign-in details are needed for an account; billing information is needed for a purchase. Without the required information, we cannot provide the corresponding feature. You can unsubscribe from product emails at any time without affecting your account.

Who receives data

Our team and service providers receive information needed for their roles. The integrations below receive data when you use the relevant feature.

Hosting and email: OVHcloud hosts the service and its backups and delivers email. Email delivery processes recipient addresses and message content for verification, invitations, training, alerts and product emails. The current list of sub-processors is on our Security page.
Stripe: Processes checkout, payments, and invoices. We exchange customer, subscription, and transaction information with Stripe to manage billing.
OpenAI: Processes the text or screenshots needed for the AI generation you request. Read the AI section below before submitting confidential content.
ElevenLabs: Processes the narration text you request to generate a voiceover. Saved narration is reused without a new request.
Google: If you choose Google sign-in, we receive an account identifier, name, email address, and verification information to authenticate you. Google also processes the sign-in request under its own policies.
Microsoft: If you choose Microsoft sign-in, we receive an account identifier, name, email address and tenant information to authenticate you. Microsoft also processes the sign-in request under its own policies.

Stripe privacy notice OpenAI privacy notice ElevenLabs privacy notice Google privacy notice Microsoft privacy statement Security and trust

We also disclose data when required by law or necessary to protect the service and establish, exercise, or defend legal claims. External websites you visit through a demo apply their own privacy notices.

Hosting and international transfers

The hosted Demo-Creator platform and its application data are hosted by OVHcloud in Germany (EU). ABIT Technology operates the service from Switzerland. This hosting location does not mean every integration processes data only in the EU.

OpenAI, ElevenLabs, Stripe, Google and Microsoft operate internationally; their processing can involve the United States and other countries described in their notices. Applicable law requires an adequate level of protection or another valid transfer mechanism, such as the European Commission’s Standard Contractual Clauses. Our Data Processing Agreement describes these arrangements.

AI features and OpenAI

When you request translation, narration, screenshot text, or quiz generation, we send the content needed for that task to OpenAI. This can include demo text, instructions, and selected screenshots. Generated output is stored with your demo when saved.

Review and redact confidential or sensitive information before making a request. If you supply your own OpenAI API key, the request uses that provider account and its settings. Using your own key does not change where the hosted application stores your demos.

OpenAI states that API data is not used to train its models by default. Provider retention rules and account-specific data-sharing settings still apply. See OpenAI’s API data controls.

Browser recorder extensions

When you start recording, the extension captures your selected browser tab or the window or screen you share, with click positions, control labels, optional short input videos and visible page text depending on the mode. Browser captures cover detected revealed or readable passwords and codes before storage, leaving passwords already masked by the site unchanged. Other secrets or private information may remain. Desktop and screen capture cannot detect passwords: pause or hide secrets before recording. Always review captures before upload. Recording is limited to 50 steps.

Recordings stay in your browser until you choose to upload them. Uploading sends your captures, demo title, context, language, and captured page text to demo-creator.com over HTTPS, using your pairing token for authorization. Importing with a demo context requests AI generation: the service sends the context, captured text, step information, and screenshot images to OpenAI to generate demo copy. The resulting demo is a private draft; uploading does not publish it. Review your source content before recording and uploading.

The extension stores the connection token, preferences, and unfinished recording locally in this browser. Captures remain until you discard the recording, successfully upload it, disconnect, or uninstall the extension. The connection token remains until you disconnect or uninstall; it is sent only to demo-creator.com to authorize uploads. Disconnecting clears local captures and the connection token but does not revoke a copied token or delete uploaded demos. Revoke extension access in workspace settings and manage uploaded content in Demo-Creator.

Browser recording uses temporary access to the tab where you open the recorder. Access ends when you move to another origin; reopen the recorder on that page and resume to authorize recording there. The extension requests scripting to record interactions, local storage for settings and captures, and unlimited storage because up to 50 screenshot and input-video steps can exceed the normal quota. Its only required website permission is demo-creator.com for uploads. Desktop capture uses the browser’s window or screen chooser.

Our use of information collected by the browser recorder complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use that information only to provide or improve the recorder’s disclosed purpose of creating editable demos. We do not sell it or use or transfer it for personalized advertising, data brokering, creditworthiness, or lending. Transfers are limited to those necessary for this purpose, legal obligations, protection against abuse, or a merger, acquisition, or asset sale with your explicit prior consent.

We do not allow people acting for us or our service providers to read recorder information except with your explicit consent for specific data, for aggregated and anonymized internal operations, for necessary security investigations, or to comply with law. Sharing a demo with your workspace or publishing it follows your own sharing choices described above.

Chrome Web Store Limited Use requirements

Cookies and browser storage

We use cookies for sign-in, verification, and access to protected content, and browser storage for preferences and requested features. We do not use advertising cookies or third-party analytics. Our demo viewing reports are first-party activity records described above.

Sign-in sessions: dm_session and dm_training keep account and learner sessions signed in for up to 30 days, unless you sign out or the session is revoked sooner.
Sign-in verification: dm_magic lasts up to 15 minutes, dm_webauthn up to 5 minutes, and dm_oauth or dm_training_oauth up to 10 minutes, to secure the sign-in method you choose.
Protected content: dm_share_* and dm_repository_* remember access granted to a protected demo or training collection for up to 24 hours.
Preferences and progress: Local storage remembers language, appearance, workspace, the cookie notice acknowledgement, quiz receipts, and training progress. It persists until cleared or removed by the relevant feature. Session storage holds temporary navigation and access information for the browser session.

You can delete or block cookies and browser storage through your browser. This can sign you out or interrupt protected content and saved progress. The footer’s cookie preferences control reopens the information notice; it does not switch off service cookies.

How long we keep data

Retention depends on the purpose, the organization’s instructions, and applicable legal requirements. Unpublishing a demo or canceling a subscription does not by itself delete its content or your account.

Accounts and workspace content: Kept while needed to provide the account or workspace and its requested features. Contact us to request account deletion. Organization-controlled content and learner records must also be addressed with the organization.
Deleted demos: Demos in Trash can be restored for 30 days and are then eligible for permanent cleanup. Authorized users can permanently delete them earlier. This is separate from backup retention.
Viewing activity: The application’s default retention for raw demo-viewing and link-click events is 90 days, with cleanup when events are recorded. Configured limits can remove records earlier. This period does not apply to learner records or quiz submissions.
Administrative records: Billing records are kept for applicable statutory periods. Support and security records are kept as needed to resolve requests, investigate incidents, and handle claims. Subscription and suppression records help document consent and respect marketing opt-outs.

Deletion from the active service does not necessarily remove existing backups immediately. Backup expiry, provider retention, and any legal preservation requirement affect when remaining copies are removed. Contact us for the retention information relevant to a specific request.

Your privacy rights

Depending on applicable law, you can request access to your personal data, correction, deletion, restriction of processing, or a portable copy. You can object to processing based on legitimate interests and withdraw consent for consent-based processing.

Contact us using the address below and identify the account or service concerned. We may ask for information needed to verify your identity. We respond within the applicable legal deadlines and explain any lawful limitation. For data controlled by a customer organization, contact that organization first; we can assist it with the request.

You can also complain to the data protection authority where you live or work, where applicable. In Switzerland, contact the Federal Data Protection and Information Commissioner (FDPIC).

Protecting your information

The application uses organization-based access controls, password hashing, and revocable sign-in sessions to protect account and workspace data. Access depends on assigned roles. No online service can guarantee complete protection against every threat.

Keep your sign-in credentials secure, review workspace roles, and remove personal information from screenshots before sharing. Use a solid redaction when information must be removed; a visual blur can leave information recoverable.

Contact and policy updates

For privacy questions or personal-data requests, write to info@abittechnology.com.

ABIT Technology, Adrian ShajkofciRue des Champs du Bourg 281920 Martigny, Switzerland

We update this notice as the service or its data practices change. The date above identifies the current version. Where the law requires additional notice or consent for a change, that requirement applies.