Privacy Policy

We try to write this in language a real human can read. Where the law makes us use a specific term (controller, processor, lawful basis), we explain what it means in plain English right next to it. If anything is unclear, email privacy@peutly.com and a founder will get back to you.

Peutly ("Peutly", "we", "us") is a business based in the Netherlands. We are the data controller, the party that decides how and why data is used, for the information you give us as a customer or visitor. We are the data processor, the party that handles data on someone else's instructions, for the demo content and viewer events that flow through Peutly on your behalf.

• Account data: name, work email, company and billing details. Collected when you sign up or pay an invoice. We don't store a password, because Peutly signs you in with an email link or through an identity provider you already use.
• Support and feedback data: anything you send us through support, surveys, or product feedback, so we can help and improve.
• Product telemetry: what you do inside the Peutly app (screens opened, feature usage, actions taken in a workspace), along with your IP address and browser user-agent. Used for debugging, security and product improvement, never sold.
• Demo content: a recording is a copy of the page you recorded. It holds that page's HTML and visible text, a screenshot at each click, and anything typed into the page while recording. Only password fields are masked at capture; everything else is captured as it appears. Images, stylesheets and fonts from the recorded page are copied onto our own CDN so the demo keeps working later. Blur, hide and replace are edits you apply afterwards in the editor, not redaction at capture time, so please don't record real customer data you wouldn't want stored. We handle all of this as your processor, on your instructions. If you need a data processing agreement in place, email privacy@peutly.com.
• Webcam and microphone recordings: if you record yourself for a demo, the audio or video is stored with that demo like any other asset.
• AI assistant and voice-over: messages you send the AI assistant, files you attach to it, and the narration scripts you write. AI conversations are kept with your workspace; attachments are deleted after 30 days.
• Viewer data: when someone opens a demo you published, we record a session with an approximate location derived from their IP address (country, region and city, looked up in a MaxMind GeoLite2 database that runs on our own servers, so the IP address itself is never sent to MaxMind), the device type, browser and operating system parsed from the browser user-agent, the page that linked to the demo and any UTM parameters in the link, which steps were viewed and for how long, and a random viewer ID that the demo player stores in the viewer's browser local storage so a returning viewer can be recognised. Once the location lookup is done we truncate the IP address (the last octet of an IPv4 address, the last 80 bits of an IPv6 address) before it is stored. Viewers stay anonymous unless they submit one of your forms. When they do, we store the fields they filled in together with the full IP address, user-agent and referrer of that submission.

This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.

The Chrome extension needs permission to run on every site, because you decide which product to record. It does nothing on a page until you press record, and it stops when you stop. It reads your Peutly sign-in cookie so it can upload the recording to your workspace. It does not record your microphone, camera or tab audio.

Most of what we hold, you give us directly, when you create an account, pay, contact support, or use the app. Some is collected automatically as you use the Service (see telemetry and cookies below). Occasionally we receive limited data from third parties such as our payment or authentication providers, and we handle it under this policy. The lawful bases we rely on for each of these are set out in section 5.

We process personal data only to (a) provide, secure and bill the Service, (b) prevent abuse and meet our legal and security obligations, and (c) improve the product based on aggregate usage signals. We may occasionally tell you about features and updates that are relevant to you. We advertise on Google and, only if you accept the cookie banner, measure which ads lead to sign-ups (see section 8). We do not show ads in Peutly or in your demos, build shadow profiles, or sell data to third parties, ever. If you withhold information we genuinely need, some parts of the Service may not work.

We rely on:

• Contract, for everything required to deliver Peutly to you.
• Legitimate interest, for product telemetry, abuse prevention, and direct service-related emails, such as a weekly summary of your demo analytics to workspace admins and, if you switch them on, alerts when a lead returns to a demo. Each of these can be turned off in the workspace settings. To keep the platform safe we automatically score workspaces for signs of abuse, such as phishing demos. A score never suspends an account by itself: a person reviews it first.
• Consent, for non-essential cookies and any marketing email you've opted into.
• Legal obligation, when tax, accounting or compliance laws require retention.

We don't knowingly collect special categories of sensitive data, and we ask that you don't put it into demos either. Peutly isn't aimed at children; if you are under 16, please only use it with a parent or guardian's consent.

Peutly runs on Amazon Web Services, with our primary region in Europe (Frankfurt). Published demos and their assets are served through a content delivery network, which caches copies at edge locations around the world so that a viewer anywhere gets a fast load. Some of our sub-processors operate outside the EU, so data may at times be stored, processed or transferred internationally. When that happens we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses or the EU-US Data Privacy Framework, to protect it. Our database also runs in Frankfurt. The providers behind the AI assistant and AI voice-over are in the United States, as are Google, which receives ad measurement data, and Microsoft, which receives site usage recordings, unless you decline them in the cookie banner. We don't offer region pinning today. If you need to know exactly where a particular kind of data sits, email privacy@peutly.com.

We use a short list of sub-processors for hosting, storage and content delivery, the database, sign-in, payments, the AI assistant, AI voice-over and web fonts. The full list, with what each one receives and where, is on our sub-processor page. We give workspace admins 30 days' notice before adding one. Anthropic and OpenAI only receive data when you use the AI assistant or generate a voice-over, and neither may train its models on it. A workspace admin can stop the AI assistant from reading captured screen text and screenshots in the workspace settings.

The terms that govern how we process data for you as your processor are in our Data Processing Agreement, which is part of our Terms of Service.

• peutly.com: when you visit this site we load Google Tag Manager, which we use to manage the measurement tags below, and Google Ads, which sets cookies (up to 90 days) to tell us which ad you came from and whether you went on to sign up, and Microsoft Clarity, which records how you scroll, click and move through this site (session replays and heatmaps) and sets cookies for up to a year. Clarity masks text you type into forms. If you decline in the cookie banner, we remove these cookies, Clarity no longer loads, and the Google tags switch to consent-denied mode (Google Consent Mode): they set no cookies and send only cookieless pings without user identifiers. The only cookie left is the one that remembers your choice (180 days). You can change your mind at any time under Cookie settings in the footer.
• The Peutly app: one essential cookie keeps you signed in (30 days), and one remembers whether the sidebar is open. Preferences such as theme and layout are kept in your browser's local storage. The app loads the same Google Tag Manager container as peutly.com and follows the cookie choice you made there: with consent it tells Google Analytics and Google Ads when you sign up, start a trial or buy a subscription, so we can see which ads work. If you declined, those tags set no cookies and send only cookieless pings without user identifiers. The live-viewers map in the analytics dashboard loads its map tiles from Mapbox, which receives the IP address and map requests of the person looking at the map (see our sub-processor list); no viewer or lead data is sent to Mapbox.
• Published demos: Peutly sets no cookies on viewers. The player keeps a random viewer ID and which steps a viewer has seen in their browser's local storage, so a returning viewer can be recognised and pick up where they left off. The viewer analytics described in section 2 (approximate location, device, referrer, steps viewed and time spent) is processed by Peutly on behalf of the demo's owner, as their processor, so the owner can see how their demo performs. It is not used for advertising and we do not combine it across different owners' demos. If the demo's owner has connected Google Analytics, Segment or Heap, those services run in the viewer's browser and may set their own cookies. That is the demo owner's choice and responsibility, including asking for consent where the law requires it.
• Demos embedded on peutly.com: pages here that show a live Peutly demo load it from share.peutly.com, which records an anonymous viewer session like any other published demo.

Our site and demos may link to services we don't control. This policy doesn't cover those third parties, and we're not responsible for their practices. Please check their own privacy notices before sharing data with them.

We'd rather tell you what we actually do than quote a policy we don't enforce yet, so here it is honestly.

• Account and workspace data: while your account exists, and until you ask us to delete it.
• Demo content: a deleted demo disappears from your workspace and stops being served straight away. We erase the recording, its files and the viewer sessions and leads it collected within 30 days of your request to privacy@peutly.com.
• Viewer sessions and engagement events, including the truncated IP addresses and the location, device and referrer details attached to them: deleted automatically 13 months after they were recorded. Leads, including the IP address, user-agent and referrer of the submission: for as long as the workspace exists, unless you ask us to remove them sooner. If you want a shorter window, or want a set of viewer records removed, email privacy@peutly.com and we'll do it.
• Internal records of app activity: 90 days. Aggregated usage counters: 396 days. Background job records: 90 days. Admin sessions: 7 days.
• Exports: a finished export stops being served 7 days after you requested it, and export videos are deleted after 30 days.
• AI assistant: attachments 30 days; conversations stay with your workspace until you delete them or ask us to.
• Server logs: 30 days.
• Database backups: encrypted, and overwritten within 35 days.
• Cancelled subscriptions: we keep the workspace for 90 days after the paid period ends, so you can resubscribe, then delete it. Closing your account on request: we delete your workspace and everything in it within 30 days of your request.
• Billing data: for as long as Dutch tax law requires.

Under the GDPR you can access, correct, port, restrict, object to, or delete your personal data, withdraw any consent you gave, and ask us not to subject you to solely automated decisions. Email privacy@peutly.com and we'll respond within 30 days (usually much sooner). We may need to verify your identity first. If you're not satisfied with our response, you can complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) or your local supervisory authority.

Data is encrypted in transit over HTTPS (TLS 1.2 or better) and encrypted at rest in our file storage and database. Signing in uses an email link or an identity provider you already use, so there is no password of yours for us to lose, and sessions run on short-lived tokens we can revoke straight away. Access to production is limited to the people who need it. No system is perfectly secure, but we work hard to keep yours safe and we're happy to walk you through our posture. Email security@peutly.com. If you believe you've found a vulnerability, see our responsible disclosure page.

We take privacy complaints seriously. Send yours to privacy@peutly.com and we'll acknowledge it quickly and work with you toward a resolution.

When we make a meaningful change we'll notify workspace admins by email before it takes effect, and we'll update the date at the top of this page. We encourage you to check back now and then.