Scope, private access, and the demo
This policy explains how Nintek (“we”, “us”) handles information inPulseWire. The owner workspace uses Microsoft Entra ID and an allow-list of authorized principals. There is no public account registration.
The live service also has a separate 24-hour, read-only demo. The demo does not require Microsoft sign-in, uses a shared demonstration workspace, and disables mutations rather than creating a personal account. A demo session is still recorded in the session ledger so it can expire and be revoked.
PulseWire does not use advertising SDKs, cross-app tracking, or behavioral advertising. It does process reading, source, generated-analysis, session, and operational data needed to run the private reader and demo.
Information PulseWire processes
- Identity and sessions. Microsoft Entra provides the principal and profile claims needed to authorize the owner workspace. PulseWire keeps a database-backed session ledger so a session can be revoked even before its signed cookie expires.
- Sources and reading activity. Feed subscriptions, source records, article metadata and text, story groupings, chronology, evidence and review state, Saved items, read state, and reader preferences.
- Generated analysis. Embeddings, briefs, scores, ranking inputs, and related model output used to group, retrieve, and explain the private edition.
- Operations. Worker and feed health, request timing, version information, errors, and AI usage or cost records needed to run, secure, recover, and troubleshoot the service.
Azure AI and requests to source websites
PulseWire uses Azure AI Foundry’s OpenAI-compatible service for configured chat and embedding deployments. It sends the source material, story context, or query needed for a brief, embedding, ranking, or retrieval operation and stores the resulting analysis needed by the reader. Deployment names are configuration, not a hard-coded model claim.
To ingest reporting, PulseWire requests RSS feeds and source pages over the public internet. A source or its hosting provider can receive ordinary network information about that request, such as timing, service IP address, and request headers, under its own privacy practices. If you open a source link, your browser contacts that publisher directly and the publisher may receive the usual browser request information.
Microsoft provides Entra identity and Azure hosting, PostgreSQL, and AI services. We do not sell personal information. Information may also be disclosed where required by law or reasonably needed to protect the service.
Offline Saved snapshots
PulseWire can explicitly download a sanitized Saved-story snapshot to identity-scoped IndexedDB for offline reading. The snapshot can include text, source evidence, chronology, and presentation data, but it excludes article images. The service worker caches the public app shell and static assets; it does not turn the private workspace into a local-first database.
Offline snapshots are not end-to-end encrypted. PulseWire verifies snapshot integrity with a checksum, which does not prevent someone with access to the browser profile from reading the stored copy. The browser or operating system may also evict it.
Export, deletion, and retention
PulseWire currently has no self-service account export, account deletion, or automated bulk-deletion route. Emailing a request starts a manual review; it is not a promise of an immediate, one-click, or fully automated result. The scope may include workspace records Nintek controls, but it does not include the underlying Microsoft account or independent provider records.
| Data or control | Where it lives | Export or backup | Deletion and retention |
|---|---|---|---|
| Microsoft Entra identity and PulseWire sessions | Microsoft authenticates the identity. PulseWire stores the allowed principal and a server-side session ledger; the ledger does not store raw tokens, IP addresses, or user-agent strings. | PulseWire has no self-service identity or account export. Microsoft provides controls for the underlying Microsoft account. | You can revoke the current session or all PulseWire sessions. Revocation does not delete the Microsoft account or Microsoft-held sign-in records. |
| Articles, story groups, embeddings, briefs, read state, and source settings | PulseWire stores this workspace data in Azure-hosted PostgreSQL, including pgvector embeddings. | There is no self-service account or workspace export in the current product. | Unsaved article bodies and embeddings are kept in full for 7 days, reduced after 7 days, and removed after 30 days. Saved or read-referenced records keep a reduced breadcrumb or saved snapshot as described below. |
| Saved stories and immutable server snapshots | A Saved item and its sanitized, checksummed snapshot remain in the private server workspace so the saved edition can be reproduced. | A Saved snapshot can be explicitly downloaded for offline reading. This is a reading copy, not a full account export. | Saved records are exempt from ordinary article pruning while they remain referenced. Removing a Saved item does not delete a separate browser copy until that copy is also removed or cleared. |
| Offline Saved copies | Identity-scoped IndexedDB in the browser profile. Copies exclude article images and are not end-to-end encrypted; SHA-256 is used for integrity, not encryption. | The copy is already local to that browser profile and is intended only for offline reading. | Remove the download in PulseWire, clear the site’s browser storage, or sign out successfully. Sign-out is blocked until the client confirms its private offline stores were cleared. |
| Read-only demo session | A 24-hour demo session uses a shared demo workspace. Demo mutations are disabled rather than saved as a personal account. | There is no personal demo-account export because the demo does not create a personal PulseWire account. | The demo session expires and its session-ledger record is eligible for cleanup. Shared demonstration source data is not personal account content. |
| Provider and support records | Microsoft, Azure AI Foundry, source websites, and any support mailbox may retain records needed to provide, secure, or support their part of the service. | Use the provider’s controls for provider-held data. Support correspondence can be requested from Nintek when applicable. | Provider retention follows the provider’s terms and legal obligations. Nintek reviews support-data deletion requests subject to security and legal needs. |
Scroll horizontally to read all four columns →
To request access to or deletion of account-associated data, emailprivacy@nintek.com. We will confirm identity, scope, and any records that must be retained for security, recovery, or legal reasons.
Sessions and security
Production sessions use a secure host-only cookie plus the server session ledger. Settings can revoke the current session or all owner sessions. A successful sign-out first clears identity-scoped offline data and then revokes the server session; if the privacy clear fails, sign-out is stopped instead of leaving a private browser copy behind under a signed-out screen.
The session ledger stores identifiers and lifecycle timestamps needed for revocation. It does not store raw Microsoft tokens, IP addresses, or user-agent strings. Expired ledger entries are removed by a cleanup task.
Children, changes, and contact
PulseWire is a general adult reading tool and is not directed to children. We do not knowingly create personal PulseWire accounts for children.
We may update this policy when the service or its data practices change. The effective and review dates at the top identify this version.
Questions about data handling can be sent toprivacy@nintek.com. Product help is available on PulseWire Support. Use of the service is also subject to theNintek Terms of Use.
Evidence note. Reviewed against immutable PulseWire release-visual authority 6b4c1c7 on August 23, 2026. Model deployment names remain operator-configured, so this policy does not name an unverified model.