ARKQON
Tracking policy
What activity signals mean, which browser identifiers are used and what they cannot prove.
Version 2026-11-11.1On this page
Who you are dealing with
ARKQON
ABN 42 839 638 864
Legal and privacy: legal@arkqon.com
General enquiries: hello@arkqon.com
Customer link activity
Public document, portal and business-card features can record visits and actions for the relevant business. Depending on the feature, this can include a link visit, a contact-button click or a PDF or print request. These records describe detected actions, not a count of verified people.
Optional customer-link measurement starts only after you choose Allow optional tracking. Decline optional tracking leaves it off. Your choice applies to ARKQON customer links on the website where you make it, in that browser, for 90 days. A different browser or website can require its own choice. Use Change privacy choice on the customer-link page to withdraw permission. This stops new optional events and queued retries; a request already sent may already have been recorded.
You can still read, download, enquire, sign and pay without allowing optional measurement. Security, access checks and records of actions you request remain necessary for those functions. Sending an enquiry records the details you submit for that business, independently of optional browsing identifiers. Declining tracking does not undo a signature, payment or enquiry.
A shared or forwarded link does not identify the person using it. Security scanners, browser privacy features and network failures can affect recorded activity. An open does not establish that prices were read, a click does not establish a completed call, and a PDF request does not establish a completed save.
Browser identifiers
Public engagement features use a random first-party browser identifier with a 90-day validity period. They also use a per-link session identifier with a 30-minute validity period. These values help group related activity. They are not a verified identity and should not be described as anonymous merely because they do not contain a name.
These optional values are read or created only after acceptance and are stored in browser local storage or session storage. Optional measurement stays off if the choice cannot be saved or read. Withdrawal removes the optional identifiers where browser storage is accessible and stops new optional measurement. It does not erase already recorded server activity. After clearing site data, optional measurement waits for a new choice; necessary requested actions and security records can still be recorded.
An enquiry uses a separate random request identifier to reconcile retries without linking it to optional browsing activity. Its pending receipt can remain in session storage until the enquiry is confirmed. If that storage is blocked, the receipt can remain in page memory so a retry during the same page visit still works. This necessary request receipt is not an alternative tracking identifier.
Optional page and control activity
ARKQON offers optional product activity recording to understand which pages and controls people use. If you allow it, we record a safe page category, an approved action name, the selected control's position where available, a safe destination category, a general referring-site category, the input type, a browser timestamp and a server receipt timestamp. We do not record what you type, message contents, customer photos, passwords, login codes, payment details, or private link tokens through this feature.
In the signed-in app, these observations are associated with your authenticated account and current workspace. The workspace owner and authorised ARKQON administrators can review that workspace's observations. Website observations are anonymous and are available only to authorised ARKQON administrators. We do not treat an account, forwarded link or referrer as proof of the physical person using a device. A recorded click is not proof that a business action completed.
This recording is off by default. You can allow or decline it in Activity Privacy on the website or Privacy and Support in the app. Your choice lasts 90 days in that browser and is separate for the website and each app account/workspace. Declining does not stop your work. Necessary security records, saved-work history and existing customer-link tracking retain their separate purposes and controls. Changing this choice stops future optional collection; it does not rewrite previous receipts.
Optional activity is visible in its report for 30 days. Daily maintenance removes expired observations in bounded batches. If maintenance fails or is backlogged, removal may take longer; expired observations are not shown in the report. Security controls limit request and storage volume. The service may therefore have incomplete observations, and these records must not be treated as a complete attendance record, exact traffic count or proof of a person's actions.
Sign-in, preferences and protection
The signed-in service also uses session cookies and browser storage for features such as preferences and draft recovery. Restricting storage can affect those features. Security checks and rate limits help protect forms and sign-in; hashing a technical identifier does not by itself make it anonymous.
Browser controls can clear or block stored values. This may sign you out, remove a local draft or reset a preference. Identifier validity periods do not guarantee that the browser physically removes an expired value at that instant. Server logs and previously recorded activity are separate from browser storage.
Push notifications require the relevant browser or device permission and a registered subscription. Permission on a phone does not imply permission on a computer. A service update cannot override a browser's refusal. Review both ARKQON preferences and device settings when changing notification choices.
Browser storage used by the service
Sign-in and access flows use short-lived verification state. Account sign-in challenges last 10 minutes, registration challenges 15 minutes and customer-portal challenges 10 minutes. Customer-portal sessions last 8 hours, or 7 days if the user chooses that option. Connected-provider sign-in correlation lasts 10 minutes and is cleared on callback. These are validity periods, not a claim that all provider logs expire at the same time.
The active-workspace cookie can last 365 days; an owner support-view cookie lasts for the browser session. These select a view, not permission to access a workspace. Authentication and authorisation are checked separately. Sign-in cookies can be renewed or removed through the authentication service and browser session controls.
Theme, homepage motion, notification-reminder choices, field-project selection and basket state can be kept in local browser storage without a fixed expiry. Document draft recovery uses a 14-day validity period. Quote handoff state lasts 15 minutes and plan draft recovery uses a 30-day validity period. An expired draft may remain physically stored until replaced or removed.
Pending-action identifiers can remain in session or local storage to check whether an interrupted correction, invitation, account link, feedback or order completed. They help prevent duplicate submissions. Removing them before reconciling an uncertain action can remove local recovery context without reversing the server action.
Offline field features can store site packs, drawings, unsent changes and attachments in the browser's IndexedDB database. The service worker can cache the field interface. The model viewer can cache up to two model files of up to 80 MiB each, without a fixed expiry. These stores can contain business records and file contents, not just technical identifiers.
Use a trusted device for sensitive work. Signing out should not be treated as confirmation that every local copy has been erased. Browser site-data controls can remove stored copies, but may also discard unsent work, saved drafts and offline files and require a new sign-in. Reconcile pending work and preserve required records before clearing it. This does not delete server records or another recipient's copies.
Referral and demo evidence
A link marked as coming from an ARKQON showcase can attribute activity to that shared link. The marker can travel with the link and is not proof of a visitor's identity or original browsing history.
Customer notifications, signatures and document activity shown in the public sample demo are simulations. No demo email or signature is sent to a real customer. They are not customer engagement evidence.
Questions about recorded activity
Use the application's notification and device controls for available preferences. Use Settings > Privacy and support for an access, correction or privacy request concerning activity associated with you. For a customer document or business card, identify the business and interaction without posting the full private link. In-app support can handle a browser or notification fault. If you cannot use these controls, contact legal@arkqon.com for privacy or support@arkqon.com for a fault. Suspected misuse can be reported directly to security@arkqon.com without needing to sign in.
This notice describes activity evidence; it is not consent to every possible tracking technology. Optional analytics or new purposes require a separate assessment and any required notice or choice. We will update the inventory and version when the actual technologies or purposes change. The Privacy policy explains complaint handling.
