Privacy notice

Beta operator and contact

SoftwareFool is an independently operated beta service, intended mainly for US users. Software Fool LLC is a planned name and is not a registered entity. Operator registration, a business address and final jurisdiction remain pending. Email [email protected] for privacy questions, correction requests or requests that account controls cannot resolve. We may verify your authority before acting.

Account, security and agreement records

Registered accounts provide an email address. Guest processing uses a random internal guest identity and a browser session cookie without requiring an email address. The service handles registered customers’ email addresses, optional first and last names, a password hash, verification status and account activity dates. Account security includes session records, sign-in address/device information, authentication factors and recovery controls. API records include key permissions, usage dates and revocation; a complete key is displayed only when created. Legal records identify the Terms accepted or Privacy notice acknowledged, the version and its integrity hash, and the decision time. The new legal workflow does not record raw IP addresses or browser strings. A Privacy acknowledgment confirms reading this notice; it is not blanket consent to optional processing.

Files, jobs and credits

The service processes submitted PDFs, images, text documents, spreadsheets and presentations to perform your requested tools. Job records include file sizes and integrity fingerprints, ordered input and options, status, times and the accepted cost. Credit records include grants, expiry, temporary beta activity, reservations, adjustments and spending. Support email contains what you choose to send; do not send passwords, recovery codes, API keys or sensitive file contents.

On-site issue reports contain the category, description, optional page or tool, job reference and optional follow-up email you provide, plus the submission time and an account link if you are signed in. They are private to the owner and kept for up to 90 days, then deleted by maintenance. Reports linked to a registered account are included in its data export and deleted on account closure. Contact support with your report reference for an anonymous-report privacy request; we may verify your authority. No files are attached and no automatic email or response time is promised. Do not include passwords, API keys, recovery codes or private document contents.

Purposes and limits of use

Information is used to operate accounts, verify and recover access, process requested tasks, deliver results, maintain legal and credit records, protect against abuse, troubleshoot and answer support requests. File contents are not used for advertising or training our or third-party AI models. The current beta has no advertising trackers or third-party behavioral analytics, does not sell personal information and does not collect payment-card data. Optional investigation access is described separately below.

Traffic protection and monitoring

Requests necessarily transmit network addresses through the connection and Cloudflare edge. For the one-time guest beta allowance, we retain a separate secret-keyed network identifier and its allocation record to prevent repeated allocations, including after cookies are cleared. IPv4 public addresses and IPv6 /64 networks define this eligibility. People sharing a network share eligibility, but cannot view one another’s files or spend another browser session’s remaining credits. This identifier is not a promise of anonymity and is not included in the short-lived analytics groups described below. Allocation and related credit audit records are retained to enforce the one-time limit and preserve accounting history. Application operational observations use sanitized route groups, response codes, timings, coarse client classifications and daily-changing keyed address groups. Those observations do not retain raw addresses, browser strings, query values, credentials, account identifiers, filenames or file contents. Observations are scheduled for removal after 7 days and may be removed sooner by a record limit. These groups are not individual people and crawler identities can be forged. Repeat-scanner enforcement separately uses bounded secret-keyed address digests with strike history expiring after 24 hours without a new qualifying burst. Active blocked requests do not prolong that history. This does not erase separate sign-in/security records or a provider’s own records.

Essential cookies and local clients

Essential browser cookies support sign-in, request protection and account messages. Blocking them can prevent account actions. The website does not currently use advertising cookies. The Python client and MCP connector use your supplied scoped API key; they do not replace website legal decisions. Keep locally saved credentials and downloaded files private. Their local copies are outside the service’s deletion controls.

Upload and result lifecycle

Inputs remain available while work is queued or processing, potentially longer than a day. Cancelled jobs schedule input removal immediately. Successful inputs are removed when the first result download starts or the result expires. Results remain available until their displayed expiry, normally 24 hours, or Delete Now. Interrupted downloads can be retried during that window. Intermediate outputs may remain needed by an active or paused flow. Delete Now blocks new access but cannot withdraw copies already downloaded or an active transfer. Expiry is an access cutoff; physical cleanup can be delayed or retried.

Optional failed-file investigation

Production failures are opted out of development investigation by default. The failure page offers a separate unchecked choice to keep and use the already uploaded files to investigate and fix the issue; no new upload is needed. Leaving without saved consent deletes those files. If the browser cannot report departure, cleanup after 24 hours is the fallback. Files retained with consent remain private for investigation. No fixed investigation retention deadline is claimed; withdrawing consent schedules deletion. Unchecking the choice withdraws consent and schedules deletion. Development environments may retain debugging files and private diagnostics; these are not the ordinary production default.

Retained history and current backup policy

Deleting files does not delete job, credit or agreement history. Account closure pseudonymizes personal sign-in details and disables access while retaining relationships needed for accounting, legal evidence and security. Recovery backups are currently disabled for this beta installation; the service does not promise recovery of accounts, records or files after host or storage loss. Earlier independently retained recovery copies may still exist and do not have a finalized universal deletion schedule. Other retained records and support messages also do not yet have a finalized universal deletion schedule. No claim is made that all records disappear when a download expires; these schedules and the recovery policy must be reviewed before paid service.

Providers, access and international processing

The beta processes jobs on an operator-managed host. Cloudflare supplies the public edge and tunnel and handles request routing/security; ZeptoMail by Zoho delivers configured transactional email and receives the recipient and message information needed for that delivery. Account emails do not attach uploaded file contents. Authorized operators and necessary infrastructure providers may access information to operate, secure or support the service. Information may also be disclosed when required by valid legal process or to protect people and the service. Provider processing can occur internationally; the final operator/provider location register remains pending. No US-only data-residency, GDPR certification, HIPAA compliance, ISO certification or regulated-data service is claimed.

Security and your choices

Private artifacts use account-scoped access, unpredictable storage identifiers, integrity checks and expiry controls. Connections use HTTPS. Recovery backups are currently disabled for this installation. These safeguards do not mean every stored upload is encrypted at rest or that no security failure is possible. You can update your profile, verify a replacement email, change your password, manage factors and sessions, revoke API keys, export account data, download/delete results and request eligible account closure. These controls remain accessible if you decline a new legal version, subject to ordinary authentication and security checks. Remaining files follow expiry after closure; closure is not a promise of immediate file erasure.

Rights, children and sensitive material

Applicable access, correction, deletion, objection and other privacy rights depend on your location and circumstances; this notice does not remove rights provided by law. Contact support for requests the account tools cannot resolve. The service is not directed to children under 13; contact support if you believe a child supplied personal information. Submit only files you are authorized to process. The beta is not offered as a certified environment for regulated or highly sensitive records. A full data-processing agreement and any required international-transfer arrangements must be reviewed before offering such a service.

Notice changes and acknowledgment

The published version and date identify the notice you read. Material service changes, registration and launch require another review. New published required notices prompt an explicit acknowledgment before new processing; saving a draft does not change what applies. Declining does not give consent, and acknowledging this notice does not opt into failed-file investigation, advertising or other optional processing. Public policies and existing-work/account recovery controls remain accessible. Save or print a copy for your records.