Security and data handling
Your survey files deserve clear handling rules. SurveyMarkup explains where browser-local work may apply, where account/server workflows apply, and what the product does not claim.
Clear scope
Local where applicable. Server/account where required.
Different tools have different handling paths. The important rule is to avoid blanket claims that are not true for every feature.
Browser-local where applicable
Some workspace preferences or tool state may be handled in the browser for features that are built that way. Users should export important work before clearing browser data or changing devices.
Server/account workflows
Uploads, reports, account access, admin functions, audit records, PDF handling, and AI-assisted review should be treated as server/account workflows unless the exact feature states otherwise.
Data handling during public beta
- SurveyMarkup is in public beta. Please do not upload confidential or real client data — use the synthetic sample files instead.
- Report Reader parses .rpt / .txt in your browser; your original file is read locally and is never modified.
- PDF upload and any account-based processing are pilot / demo workflows; treat them as server/account workflows where a feature enables them.
- Map workspace state, settings, and export history may be stored locally in your browser (for example IndexedDB) where applicable.
- Every result is advisory and unverified — not for survey deliverables. A registered surveyor must confirm any finding before it is relied on.
- No ISO, SOC 2, or equivalent certification should be assumed unless it is explicitly published.
What SurveyMarkup does and does not do
Trust starts with precise scope, not padlock marketing.
What it does
- Organises review workflows around findings, evidence, and next actions.
- Keeps evidence visible so users can trace a note back to its source context.
- Helps prepare internal review notes for reports, PDFs, and exported linework.
- Keeps qualified survey judgement central to the workflow.
What it does not do
- Certify legal boundaries, cadastral compliance, or coordinate correctness.
- Replace qualified survey review or source-data checking.
- Make legal guarantees about output suitability.
- Claim that every feature keeps every file local when a server/account workflow is involved.
Compliance and security honesty
These statements should stay conservative until certifications, policies, or controls are formally verified.
No ISO, SOC 2, or equivalent certification should be assumed unless it is explicitly verified and published.
No absolute security claim is made; security depends on product controls, user practices, and deployment context.
No legal or cadastral guarantee is made for survey conclusions or exported files.
No blanket all-files-stay-local claim is made across account, upload, PDF, report, admin, audit, or AI workflows.
Third-party tools and subprocessors
Tools and services used to run SurveyMarkup during the public beta — listed so handling stays transparent.
| Tool / Service | Purpose | Data handled | Location |
|---|---|---|---|
| STRATO VPS | Hosting for the website, application services, and database (Germany-based provider) | Site traffic, account/session data, pilot/demo test uploads | Germany (EU) |
| Self-hosted fonts | Typography (Space Grotesk, IBM Plex) — no external font CDN | None — font files served from our own domain | Same origin |
| First-party analytics | Anonymised usage events — no third-party analytics processor | Page paths and anonymous session ids; no PII, no file names | Our server (same VPS) |
| PostgreSQL (self-hosted) | Application database | Account and pilot request metadata | Our VPS (Germany) |
| Redis (self-hosted) | Session and cache store | Session tokens and ephemeral data | Our VPS (Germany) |
| Sentry (EU region) | Error diagnostics — scrubbed of file names, file contents, and survey data; active once error tracking is enabled for the deployment | Technical error context only — browser/server details, app version, stack trace; never your uploaded files | EU (Sentry EU data residency) |
| Stripe | Optional one-off pilot support payments — entered on Stripe-hosted pages only; card details never touch our servers. There is no subscription billing and no plan checkout during the invite-only pilot | Payment status, amount/currency and a truncated Stripe reference — never card numbers or card security codes | Stripe (global payment provider) |
| Moonshot AI (Kimi) | AI explanations and summaries — when used, the relevant QA findings or report text are processed under Moonshot's terms on servers outside Australia; the optional standards assistant sends only a typed question plus public standards text | QA findings or report text you ask to be explained; for the standards assistant, only the typed question and public-standards excerpts | Moonshot AI (servers outside Australia, incl. China) |
| Google Maps Platform (optional) | Map tiles for the Map Linework basemap — no file contents | Standard map-view parameters needed to fetch tiles, and your IP address as part of the tile request — no survey file contents | Google Maps Platform |
No third-party analytics, advertising, or visitor-tracking services are active during public beta; error diagnostics (the Sentry row above) carries scrubbed technical error reports only — never your uploaded files. Payments (the Stripe row above) are optional one-off pilot support payments on Stripe-hosted pages: we keep a minimal payment record, never card numbers, and there is no subscription billing or plan checkout during the invite-only pilot. The AI row covers the AI explanation features — when you use them, the relevant QA findings or report text go to Moonshot AI (Kimi) as disclosed in the Privacy Policy; the optional standards assistant sends only a typed question plus public standards text. The basemap receives only the parameters needed to fetch map tiles. Any pilot/demo upload should use synthetic or cleared test files. Full open-source attributions are available on the Third-party notices page.
Safety & scope
SurveyMarkup does not certify survey accuracy, cadastral compliance, legal boundaries, or coordinate correctness. It helps prepare and review working information, but original data and final outputs must be checked by a qualified user before use.
Assistance only - professional review remains required.