Privacy policy
Effective date: 29 October 2026
Policy URL: https://paneshot.com/privacy/
Serkan Gunes, at 15 Nightingale Crescent, Bradville, Milton Keynes, MK13 7UE, is responsible for the personal data described in this policy and acts as its controller. Contact us at support@paneshot.com. Our website is https://paneshot.com/.
This policy covers the Paneshot macOS app, the static website, Pro purchases and support correspondence.
What Paneshot does on your Mac
Capture, editing, text, QR and payment-card recognition run on your Mac. Paneshot does not upload captured pixels, recognised text, translations, recordings or document content to its own service, except what you choose to attach to a bug report (see Bug reports below). Ordinary captures are copied to the Mac's system clipboard automatically. Private Handoff, Handoff Boards, imported images, composition changes and edited output need an explicit delivery action; saving to a file is also explicit. If you choose to send content to another app or external storage service, that recipient's own terms apply.
The app has no Paneshot account or first-party cloud storage for captures. Each eligible purchased licence can activate one macOS user installation at a time, not every user account on a Mac. This is not a hardware restriction. Free use and the 14-day Pro trial create no licensing identifier and make no licence-status requests when no purchased credential is stored. A stored purchased credential can still be checked after expiry or revocation so an eligible purchase can recover. Purchased Pro requires online activation and daily renewal attempts, with a seven-day signed authorisation. A network failure is not revocation and does not extend that expiry. Losing purchased access does not end an independently active trial or delete captures, edits, annotations or pins. Free remains available.
Every installation starts a 14-day Pro trial on first launch, with all metered features unlimited and every Pro feature available. After the trial, Free allowances reset on the first day of each local calendar month: 5 successful Scrolling runs, 10 successful non-empty Text, QR and payment-card recognition runs, 10 completed Magnify placements, and 5 successful Share-ready Frames exports. Text, Blur, Redact and all capture modes except Scrolling are unlimited on Free. Usage records are kept locally and are separate from optional analytics. The current app creates no analytics installation or user identifier.
The app's temporary crash-recovery cache can restore one active capture only while its file is less than 24 hours old. While Paneshot is running and its event loop is available, a once-a-minute check removes expired recovery and drag PNGs without clearing the in-memory capture. Normal quit removes active recovery and expired drag files; fresh drag files remain available to their receiving apps. When Paneshot is stopped or suspended, files may remain until the next launch or expiry check, but expired recovery is not restored. This is not guaranteed wall-clock deletion at 24 hours. Pins stay in memory only, are not written to disk or the recovery cache, and disappear when the app quits. Screen recordings are saved as video files in the same temporary cache and removed after 24 hours like drag files, unless you save them somewhere yourself. They contain no audio and are not sent anywhere.
Everything Paneshot does with the content of a capture happens on your Mac. Features that read text, QR codes or card numbers, find or cover sensitive details, find where faces appear, translate text, compare captures, collect captures into a board or export them keep their working data in memory for the image you are working on. That data is the pixels of an area you select to read, recognised text, your searches, face positions and the capture used for a comparison. It is not saved to the recovery cache and not sent. Paneshot does not identify or recognise anyone. Where you turn face detection on, it only finds where faces appear so they can be covered. When automatic redaction finds something, the redacted image is what reaches the clipboard and the recovery cache, and the unredacted image stays in the open Editor's memory.
Settings, such as your redaction rules, folders, file-name templates and chosen apps, are stored in the app's preferences on your Mac. Features that save files write them only where you choose. Features that hand text, images or files to the Shortcuts app or another app give them only to the one that asked, and what that shortcut or app does with them is up to you and its own terms.
Translation uses Apple's on-device translation. macOS translates the text on your Mac and it is not sent to us. The first time you use a language, macOS may ask you to download its language data from Apple, which is covered by Apple's terms.
Paneshot also writes technical diagnostics to the macOS system log on your Mac. They record the stages and timings of some actions, such as a translation, with counts and error types, and never capture content, recognised text or languages. They stay under macOS's own log retention and reach us only if you choose to include them in a bug report.
The app does not provide a visible capture history.
App analytics
Product analytics is off by default. The app collects successful feature-use counts only after you choose Allow analytics at first launch or turn on Share product analytics in Preferences → Analytics. This choice is optional for both Free and Pro and does not affect your features, limits or licence.
While the app is running and you have opted in, it adds up successful uses of supported features by calendar month in UTC and attempts to send those totals once an hour directly to PostHog Cloud in the European Union. Reports contain the feature name, count and month. All installations use one shared reporting identifier, not an identifier for your installation or you. We use totals to understand which features are used, not to measure individual users or histories.
The app does not send captured pixels, recognised text, filenames, URLs, licence details, payment data or your email address in analytics reports. It does not send individual-use timestamps, device or session identifiers, app or macOS versions, or your Free or Pro status. It does not use session replay, screen-view tracking or automatic error collection. It requests no person-profile processing or location enrichment and does not include your IP address in the report itself. The network session uses no cookies or persistent cache.
PostHog's infrastructure still receives your connection IP address and the time a report arrives. Aggregate reporting does not make this connection information anonymous. Retention of reports and provider-held connection information is addressed below.
You can withdraw consent at any time in Preferences → Analytics. Turning analytics off stops new collection and reporting, discards pending counts and cancels the current sending task. A request already sent may finish. Turning the switch off does not itself delete reports already received by PostHog.
Counts stay in memory only. Unsent counts disappear when you quit; failed reports are discarded rather than retried. Later opt-in starts with empty counters. Your consent choice is saved locally, but the app does not create an analytics installation identifier.
Website hosting
The static marketing website and purchase and authorisation service use Cloudflare Workers; purchase and payment-event records are stored in Cloudflare D1. Cloudflare may process network and request data such as an IP address, request path, time and technical headers to deliver and protect the website and licence-status service. This is separate from optional app analytics. We do not intentionally record request contents.
Website visit and download counts
When you open a page on the website, leave it or click a Download button, the page sends events to PostHog Cloud in the European Union. We use PostHog's cookieless mode: it sets no cookies and uses no local or session storage on your device. The PostHog code that does this is part of our own page, so no script is loaded from PostHog's servers. Each event contains:
- the event name, the page address without any query string or fragment (which shows the language and page) and the page title;
- the site you came from, shortened to its domain name, and any campaign labels (utm_source, utm_medium, utm_campaign, utm_content and utm_term) on the address you arrived at;
- your browser and operating system with their versions, the device type (for example desktop or phone) and a technical identifier for the page view;
- when you leave a page, how long you stayed and how far down you scrolled.
The events do not contain screen or window size, time zone, language setting, advertising click identifiers, your email address or any licence or purchase detail. We ask PostHog for no person profile, and the page does not put your IP address in the events.
PostHog's servers still receive your connection IP address, your browser's user-agent text and the time each event arrives. In cookieless mode they replace the visitor identifier with a hash made from your IP address, user agent and our website's host name, plus a secret value that changes every day and is deleted after that day's events are processed. PostHog states that the hash cannot be turned back into the IP address or user agent, and the stored events we can see contain neither. We use the hash to count unique visitors, sessions, bounces and time on page for that day. The same person looks like a new visitor the next day, and we do not link visits across days or to purchases, licences or app analytics. Because your IP address and user agent are used to make the hash, we treat this as processing of personal data, not as anonymous.
Downloads that start elsewhere, such as from the licence email, are not counted. Nothing is sent when your browser signals Do Not Track or Global Privacy Control, and the website and downloads work either way. A page that Chrome only prepares in advance is counted when you open it, not before.
Pro licence authorisation
When you activate or renew a purchased licence, the app sends its signed purchase credential, a randomly generated licence-specific public key, a fresh request identifier and proof that it holds the matching private key to our service over HTTPS. The service checks purchase, refund, dispute and current registration state. It returns a signed decision for the requesting key. A licence's first registration requires its valid purchase credential and proof of the local key, not an email code.
The public key is linked to your purchase and is personal data, even though it is random and contains no hardware information. We do not collect a hardware fingerprint, serial number, Mac name or cross-product identifier. We do not keep a list of past installations or connect licensing records to analytics. Captures, recognised text and edits are not sent. The database stores the licence identifier, order records and current binding, not the signed purchase credential. We do not intentionally log credentials, keys, codes or request bodies.
The private key stays in the Mac user's local, non-synchronising Keychain. Paneshot accesses it silently without requesting Touch ID, a password or other authentication prompts. A cached authorisation cannot unlock Pro without the matching local private key. Removing the app or its saved licence does not release the service registration. Reinstalling or updating can reuse the registration if the same Keychain key survives and is accessible. A lost, damaged or inaccessible key, a wiped system or a different macOS user installation can require transfer or recovery; copying preferences or the licence email does not copy the private key.
Changing a registered key requires your explicit confirmation and a single-use eight-digit code sent only to the stored checkout email. The app does not ask you for a destination email. Codes last ten minutes and allow at most five confirmation attempts. Requests are limited to one email attempt per 60 seconds and five per rolling hour per licence, including failed or uncertain sends, with additional connection-based protection. Requesting a code, a failed delivery, a wrong or expired code, or cancelling locally does not replace the current registration. One successful self-service transfer is allowed per rolling 30 days; the first registration does not count. Authenticated support may approve a one-hour exception to that cooldown after checking ownership. It cannot bypass email possession or payment eligibility, redirect the code or silently register another key. Loss of the original mailbox needs a separately approved support identity-and-email-change procedure, not a promise of automatic recovery.
Paneshot attempts background renewal no more than once a day. You can also check manually in Preferences. Each signed active authorisation lasts seven days. A network or service failure is not revocation and does not extend the expiry. Replacing the registration prevents the old key from renewing, but its already issued offline authorisation can remain usable until expiry. A verified revoked decision ends purchased access when received; a decision that the licence is registered elsewhere cannot authorise this installation. An independently active trial and your existing work remain intact.
The 2.0 release requires installation-bound authorisation. Older clients cannot renew unbound authorisations, and 2.0 does not accept their cached grants. Update to 2.0.1 or later to activate or renew Pro. Older clients can retain already issued 30-day authorisations until expiry; those grants cannot be cancelled remotely. Historical offline-only private builds are outside that mechanism. This does not mean that all old copies can be disabled remotely.
Pro purchases and email delivery
Pro is a one-off purchase through Stripe-hosted Checkout using Stripe Managed Payments, shown as Sold through Onelink. Stripe is the merchant of record for these transactions and handles payment details, receipts, fraud screening and indirect taxes within its Managed Payments terms and tax coverage. Serkan Gunes remains the software seller and licensor. Stripe processes payment information under its own privacy terms. We do not receive or store payment-card numbers.
After Stripe confirms payment, we store the purchaser's email address, purchase and payment references, licence identifier, chosen email language, delivery details, delivery and recovery attempt records, and refund and dispute status in Cloudflare D1. Delivery details include the download link and the information needed to send the original licence email again. Payment-event records include event references, types, states and timestamps so refunds and disputes can be applied to the correct purchase without processing the same event twice. These records do not contain card numbers or the signed licence credential; we can recreate the existing credential for verified recovery.
Resend sends a transactional email containing the licence key, download link, activation instructions, order reference and support contact. We send the purchaser's email address and message content to Resend. Its email service is configured in Ireland.
For a lost purchase credential, use the email-only recovery page at https://buy.paneshot.com/recover or contact support@paneshot.com. The page sends the existing credential only to the purchase email, never shows it or purchase details in the browser and does not reveal whether an address has a purchase. It processes the email and connection IP for matching and abuse prevention, including hashed email values for request limits. Hashing does not make those values anonymous. Receiving the credential does not reset an installation registration, waive a transfer cooldown or change the stored recipient. Use the in-app code process above to move a registered licence. If you have lost access to the original mailbox, contact support for assessment; no automatic mailbox-change route is provided.
For support, we receive your email address, message and any information you choose to include. Cloudflare Email Routing forwards new support messages to the seller's Infomaniak mailbox. We use Spark to access and manage support correspondence. Support emails received before this mailbox change may remain in the seller's Gmail mailbox under the same retention policy.
Bug reports
Choosing Report a Bug… in the status menu opens a window where you describe what went wrong. Nothing is sent until you press Send Report, and Paneshot never sends a report by itself. It has no automatic crash or error reporting.
A report contains the description you write. It also contains, only if you leave them on or add them: the diagnostics shown in the window, a reply email address, your current capture and technical details of your latest translation. Diagnostics are the Paneshot version, whether it is a development build, the macOS version, the processor type, the app language, display sizes and scales, whether Screen Recording and Accessibility access is granted, and where new captures open. You can switch diagnostics off. A capture is attached only if you tick its box, and it contains whatever the capture shows. The translation details are attached only if you tick their box, which is off by default. They are the stages and timings of your latest translation, the capture's size in pixels, how many lines and blocks of text were found, the translation engine and any error type. They never contain the text or the languages. Diagnostics hold no capture, screen text, licence or purchase details, serial number, Mac name or file path. Please do not include passwords, payment details or anything else you do not want us to see.
The app sends the report over HTTPS to our purchase service. The service checks its size and format, limits requests by connection IP address and emails the report to support@paneshot.com through Resend. It does not store the report and we do not intentionally log its contents. Each report has a random reference number made for that report alone; it identifies nothing about you or your other reports. After delivery the report is support correspondence in the mailbox described above. We use it only to investigate the problem and, if you gave an address, to reply to you.
If a report cannot be sent, Email Support Instead opens your own email app with the same text. That message is ordinary support email.
Why we use this information
We use purchase and payment references to fulfil an order, activate, renew or revoke its licence, deliver or recover its credential, handle refunds or disputes, and provide support. We use bug reports to investigate the problems they describe and to reply to you. We use the optional feature-use totals described above to understand use of Paneshot's features, not users or individual histories. We use website and service data to serve and secure the website and operate the purchase service.
We rely on these UK/EU lawful bases:
- Contract: creating and managing the Pro licence, checking purchase eligibility, registering its installation-specific key and proving possession, activating or renewing its authorisation, confirming transfers and recovering its credential, and responding to purchase requests.
- Consent: optional product analytics. You can refuse or withdraw through Preferences → Analytics without losing Free or Pro access. Withdrawing does not affect the lawfulness of processing before withdrawal.
- Legitimate interests: operating and securing the website and purchase service, counting website visits (unique visitors per day, sessions, bounces and time on page) and Download clicks, preventing fraud, handling disputes, support and the bug reports you choose to send. We will balance these interests against your rights and may need to stop processing where you object and there is no overriding reason to continue.
- Legal obligation: retaining or disclosing records where applicable accounting, tax or other laws require it.
Licensing processing is separate from optional analytics. We do not use your analytics choice to authorise licence checks, installation registration or transfers.
Retention
- Feature-use counts on your Mac remain in memory until attempted delivery, withdrawal or quit. Your consent choice remains in saved preferences after relaunch.
- Our current PostHog Product Analytics plan has a one-year retention limit for feature-use reports and website visit and download events. This does not set the retention periods for provider connection/security logs, backup copies, exports or derived data.
- We retain your email address and essential purchase and licence information for as long as necessary to provide licence activation, verification and recovery. We also retain necessary refund and dispute records to maintain accurate licence eligibility. We review deletion requests individually and retain information only where there is a continuing contractual, legal or other lawful need.
- While the licence registration is needed, we keep only its current public key, a registration-generation counter, any current transfer cooldown timestamp and any one-hour support exemption. A transfer replaces the old key; we keep no installation-history list.
- At most one pending transfer request per licence contains the requesting public key, request identifier, generation, keyed code hash, expiry, delivery flag and bounded attempt state. A new request replaces the previous one and successful transfer deletes it. Separate request identifiers and email-attempt timestamps enforce the rolling quota. No plaintext code is stored in D1. It exists temporarily in delivery memory and necessarily in Resend's systems and the recipient's mailbox.
- Each scheduled service run removes expired pending requests, email-attempt records at least one hour old, expired support exemptions and cooldown timestamps at least 30 days old. Expired data cannot authorise a transfer, but live rows can remain until the next successful scheduled run. Deleting an order cascades to its binding and temporary transfer data; it also affects entitlement and recovery, so this is not an automatic rights-request action. These limits do not impose deletion deadlines on infrastructure logs, mailboxes or backups, or replace the separate purchase/accounting retention review.
- Stripe determines retention of payment and tax records under its own terms and legal duties. We do not set its retention period.
- We retain a bug report, including any attached capture or translation details, in the support mailbox until the problem is resolved and for no more than 12 months after we receive it, then delete it. Our purchase service keeps no copy. This replaces the support-email period below for bug reports.
- We retain other customer support emails for up to two years after an issue is closed, unless longer retention is necessary for a dispute or legal obligation.
- Our email and infrastructure providers, including Infomaniak, Spark, Cloudflare, Resend and PostHog, and Google for support correspondence retained from before the mailbox change, retain technical, delivery and security records under their applicable terms, policies and legal obligations. Retention periods vary by provider and record type. The support-email period and PostHog Product Analytics limit above do not set deletion deadlines for all provider logs, backups, exports or derived data. Requests concerning provider-held copies are assessed separately under applicable data-protection law.
- Temporary capture retention on the Mac is described above.
International processing
PostHog uses its EU Cloud service; Resend is configured in Ireland. New support email is forwarded through Cloudflare Email Routing to the seller's Infomaniak mailbox, hosted in Switzerland. We access support correspondence through Spark. Support emails received before the mailbox change may remain in Gmail. Our providers may also process data in other locations.
Where personal data is transferred outside the United Kingdom, we use appropriate safeguards as required by UK data-protection law. These may include UK adequacy regulations, the UK Addendum to the EU Standard Contractual Clauses, or other legally recognised transfer mechanisms. You can contact support@paneshot.com for further information about the safeguards applicable to your data.
Your rights
If you are in the UK or EEA, you may have the right to ask for access to your personal data, correction, deletion, restriction of processing or a portable copy. You may also have the right to object to processing or withdraw consent where consent is the legal basis. These rights are subject to applicable law and its exceptions. You may complain to your data protection authority.
To make a request, contact support@paneshot.com. We may reasonably verify your identity before responding. Paneshot has no customer account, and you do not need to enable analytics to make a request. If you are in the UK, you may also complain to the Information Commissioner's Office.
The shared analytics identifier cannot isolate your contribution to aggregate reports. Your purchase email or licence reference is not an analytics lookup key. We will assess the information available and explain any identification limits and actions we can take under applicable law. We do not link analytics to purchases or introduce identity tracking just to identify requesters. Turning off analytics stops future reporting as described above; retention and rights relating to reports already received must be assessed separately.
Contact
Serkan Gunes
15 Nightingale Crescent, Bradville, Milton Keynes, MK13 7UE
Email: support@paneshot.com
Website: https://paneshot.com/