Privacy Policy

1. Who we are, and our two roles

Framvis, operated by an independent software developer based in Spain, is the controller for the personal data we need to run the Service: your account, sign-in and security events, support requests, and billing metadata. Contact: support@framvis.com.

For the material you capture and the leads your demos collect, you are the controller and we act as your processor — we handle that data to provide the Service to you. Those two roles are separate throughout this policy.

2. What we collect

Account & security. Your email address, a hashed password, and — if you enable it — an encrypted two-factor secret and hashed recovery codes. We record sign-in attempts, session and “remember me” tokens (hashed), and rate-limit counters, which can briefly contain an IP address or a hashed email.

Content you create. Captured walkthroughs, demo configuration, step text, translations, generated voiceover audio, personalisation variables and published demo versions. Captured recordings may contain personal data from your own product — see §6.

Leads. If you switch on the email gate, the visitor’s email address plus a random demo-session identifier. You may also define up to five extra fields (for example “Company”); those answers are stored with the lead and are yours.

Demo & site analytics. Cookieless counts of views, step progress, calls-to-action, traffic source and coarse replay-performance samples. No IP address is stored in these tables.

Support. Ticket text and any files you attach. Mail sent to our support address is read live from the mailbox and is not copied into the application.

Billing. Provider customer, subscription and price identifiers, and an append-only record of billing events. We never see or store your card details — see §5.

3. How & why we use it

To provide and secure the Service, process your subscription, answer support requests, and understand product usage in aggregate. Legal bases (GDPR Art. 6): performance of our contract with you, our legitimate interests in operating the Service securely and preventing abuse, your consent where we ask for it, and legal obligation for accounting records. Where we process your captured content and leads, we do so on your documented instructions as your processor. We do not sell personal data and we do not use it to train AI models.

4. Cookies & browser storage

An essential session cookie keeps you signed in; it is required for the app to work and needs no consent. If you tick “remember me”, an optional persistent cookie is set on that device — it is separate from the session cookie and expires at a fixed date. Viewing a password-protected or email-gated demo sets a short-lived access cookie scoped to that demo.

We use no advertising or third-party tracking cookies. Our own analytics is cookieless and uses a random identifier held in your browser’s local storage. Two third parties may set their own storage on the pages where they run: Cloudflare Turnstile on sign-in and support forms, and Paddle on the checkout page.

5. Who we share data with

We use a small number of sub-processors to run the Service. Each receives only what its function requires: our hosting provider (IONOS), on servers in Spain, hosts the application, database and private files; Cloudflare provides the anti-abuse check on our forms and stores our off-site database backups in a bucket restricted to the EU jurisdiction; Google Cloud (Vertex AI) processes demo text and generates voiceover when you use the AI features, configured to the EU region.

Paddle is our Merchant of Record. Paddle sells to you in its own right and is an independent controller for the transaction, not our processor — the relevant Paddle entity depends on where you are, and Paddle’s own buyer terms and privacy notice apply.

Recipients you choose. If you connect an integration, we send the events you select to that destination — a Slack channel, HubSpot, or any HTTPS endpoint you configure. Those are your instructions to us, and once delivered that data is governed by that provider’s terms.

A current list is kept at Sub-processors. We do not sell personal data.

6. Data in your recordings

When you capture a walkthrough of your own product, you decide what is recorded and you are the controller for any personal data it contains; we act as your processor. You must have a lawful basis and inform the people concerned.

What we do automatically: text typed into form fields is masked at capture and canvas content is not recorded. That is not a guarantee that a capture contains no personal data — ordinary page text and element attributes are recorded, so avoid capturing screens that show real customer data.

Two different correction tools, and the difference matters. A blur is a visual overlay only: the underlying text is still present in the stored recording. A data scrub irreversibly removes the text you name from the stored data, its translations, generated audio and every published version. Use the scrub, not the blur, when something must actually be gone. A scrub reports anything structural it could not safely rewrite, so you can rotate or revoke instead of assuming.

Replayed images load from wherever your product served them. If your captured pages referenced images on other hosts, a viewer’s browser contacts those hosts directly when the demo plays, which discloses their IP address and the time of the request to them. Those hosts are determined by the content you captured, not chosen by us.

7. Retention

Your account and content are kept while your account exists. Deleting your account removes your live content and unlinks the private files that belong to it; support threads may be retained in anonymised form, and billing records are kept for as long as the law requires us to keep them.

You control your own content directly — delete a recording, revoke a share link, erase a lead, or scrub text from a capture at any time.

Operational data: short-lived abuse and rate-limit records are kept for days; delivery history for your integrations is pruned after 30 days; database backups rotate on roughly a weekly local cycle plus an off-site copy.

We are still finalising fixed expiry windows for demo leads and demo analytics; until those are agreed and published here, that data is kept while the demo it belongs to exists, and you can delete it yourself at any time.

8. Your rights

You have the rights of access, rectification, erasure, restriction, portability and objection under the GDPR, and the right to complain to your supervisory authority.

For your account and billing data, contact us directly. For personal data inside a customer’s demo or lead list — for example if you are a visitor who submitted an email — the Framvis customer running that demo is the controller and decides; contact them, and we will assist them as their processor. If you are not sure who that is, write to us and we will point you to the right party.

9. International transfers

The application, its database and its off-site backups are hosted in the EU. Some of the providers in §5 are, or are affiliated with, companies outside the EEA, and support or infrastructure access from outside the EEA is possible. Where that happens, those providers publish their own data-processing terms and transfer safeguards, which we rely on and which are linked from our Sub-processors page.

We do not claim that every party involved processes data exclusively inside the EEA. In particular, payments, the anti-abuse check, any integration you connect, and the third-party hosts referenced by your own captured pages may involve processing elsewhere.

10. Changes

We may update this policy; material changes will be notified in-app or by email. This version reflects the Service as built and is maintained by its developer rather than reviewed by external counsel.

Questions about this document? Contact support@framvis.com.