Legal

Security and privacy at Layerpath

What we store, where it lives, which AI reads it, and how to delete it. Our privacy policy has the full legal text.

Last updated November 3, 2026

At a glance

• Where data is stored: in the United States, on Amazon Web Services, Vercel, and Supabase.

• AI providers: Google (Vertex AI and the Gemini API), Amazon Bedrock running Claude models, OpenAI, Deepgram, and ElevenLabs. We don't send your information to Anthropic directly.

• Training: we don't use your walkthroughs, screenshots, recordings, or messages to train AI models.

• Sign-in: with Google, or with your email and a password or a magic link.

• Sharing: a published walkthrough opens for anyone with its link. You can unpublish or delete it in Layerpath.

• Deletion: delete walkthroughs in Layerpath, or email support@layerpath.com. We erase the files or integration data you ask about within 30 days. Backup copies of a deleted account are gone within 3 months.

• Security issues: email security@layerpath.com. We confirm we got your report within 2 business days.

Where your data lives

Layerpath's servers, storage, and database are in the United States, on Amazon Web Services, Vercel, and Supabase.

Some AI services we use can handle a request in another country where the provider has data centers. Amazon Bedrock can send a request to any AWS region it supports. Google's AI services may handle or briefly cache a request in any country where Google has facilities.

Members of our team who work outside the United States, including in India, may access your information to support you and keep Layerpath working.

When we move personal information out of the EEA, the UK, or Switzerland, we use the European Commission's Standard Contractual Clauses or another legal safeguard.

Which AI we use

AI reads your screenshots and recordings, writes the words for each step, places hotspots, blurs names and email addresses, translates, turns speech into text, and makes voiceovers. This table covers every AI provider Layerpath uses: in the Layerpath app, the browser extension, shared walkthroughs, and Layerpath Agent in Slack, ChatGPT, and Claude.

We don't send your information to Anthropic directly. In our Slack app, Claude models run inside Amazon Bedrock. Anthropic doesn't receive those messages, and Amazon Bedrock doesn't keep requests for the Claude models we use. When you use Layerpath in Claude, the results you ask for go back to your Claude chat, where Anthropic's privacy policy applies. Each provider keeps and uses what it receives under its own terms, linked in our privacy policy.

What Layerpath Agent receives

In ChatGPT, Claude, and MCP assistants

• When you connect: your Layerpath sign-in and the Layerpath workspace you pick. ChatGPT or Claude then holds a sign-in token for Layerpath. We never see your ChatGPT or Claude password.

• With each request, only what that action needs: what the walkthrough should show, the change you want, which walkthrough or step it's about, or a Loom link you paste (or a YouTube link, in ChatGPT).

• Screenshots or recordings you add in Layerpath's upload box in the chat. In ChatGPT, also the files you attached to the chat when you ask for a walkthrough from them. Claude doesn't pass us the files you attach to a Claude chat.

• From ChatGPT, IDs that tell your chats apart. We keep only a scrambled (one-way) form of them.

• The step you pick in Layerpath's editor in ChatGPT or Claude, so "this step" in your next message means that step.

We don't receive your chat history, or ChatGPT's or Claude's memory. We don't build a profile of you from your requests, and we don't send what you write in ChatGPT or Claude to our product analytics.

What we send back: walkthrough names, the words of each step, pictures of steps, share, embed, video, and PDF links, your workspace's brand voice notes when a walkthrough uses them, and the IDs needed to find a walkthrough again. ChatGPT and Claude keep these as part of your chat, under OpenAI's or Anthropic's privacy policy.

Claude Code, Codex, and other MCP assistants connect through the same Layerpath MCP server as Claude, and the same rules apply. Results go back to that assistant, under its provider's privacy policy.

In Slack

• When someone adds Layerpath to your Slack: your Slack workspace's name and ID, the Slack ID of the person who added it, and a token that lets Layerpath read and post messages as its app.

• Messages that mention @Layerpath, messages in a direct message with Layerpath, and replies in threads where Layerpath is working, including replies people post to each other there.

• When you mention Layerpath in a thread for the first time: the earlier messages, screenshots, and videos in that thread, and the text of canvases shared there.

• The screenshots, screen recordings, and Loom or YouTube links you share with it.

• When someone posts a Layerpath link anywhere in your Slack: the link and where it was posted, so Layerpath can show a preview.

• Each person's Slack ID, display name, and time zone, and whether they're a guest or from another company.

Slack also sends us other messages from channels Layerpath is in. Unless a message is in a thread Layerpath is working in, we drop it as it arrives, without reading, using, or keeping it. Guests, and people from other companies in a shared channel, can't use Layerpath in your Slack. Layerpath's replies and walkthrough previews are Slack messages, kept under your Slack workspace's settings and Slack's privacy policy.

Who can see your walkthroughs

• Your workspace: members of a Layerpath workspace can see the walkthroughs in it. If your company runs the workspace, its admins can see and manage them.

• Share links: new walkthroughs publish at a share link that anyone with the link can open, without a Layerpath account. You can unpublish or delete a walkthrough in Layerpath.

• Exports: a PDF guide or video export works without publishing the walkthrough. Anyone with an export link may be able to open it.

• Our team: only team members who need to can look at your content, to answer your request, fix a problem, or keep Layerpath secure.

• Viewers: when someone opens a walkthrough you shared, we record the view: their rough location (from their internet address), browser type, the page that linked to it, time spent on each step, and a random ID for the visit. We don't put a tracking cookie on their device. If your walkthrough has a form, we keep what viewers enter in it.

We don't sell your personal information, we don't share it for targeted advertising, and we don't show ads.

Blur private details

Ask Agent to blur names and email addresses in your screenshots. You decide what to record, so leave out passwords, API keys, and customer data you don't want in a walkthrough. Agent can make mistakes. Review the walkthrough before you share it.

How long we keep it

Delete your data or disconnect

• Delete a walkthrough in Layerpath. Its share link stops working within a few minutes. To have every copy of its files erased from our storage, email support@layerpath.com and we erase them within 30 days.

• Delete integration data or your account: email support@layerpath.com, or submit a data subject access request. For Slack, ChatGPT, or Claude data, include your Slack workspace's name or the email you sign in to Layerpath with. We delete integration data within 30 days. Backup copies of a deleted account are gone within 3 months.

• Disconnect: in ChatGPT, open Settings, then Apps. In Claude, open Customize, then Connectors. To remove Layerpath from Slack, use Slack's app settings, or in Layerpath open Settings, then Integrations. Disconnecting stops new information from reaching us. It doesn't delete walkthroughs you already made. When Layerpath is removed from your Slack, we drop the token Slack issued for it and delete Layerpath's memory of your threads within 7 days.

• Fully revoke ChatGPT or Claude access: disconnecting in ChatGPT or Claude stops that app from calling Layerpath, but it doesn't end your Layerpath sign-in on our side. To end it, an Owner or Admin can disconnect you in Layerpath under Settings, then Integrations, or you can email support@layerpath.com.

Sign-in and access

• Sign in with Google, or with your email and a password or a magic link.

• Workspace roles are Owner, Admin, Editor, and Viewer. Owners, Admins, and Editors can create walkthroughs. Viewers can't.

• In Slack, a Layerpath workspace Owner or Admin connects Layerpath once. Your Slack admins may also need to approve the app. After that, full members of the Slack workspace can create walkthroughs.

• Enterprise plans include a security and procurement review. Talk to sales.

Service providers

Besides the AI providers above, these companies host, store, or process data for us:

• Amazon Web Services: hosting, storage, and video exports

• Vercel: hosting the Layerpath app and share pages, and visit counts

• Supabase: database

• PostHog: product analytics and session recordings in the Layerpath app

• Google: Google Analytics on our website, and Google sign-in

• Loops: sign-in, account, and product emails

• Stripe and Chargebee: payments and billing events

• Dash0: server logs

• Chatwoot: the help chat in the Layerpath app

• Firecrawl and Brandfetch: reading your company's website and logo for Brand memory

Report a security issue

Email security@layerpath.com. Tell us what you found, how to reproduce it, and what it affects. We confirm we got your report within 2 business days, and we keep you posted while we fix it. When you look for issues, don't access or change other people's data, and don't slow down or break Layerpath for others.

FAQ

Which AI does Layerpath use? Google's Gemini models (through Vertex AI and the Gemini API) read your screens and video, write the steps and callouts, place hotspots, blur names and email addresses, and translate. In our Slack app, Claude models made by Anthropic run inside Amazon Bedrock to understand requests and write replies. OpenAI turns speech into text when our main provider can't, summarizes your editing history, makes voiceovers in OpenAI voices, and writes some step text. Deepgram turns speech into text. ElevenLabs makes voiceovers and voice clones. We don't send your information to Anthropic directly.

Do you train AI models on my content? No. We don't use your walkthroughs, screenshots, recordings, or messages to train AI models.

Where is my data stored? In the United States, on Amazon Web Services, Vercel, and Supabase. Amazon Bedrock may process an AI request in any AWS region it supports, and Google may handle or briefly cache a request in any country where it has facilities. Team members outside the United States, including in India, may access your information to support you.

Does Anthropic or OpenAI get my data? We don't send your data to Anthropic directly. Our Slack app uses Claude models inside Amazon Bedrock, and Bedrock doesn't keep requests for the Claude models we use. OpenAI's API receives audio from recordings and the words of your walkthrough and edits when Layerpath uses it for speech-to-text, voiceovers, editing-history summaries, or some step text. If you use Layerpath in ChatGPT or Claude, the results you ask for go back to that chat, where OpenAI's or Anthropic's privacy policy applies.

Does Layerpath read every message in our Slack? No. It reads messages that mention it, direct messages to it, and threads it's working in. When someone posts a Layerpath link, it receives that link and where it was posted, to show a preview. Other messages from channels it's in are dropped as they arrive, without being read, used, or kept.

Who can open a walkthrough I make? Members of your Layerpath workspace, and anyone with its share link once it's published. You can unpublish or delete it in Layerpath. Anyone with an export link may be able to open a PDF or video export.

How do I delete my data? Delete walkthroughs in Layerpath, or email support@layerpath.com. We erase the files or integration data you ask about within 30 days. Backup copies of a deleted account are gone within 3 months.

How do I report a vulnerability? Email security@layerpath.com. We confirm we got your report within 2 business days.