Eigenexis Systems privacy

Privacy notice

Your documents don't need to leave your computer for everyday PDF editing. When Lambda PDF Basic shares technical data with us, you can see what is being shared. This notice covers this website and Lambda PDF Basic, and it keeps six kinds of data strictly apart.

01

At a glance

What this notice commits to

  • You should not have to upload personal, confidential, financial, legal, medical, engineering, or business documents to merge, split, edit, rearrange, annotate, compress, sign, or perform any other ordinary PDF operation. Lambda PDF Basic is designed to do this work on your computer.
  • Optional telemetry is off by default. Turning a category on is your choice, and turning it off deletes its queued, unsent events.
  • Required licensing data is minimal: a device ID, the device public key, a hashed hardware ID, the device name, and the application version.
  • Telemetry uses a resettable installation ID that is not your device ID or your account, so it cannot be joined to either by design.
  • A PDF is only ever sent through an explicit, cancellable, per-file submission flow. There is no other path that can attach a document.
  • This website sets no cookies, loads nothing from third-party origins, and does not process payments.
Current status

Lambda PDF Basic is not released. The application behaviour described here is the planned design that the product must meet before release. Accounts, purchasing, and licensing do not exist yet, and early-access registration is currently paused.

02

Categories

Six categories, never merged

Each category has its own purpose, its own trigger for leaving your device, and its own rules. Information from one category is not folded into another.

The six data categories used by this website and Lambda PDF Basic.
CategoryExamplesWhen it leaves your deviceRequired?
1. Website and account informationPages you request from this website; later, an Eigenexis account email, display name, passkey public keys, and sign-in sessions.When you use this website, and in future when you create or use an Eigenexis account.Needed only for an account. Accounts do not exist yet.
2. Purchase and licensing informationOrders from a payment processor, licences, and the device details needed to activate: device ID, device public key, hashed hardware ID, device name, and application version.At purchase, activation, licence refresh, and deactivation.Required for licensed use once purchasing opens. Nothing is collected today.
3. Application telemetryFeature-usage counts, coarse performance timings, and compatibility facts, under a resettable installation ID that is not linked to your account.Only if you turn on the matching optional category.Optional and off by default.
4. Crash and diagnostic informationCrash signatures, module versions, and sanitized logs in which file paths and names are replaced by hashes.Crash reports only if you enable them; diagnostic packages only when you review and send one.Optional.
5. User-submitted diagnostic documentsA specific PDF you choose to send, for example when support needs to reproduce a problem.Only through the explicit, cancellable, per-file submission flow.Never automatic.
6. Document contentsThe PDFs and other documents you open, edit, and save.Never, for everyday PDF operations.Not collected.
03

Category 1

Website and account information

Website. This website is delivered by Cloudflare. Cloudflare provides DNS, TLS, edge delivery, application runtime, and database services, and may process limited connection and security information to deliver and protect the site under its own service practices. Eigenexis Systems has not added advertising pixels, behavioural profiles, cross-site trackers, payment processing, or account cookies.

Accounts. Eigenexis accounts are planned, not available. When they open, an account will hold your email address, display name, passkey public keys, and active sessions, on dedicated account services separate from this website.

04

Category 2

Purchase and licensing information

Purchasing is not open, and this website does not take payment. When it opens, orders will come from a payment processor; card details will not be stored by Eigenexis Systems.

To activate and refresh a licence, the application will send only a device ID, the device public key, a hashed hardware ID, the device name, and the application version. No IP address, user-agent string, or document information will be stored with licensing records.

How activation and computers are planned to work

05

Category 3

Application telemetry

Every optional telemetry category is off by default, and each one can be turned on or off separately:

  • Stability: crash signatures and module versions
  • Performance: operation timings in coarse ranges
  • Compatibility: operating-system build, graphics vendor and model, display scaling, and a memory range
  • Product improvement: counts of the capabilities used in a session

Telemetry is sent under a random installation ID that you can reset and that is unrelated to your licence or account. Each event is limited to an allowlisted set of fields: file names, paths, document titles, and text content are rejected, and event times are truncated to the hour. Licence activation and update checks send only what those features need, and only while you use them.

06

Category 4

Crash and diagnostic information

Crash reports are sent only if you enable them. A diagnostic package is created only when you ask for one: it contains sanitized logs, in which paths and file names are replaced by salted hashes, and basic system facts. Before anything is sent, the application shows each item and states whether the package contains any document-derived information. Nothing leaves your device until you review and confirm it.

07

Category 5

User-submitted diagnostic documents

If support needs an actual PDF, the application first shows a summary: the file name, size, SHA-256 fingerprint, destination, purpose, and retention. You must confirm that exact summary; if the file or destination changes, the confirmation no longer applies. You can cancel until sending completes, and cancelling deletes any staged copy.

The telemetry and diagnostic features have no way to attach a file. This submission flow is the only path, so a document can never be sent implicitly.

08

Category 6

Document contents

Your documents don't need to leave your computer for everyday PDF editing. Opening, viewing, editing, merging, splitting, rearranging, annotating, compressing, signing, printing, and saving are designed to run locally and do not upload document contents. Eigenexis Systems does not collect the contents of your documents.

09

Transparency

The Privacy & Data Sharing page

When Lambda PDF Basic shares technical data with us, you can see what is being shared. The application is designed to include a Privacy & Data Sharing page that shows:

  • Every data category, its purpose, whether it is required or optional, and its current setting.
  • The exact next telemetry payload, generated by the same code that sends it, with its size and SHA-256 fingerprint.
  • Recently transmitted data: the last transmissions with their time, size, fingerprint, categories, and payload, kept on your device for 30 days.
  • For a diagnostic package, every included item and whether any of it is derived from a document.
10

This website

This website today

Current intake status
Early-access registration is currently paused. The production form does not accept or store real applicant information while its separate privacy and operations gate remains incomplete.
Information collected when intake is active
When registration is reopened, the form will record the name, professional email, organization, country or region, role or discipline, selected workflow, optional message, and consent choice that you provide. The server records the submission time, applicable consent-text version, and time consent was recorded.
How that information is used
Eigenexis Systems will use it to assess release fit, contact selected participants, communicate qualification milestones, and provide public-beta availability updates when you have consented. A future submission will not create an account, prove identity, provide product access, or create a commercial licence.
Network and browser privacy
When registration reopens, the application record will not include your IP address, browser fingerprint, forwarding headers, browser user-agent history, or payment information.
Cookies and display preference
No application cookie was observed across the qualified production pages, assets, API responses, errors, or redirects. The site stores the light or dark theme choice in your browser. It contains no personal information, is not linked to any request, and can be removed by clearing the site's browser data.
Storage and retention
When intake is active, accepted requests are stored in a private server-side database on Cloudflare. It is bound to the application, and the browser receives no database credentials or public record-reading interface. The application removes requests after one year and removes expired protection data on a deployed schedule. Scheduled expiry and controlled deletion procedures have been verified with non-personal test records. No applicant submissions are currently stored because registration is paused. Provider recovery copies may persist for a limited period under Cloudflare's service policies.
Consent banner
No generic consent banner is shown because Eigenexis has not enabled advertising, behavioural tracking, profiling, or other non-essential application storage.
11

Your choices

Requests and changes

A monitored privacy-request channel is not yet operational. Before real intake reopens or accounts launch, Eigenexis Systems must publish and test a privacy address and approve procedures for access, correction, consent withdrawal, and deletion requests. No new applicant information can be submitted through the production site in the interim. Do not send identity documents, sensitive personal records, or document contents through any website field.

This notice will be updated before accounts, purchasing, or the application launch, and the date at the top will change when it is.

How the website and planned licensing are secured