Information
Privacy
Preview information · 16 October 2026
This page describes the current PlotProof public preview. PlotProof is a data-preparation project for teams that work with supplier plot files.
Files checked with the free validator
The no-login checker accepts GeoJSON (.geojson), JSON (.json) containing a GeoJSON FeatureCollection, Feature or geometry, and CSV (.csv) with plot_id, longitude and latitude columns, up to 25 MiB. It reads a selected file in this browser tab and does not send its contents to the validator API or save them in PlotProof's app database. The result and parsed contents remain in the open page while the result is displayed; reset the checker or close the tab to clear that page state. The included synthetic fixture is fetched from this site. A cleaned export is prepared in the browser only after review and explicit confirmation, as a separate file; the original file is not changed.
Optional first-party usage measurement
The consent prompt asks whether PlotProof may record public page loads, supported-file check starts and completions, synthetic demo starts and completions, cleaned-file download actions, and successfully saved enquiries. A file check completes when the browser validator returns a result. A demo completes when the included synthetic sample returns a result. A download count means PlotProof generated the cleaned file and triggered the browser download; it does not confirm that the browser saved it. An enquiry count is written only after its database save succeeds and only when optional measurement consent is also present. Email-link clicks are not counted as enquiries.
For page, check, demo and download actions, the first-party event request contains only the event category and consent flag. For an enquiry, the contact request separately sends the form fields needed to save and answer it; after a successful save, the server adds an event row containing only the category and timestamp. The event store does not contain file contents, filenames, coordinates, enquiry fields, IP addresses or a stable visitor identifier. Request headers are not copied into event rows. Events are counted individually: page loads are not unique people, and events are not linked into individual journeys. This event stream is stored in PlotProof's app database, not sent to a paid analytics vendor. Existing platform analytics integrations, if enabled separately by the owner, are not the source of these dashboard counts and need their own configuration and privacy review.
Measurement is optional and opt-in. Until you choose Allow, or if you choose Decline, no funnel events are sent from this browser. Declining does not limit the free checker. The choice is stored in this browser's local storage without a visitor identifier. Clear this site's local storage to see the prompt again. The app removes event rows older than 90 days during a later event write; if no later event is recorded, cleanup is deferred until one occurs.
Early-access and demo enquiries
The enquiry form asks for your name, email address, company or organisation, team type (importer, consultant, supplier team or other), and whether you want to ask about early access or a product demo. It also records that you checked the consent box. The form does not ask for plot files or payment details. These details are used to review and reply to the request; submitting the form does not subscribe you to marketing emails.
After you submit, PlotProof saves the name, email and a message containing the company, team type, request type and consent result in the app database with a server-created timestamp. The app then attempts to record the enquiry in the PlotProof team dashboard. If that capture does not record it, the app attempts to send a notification to the company inbox at plotproof-3@polsia.app. These notification paths are best-effort; a successful form response means the database record was saved, not that a person has replied. If neither notification path can be confirmed, the form asks you to contact the company inbox directly.
No enquiry retention period or self-service deletion workflow is currently specified in this preview. For a privacy question or a request about enquiry information, write to plotproof-3@polsia.app.
Email contact
You can also contact PlotProof directly at plotproof-3@polsia.app. An email-link click does not create an app database enquiry record; information in a direct email follows that email path instead.
Founder dashboard setup
The private event dashboard is available only when Polsia supplies the configured company-owner email for the deployment and that owner creates and verifies an account. Better Auth sends an account-verification email through the configured email proxy; this account setup message is separate from funnel measurement. The event API itself sends no email or other outbound message. If owner configuration, the database or event API is unavailable, the dashboard reports the data as unavailable rather than showing invented values.
Website operations
The website runs on the Polsia platform. The platform may process technical connection information in its infrastructure logs to provide and protect the service. The PlotProof funnel-event handler does not read or store IP addresses, but this does not describe separate platform logs.
Requests and questions
For a privacy question or a request relating to information you emailed us, write to plotproof-3@polsia.app. Please do not attach supplier plot files unless email is an appropriate channel for that file.
Changes
Update this information if PlotProof changes its analytics consent, event fields, retention, account setup, supplier-file handling or other data processing.