How SurveyMarkup handles information.
SurveyMarkup is operated by Tim Albash, sole trader, ABN 50 427 523 590.SurveyMarkup is an Australian survey-assistance product and is responsible for personal information handled through this site. For the operator's legal identity or any privacy question, contact admin@surveymarkup.com.au.
The current public beta uses fictional examples only. Real customer-file intake is disabled at the browser and server boundaries. Contact details are handled only when you choose to prepare and send an email, while demonstration state may be stored locally in your browser where applicable.
We may receive information you choose to send in a workflow-interview email, account access request or support message. Do not attach, paste or send a client file during the synthetic public beta.
If you send an enquiry through the services enquiry form, we collect the name, work email, firm (optional) and message you provide. We store these details to respond to your enquiry and to confirm the scope of any review by email — not for marketing. The five named UTM campaign tags may also be stored with the enquiry so we can understand which outreach link produced it. Advertising identifiers and unknown query parameters are ignored. You can ask us to delete your enquiry details at any time by emailing admin@surveymarkup.com.au.
The Map Linework may use browser storage such as IndexedDB to save workspaces, settings or export history locally.
Real customer-file intake is disabled during the synthetic public beta. Public demonstrations use bundled fictional content and do not need a client file.
The site and account services run on SurveyMarkup's configured German hosting. Browser-local demonstration data, such as Map Linework workspace state, stays on your device until you clear it. The dormant S3-compatible upload/object-storage path is not available in the synthetic public beta and must be documented again before real-file use is enabled.
Map Linework loads CARTO and OpenStreetMap map resources directly in your browser by default. If you select Esri satellite imagery, your browser connects directly to Esri. Those providers receive standard network data such as your IP address plus viewport, zoom and tile requests; they do not receive customer-file content or drawn feature attributes from SurveyMarkup. Optional Google map/search paths remain separately configured. AI features are off and provider credentials are empty for the synthetic public beta, so no customer or project context is sent to Anthropic, OpenAI, Moonshot/Kimi or another AI endpoint. These providers remain listed as dormant code-supported paths and would require an updated disclosure before activation.
No public payment, support-payment or subscription offer is active in the synthetic public beta. Stripe remains an inactive, code-supported processor and receives no checkout data from this public workflow. This policy and the public offer must be updated before any payment path is activated.
SurveyMarkup uses session cookies where required for access. Usage analytics are first-party, cookieless and pseudonymous: our server records individual allowlisted event names, a public route identifier, allowlisted coarse properties, a random per-tab session identifier and the server timestamp. It does not accept raw or private paths, query strings, account identifiers, email addresses, file names, file contents or coordinates. No analytics data is shared with a third-party analytics processor, and no advertising trackers are active during public beta.
Sentry error diagnostics are used only when a deployment has a configured Sentry project. Error reports contain technical context only — browser or server details, app version, and a stack trace — and are scrubbed of file names, file contents, and survey data before they are sent. They never include your uploaded files. Hosting and residency follow the selected Sentry project and must be confirmed for the active deployment; no EU-residency promise is implied by the code alone.
A configured SMTP provider receives the recipient address, name and transactional message needed for account, pilot, enquiry or payment notices. Optional Google or Microsoft OAuth sign-in sends the standard authorisation request and receives the email identity needed to match an invited account; it never creates an uninvited account. Optional Twilio Verify receives the phone number and delivery metadata needed for SMS account authentication. Each provider's terms and processing region apply only when that feature is enabled.
You can request access to, or correction of, the personal information we hold about you, and you can ask us to delete it. To exercise these rights or raise a concern, contact admin@surveymarkup.com.au. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC).
Do not email, attach, paste or attempt to submit a client file during the synthetic public beta. Use the fictional worked example and bundled demonstrations only.
Real customer-file intake is disabled during the synthetic public beta. We retain account data and any previously stored account material while the account is active, or until you ask us to delete it. Any previously stored account material is not automatically deleted at the end of a session. To request access, correction or deletion, email admin@surveymarkup.com.au. Browser-local data (IndexedDB) stays on your device and can be cleared by you at any time. We do not promise immediate or automatic deletion, and deletion requests may be subject to legal, security or accounting requirements.
SurveyMarkup uses self-hosted fonts (Space Grotesk, IBM Plex) and open-source libraries disclosed in the Third-party notices page. No third-party analytics or advertising trackers are active during public beta.
For privacy questions, contact admin@surveymarkup.com.au.