Effective and last updated: 24 October 2026

Privacy Policy

You can draft a survey locally without an account. Cloud sync, sharing, support uploads and browser push involve additional data handling. This policy explains those choices and how to request access, correction or deletion.

1. Who operates Traverse

Traverse at traverse.ng is operated by KLEVAR LTD, a Nigerian private company limited by shares, RC 8850017. KLEVAR LTD is responsible for account, service-operation and support data it determines how to use. When we host survey content on your instructions, we process that content to provide the service; you remain responsible for the lawful use of personal data about your clients, landowners and other people.

Registered address: Behind 7Steps, Edem Road, Ngwo, Enugu State, Nigeria.
Privacy requests: info@klevar.ai. Please mention Traverse.

2. Data on your device

Projects can contain coordinates, boundaries, survey observations, buildings and other measured features, client or landowner details, project notes, drawings and generated plans. Local work is stored in your browser or Windows application storage. Prepared files and projects can remain available offline. Your device may also hold preferences, recovery copies, notifications and sign-in state.

Local storage is not a server backup. Clearing browser data, changing devices or uninstalling the app can remove local work. Signing out does not delete your local projects. Export and protect recovery copies yourself, particularly on shared devices. Files you download or send to someone else are outside Traverse's control.

3. Accounts and Google sign-in

For an account we process your email address, account identifier, authentication/session records, workspace memberships and the profile information you provide. Email/password authentication is handled by our authentication provider. We do not receive your Google password.

If you choose Google sign-in, Google supplies the basic identity information you approve, including your Google account identifier, email, name and profile picture where supplied. We use it to authenticate you, associate your verified identity with the right account and maintain your session. The current sign-in permissions do not give Traverse access to Gmail messages, Google Drive files, contacts or calendars.

You can remove Traverse's connection in your Google Account connections. Removing that connection does not itself delete an existing Traverse account, cloud records or local files. Contact us to request their deletion. Older Traverse accounts may retain imported Firebase identity mappings and project records so verified users can recover their earlier work.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements where applicable. We do not sell Google account data or use it for advertising or general-purpose AI model training.

4. Optional connected features

5. Service information, storage and analytics

Our hosting and security providers process technical request information such as IP addresses, timestamps, browser/device details, error and security events, and service status. We use necessary records to deliver the service, prevent abuse, diagnose faults and protect accounts. Browser storage and authentication cookies or tokens support local projects, preferences, sessions and offline recovery.

Usage analytics. We record which screens and tools are used, such as opening a screen (including using the command search, where we record which command you chose and, when nothing matched, only how long the search was and the nearest topic, never the words you typed), creating a plan, importing coordinates or exporting a plan, together with simple counts such as the number of points imported. The same applies to subdivision and roads work (for example generating, keeping or rejecting a layout), layout outputs, paper settings, traverse adjustments, coordinate setup, signing in (which method was used and whether it succeeded, never your password), cloud sync outcomes, backup restores, install and update of the web app, desktop app updates and turning browser push on or off. We also record how quickly screens load and actions finish, both as a rating such as good or slow and as the exact time in milliseconds, and a size class for your screen (phone, tablet or desktop), your browser family and major version, and your operating system family; we do not record the full browser identifier or screen size. We record your approximate location as the country, region and city that our hosting provider derives from your network address when the app reports to our server; the network address itself is not stored. We use these details to count how many people use Traverse each day, how often their sessions run without errors, how far people get through common tasks such as creating, importing and exporting a plan, and how many come back in later weeks. Vercel Analytics measures page visits and basic browser information. We use this to understand which features matter, find where people get stuck, help you when something goes wrong and plan improvements. Screens are recorded as route templates without project identifiers. We remove URL query strings, fragments and project identifiers from page URLs.

Who the analytics belong to. When you are signed in, usage analytics and error reports are linked to your account, so that when you tell us something went wrong we can find your sessions and fix it for you. Each browser or device also carries a random installation identifier that links its sessions over time, even before you sign in or if you only work locally; it is not derived from your hardware and is reset if you clear the site's storage. A short support code made from that identifier is shown in Settings under Privacy & data; you can read it out to support so we can find the right device quickly. These identifiers are stored with the events in our database and are visible only to us.

What never enters analytics. Your project content is not analytics: coordinates, bearings and distances, parcel and client names, plan titles, uploaded files and drawings, exported documents and anything you type into a plan are never collected as analytics or error reports. Before anything is sent, and again on our server, we remove coordinates and other long numbers, email addresses, identifiers that appear inside messages, tokens and long quoted text.

Error reports. The website and desktop app send details of crashes and errors so we can find and fix them: the error type and message, the code location (stack trace), the screen route, the app version, the environment (for example the website or desktop app), the browser or app type, a random identifier for the current browser tab session and, as described above, your account when you are signed in and the device's installation identifier. An error report can also include the part of the app where it happened (for example saving or syncing), the names of the last few screens and actions in that tab with how many seconds earlier they happened, whether the device was online, whether the browser keeps Traverse's storage permanently and roughly how full that storage was (under half, half to 90% or over 90%). It never includes what you typed, imported or drew, and the same scrubbing applies as for usage analytics.

Service signals. To find problems that never become an error, the app also records small signals: when a request to our service was slow or timed out and whether it then succeeded, when cloud sync got stuck and when it recovered, interface friction such as pressing the same button repeatedly, undoing straight after an action, closing an import without finishing it or hitting the same validation message twice, warnings and errors that our own code writes to the browser console, and when your browser's storage for Traverse is nearly full. Our server keeps its own record of requests that failed on its side and a small sample of how long requests took: the route, the status, the timing and a random request identifier that lets us match a failure you saw to the request behind it. Signals carry screen and control names and counts; console messages are scrubbed the same way as error reports. None of this includes your project content: coordinates, parcel or client names, uploaded files and drawings never enter analytics.

Session recordings. To see exactly what went wrong, the app keeps a recording of how the page looked and changed: its layout, where you clicked and scrolled, which screens you moved between and how long things took. Before anything leaves your device, every text box is masked, the text inside plans, coordinate and label tables, project and group lists, Layout Studio, paper customisation, imports and dialogs is replaced with asterisks, and drawings, canvases, previews and images are blocked out entirely, so a recording never contains your project content. For everyone, the last minute or so is kept only in your browser's memory and sent to us when an error happens (with about ten seconds more), or when you send a problem report; we keep at most one recording per kind of error and five per session. Recordings are stored privately, linked to your account and device like other analytics, and deleted after 30 days.

Tester mode. If you agree to help us test Traverse, we can switch on tester mode for your account. While it is on, your whole session is recorded in the same masked way rather than only the minute before an error, the trail sent with error reports is longer and names the settings an action used (never their values), and slower responses are reported. Settings under Privacy & data tells you when tester mode is on, and you can ask us to switch it off at any time.

Problem reports. "Report a problem" in Settings under Help & support, or on the Help page, sends us what you write, your support code, the last steps you took in the app (their names only), the page you were on, the app version and your device type, and, unless you have turned recordings off, the masked recording of the last minute. You can choose to add a screenshot; it is masked the same way as recordings before it is sent. Please do not include coordinates, client details or other plan content in what you write; long numbers such as coordinates are removed from reports anyway.

Your right to object. Usage analytics, session recordings and error reports are on by default because we rely on our legitimate interest in keeping Traverse working and improving it (see section 6). You can turn usage analytics and recordings, or error reports, off at any time, without losing any features or local drafting: use change your analytics choice, or, in the app, choose Settings → Privacy & data → Usage and error reporting. Your choice is remembered in that browser's local storage. If your browser sends a Global Privacy Control signal, we treat it as an objection to both. Turning them off stops further events; it does not erase events or aggregate statistics already received. Browser push has its own consent choice. These legal pages do not load analytics or advertising scripts.

6. Why we process data

We process account, project and session data as needed to provide the service you request and perform our agreement with you. We rely on our legitimate interests in operating, securing, fixing and improving Traverse for usage analytics, masked session recordings and error reports; when you are signed in these are linked to your account and to your device's installation identifier so we can help you, they never include your project content, and you can object to them at any time as described in section 5. Tester mode is switched on only with your agreement. We process problem reports you send to answer them and fix the problem. We rely on your specific consent for support content where consent is requested and for browser push; you can withdraw that consent without losing local drafting. We use necessary, proportionate security and abuse-prevention records for our legitimate interests in protecting the service and its users, and retain records where a legal obligation requires it. A user's authorization to upload client data does not replace that user's own lawful basis for handling it.

7. Providers, disclosure and international processing

We use Supabase for authentication, hosted database and file storage; Vercel for website/API hosting and delivery; Google for the sign-in you choose; and Resend for service email. Browser push uses your browser's push-service provider. Usage events and error reports are stored in our Supabase database. Sentry may process redacted diagnostics only when that feature and its relevant consent are enabled. These providers process data for their service functions and under their applicable terms and data-protection arrangements.

The current hosted database is in Paris, France. Hosting networks, identity, email and other providers may process information in additional countries. We do not promise that all data stays in Nigeria or Europe. Current provider terms include data-processing and security obligations; applicable international-transfer arrangements can include contractual safeguards and Standard Contractual Clauses. Their scope depends on the provider and transfer. Contact us for information about the safeguards relevant to your data.

We do not sell survey content or account data. We disclose content to recipients you authorize and to service providers as needed to operate Traverse. We may also disclose information where legally required, to protect rights and security, or as part of a lawful business transfer subject to appropriate confidentiality and notice.

8. Retention and deletion

Local data remains until you remove it or your device/browser removes it. We retain cloud account and project records while needed to provide your requested service, recover operations and protect account ownership. Support and operational records are retained only as needed to resolve the request, investigate security events or meet applicable legal duties. We review retained records against those purposes rather than promising an unimplemented automatic deletion period. Error reports are deleted automatically after about 90 days, session recordings after 30 days and usage events after about 13 months. Problem reports you send are kept while we work on them and as a support record.

Request cloud account or project deletion by emailing the privacy contact from your verified account address. We may ask for proportionate proof of ownership and clarify the scope to avoid deleting another person's work. Deletion requests are subject to applicable legal obligations and other people's rights. Deleted information may remain temporarily in protected recovery backups until those backups rotate out; it is not used for ordinary service access. Independent recipient copies and files on devices are not erased by a cloud deletion request.

9. Security and your rights

We use encrypted network connections, authentication, tenant-scoped server access controls and protected operational backups. No system is completely secure. Protect your device, account credentials, sharing links and exported files, and tell us promptly about suspected unauthorized access.

Subject to applicable law, you can request access, correction, erasure, restriction, a portable copy, or object to processing, and withdraw consent where processing relies on it. Email info@klevar.ai and identify the account and request without sending your password. We will verify requests proportionately and respond within applicable legal time limits. You may complain to the Nigeria Data Protection Commission or another competent data-protection authority.

10. Children and policy changes

Traverse is intended for adult professional and educational survey work, not for children under 18. Do not submit a child's personal information without a lawful basis and the protections required by applicable law. Contact us if you believe a child has provided account information.

We will publish changes here with an updated date and provide additional notice for material changes where required. A future new purpose or optional tracking feature needs its own appropriate legal basis and notice.