slicer.dev
Back to home

Privacy Policy

Last updated: August 27, 2026

Introduction

slicer.dev ("we", "our", or "us") respects your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website, Chrome extension, and related services (collectively, the "Service"). Please read this policy carefully.

Our commitment: We collect only what we need to provide and improve the Service. We do not sell personal information, and we do not use Website Audit, Journey Audit, or Slice page content for advertising. We use product analytics and limited campaign-attribution data to understand feature use and measure conversions. After sign-in, product events may be linked to your account so we can provide support, enforce allowances, and understand the customer journey. The extension never tracks browsing history or captures page content in the background.

Information We Collect

We collect different types of information depending on how you use the Service.

  • Account information: If you create an account, we collect your email address, name, and any profile details you provide.
  • Website analytics: On our website (slicer.dev), we capture pageviews, clicks, feature interactions, device/browser information, and campaign attribution. Before sign-in these events generally use a browser identifier. After sign-in, analytics may include your account identifier, email address, name, and subscription plan.
  • Extension usage analytics: The Chrome extension collects anonymous interaction events to help us improve the product — for example, which features are used, which export formats are chosen, and whether operations succeed or fail. Each event includes an anonymous session identifier and the extension version. No URLs, page content, browsing history, or personal information is included in these events.
  • Content you create: Slices, exports, and other content you save or generate through the Service may be stored and processed to provide the Service.
  • Website Audit data: When you submit a URL, we collect the submitted domain and URLs, captured public page content, DOM structure, computed styles, screenshots, accessibility and runtime measurements, navigation relationships, generated findings, report interactions, and operational metadata such as duration, cost, status, and abuse-prevention signals. If you request a completion email, we also collect that address.

Data Collected by the Chrome Extension

The Chrome extension does not collect data in the background and never monitors unrelated browsing activity. It collects data in three categories:

Anonymous usage analytics

The extension sends anonymous usage events (via PostHog HTTP API) when you interact with its features — for example, activating the extension, selecting an element, choosing an export format, or completing a generation. These events help us understand which features are used and where errors occur so we can improve the product.

To protect your privacy, the extension enforces a strict block-list that prevents the following from ever being included in analytics events: URLs, page URLs, hostnames, page content, HTML, CSS, email addresses, and names. Events contain only an anonymous identifier (a random UUID stored locally in the extension), a session identifier, and the extension version number. After you sign in, the anonymous identifier may be linked to your account ID (an opaque UUID, not your email or name) so we can understand usage patterns across sessions.

Slice data (on explicit use only)

  • Page content: When you select a UI component to slice, the extension captures the HTML structure, CSS styles, and a screenshot of that component. This data is sent to our servers solely to provide the requested extraction and AI code generation.
  • Capture safeguards: The extension excludes executable and unsupported content from the captured structure and applies automated filters to reduce accidental disclosure. A capture can still include text, images, and other information visible on the selected page, so you should not capture material you are not authorized to process.

Journey Audit data (on explicit recording only)

When you start a Journey Audit, the extension captures each page or state you choose in that recording. A capture can include its URL and title, page structure and visible text, computed styles, images, a screenshot or thumbnail, viewport details, and the clicks or navigation relationships that connect the captured steps. This can include pages behind a login. Recording is limited to the browser tab where you started it and stops when you finish or discard the journey. We store these captures in your account so we can reconstruct the journey and generate the requested audit and findings.

What We Do NOT Collect

  • We do not track browsing history unrelated to an explicit Slicer action
  • We do not collect page data unless you explicitly use Slice or start a Journey Audit recording
  • We do not inject ads or tracking scripts into webpages
  • We do not sell or share personal data with advertisers
  • We do not use captured website or component content for personalized advertising or audience profiling

How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve the Service
  • Capture submitted or explicitly recorded pages and generate Website Audit and Journey Audit reports and replays
  • Authenticate users and manage accounts
  • Process payments and manage subscriptions (where applicable)
  • Send you service-related notifications and support
  • Analyze product usage and campaign conversions to improve the product and understand acquisition performance
  • Comply with legal obligations and enforce our terms

Cookies and Similar Technologies

Website: We use cookies and local storage on our website to maintain sessions, remember preferences, measure product usage (via PostHog), and, where enabled, attribute advertising conversions. You can use our cookie controls or your browser settings; disabling certain cookies may affect measurement or website functionality.

Chrome extension: The extension does not use cookies. It stores a single anonymous identifier (a random UUID) in chrome.storage.local for usage analytics. This identifier cannot track you across websites and is used solely to group anonymous usage events within the extension.

Third-Party Services

We use the following third-party services. Each has its own privacy policy; we encourage you to review them:

  • Supabase (authentication, database): Stores your account information and usage data. Privacy Policy
  • Stripe (payment processing): Processes subscription payments. We do not store your payment card details. Privacy Policy
  • OpenRouter (AI processing): When you use Slice, sanitized component data is sent to AI models via OpenRouter for code generation. Website Audit and Journey Audit also send captured page evidence to AI models to generate and review findings. OpenRouter and the selected model provider process the request under their current data-handling settings and policies. Privacy Policy
  • Browserbase (remote browser infrastructure): Loads URLs submitted to Website Audit and processes the resulting browser session and capture data. Privacy Policy
  • Vercel (hosting): Our backend infrastructure. Privacy Policy
  • PostHog (product analytics): Website — measures pageviews, clicks, feature usage, and conversion events via the PostHog JS SDK; signed-in events may be linked to your account. Chrome extension — sends anonymous usage events (feature interactions, export format choices, success/error rates) via PostHog HTTP API. The extension never sends URLs, page content, browsing history, or personal identifiers. We use this data for product analysis and campaign conversion measurement, not to build interest profiles or deliver personalized ads. Privacy Policy
  • Advertising and conversion partners (including Google, Meta, and X): Receive limited campaign, browser, and transaction identifiers when enabled so we can attribute signups and paid conversions. We do not send captured website or component content to these partners.
  • Resend (transactional email): Delivers account, audit, billing, and requested report notifications and processes the recipient address and delivery events needed for those messages. Privacy Policy

Chrome Web Store Compliance

Our use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:

  • Page data is captured only after an explicit Slice or Journey Audit action and is used only to provide those user-facing features
  • We do not sell user data or page content to third parties
  • We do not use captured data for advertising or profiling
  • We do not transfer captured page data to third parties except as necessary to provide storage, hosting, extraction, and AI generation
  • The extension collects anonymous usage analytics (via PostHog HTTP API) to improve the product. These events contain no URLs, page content, browsing history, or personally identifiable information. A strict block-list prevents sensitive data from being included.

Data Retention

We retain your information for as long as your account is active or as needed to provide the Service, comply with law, resolve disputes, and enforce our agreements. You may request deletion of your data subject to applicable law.

Captured component data (HTML, CSS, screenshots) is processed for AI generation and may be retained when needed to provide saved projects, history, troubleshooting, security, or abuse prevention. Extraction metadata, including timestamp, type, and source domain, is stored with your account.

Website Audit captures and Journey Audit captures, screenshots, previews, findings, and report metadata are retained so the report can be viewed, claimed, shared, or re-opened. Unclaimed anonymous audit journeys and their captures are normally deleted after 7 days; limited job and operational metadata may remain for up to 30 days. If you claim an audit or create a Journey Audit in your account, its captures remain until you delete the associated journey or account, or we remove them under a legal or operational requirement. Shared reports use a private, unguessable token, but anyone with the link may be able to view the report.

Legal Bases and International Processing

Depending on the feature and your location, we process information to perform our contract with you, with your consent, to comply with law, or for legitimate interests such as securing, operating, measuring, and improving the Service. Our providers may process information outside your country. Where required, we rely on appropriate transfer safeguards.

Your Rights

Depending on your location, you may have rights to access, correct, delete, or port your personal data, or to object to or restrict certain processing. This includes data held by our analytics providers. To exercise these rights, contact us at the email address below. You may also have the right to withdraw consent and to lodge a complaint with your local data-protection authority.

Security

We implement reasonable technical and organizational measures to protect your information. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last updated" date. Your continued use of the Service after changes constitutes acceptance of the updated policy.

Contact Us

If you have questions about this Privacy Policy or our data practices, please contact us at: privacy@slicer.dev