sheetzer

Plain-language policy

Privacy at Sheetzer

The homepage converter processes your selected image locally in your browser. This notice describes that local processing, optional product analytics, advertising consent, and the limited information the website may otherwise handle.

Effective 14 August 2026

Your selected image and generated output are not intentionally uploaded by the rebuilt homepage converter. Conversion happens on your device. If that behavior changes, Sheetzer will show a clear notice before file selection and update this policy.

Image conversion

When you choose an image on the homepage, browser code reads it, creates a preview, traces it, and prepares the selected download format on your device. The converter does not require an account and does not send that selected file to a Sheetzer upload endpoint in this release.

Downloaded files remain under your control. Your browser or operating system may keep its own download history or cached data according to your device settings.

Browser preferences

Sheetzer may use the following first-party browser-storage entries:

These values do not contain your image, filename, name, email address, or form content. You can remove them by clearing Sheetzer site data in your browser.

To apply and protect the rolling 24-hour free allowance, Sheetzer assigns the browser a random HttpOnly first-party device token and derives pseudonymous abuse-prevention keys from that token, the signed-in account identifier, the requesting IP address or IPv6 network prefix, and basic browser request headers. Matching accounts, devices, browsers, or network addresses can share one allowance so creating or switching Free accounts does not reset usage. Sheetzer stores these derived keys and individual use timestamps in private server storage; they do not contain selected images or generated files. Each timestamp expires after 24 hours. A separate signed, HttpOnly first-party counter remembers up to five successful counted uses so returning users can become eligible for a promotion. A website cannot read a device MAC address, and Sheetzer does not attempt to collect one.

If you create an account, Sheetzer uses a secure, HttpOnly session cookie and a long-lived, HttpOnly remember token to keep you signed in across browser restarts and routine server-session cleanup. The server stores only a one-way hash of the remember-token secret, renews its lifetime when it restores your session, and replaces it after a new successful sign-in. The token remains active until you sign out, clear Sheetzer site data, Sheetzer revokes it for security, or the browser remains unused for ten years. Neither authentication cookie is available to homepage JavaScript.

Analytics and advertising

Optional first-party product analytics. Sheetzer asks before collecting product analytics. Until you allow analytics, Sheetzer's browser-side conversion activity logger does not send optional conversion, reliability, performance, or UX events and does not create its analytics session identifier. If you allow analytics, Sheetzer may record page visits, broad referral and campaign source, converter actions, trace style, output format, successful traces, downloads, broad device/browser/operating-system categories, language, timezone, viewport size, connection category, and Core Web Vitals. This helps identify usability, conversion, reliability, performance, and search-discovery improvements. When you export or save a result, the optional analytics may also compare privacy-minimised technical settings and geometry immediately before and after the action so Sheetzer can understand which controls and workflows lead to successful or failed results. Product analytics alone does not capture the image/file contents or text you type into free-text fields.

Optional product improvement previews. This is a separate choice inside Cookie settings and requires Product analytics to be enabled. If you explicitly enable it, Sheetzer may store a low-resolution diagnostic thumbnail of the selected input and the generated result when you export or save. Each preview is reduced to a maximum of 240 pixels per side and is used only in the private admin improvement dashboard. Full files, filenames, typed text, credentials, keystrokes, raw IP addresses, and raw browser user-agent strings are not stored in these previews. If this separate choice is off, no visual preview is sent.

Random browser and session identifiers used by product analytics are transformed into one-way server-side hashes. Broad country may be derived from a trusted hosting/CDN country header; when one is unavailable, Sheetzer may use the browser timezone or language-region as an approximate fallback. Raw IP addresses are not stored in conversion activity records for this purpose. Analytics event files, including any explicitly consented low-resolution previews, are stored in a private server directory outside the public website. Sheetzer does not automatically delete this analytics history on a fixed-day schedule in the current release; authorized administrators manage retention manually by UTC date/time range, subject to applicable legal, security, billing, dispute, and user-deletion requirements.

An administrator can manually ask an AI service to analyze an aggregate report. That report contains summary totals, funnel stages, daily trends, conversion types, acquisition categories, and performance metrics. It excludes visitor and session identifiers and excludes individual event rows. Aggregate data is sent only when the administrator uses that action and configures the service.

Sheetzer uses Google AdSense to place and measure advertising. The Sheetzer cookie preference layer keeps optional advertising disabled until you allow the Advertising category. For visitors in the European Economic Area, United Kingdom, and Switzerland, Google's certified Privacy & Messaging consent message may also ask for the additional choices required for personalized or non-personalized advertising before eligible ads are shown. Google may process technical identifiers, device information, IP-derived location, consent choices, and ad interactions according to its policies and the options you select.

Use Cookie settings at any time to allow, decline, or withdraw optional Sheetzer analytics and advertising. Necessary storage for security, account sessions, quota enforcement, checkout state, and remembering your privacy choice remains available because the service cannot operate correctly without it. Sheetzer does not load Google Analytics in this release.

Hosting and security logs

Like most hosted websites, the server may receive technical request information such as an IP address, requested URL, date and time, browser user agent, and response status. This can be used to deliver the page, prevent abuse, diagnose failures, and protect the service. Sheetzer does not claim a fixed log-retention period until the effective hosting configuration has been verified; logs should be kept only as long as operational or security needs require.

Accounts and payments

When you create an account, Sheetzer stores the name and email address you provide, a one-way password hash when password login is used, account and plan status, relevant acceptance timestamps, and last-login time. If you continue with Google or Facebook, Sheetzer also stores the provider name and a one-way hash of the provider's stable account identifier so future sign-ins can find the correct Sheetzer account. Provider access tokens are not retained. Passwords are not stored in readable form. Do not reuse a password from another service.

When you use Paddle checkout, Sheetzer stores the Paddle customer, subscription, transaction, and price identifiers needed to connect the purchase to your account; the selected Sheetzer plan and billing cycle; subscription status; current or next billing dates when supplied; and signed webhook event identifiers used to prevent duplicate processing. Sheetzer also creates a short-lived random checkout token that links a signed-in account to the expected server-side Paddle price mapping. The browser receives a Paddle transaction ID rather than a client-controlled Paddle price. Paddle may send the account email and other billing fields needed to process and administer the transaction. Sheetzer also records the accepted Terms and Refund Policy versions and timestamps for paid checkout consent.

Paddle handles card and other supported checkout payment details. Sheetzer does not receive or store your full payment-card number or card security code. Paddle processes its checkout and customer portal under Paddle's own privacy and payment terms, while Sheetzer receives only the identifiers and billing state required to provision and support your Sheetzer account.

If you use an enabled manual-payment fallback, Sheetzer stores the selected plan, amount and currency shown at submission, PayPal, KAST, USDT, or BTC method, provider transaction reference or blockchain transaction hash, payer name or wallet label, optional non-sensitive verification note, transfer code, submission time, review status, and administrator review note. Manual paid access remains pending until an administrator independently verifies the transfer.

Sheetzer does not ask for or store PayPal or KAST passwords, wallet seed phrases, private keys, one-time security codes, or bank-login credentials.

Account and payment records are retained while the account or plan relationship remains active and afterward as reasonably needed for billing, fraud prevention, disputes, legal obligations, and service records. You may request account closure or deletion, subject to records that must or reasonably need to be retained.

Email

Sheetzer may send transactional billing or account emails to the address on your account. Manual-payment submissions also generate status emails when they are submitted, approved, or rejected. If you contact Sheetzer by email, Sheetzer receives the address, message, and attachments you choose to send. Do not send passwords, payment-card details, wallet secrets, or personal images unless they are necessary and a suitable method has been agreed. Email is kept only as needed to handle the request and related obligations; no fixed period is asserted here.

Sharing and service providers

Sheetzer does not sell user images, browser preferences, account details, or payment-verification records. Technical request data is necessarily handled by the hosting and network providers that deliver the site. Email is handled by the relevant mail providers. If you choose Google or Facebook login, that provider handles authentication and shares the identity, name, and email fields you authorize according to its own terms and privacy policy. For Paddle purchases, Paddle is the authorized reseller/Merchant of Record and processes checkout, payments, applicable transaction taxes, receipts, invoices, recurring billing, cancellation billing actions, payment refunds, and its customer portal; Sheetzer receives only billing identifiers and subscription events required to provide the purchased service. A separately enabled legacy manual-payment route may involve the selected external payment provider and the transfer information submitted for verification. Google also handles advertising and consent data as described above; see How Google uses information from sites or apps that use its services.

Your choices

Changes to this notice

This notice will be revised when the website's data handling materially changes. The effective date above identifies this version.

Contact

Privacy questions can be sent to support@sheetzer.net.