Plasmid Map
Tools

A WORKSPACE FOR THE BENCH

Your files, on your device.

Your sequences stay in your browser.

Sequence processing

Plasmid Map reads files that you choose and processes their contents in your browser. The application does not upload sequences, filenames, annotations, chromatograms or projects to an analysis server. Sequence contents are not placed in URLs. The example file is a public sequence fetched from this site's static assets.

Local storage and downloads

The workspace saves its current project in IndexedDB when browser storage is available. This includes the editable sequence data and the original imported files. Editor preferences may also be stored in local storage. These records belong to this browser profile and domain; another person using the same profile may be able to reopen them. Clearing this site's browser data removes the local recovery copy. Private browsing, storage limits or browser cleanup can also remove it.

Downloaded .pmap projects contain unencrypted sequence data and imported originals. GenBank, FASTA, comparison reports and original-file downloads remain on your device until you remove them. Read comparisons run in a local browser worker; their reports are not added to the saved project automatically. The application has no account system or cloud backup. Save a project file somewhere appropriate for your data before clearing browser storage.

Website delivery

Cloudflare receives ordinary connection information, including request paths, browser headers and IP addresses, to deliver and protect the website. Application scripts, fonts and editor dependencies are served from this domain. The site does not load advertising. Page analytics is described below. External source and documentation links lead to websites with their own policies.

Anonymous diagnostics and tool counts

We use Cloudflare Analytics Engine to count public-page visits, tool loading, successful lookups or calculations, rejected inputs, and export requests or failures. Each tool outcome is counted at most once per page visit. We also record page-speed measurements and fixed error categories to find broken controls. These records contain the public page path, country, device category, whether the request appears automated, and application build version. Page-visit counts also note the domain of the website that linked to the page (if your browser shares one) and a broad source category taken from it or the link's campaign source tag, such as a named search engine or AI assistant. For the slowest response on a page, speed measurements note how the delay divided between waiting, running and redrawing, whether it followed a tap, click or key press, and the broad kind of control involved, such as a button or link. In browsers that report it, they also note whose script ran longest during that response (this site's, a browser extension's or another site's), how it was started, and how the time divided between scripts, page layout and drawing, never the script's address or name. For page loading, they also note how the wait divided between connecting, the server's reply and fetching and drawing the largest image or text, whether that was text or an image, when the largest layout movement happened, and whether the page was opened fresh, reloaded, returned to or loaded in advance. They use no visitor identifier or tracking cookie.

We do not send sequence text, file contents or names, input values, calculation results, clipboard contents, error messages or stack traces with these events. Export counts record a request or completed clipboard operation, not proof that a file was saved. Automated tests are excluded from ordinary reports.

The embedded sequence-editing workspace is excluded from these page and browser-event counts. Its sequence editing, imports, project saves and exports remain untracked.

Hosting diagnostics

Cloudflare keeps sampled request and error logs for up to seven days to help diagnose server failures. These hosting logs can include requested page paths (query strings are removed) and ordinary request metadata. They are separate from the anonymous tool counts described above; application inputs are not added to them.

Google Analytics

We use Google Analytics 4 to understand page visits and whether a visit used a tool: the first calculation result on a page sends it one fixed tool_used event with the page path, never what you entered or the result. It may set first-party _ga cookies to recognize repeat visits. Google receives the page path, page title, limited campaign tags, the referrer's origin, and ordinary browser and connection information, including your IP address and the approximate location our hosting provider works out from it (country, region, city and approximate coordinates). Our server passes that location on because these requests reach Google through this website. Automatic enhanced measurement and advertising features are disabled. We do not send tool inputs, file names, sequences, calculations or simulated scene settings to Google Analytics. Event-level data is retained for 14 months; aggregate reports may remain available longer. See Google's Privacy Policy.

Google Analytics does not load for visitors in the EEA, UK, Switzerland or Quebec, when location is unknown, or when the browser sends Global Privacy Control. Automated and synthetic test traffic is excluded. You can remove analytics cookies through your browser's site-data controls.

The embedded sequence-editing workspace does not load Google Analytics. Public reference and calculator pages use the page-view settings described above.

Email

If you email us, your address and message are used only to reply.

Contact: hello@plasmidmap.com.

Last updated September 29, 2026.