Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

PointSav Digital Systems

Data sovereignty and zero-state telemetry

← All revisions

f8f2bb7c · PointSav Digital Systems ·

Correction: security/data-sovereignty-telemetry.md — real telemetry daemon stores unmasked IPs, contradicting the published GDPR/PIPEDA masking claim (EN+ES)

View the full record as of this revision →

@@ -9,11 +9,30 @@ audience: vendor-public
bcsc_class: current-fact
language: en
paired_with: data-sovereignty-telemetry.es.md
last_edited: 2026-05-25
last_edited: 2026-07-30
category: security
---


**Major correction (2026-07-30) — active compliance-relevant discrepancy, not just an
architecture description gap:** this article makes a public GDPR/PIPEDA compliance
claim — that IP masking is "applied at receipt," dropping the final octet before any
record is written, so "the platform never holds the full address." The real ingestion
code contradicts this directly. `app-mediakit-telemetry/src/bin/telemetry-daemon.rs`
reads the `x-forwarded-for` header verbatim and appends the **full, unmasked** IP
address — together with the raw timestamp, requested URI, and full user-agent string —
to a plaintext CSV file (`assets/ledger_telemetry.csv`), with no octet-dropping or
masking logic anywhere in the function. The downstream `omni-matrix-engine.rs` then
performs a MaxMind GeoIP lookup directly against that same full, unmasked
`std::net::IpAddr` (`ip_addr.parse()` at line 204) — a masked address (final octet
zeroed) would not resolve to a useful lookup, so the current design depends on holding
the complete address, the opposite of the article's claim. No cookie-related code was
checked as part of this pass (out of scope for this finding); the IP-masking claim
specifically is what this correction addresses. **Flagged as a live compliance/privacy
discrepancy, not resolved unilaterally** — this touches a real, publicly disclosed
privacy posture claim, not just an internal architecture description, so it is being
escalated to Command/project-totebox by mailbox in addition to this callout, per this
archive's standing practice for legal/compliance/anonymization content (draft
conservative, flag, never silently resolve).

[[pointsav-overview|PointSav]] platform interfaces operate on a zero-state telemetry architecture: no personally identifiable information (PII) is collected, no tracking cookies are deployed, and no session state is retained. Operational metrics are limited to anonymized, IP-masked geospatial signals used for infrastructure auditing. Operators in regulated industries gain a public-facing posture consistent with GDPR, PIPEDA, and equivalent data-minimisation requirements, without requiring cookie-consent frameworks. See also [[sovereign-telemetry|sovereign telemetry]] and [[telemetry-architecture|the telemetry architecture]].
Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. The full trademark notice appears in the footer of every page on this site.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →