Privacy & security

This page summarises how TurtleScene handles your recordings, your account and the people who view your demos. It is a plain-language summary of our privacy policy and terms of service, last updated 23 September 2026. If anything here differs from those documents, they take precedence.

#Who is responsible for your data

TurtleScene is made by Turtle Techsai, based in Nagpur, Maharashtra, India.

• For your account and how you use TurtleScene, we are responsible for the data.
• For personal data inside your recordings, and for data collected from people who view your demos (including lead form answers), you are responsible, and we process it on your behalf.

You own your content, and you own the output TurtleScene generates from it.

#Where your data is stored

Your data is stored with Microsoft Azure in the United States. Payment records are also held by Razorpay in India. If you use TurtleScene from elsewhere, your data is transferred to and processed in the United States and in the other countries where our providers operate.

#Who processes it

We share personal data only with the providers that help run TurtleScene:

We also share data when you tell us to, for example with Slack, HubSpot or a webhook you connect, or with anyone who has the link to a demo you make public.

#Your content and AI

TurtleScene sends the content it needs (a recording, frames from it, or the text of a script) to the AI providers above so they can return a result. We use their paid business services, under terms that don't allow them to train their models on your content. We don't use your content to train AI models either, and we don't sell personal data or use it for advertising.

AI can get things wrong. Review what TurtleScene generates before you publish it.

#How your data is protected

• Data is encrypted in transit (HTTPS) and at rest.
• Passwords are stored as one-way hashes, never as the password itself.
• If you give TurtleScene login details so it can explore your own web app, they are encrypted (AES-256-GCM) before they are stored, and used only to sign in to that app for you.
• Each workspace can only reach its own data.
• Recordings and exports are kept in private storage and handed out through links that expire.

#Control who sees your work

Nothing you make is listed anywhere public. Who can see it depends on the output:

• Public link. A clickable demo is only viewable by others while Public link enabled is on (Personalize › Share in the editor). Switch it off to take the demo down.
• Password. Add a password to a clickable demo under Password protect in the same tab. The password is checked by TurtleScene's servers and is never sent to the viewer's browser. Password protection is available on Starter and up. If the workspace moves to a plan without it, a demo with a password isn't shown to viewers at all until you remove the password or upgrade; it's never shown without its password.
• Search engines. Turn on Hide from search engines (noindex) in the SEO tab to ask search engines not to list a demo.
• Narrated video links. The player page you open with Open player or copy with Share link is unlisted: anyone with the link can watch, and the link contains a long random ID. There's no public or private switch for it. To stop sharing a narrated video, delete it. See Render, download & share.

Anything you publish can be seen by anyone who has its link, and images inside published demos are served from unlisted addresses so viewers can load them. Record in a demo account where you can.

• Clickable demos: + Blur replaces that area of the published image, so viewers can't see what was under it. Viewers, embeds and exports get a copy of the screenshot with the area destroyed; only the editor shows your original. Blur protects a demo from the moment you add it, so blur private details before you share. See Using the editor.
• Narrated videos, their formats and story videos: in the narrated video's editor, Blur marks areas of the recording to destroy. Everything made from that recording after you save it uses a copy of the recording with those areas destroyed: the video and its translated versions, the cuts, GIF, thumbnail and help article, the clickable demo's screens and story videos. A video rendered before you added the blur still shows the area until you render it again, and its share link plays the blurred recording instead until then. Your original recording is kept unchanged in your workspace, and the first AI analysis that finds the steps of a new recording runs before you can add a blur. Find sensitive info sends a few frames of the original recording to the same AI services to suggest areas to blur; it never blurs or saves anything by itself. See Blur private details.

See Share & embed and Lead capture & passwords.

#What we collect from people who view your demos

When someone views a demo you've shared, TurtleScene records a random session identifier, which steps they viewed, whether they finished, the page they came from, their browser type and their approximate country. It also stores the answers to any lead form you add. You see this on the Analytics page and in your lead CSV.

We never email the people who fill in your lead forms. Their answers belong to you.

#Cookies and email

• Cookies: we use the cookies needed to keep you signed in and protect your account, plus Google Analytics on our own website and app. There are no advertising cookies. Google Analytics is never loaded on a published demo or embed.
• Email: account emails, such as password resets, invites and "your video is ready", are not tracked. Product and onboarding emails record whether they were opened and which links were clicked, and every one has an unsubscribe link. Unsubscribing never affects account emails.

#Delete your data

• One item: in the Library, open the item's ⋯ menu and choose Delete. This removes the item and everything generated from it, including the video, its formats and its share links. It can't be undone.
• One recording: on the Recordings page, click the bin icon on the recording, then Delete recording. The video file is removed from storage and can't be recovered. Demo videos, story videos and clickable demos made from it are kept until you delete them from the Library. See Recordings library & reuse.
• Your whole account: email contact@turtletechsai.com from the address on your account. Download anything you want to keep first. We delete your account and content within 30 days, and copies in backups are removed as those backups expire, normally within a further 35 days.

Demo views and lead form answers are kept until you delete them or close your account. Server logs are kept for a limited period, normally no more than 90 days. Billing records are kept as long as tax and accounting law requires.

#Your rights

Depending on where you live, you can ask us for a copy of your personal data, to correct or delete it, to send your content to you in a portable format, to limit or stop certain uses, or to withdraw consent. Email contact@turtletechsai.com from the address on your account. We may need to confirm your identity, and we reply within 30 days.

Complaints about how we handle personal data can go to our Grievance Officer at the same address. If you viewed someone else's demo and have a question about your data, contact the company that shared it.

#Related

• Get help
• Members & roles: everyone in a workspace can open and edit its work.