Privacy Policy

This covers this marketing website, including its pricing and checkout pages.

• No analytics, advertising or tracking. This website runs no analytics, advertising or tracking scripts and sets no tracking cookies. It does not use browser storage at all.
• Fonts are served from this website. The typefaces are bundled into the site when it is built, so your browser makes no request to a font provider.
• Hosting. The website is served by Amazon Web Services. As with any website, your browser sends your IP address and standard request information, such as the page requested and your browser type, to deliver each page and to protect the site from attacks. We do not use this to analyze, profile or follow your visits.

When you buy a plan on this website, the email address you enter is sent to the Proovyt application. It uses the address to start a checkout session with Stripe, our payment processor, to check whether the address already has a paid plan, and, once payment succeeds, to attach the plan to your account or to set up a new one. The order details you choose, such as the plan, billing period and Team seat count, go with it.

Your name, billing address and card details are entered into Stripe’s own payment form on that page. They go directly to Stripe and never reach Proovyt’s servers. The checkout page, and only that page, loads Stripe’s code, which sets Stripe’s own cookies to prevent fraud and secure the payment. Stripe handles that information under the Stripe Privacy Policy.

If the purchase creates a new account, we email you a single-use link to set your password. The account cannot be used until you open that link, which proves you control the mailbox. The link lasts seven days.

When you send the contact form, your name, email address, the subject you choose and your message are sent to the Proovyt application, which emails them to our team inbox with your address as the reply address. It also emails you a short confirmation. The application stores none of it in its database. The message is kept in our inbox as described in section 3.8, and we use it only to answer you.

The form loads no third-party script and no CAPTCHA. To stop automated spam it includes a hidden field that people leave empty, and it notes how long the form was open before sending. The application limits how many messages one network address and one email address can send. It counts these with one-way hashes and keeps no address in readable form.

• Name and email address. Collected when you sign up, buy a plan or accept an invitation. Your email address is your sign-in and the address we write to.
• Your password stays with our identity provider. Sign-in runs through Amazon Cognito using a protocol that proves your password without sending it. Your password never reaches Proovyt’s servers, and we never see or store it. Passwords must be at least 12 characters with upper and lower case letters, a number and a symbol.
• Email verification. An account works only after its email address is verified. A sign-up that never verifies is deleted automatically.
• Two-factor authentication. You can turn on a second sign-in step with an authenticator app. The secret and the codes are handled by Amazon Cognito. We never send codes by text message or email.
• Sessions. When you sign in we create a session and set the cookies listed in Cookies and Browser Storage below. We store a one-way hash of the session token, the time it was created and last used, and when it expires. We do not store your IP address or browser details with your session.

• Workspace details. The workspace name, its plan, its settings, who belongs to it and in what role.
• Invitations. On the Team plan, the admin can invite people by email. We store the invited address and send the invitation on the admin’s behalf.
• Workspace activity log. Each workspace keeps a record of who did what in it and when, such as publishing, exporting or deleting a demo, invitations, member and role changes, plan and seat changes, and account deletion requests. Each entry holds the person’s account identifier and the display name they had at the time, the action and what it acted on. It never holds passwords, tokens or addresses, other than an invited email address. Only the workspace admin can read it, and it is kept for the life of the workspace.
• Billing records. Your Stripe customer and subscription identifiers, your plan, billing period, subscription status, renewal date and, on Team, the number of seats. Stripe holds your payment method, billing address and invoices. We never hold full card numbers.

The service stores what you put into it. That includes screenshots you capture or import, the text, labels, hotspots, callouts and edits you add, intro and end cards, branding such as a logo, brand name, website link and favicon, audio such as background music, and your workspace defaults.

Page copies (HTML capture, beta). On the Pro and Team plans, each step recorded with the Proovyt Capture extension also holds a copy of the web page you recorded, alongside its screenshot. A page copy holds the page’s visible text, its layout and the styles that give it its look, the images it shows and the font files it uses, where the website allows them to be read. Together, screenshots and page copies are the content of your demos, and you own them.

Screenshots and page copies can contain personal information. They show whatever was on the screen, which can include names, email addresses, customer records or other details. Proovyt does not automatically detect, mask or remove personal information from them. You decide what to record and what to hide. For a screenshot, blur and solid redaction are baked into the image pixels. For a page copy, blur replaces the covered text with blocks and the covered images with blurred copies, and hide removes an element. Both are applied, and checked by the service, before a demo is published or exported, so the original is not sent to viewers. You are the controller of personal information in your content, as section 02 explains.

Publishing. When you publish a demo, the service copies only the screenshots and page copies that demo uses, with blur, redaction and hidden elements already applied, into a separate location for that published version. The rest of your workspace stays private. Anyone you share a published demo with, or who has its link, can view it, subject to any password or expiry date you set. Unpublishing, republishing or deleting the demo removes the superseded copies.

The extension records a click-through of your product into demo steps. It records only after you press Start recording, and only in the tab where you started. For each click it captures a screenshot of the visible tab, the click position, the page title and host name, and the label of the element you clicked, such as a button’s text. It never reads what is typed into a field, although a screenshot shows whatever is visible on screen at that moment.

On the Pro and Team plans it also records a copy of the page at each click, as described in section 3.6. The copy never holds what is typed into a text field, text area or editor. Those areas are kept as part of the screenshot. It never holds scripts, links, or the names and contents of form fields. Images and font files are read from the page’s own addresses as data and are never run. If your workspace moves to a plan without HTML capture, page copies you already recorded stay with their demos and keep working, and the extension records no new ones.

The extension sends what it records only to Proovyt, using a capture token that can only create demos in your connected workspace and show which account is connected. It expires after 90 days. You can revoke it at any time from the connect page or the extension. Changing or resetting your password, turning two-factor authentication on or off, and deleting your account revoke it too. The extension has no access to your other tabs, cookies or browsing history, and it runs no code fetched from elsewhere. What it records waits in the extension only until it is uploaded or you discard the recording, and then becomes part of your demo and is kept as part of it.

While it is connected, the extension keeps its capture token, your account email, your workspace name and whether your plan includes HTML capture in Chrome’s storage on your device, as section 08, Cookies and Browser Storage, lists. Disconnecting removes them, and removing the extension deletes everything it stored.

Our use of information received from the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use it only to provide the capture you asked for and the demos you make from it. We never sell it, never use it for advertising, and never use it to decide creditworthiness or for lending. We transfer it to others only in these cases.

• To the service providers in section 7.1 that host and deliver the service for us.
• To the people you share a published demo with.
• To protect against fraud or abuse, or when the law requires it.
• As part of a merger, acquisition or sale of assets, after asking for your consent first.

Our staff read it only with your consent for specific content, for example when you ask for help with a demo, when security requires it, such as investigating abuse, or when the law requires it.

• Messages you send us. When you contact us, we keep the message and our reply to help you and to keep a record.
• Service email. We send email to verify your address, to set up or reset your account, to deliver Team invitations, and about your account and its security. Stripe sends payment receipts and billing notices. We do not send you marketing email unless you have asked for it.
• Security records. To stop abuse, we count attempts at sign-in, sign-up, password reset, checkout and similar actions against your IP address and email address for the length of each limit window. Our servers and load balancer keep technical logs, which can include IP addresses, to keep the service secure and to diagnose faults.
• Product usage records. To understand how people use Proovyt and improve it, our servers record a short list of steps a workspace takes in the application. For example, signing up, confirming an email address, connecting the capture extension, creating and publishing a first demo, clicking an upgrade button, and starting, completing, changing or cancelling a subscription. Each record holds only the step, the time, your workspace and account identifiers, and a few fixed details such as the plan or which upgrade button was clicked. It never holds your name, email address, IP address, browser details or anything you typed or recorded. These records stay on our own servers, use no cookies or third-party analytics tools, are never sold or used for advertising, and are not shown to other customers. When you send the contact form, we count the message by its subject only.
• Operator actions. Our staff can suspend an account or workspace, take down a published demo, change a plan for a support case, or reset two-factor authentication after verifying who you are. Operators sign in with required two-factor authentication, and every such action is recorded with its reason in an append-only audit log.

To tell the demo’s owner how the demo is doing, the page sends a small event when it is viewed, when each step is reached, when the demo is completed, and when its call to action is clicked. Each event holds the demo, the event type, the step number, the number of steps, the day, a random identifier created for that one page load and forgotten when the page closes, and a unique viewer value.

How unique viewers are counted without tracking. The unique viewer value is a one-way hash of a salt that changes every day, your IP address, your browser’s user agent and the demo. We store only the hash, never the address. Yesterday’s salt is deleted, so once the day is over a stored hash can no longer be tied back to an address. The same person counts once per day per demo.

Bots. Requests from known crawlers, link previews, scripts and automated browsers are dropped and never counted. Automated browsers that identify themselves send nothing at all.

The owner sees totals such as views, unique viewers, completion and where viewers stopped. On the Free plan the owner sees basic view counts.

A demo’s owner on Pro or Team can protect it with a password, an expiry date or both. If you type the password, the page keeps a signed pass for that demo in your browser’s session storage, so you are not asked again in the same tab. It is removed when the tab closes and lasts at most two hours. We do not set a cookie for it. Unlock attempts are rate limited using a hash of your IP address.

On a demo with background music, the player remembers your volume in local storage and whether sound is on in session storage. When a demo is embedded on another website, that website’s owner controls the page around the demo, and any cookies or scripts it runs are governed by its own privacy notice. The Proovyt frame inside it behaves exactly as described here.

Our load balancer keeps a standard access log of requests to demo pages, which includes the IP address and the address of the page requested. It is kept for 30 days, used only for security and fault diagnosis, and never used for analytics or to identify viewers.

• Your name and email address, and your company if you give it.
• Your answer to a consent checkbox, if the owner added one, together with the exact wording you saw. The wording is the owner’s own. Ticking it is never required to continue.
• The time of your first and latest submission, and how many times you sent the form for that demo.
• How you used the demo. Your visits, the furthest step you reached, how many steps you viewed, whether you completed it, your time in the demo, and when you were last seen. This includes the steps you viewed in the same page load before you sent the form.

To recognize you on a later visit, the page keeps a signed token in your browser’s local storage after you send the form. It names only that demo and that lead, and it expires after 180 days. While it is there, the form is not shown again on that device and your later visits count toward your progress. You can remove it at any time by clearing this site’s data in your browser.

Only the demo’s owner and the workspace admins can see a lead and its progress. A teammate the demo is shared with does not. Every field you type, the consent answer and the consent wording are encrypted together with AES-256-GCM under a key used only for lead data, bound to that workspace, demo and record, so a copied record cannot be read anywhere else. Your email address is also kept as a keyed one-way hash so a second submission updates your existing record instead of adding another. No lead field is written to our logs.

The form is protected against spam without any third-party script or CAPTCHA. Submissions that look automated are discarded and stored nowhere.

A lead is deleted automatically once it is older than the period the workspace admin chooses, from 30 to 730 days, 365 days by default, counted from your first submission. The owner can delete it sooner, and deleting the demo deletes its leads. When a lead is deleted, the visits linked to it become anonymous, and those anonymous events are deleted after 6 months like all viewer analytics.

The owner can export and delete leads at any time, on every plan, including after a downgrade. To see, correct or delete your details, contact the person or company that shared the demo with you. If you contact us instead, we will pass your request to them and help them respond.

Where the law of the European Economic Area, the United Kingdom or Switzerland applies, we rely on the following bases.

• Performance of our contract with you, for your account, the service and billing.
• Our legitimate interests in securing and improving the service and in preventing abuse, which we balance against your rights. That includes the product usage records and security records.
• Compliance with legal obligations, for tax and accounting records and lawful requests.
• Your consent, where we ask for it, which you can withdraw at any time.

Proovyt has no generative AI features today. The first draft of a callout is written from the label of the control you clicked, not by an AI model. We do not send your content, page copies, viewer analytics or lead form data to any AI provider, and we do not use them to train machine-learning models, ours or anyone else’s. If we add AI features, we will update this policy and our subprocessor list before they process your information.

We do not sell personal information. We do not share it for cross-context behavioral advertising or targeted advertising. We do not use it to profile people for decisions that have legal or similarly significant effects.

We rely on a small set of providers. Each is bound by contract to protect the information and to use it only to provide services to us. They are Amazon Web Services, for hosting, storage, content delivery, sign-in (Amazon Cognito) and email delivery (Amazon SES), and Stripe, for payments. Where we act as a processor for customers, these providers are our subprocessors.

Our Subprocessors page lists each one with what it does, the personal data it receives and where it processes it, and names any provider we plan to add before it starts. Sentry, for error reporting, is listed there as not yet in use.

ProfytAI also runs a shared access control service, on Amazon Web Services in Singapore, that decides who may reach which workspace and demo. It holds only identifiers and the relationships between them, such as which account belongs to which workspace. It holds no names, email addresses, screenshots or lead form data.

On the Team plan, the workspace admin can see every demo in the workspace and the name and email of each member. Members see their own demos and those shared with them. Anyone you share a hosted link or embed with can see the published demo. Lead form data is visible only to the demo’s owner and the workspace admin.

• Legal and regulatory. We may disclose information if the law requires it, in response to a valid legal request, or to protect the rights, property or safety of Proovyt, our users, viewers or the public. Where we receive a request for customer content or lead data, we will try to redirect it to the customer and, where the law allows, tell the customer first.
• Business transfers. If ProfytAI Pte. Ltd. or Proovyt is involved in a merger, acquisition or sale of assets, information may move as part of that transaction. We will tell you before your information becomes subject to a different policy.

You can delete demos and leads yourself at any time. You can also delete your whole account yourself, on every plan, without contacting us. Open Manage Account from the menu under your name, find the Delete Account card, and select Delete My Account.

• Take a copy first. The Your Data card on the same page downloads a file with your account, the workspaces you belong to, and the demos you created with their hosted link settings and a summary of their analytics. Lead details stay in the service and are exported as CSV files from a demo’s Analytics tab. A project file from the editor keeps a demo together with its images.
• What happens to each workspace. The card lists them. A workspace that only you belong to is deleted with your account. A workspace that has other members stays, you leave it, and the demos you made there stay with that workspace, because they belong to the customer that owns it.
• What must be done first. The card says if anything stops the deletion. If you own a workspace that has other admins, make one of them the owner in Members, so its billing has someone to belong to. If you are the only admin of a workspace that has other members, make one of them an admin or remove them. If a workspace that only you belong to has a paid plan that still renews, cancel it in Billing, so nothing is charged after your account is gone.

To confirm, you type your email address and your password, and the code from your authenticator app when two-factor authentication is on. You are then signed out everywhere and the capture extension is disconnected. Hosted demos and embeds in the workspaces being deleted stop playing at once, and their open invitations stop working. Nothing is removed for 7 days. During that time you can sign in and select Keep My Account to bring everything back, hosted demos included. When the 7 days end, your account, your sign-in identity, and those workspaces with all their demos, files, published copies, analytics and leads are deleted from the live service. Backups then roll off on the schedule above, and nothing is restored from a backup for a deleted account.

What we keep, and why. We keep a record that an account was deleted, holding only its email domain, never the full address. Product usage records lose every link to you. A workspace you leave keeps its activity log entries naming you, because they are that workspace’s record of what happened in it. Stripe keeps its own record of your payments and invoices under its retention rules. We may keep other information for longer where the law requires it, to resolve a dispute, or to enforce our agreements, such as the record of an operator action.

If you cannot sign in. Write to us through our contact page, using the email address on the account. We will verify that the request comes from you, run the same deletion for you, and reply within 30 days.