Privacy without the vague parts.

The short version

Slurp is intentionally built without product analytics. Normal app use does not send Slurp your download URLs, download history, downloaded media, site-usage statistics, feature usage, or behavioral telemetry. Support reports contain only information you choose to submit; optional investigation and follow-up processing is described below.

What the app sends over the network

Slurp contacts the services needed to perform the action you request: media sources, update services, browser companions when you use them, Telegram when you connect your own account, and the Slurp licensing service for trial and license operations. Media is downloaded to your Mac rather than proxied through a Slurp media cloud.

Trial and licensing data

To enforce the trial and manage licenses, the Slurp licensing service processes a randomly generated installation identifier and timestamps. License records can include the license recipient or purchase email, license source (purchased or complimentary), license status, Slurp major version, activation count, installation identifiers for activated Macs, app version, activation/deactivation timestamps, and license-email delivery status. Purchased licenses can additionally include Stripe Checkout Session / Payment Intent / Customer identifiers. Complimentary licenses can include a short developer-only administrative note and an audit record of issue, reissue or revocation actions.

The licensing database stores a cryptographic hash of the license key rather than the plaintext key. Slurp does not derive the installation identifier from your Mac serial number, MAC address, Apple ID, or similar hardware/account identifiers.

Payments and license email

Payments use Stripe Managed Payments. At checkout, Link acts as merchant of record for the transaction and processes the information needed for payment, applicable indirect taxes, receipts, transaction-level support, and subscription order management. Slurp does not store your full card details. Transactional Slurp license email is sent through Resend, which receives the purchase email address and the message content required to deliver your license.

Website contact form

If you use the website contact form, Slurp processes the information you choose to submit, such as your name, reply email, topic, message, and any optional Slurp version or affected URL. The form is protected by Cloudflare Turnstile, which may process browser and network signals to distinguish legitimate visitors from automated abuse. Messages are delivered through Resend to the appropriate Slurp inbox. The contact form does not create a separate Slurp contact-message database.

Verified Slurp user reviews

If you choose to submit a review through Slurp, the review service processes the display name, 1–5 star rating and review text you provide, together with submission and publication timestamps and, when attached to the one-time invitation, the Slurp version/build. The review database does not receive your download URLs, filenames, browsing history or media history.

When an eligible licensed user requests a review invitation, the app sends a randomly generated review-specific installation identifier, the Slurp version/build, the review eligibility protocol version, and the already-issued signed license entitlement. The review service verifies that entitlement cryptographically to confirm an eligible active license. Purchased and complimentary licenses can qualify. It does not receive the raw license key, purchase email or Stripe account details. The signed entitlement is not stored; the service stores only one-way hashes of the random review installation identifier and the entitlement’s license ID for invitation throttling and duplicate-review prevention. The review installation identifier is not derived from your Mac serial number, MAC address, Apple ID or download activity.

Review invitations use one-time random tokens. The database stores a cryptographic hash of the token rather than the plaintext token. When a review is submitted, Slurp sends a moderation notification through Resend to the Slurp reviews inbox. That notification contains the review display name, rating, review text, review ID, submission time and, when available, Slurp version/build; Resend and the receiving email provider may process the message and delivery metadata to deliver it.

Approved reviews are published on the public Reviews page with the display name, rating, review text and publication date. Reviews are moderated only for neutral criteria such as spam, personal information, abusive or illegal content, duplication, relevance and legal requirements; low ratings are not a rejection reason.

Website support search

The Support page can search Slurp FAQs, guides and help topics locally in your browser. The search index is downloaded as part of the website, but the words you type into the support search are not sent to Slurp or to a third-party search provider.

In-app support requests

If you use Contact Support or Report this problem inside Slurp, the app sends the information needed to handle that request, including your reply email, category and message. Depending on what you choose to include, a report can also contain the Slurp version and build, macOS and processor information, download-engine versions, source/provider category, error details, relevant output settings, and diagnostic events associated with the problem.

In Slurp 1.0.13 or later, the problem-report flow asks you to review and include redacted diagnostics before sending. You can instead choose to contact support without diagnostics; general support messages do not require them. The affected media URL is a separate optional choice, and screenshots are optional. The support-report pipeline is designed to exclude or redact passwords, cookies, licence keys, authentication tokens, signed media URLs, full local file paths, unrelated download history, unrelated logs, and media content.

AI-assisted site fixes and optional updates

A support report can help Slurp investigate a broken site. Reports from public sites can be considered for focused compatibility repairs, including site-specific extraction logic. A repair must pass independent reproduction, intended-media, download, playback and regression checks before it can be published. If the video cannot be identified clearly, suitable test pages are unavailable, or the checks cannot pass within the resource budget, the case needs further investigation. Changes to the app architecture or core engine require a separate release.

AI-assisted compatibility investigations run on local infrastructure operated by Slurp in Denmark. The model receives a reduced technical summary, relevant extraction code and bounded observations from investigation tools. If you choose to share the affected link, those tools can open that public page in a fresh, temporary browser session. The model can receive the shared page URL, observed player and media URLs, quality options, network details and, when useful, a screenshot of the public page. Page content is treated as evidence, not as instructions. For reports submitted from 1 October 2026, a limited, redacted version of your description may also be processed locally in a separate AI step with no tools or action permissions. That step extracts a small set of reported symptoms, such as whether a direct download failed while the browser companion worked. Only those structured, unverified claims are passed to the investigator; the description cannot authorize actions or change verification and publication rules. Passwords, authorization values, cookies, email addresses, local paths and links in the description are filtered before this step. Links in a message are not automatically opened: the separately shared affected link is the investigation starting point. Older descriptions remain excluded unless their author separately authorizes this use. Your reply email, raw diagnostic log, credentials and user-uploaded screenshot are not passed to the automatic model.

The investigation does not use your browser profile or signed-in session. Selected public media may be downloaded temporarily on the operator’s Mac to check that a proposed fix saves the intended video and plays correctly. Independent reference samples are prepared before the model writes its repair. These support checks are separate from ordinary downloads, which go directly from the source to your Mac. Temporary verification media is removed after the check.

If you separately choose to share the affected link, an isolated verifier on an operator-controlled Mac may open that public link and temporarily download its media to test a proposed fix. This process uses no personal browser session or login credentials. Temporary test media and process output are deleted after the attempt. These test downloads are separate from your normal downloads, which continue to go directly to your Mac.

You can independently choose to receive a fix update in Slurp, by email, or both. Both choices start off and are remembered for your next report. Email updates are delivered through Resend and contain the report reference and next steps, without the media link or diagnostic details. In-app status uses a private report token and remains available for the support retention period. Automatically retrying a failed download is a separate choice for each report; it requires an in-app update and a verified installed fix and respects a paused queue.

In Slurp 1.0.13 or later, early site fixes and automatic result sharing are separate choices, both unchecked for each new report. They require in-app follow-ups. Early-fix consent permits a verified site update to be offered before general release. Result-sharing consent sends only the report reference, fix version, event type and whether the result came from an automatic retry or your explicit answer. Installation, retry start and success or failure are recorded; no media URL, filename, credentials or logs are sent with these events. You can also explicitly choose “It works” or “Still fails” without turning on automatic result sharing. Answers waiting for a connection remain on your Mac until they can be sent.

Report outcomes are deleted with the expiring support follow-up. Reduced verified findings may be kept for up to 30 days to help check later fixes. During the report’s retention period, a consented public link may be used in the investigation and independent verification of its fix. Only share public pages that work without sign-in. A Slurp-operated computer may open a shared page and temporarily download media to reproduce the problem and test a fix. Regression references are drawn from trusted public test pages and prepared independently of the proposed repair. A reported failure stops expansion of an early fix. Restoring a generally released repair requires a signed replacement update; it does not instantly change offline Macs.

Slurp’s operator receives minimal investigation-outcome alerts through Resend and Pushover, with a link to the private activity page. These alerts do not contain the reporter’s email, message, media URL or diagnostics. The support database’s EU storage setting does not determine where email services, push services or the operator’s test machine process their respective data.

EU storage for support cases

Case metadata and private attachments submitted through Slurp’s in-app support flow, and the Verified Slurp user review database, are stored in Cloudflare resources configured for the European Union. Private report pages are protected with Cloudflare Access and are not publicly browsable.

Support notifications are sent through Resend and delivered to Slurp’s support mailbox. Those email providers may process message copies or delivery metadata under their own privacy terms. The EU-storage statement above applies specifically to the support case database and private attachment storage rather than every downstream email replica, backup, or log.

Infrastructure

Cloudflare hosts the website, licensing API, license database, support API, support case storage, private support attachments, Verified Slurp user review service and database, and public download files. Infrastructure and security providers may process standard network metadata such as IP addresses as part of providing delivery, abuse prevention, authentication, and service operation under their own privacy terms.

Retention and legal basis

Where data-protection law applies, purchase and licensing data is processed as necessary to provide the product and license you requested, to protect the service against abuse, and to meet applicable legal obligations. License records are retained for as long as they are reasonably needed to support a perpetual license and associated purchase records. Trial records are retained to enforce the trial.

In-app support case data and private attachments are automatically deleted after 30 days. Rejected review content is automatically deleted after 30 days, and unused review tokens that have been expired for more than 30 days are deleted. Approved reviews remain published until removed following an applicable request. Website contact messages are not stored in a separate Slurp contact-message database, although copies can remain in the email systems used to deliver and handle the conversation.

Your choices and rights

You can deactivate a Mac from Slurp’s License window. For access, correction, deletion requests where applicable, or any privacy question, use the Contact form. Some purchase records may need to be retained where required by law or to maintain your license.

Changes

If this policy changes materially, the effective date above will be updated. Slurp will not quietly turn product analytics or download tracking on without updating this policy and the product experience.