Privacy

Privacy at EditFileNow

How EditFileNow handles files, temporary processing, usage information and cookies.

Different EditFileNow tools handle files in different ways. This page explains when a file stays in your browser, when it is sent to EditFileNow for processing, and what usage information we record.

Designed for on-device processing

Supported local work stays in the browser without a source-file upload. Unsupported inputs are rejected before processing.

On-device when supported

Local processing is preferred. Optional image compression fallback requires an available server, a clear explanation, and explicit confirmation before upload. Local PDF tools do not upload when unsupported.

Temporary server processing required

Server tools explain temporary server processing before you start the upload.

When your files stay on your device

Supported local image and PDF tools process the file in your browser. Their source and result files are not uploaded to EditFileNow for that processing. Some image compression tools first try to work locally and may offer a separate server option when available. The tool explains that option before an upload.

When EditFileNow processes a file on its server

Tools such as Compress PDF, Word to PDF and PDF to JPG require server processing. Selecting a file can show a preview on your device; the upload starts when you choose the processing action. Server jobs use private storage and an access-controlled, time-limited download link. These safeguards reduce exposure, but no online service can promise absolute security.

Temporary files and remaining records

Server-job source and result files are temporary. The current default expiry is about 60 minutes from job creation, not 60 minutes after the result is ready. EditFileNow's scheduled cleanup is designed to remove those files after expiry; the actual removal time depends on that process running. A download stops being available after expiry even if cleanup is delayed. Some failed or cancelled jobs can have their files removed sooner.

Removing file content does not immediately remove every non-content job record. Records can retain the operation, file format and size, status, timing and error category. The application does not put your uploaded file content or filename into its analytics records. Retention of server backups and host-level logs depends on the production setup and is not confirmed here.

Usage measurement and cookies

Automatic anonymous aggregate measurement is disabled by default. When enabled after privacy review, it counts eligible public page views, processing starts and outcomes, browser-initiated downloads and server-served download authorizations. It does not confirm that a file was saved on your device. Aggregate records contain fixed page/tool identifiers and totals, never IP addresses, user agents, session or visitor identifiers, fingerprints, filenames, file contents or full URLs. Necessary security/session cookies continue to support the tools independently.

Deduplication records hold random single-operation tokens and temporary processing-job references, without creating visitor profiles. These operation-level records expire after 24 hours and are removed by scheduled maintenance. Daily aggregate totals are retained for 24 months, then combined into all-time totals. Maintenance timing depends on the scheduler running. These totals are not used for advertising or linked to consented visitor records.

You can object to aggregate measurement using the controls below when it is enabled. The preference uses a necessary, signed opt-out cookie as well as your existing browser session. It contains no visitor identifier and applies to new requests until you resume measurement or the cookie expires (up to one year). Do Not Track and Global Privacy Control requests also disable collection. Server operations already accepted can finish contributing anonymous outcomes.

EditFileNow's optional consent-based first-party usage measurement is off unless you allow it for this browser session. If allowed, it records page views, tool use, processing outcomes and download clicks. Records can include a page or tool identifier, exam category and general error category, but not the contents or names of your selected files.

When measurement is allowed, a first-party filefit_visitor cookie counts returning browsers for about one year. Its random identifier is stored as a keyed hash in the analytics database. Changing your choice clears the browser cookie and stops future optional measurement when off; it does not delete earlier database records. EditFileNow has not yet defined an automatic deletion period for those records.

The necessary EditFileNow session cookie supports security and features such as keeping server-processing jobs accessible only to your browser session and administrator sign-in. A separate CSRF cookie helps protect forms. The example idle session lifetime is 120 minutes and can differ by deployment. Browser-local file processing uses temporary browser memory, not an analytics or advertising cookie.

No advertising cookies or live ads are loaded now. A certified consent platform will be configured separately before future Google advertising is considered.

Privacy choices

Choose whether EditFileNow may use its own optional usage measurement in this browser session. This choice does not control file processing, and it is not an advertising consent dialog.

First-party analytics: Off

Anonymous aggregate measurement: On

You can return here from the footer at any time. If the session expires, analytics returns to off. Your files and downloads work either way.

Processing software and questions

The current application code does not send your file to an external file-conversion API. Some server tools use processing software installed on EditFileNow's server. We will review this notice if the way files are processed changes.

For a question about privacy, your files or a processing job, email support@editfilenow.com. Include the tool and approximate time if helpful, but please do not email a sensitive file unless it is needed to explain the issue.