Privacy and account data

Account and activation data

SigmoNet stores the email address, activation and plan information needed to authenticate an account, enforce project limits, process upgrades and protect the service. Authentication cookies are Secure, HttpOnly, SameSite=Strict and host-only for sigmonet.com.

Engineering projects

The Private Local Project Library is stored encrypted in the browser. Where a SigmoNet workflow explicitly uploads project or collaboration data to the service, access is limited to the authorized account/project workflow and protected in transit. Local-only project and survey workflows are not silently uploaded.

SigmoNet Mobile

SigmoNet Mobile uses the account email and PIN to authenticate with sigmonet.com. The authenticated session, imported project data and collected survey measurements are stored in app-private encrypted local storage. The mobile app may read nearby Wi-Fi scan information such as SSID, BSSID, RSSI, frequency, channel, channel width and capability information for WLAN engineering and site-survey purposes.

Android protects Wi-Fi scan-result APIs with Nearby devices and location-related permissions. SigmoNet Mobile does not use GPS coordinates for floor-plan placement in the current mobile release; the engineer manually selects the measurement position on the floor plan. The app does not request background location.

Survey notes and selected photos are optional and are kept with the encrypted local survey data/export unless the user explicitly transfers that survey through another SigmoNet workflow. When the user explicitly runs an active network test, the app exchanges test traffic with SigmoNet endpoints to measure latency, packet loss and short upload/download throughput.

Cookies and browser storage

SigmoNet separates essential storage from optional Preferences, Analytics and Marketing categories. Optional categories are off until you choose them. The consent choice itself is stored in a first-party cookie so the site can remember your decision.

Signed-in users may also have a limited server-side consent history containing the policy version, selected categories, source and timestamp. Anonymous visitors are not assigned a persistent server-side identifier just to build a consent ledger.

See the Cookies & Browser Storage policy for the current inventory and use Cookie settings to change optional choices.

Support and email

Information submitted through support or activation forms is used to handle the request, deliver security messages and maintain an audit history. Runtime data and mail credentials remain outside the public document root and are never deployed from Git.

Retention, deletion and your rights

Where GDPR applies, you may request access, correction, deletion, restriction, objection or portability as applicable. Account-deletion requests can be initiated at sigmonet.com/account-deletion. SigmoNet may verify account ownership before destructive action is taken and may retain limited records only where required for security, fraud prevention, legal, accounting or other legitimate compliance purposes.

For other privacy questions, contact privacy@sigmonet.com or use SigmoNet Support.