Privacy Policy

About this notice

Peter Sobol, doing business as Sobolsoft, operates sobolsoft.com, the browser apps and account services at apps.sobolsoft.com, and Sobolsoft Read-only Reporting, a private tool for preparing sales and website-performance reports for authorized Sobolsoft operators. This notice explains the website, account, subscription, support, and reporting practices described below. It does not describe every downloaded desktop application's handling of files, accounts, or services; consult the information supplied with the particular application. Licensing and service terms are separate in our Windows End-user License Agreement and Browser App Terms.

Notice version: 2026-10-21. Permanent copy of this notice. Acknowledging this notice does not turn on optional analytics or marketing and does not waive your privacy rights.

Privacy questions and requests can be sent to natesobol@gmail.com. Please do not include passwords, API credentials, full payment-card details, or other unnecessary sensitive information.

Website, purchases, and support

• Website operation: our hosting and security services process technical request information, which can include IP address, requested URL, browser information, and request time, to deliver the website, investigate errors, and protect against abuse. Cloudflare Web Analytics supplies website-performance and traffic statistics, including page views, visits, and popular pages. Visits are not necessarily distinct people, and reported traffic can be estimated or sampled.
• Shopping cart: the website stores cart contents in your browser's local storage so they can survive navigation and later visits. You can remove this information through your browser's site-data controls; doing so can clear your saved cart.
• Purchases: checkout uses Stripe. Sobolsoft stores order, payment-status, product, and license-fulfillment information to process purchases, provide licenses, maintain records, and resolve purchase questions. Internal reports summarize recorded payments and orders; they are not a record of full payment-card numbers.
• Support: when you contact us, we process the contact details, subject, message, and any product or order reference you provide. Technical and message-delivery information can also be processed to prevent abuse, route requests, and investigate failures. Support processing can include automated or AI-assisted handling through OpenAI and Cloudflare services, as well as staff review. Do not submit sensitive information that is unnecessary for your request.
• Email: Resend is used for application-generated email. Email providers process recipients, message content, and delivery information as part of sending and handling messages. Our ordinary mailboxes also use their respective email providers.

Browser apps: files and account information

Your selected files and generated results are processed on your device, not uploaded to Sobolsoft for processing. This does not mean that using an account is offline or anonymous. The site contacts our services for authentication, account settings, authorization, subscription management, and operational reporting. If you choose an app function that opens a third-party website or retrieves remote material, that destination receives the requests needed for the function. Files you deliberately attach to a support message are handled as support information instead.

We process the following information for browser-app accounts:

• Account and profile: an account identifier, email address, verification status, optional name, any profile image provided through sign-in, creation/update times, and linked sign-in methods. Password accounts store a password hash, not the password as readable account data. The password you submit is processed over a secure connection to create or check that hash. Verification, recovery, and email-change flows use temporary security tokens.
• Sign-in and security: session identifiers, session creation and expiry times, and associated technical information such as IP address and browser information. Rate-limit records help prevent excessive sign-in attempts and email abuse. Necessary cookies keep you signed in and protect authentication; these operate separately from optional analytics. A sign-in session normally lasts up to seven days and may renew while you use the service. You can sign out or revoke sessions in Account settings. Clearing browser cookies may sign you out.
• Favorites and settings: the apps you favorite and account preferences you choose, associated with your account so they can be available when you sign in again. Browser-only app settings or unfinished work may instead remain in local browser storage; clearing site data can remove them.
• App-operation and token records: account identifier, app and action, a run reference, request time, allowance day, admission decision, and whether a free token was consumed. We use these records to apply the shared daily free-token allowance, avoid duplicate deductions when a request is retried, provide account status, investigate errors or abuse, and prepare operational summaries. The Free plan comparison shows the current allowance. These records do not contain filenames, file contents, output contents, or ordinary button-click activity.
• Agreement records: the account, time, agreement method, exact acceptance wording, and document versions acknowledged or accepted. Paid checkout separately records the recurring-payment authorization wording and version, the offer, and a reference linking the authorization to its checkout session and account agreement. We retain this evidence and the corresponding terms and notice versions; acknowledging this notice is not consent to unrelated data use.
• Account and checkout source: when a first-party app link or account-required action leads to account creation or subscription checkout, we save the published app identifier, link placement, source time, and the type of evidence with that account or checkout. Signup source and checkout source are separate records. Missing, expired, or historical source information can remain unknown; we do not reconstruct it by assigning a later-used or favorited app. A source describes the observed account flow, not a person's reason for subscribing. These operational source records do not add a persistent browser identifier or match optional analytics identifiers to your account.
• Billing: Stripe customer and subscription references, checkout status, trial eligibility and start/end dates, payment and invoice references, amounts, currency, billing dates, cancellation status, and trial or paid-through access. A card-required trial records the recurring authorization and its offer before checkout; entering the trial does not count as a paid invoice. Stripe collects and processes the payment details and billing information needed for payment, tax, fraud prevention, and its legal obligations. Our account pages may display limited card details, such as brand, last digits, and expiry. We do not store full card numbers or security codes in the Sobolsoft account database.
• Subscription confirmations: a saved copy of the confirmation email and receipt, recipient address, payment amount, invoice and subscription references, paid-through date, authorization and document references, creation/sending times, sending status, and the email provider's message reference. These records let us provide the confirmation, avoid duplicate sends, and investigate uncertain delivery. A provider accepting a message does not prove that it reached the inbox. Confirmation records are retained with billing and agreement evidence; the login-gate deletion schedule does not apply to them.
• Internal trial and subscription notifications: named operational emails to authorized Sobolsoft operators can include your profile name and verified account email, trial or payment status and dates, collected amount/currency, signup and checkout source apps, sign-in method, favorite apps, and a limited summary of authorized primary actions and quota denials. Authorized actions are starts, not evidence of completed file processing or a count of files. These emails support account operations, subscription reconciliation, and product-flow reporting. We save a snapshot of the notification, its intended recipients, sending status, and provider reference so retries do not change the reported event or duplicate a send. Files, filenames, file contents, generated results, credentials, full card details, and optional browser analytics identifiers are excluded.

Cloudflare hosts the account service and its D1 database. Resend processes account verification, password recovery, email-change, and other service emails. Stripe processes billing and payment-method changes. Necessary account and payment processing is not switched off by declining optional website analytics. See Cloudflare's privacy policy, Resend's privacy policy, and Stripe's privacy policy for their own practices.

Google and Apple customer sign-in

If you choose Google or Apple sign-in, that provider authenticates you and sends us the identity information and tokens needed to create, find, or link your Sobolsoft account. This can include a provider account identifier, email address and verification status, and a name or profile image where supplied. Apple may supply a private relay email address when you choose Hide My Email. Sobolsoft does not receive your Google or Apple password.

Customer sign-in requests basic identity and email information. It does not request your Gmail messages, contacts, Google Drive files, or permission to read your iCloud files. We use the received data for the sign-in and account functions you choose, account security, and related service communication. Stored OAuth access and refresh tokens are encrypted. Token and account records may remain until their removal even if a token has expired or provider access has been revoked; disconnection is not a general deletion request.

You can manage linked methods in Account settings and revoke provider access through Google Account connections or your Apple account's Sign in with Apple settings. Ensure that you retain a working Sobolsoft sign-in method before removing one. Revoking a connection can prevent future provider sign-in; it does not automatically cancel a subscription or erase an existing Sobolsoft account. For deletion requests, contact us as described below. The provider's own privacy policy also applies to its processing.

Google sign-in data are not sold or used for personalized advertising, data-broker products, or credit decisions. Our use and disclosure of Google API data must follow the Google API Services User Data Policy, including its Limited Use requirements where applicable. The customer sign-in connection is separate from the optional Gmail browser tools and the private reporting connection described below.

Optional Gmail browser features

Connecting a Gmail browser tool is a separate choice from signing in to a Sobolsoft account. Account sign-in alone does not grant access to your mailbox. When a Gmail feature is available to you, the tool explains its access before you choose Connect Gmail and approve Google's permission request. You can use Sobolsoft account services without connecting Gmail.

The Gmail sender requests send-only access. It uses the recipient addresses, subject, message body and optional local attachments that you enter to submit the message you request directly to Google. It does not request permission to read your inbox. All listed recipients appear together in that message's To field. A send log remains in the open page; an accepted request is not a guarantee of delivery. The sender does not automatically retry a send whose outcome is uncertain.

Read-only Gmail tools request separate read access. The attachment downloader, email-data extractor, email-address extractor and printer use message headers, bodies, labels and attachments as needed for the folder, label, search, range and action you choose. The new-mail alarm checks unread Inbox message identifiers, sender and subject headers, and an available message summary while its page is open and visible; it does not retrieve full message bodies or attachments. These tools do not request permission to send mail, delete messages, change labels or mark messages read. Read-only access is broad enough to read mailbox contents even when your chosen operation retrieves a smaller selection.

Gmail processing occurs in your browser. Gmail reads and message submissions travel directly between your browser and Google over HTTPS. The Gmail connection's access tokens, retrieved mail, addresses, attachment names and bytes, extraction results, local sounds and send logs are not sent to Sobolsoft servers for processing or saved in the Sobolsoft account database. App-action authorization identifies the app, action and request; it does not include Gmail tokens, messages, recipient addresses, filenames, filters, results or attachments. Ordinary hosting, account and security requests remain separate as described above.

Gmail working data stay in the current page's memory. These tools do not save Gmail tokens or mailbox data in localStorage, sessionStorage or IndexedDB and do not persist refresh tokens. Access can expire and require you to connect again. Other site preferences, such as an app's zoom setting or optional analytics choice, can use browser storage without containing Gmail data.

Disconnecting forgets the local Gmail token and prevents further authorized mail requests. Read-only tools clear their retrieved mail and results. User-entered compose fields and the sender's log can remain in the open page until you reload or close it. Reloading or closing the page discards in-memory working data. Files you deliberately save, clipboard text, printouts, saved PDFs and messages you send remain in their chosen destinations and must be managed there.

Disconnecting does not revoke Google's saved permission grant. You can remove that grant through Google Account connections. Revocation stops future authorized access; it does not erase previously saved files, sent messages or other copies you created.

We use Gmail information only for the feature you choose. We do not sell it, use it for advertising, disclose it to data brokers or use it to train general-purpose AI models. The Gmail tools do not forward message content to an AI service, analytics service or Sobolsoft staff. If you deliberately paste email content into a support request, that content is handled under the support practices described in this notice; avoid supplying unnecessary sensitive information.

The use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Optional Outlook.com and Hotmail connections

Connecting a personal Outlook.com or Hotmail mailbox asks for a separate Microsoft permission. Ordinary Sobolsoft account sign-in does not grant mailbox access. Delegated Mail.Read permission allows the app to read your mailbox on your behalf; the tool loads the folder or email range you choose. The tools do not request permission to send, delete or change messages.

The tools use message headers, addresses, subjects, dates and bodies to save text files, create PDFs, extract addresses or text, or prepare printing. Checked messages and your selected fields or rules determine the output. HTML previews can also retrieve original message data to display supported embedded images. Remote images and scripts are omitted.

Mailbox requests go directly between your browser and Microsoft over HTTPS. Microsoft access tokens and mailbox content are not uploaded to Sobolsoft for processing or stored in the account database. Access tokens, retrieved messages, previews and generated results are held in the current page's memory. Microsoft's sign-in library can use temporary browser session storage for sign-in state. Microsoft controls its own sign-in session and cookies.

Disconnect ends this app's local connection and clears its cached access, retrieved messages, previews and results. Reloading or closing the page ends the local mail session. Downloads, text already copied to the clipboard, and printed or saved PDF copies remain in their chosen destinations. Disconnect does not sign you out of other Microsoft sites or revoke Microsoft's saved permission grant; manage that separately in Microsoft account app permissions.

Ordinary Sobolsoft account and app-action records remain separate, as described above. Optional app usage analytics do not receive Microsoft tokens, mailbox content, email addresses or extracted results.

Login-gate operational reporting

When an app's primary operation requires sign-in, we record the app, time, and a hashed reference for that particular request. A short-lived handoff reference lets us determine whether that request is followed by a successful login or creation of an account within one hour. When that handoff creates an account, a separate durable account-source record can save the originating app as described above. Gate counts measure requests and outcomes, not distinct people. An unmatched request does not establish that a person deliberately ignored the prompt.

The gate-reporting table does not store email addresses, account identifiers, IP addresses, filenames, files, or results. It does not create a persistent visitor identifier or tracking cookie and does not match browsing across unrelated sites or devices. Authentication still uses account and security records to verify the outcome. A temporary handoff reference may travel with the sign-in flow, including its return address or that tab's storage; it is not a marketing profile.

This limited reporting operates independently of optional analytics to measure and troubleshoot the account-access flow. Individual gate records are eligible for deletion after 31 days and are removed by routine service cleanup; this is not an immediate deletion guarantee at an exact second. The aggregate gate viewer shows aggregate counts. Account-source handoffs expire after one hour and are eligible for routine cleanup after expiry; durable source snapshots do not contain the raw reference. Account creation counts, trial and paid account totals, app-operation and token records, account and checkout source snapshots, and named service notifications are separate records with different retention needs.

Google data and the reporting application

Website visitors do not need to grant access to their Google Search Console or Analytics data for Sobolsoft's private reporting tool. This reporting authorization is for Sobolsoft's authorized reporting operator, not the optional customer Google sign-in described above.

The reporting connection uses read-only authorization for Google Search Console. It retrieves Sobolsoft property-level search clicks, impressions, click-through rate, average position, dates, search queries, pages, device categories, and country-level statistics. It uses these figures to prepare reports, compare reporting periods, and identify pages or search topics to review. Search Console statistics do not tell us who an individual searcher is.

The current authorization also includes Google Analytics read-only permission. Google Analytics collection by this reporting tool is not currently connected. If connected for an authorized Sobolsoft property, its reporting purpose is traffic-source, engagement, and conversion-event statistics. The presence of a permission does not mean those data have already been collected.

This reporting connection does not request access to Gmail messages, contacts, Google Drive files, or permission to edit Search Console or Analytics settings. Google access can be removed through your Google Account connections settings. Removing access stops future authorized reads; it does not automatically erase reports already created.

Optional website analytics

Optional website analytics are off unless you accept them. We do not show an analytics banner on ordinary website pages. You can opt in or change your choice using Analytics preferences at the bottom of the current Privacy page. A previously saved acceptance remains effective until it expires or you withdraw it.

When you accept optional analytics, we store a random identifier in this browser's local storage for up to 90 days, without extending its expiry on each visit. A visit session ends after 30 minutes of inactivity. We record product views, download and purchase-button clicks, checkout readiness, payment submissions, and general error categories. We connect consenting activity to confirmed orders to understand how people find and purchase software. Attribution considers the preceding 30 days on the same browser; we do not match people across devices or by email.

This data includes product identifiers, timestamps, coarse device/operating-system categories, referrer hostnames, and registered campaign identifiers. These analytics records do not include names, email addresses, payment credentials, license keys, full referrer URLs, or arbitrary query strings. A download click does not tell us whether software was installed or activated.

Accept and Decline are optional choices. Leaving analytics off or declining does not affect downloads, checkout, or licenses. To withdraw a saved acceptance, use Withdraw analytics consent at the bottom of the current Privacy page; this removes the browser identifiers and stops future optional collection. Global Privacy Control is treated as declining optional analytics. Already collected events and order-attribution links expire after 90 days; identifier-free daily summaries and scheduled report snapshots are retained for three years. Financial, support, and license records have separate retention needs. Contact us using the address above for requests concerning previously collected information.

Optional browser-app analytics

Browser-app analytics are off unless you choose to allow them on the browser-app privacy page. When enabled, they record the visited app page, visit time, referring site hostname, registered campaign, and approximate device and operating system. Fixed categories describe whether a visit came from search, another website, Sobolsoft, a registered campaign or directly, and whether the app was reached through a catalog, category, product page or another app. Session storage retains the entry hostname and categories across catalog navigation; full referring URLs, search terms and arbitrary query values are not retained.

Instrumented app functions can record an authorized start, completed processing, a processing failure, or output handed to the browser. A browser handoff does not prove that a file was saved to disk. Previews, cancelled runs and file-processing runs without output are not counted as completed processing; a completed search can return no matches. Coverage varies by app. Supported browsers can also report coarse good, needs-improvement or poor ratings for loading speed (LCP), interaction responsiveness (INP) and visual stability (CLS). Performance entries, page element details and raw metric values are not sent.

A pseudonymous random browser identifier is stored for up to 90 days; session identifiers expire after 30 minutes of inactivity. Analytics are separate from account and token records. The analytics service uses the request IP transiently for abuse-rate limiting and does not store it with the event. Analytics do not include selected files, file names, file contents, contact or email fields, error messages, or generated results. No consent prompt is shown in the apps. Turning analytics off or enabling Global Privacy Control stops future optional observations. Unsupported or unobserved measurements remain unavailable.

Reporting storage, use, and disclosure

Scheduled reporting runs within Cloudflare, using protected reporting credentials and private aggregate storage. Authorized operators can also keep local exports. The scheduled report viewer only exposes aggregate data after its access checks, never browser identifiers or individual order-attribution links.

The aggregate reporting pipeline reads Sobolsoft sales records from Cloudflare D1 and traffic statistics from Cloudflare. It processes order-level records to produce summaries. Saved aggregate report data exclude customer names, customer email addresses, payment identifiers, and license keys. The separate internal trial/subscription notification channel described above includes the account and event details needed by authorized operators and is not part of the aggregate report viewer. Google search queries and public page names may appear in aggregate reports; query filtering reduces, but cannot guarantee the removal of, accidentally sensitive text.

Report data and generated HTML, graphs, and email files are stored in Sobolsoft-controlled storage. Local reporting tools use Windows account-bound encryption and restricted file permissions for stored Google authorization and reporting-provider credentials. Scheduled reporting uses Cloudflare Worker secrets. Report files are separate from those protected credentials. Private reports and credentials are not intended for publication in the website's source repository.

Reports are for authorized Sobolsoft operators. When email reporting is enabled, report content and recipient addresses are processed by Resend and the recipients' email providers. Authorized report-review and AI-assisted development tools may process selected report information during setup, review, or troubleshooting. These are separate from the reporting tool's Google permissions; the reporting sign-in itself does not grant those tools additional Google Account access.

Google API data are used for the authorized reporting purpose, not sold to data brokers, used for personalized advertising, or used to make lending or credit decisions. Access and disclosure must remain consistent with the Google API Services User Data Policy, including its Limited Use requirements where applicable. Changes to Google data access or use that require additional consent will be disclosed before that new use begins.

Service providers process information to supply the relevant hosting, security, payment, email, support, or reporting functions. Information may also be disclosed when required by applicable law or as necessary to investigate abuse and protect security. Provider processing may take place outside your country and is subject to the providers' applicable terms and privacy notices.

Retention, security, and your choices

Browser accounts: account profiles and linked sign-in records are retained to provide and secure the account. Favorites remain until you remove them or they are removed with the account. We keep app-operation and free-token records, account/checkout source snapshots, trial and subscription/payment records and confirmations, internal service-notification snapshots, and agreement evidence for account operation, billing reconciliation, security, dispute handling, and applicable legal obligations. There is currently no fixed automatic purge period for those durable account ledgers. Copies sent to authorized operator mailboxes and provider-held delivery records have their own retention and are not erased by source-reference expiry. Authentication-token expiry does not itself guarantee deletion of every underlying database or backup record. Temporary rate-limit records and expired one-hour attribution handoffs are removed by routine cleanup; gate records have the separate 31-day schedule described above. Provider-held records and backups can have different retention periods. We assess access and deletion requests rather than promising that signing out, cancelling renewal, or disconnecting a provider erases all records.

There is currently no automatic fixed-period deletion schedule for local reporting snapshots and generated reports. Removing a Google connection alone does not delete those files, stored authorization files, backups, or copies already sent by email. Retention of orders, licenses, support records, provider records, and backups can differ from report retention.

Contact the privacy address above to request access, correction, deletion of information we control, removal of stored authorization, or cessation of future reports. Identify the relevant account, record, or report without sending credentials. Account deletion requests are handled through this contact process; there is not currently a self-service delete-account button. Cancelling a subscription is a separate action available in Account → Plan & billing; ask support if you need help with both cancellation and deletion. We may need to verify your authority before acting. We will assess requests under applicable law and explain relevant limits, such as records needed for accounting, security, legal obligations, or license support. Depending on your location and the applicable law, you may also have rights to data portability, restriction, objection, withdrawal of consent for consent-based processing, or a complaint to your local data-protection authority. You can contact the relevant provider about information it controls.

Where data-protection law requires a legal basis, necessary account and subscription processing supports providing the service you request; security, abuse prevention, and proportionate operational reporting support our legitimate interests, subject to the safeguards and balancing required by that law. Accounting or legally required disclosures may be required by law. Optional analytics use your choice to opt in and can be withdrawn as described above. These explanations do not make all processing consent-based or override rights applicable in your location. We do not knowingly create browser accounts for children in circumstances that require authorization we have not obtained. Contact us if you believe a child's account or information requires review.

Access controls, encrypted credentials, and secure connections help protect information, but no system can guarantee absolute security. Deletion of an active copy does not necessarily immediately remove backup copies or copies controlled by email recipients or independent providers.

Changes and contact

We will update this page when the described practices change and revise the date above. Where additional notice or consent is required, updating this page alone does not replace that requirement. Archived versions preserve the notice associated with an account's acknowledgement; an acknowledgement is not a waiver of rights or permission for an undisclosed new use. For questions about this notice, browser accounts, or the reporting application, email natesobol@gmail.com.