PUBLIC DOCUMENT DIRECTORY
Compliance, Privacy & Security
Sphinixx is still in testing. These documents show current policies, engineering controls, assessments and evidence boundaries. They are not certifications, regulator approvals, legal advice, or proof that every requirement has been satisfied. Closing the remaining compliance gaps and obtaining appropriate independent/legal review is part of the next phase.
Privacy & product policy
Security & assurance evidence
Website analytics and your choices
Sphinixx operates this website. Contact info@sphinixx.co.uk about privacy, access, erasure, objections or other data rights. You can also complain to the UK Information Commissioner's Office.
Optional Sphinixx usage statistics help us understand pages, referrals, gallery/tutorial use, shop interest, contact actions, technical health and installer interest. Collection starts only after you choose it in Analytics preferences. Consent is the basis for this optional processing and device storage. Rejecting does not affect access or downloads. Use the preferences button on every page to withdraw consent or exclude this browser. Global Privacy Control and Do Not Track signals block analytics.
The first-party collector receives fixed page categories, approved campaign tags, installer/version identifiers, coarse load-time buckets and counts of actions or errors. It does not receive arbitrary query strings, full referrer URLs, email addresses, message contents, stack traces, precise location or recorded browsing behaviour. Network addresses and user-agent headers are necessarily handled during delivery; our analytics datastore does not retain their raw values. A rotating network HMAC used solely for abuse limits expires within 24 hours. The hosting provider may separately maintain access/security logs; those are not connected to this dashboard and their account-level retention requires verification.
After consent, a random tab identifier in session storage groups activity until 30 minutes of inactivity. We store its one-way hash with events; it is not a persistent person or cross-device identifier. A later session in a previously active tab can be labelled returning tab activity. Preferences are stored locally for up to 180 days; owner exclusion lasts until you reverse it. There is no fingerprinting, session replay, keystroke capture or first-party analytics cookie. Opening a new tab or clearing storage may create a different session.
Event records have a 180-day retention window in a private server datastore outside the public website, with access restricted to authorised operators. Deletion runs on the next daily maintenance pass or first access on a new UTC day; without a scheduled task, deletion may be delayed while the service is idle; encrypted private backups must expire within 30 days. No raw analytics record is published. Exported dashboard reports contain aggregates. Historic unidentified owner traffic cannot be reliably removed from hosting statistics. Installer clicks measure intent and do not prove transfer completion or installation.
Google Analytics is disabled until configured by the owner. If enabled, a separate unchecked Google Analytics choice appears before any Google tag is loaded. Choosing it permits Google to process usage statistics and analytics cookies, including network/device information necessary for its service; Google processing may involve international transfers. Our manual events use fixed categories and sanitised page locations. Advertising features, Google signals and automatic enhanced measurement must remain off. Google event retention must be set to two months, with activity-based retention reset disabled. Review Google's privacy information. Withdrawing the Google choice disables collection, clears accessible Google Analytics cookies and reloads the page to remove the tag.
These are engineering controls and disclosures, not legal certification. The owner must confirm hosting location, processor terms, access-log retention, backup deletion, the applicable lawful basis and Google transfer arrangements before enabling the relevant services. Read the measurement and privacy evidence.
Reading these documents
Some evidence is an engineering snapshot and can become stale as the product changes. A document describing a control does not by itself prove that the deployed service satisfies a legal requirement. Where a document records a gap, partial implementation or future action, that limitation is intentional and should remain visible until the underlying work is complete.