Data policy
data policy.
What Spectre Spaces keeps, for how long, and what ends it. Written from the code, item by item.
Effective November 20, 2026.
Our principles
Spectre Spaces was built from the ground up around a few rules, and the software enforces them:
- The agency owns its book. We hold it to run the service for the agency, never to sell it.
- Medicare data belongs to the beneficiary. It comes in only with their consent, stays only as long as that consent says, and never goes to an AI tool.
- Proof is permanent. Consents and the audit trail are append-only, so what was agreed, and when, can always be shown.
- Health information stays out of logs. Our servers mask personal details before writing a log line.
- Fail closed. Every flow that touches health information sits behind a gate that stays shut until its agreement is recorded and its code checks pass.
This page describes the timers and limits our code sets today. Where nothing ends a record automatically, we say so.
Medicare data
| What | How long | What ends it |
|---|---|---|
| One-hour plan review records | One hour from when the beneficiary shares, at most. Held in a short-lived encrypted cache, never in our database or logs. | Deleted automatically at the hour, or at once when the beneficiary stops, the agent ends it, or consent is withdrawn. |
| Medicare access tokens (one-hour review) | Not kept. | Sent to CMS to be cancelled right after the records are read. |
| Sharing link or QR code | 15 minutes to start; a link sent before a meeting works until the meeting ends, never more than three days. | Expires on its own; only a fingerprint of the link is stored. |
| Partner app summary | Readable by the named partner app only during the beneficiary's hour. | The hour ends. After that, the partner's own policy covers its copy. |
| Saved Medicare record | Until the agency disconnects it or a deletion request is handled. | Disconnecting removes the tokens and claim details of the most recent connection. A short record (identifiers, summary labels, an audit line) stays. Revoking at Medicare.gov stops new data only. |
| Medicare consent record and audit lines | Kept for at least ten years. | Nothing; they hold no health information and cannot be changed. |
The agency's book
| What | How long | What ends it |
|---|---|---|
| Clients, households, policies, appointments, tasks, documents | Until the agency deletes them. | Deleting hides the record from the app; the database row stays. Ask us to remove it for good. |
| Spaces Ink documents | Until deleted by someone allowed to manage them. | Deleting removes the document. |
| Text threads, call logs, lead submissions, emails and letters written in the space | No automatic timer. | Ask us to remove them. |
| Pemby chats, saved preferences, and workflow runs | No automatic timer. | Ask us to remove them. |
| Budget and utility reviews, field visit lists | No automatic timer. | Ask us to remove them. |
| Billing events from Stripe | No automatic timer. | Ask us; Stripe keeps its own copy. |
| Seats (accounts) | Removing a seat turns it off and keeps the record. | An account that wrote activity history or a consent record is turned off, not deleted. |
Records that can't be changed
| What | How long | What ends it |
|---|---|---|
| Consent records and their evidence | At least ten years from when they are recorded. | Nothing deletes them automatically after that. |
| Signed Scope of Appointment copies | Ten years from when they are stored. | Can't be changed or removed during that time. |
| Audit trail | Kept; each agency's chain is hash-linked and checked nightly. | Cannot be changed or deleted, in the app or with our admin tool. |
| Client activity history and the text log | Kept with the client record. | Cannot be changed or deleted by people at the agency. |
Sessions, devices, and links
| What | How long | What ends it |
|---|---|---|
| App session | Ends after 30 minutes without activity. | Inactivity or signing out. |
| Offline copy of the book in your browser | Until you sign out in that browser. | Signing out. Ending a session for inactivity does not clear it. |
| Wallet card links | 30 days. | The link expires. |
| Log lines | Kept for operations. | Personal details are masked before a line is written. |
This website
| What | How long | What ends it |
|---|---|---|
| Request-access and developer submissions | No automatic timer. | Your request, or when we no longer need them. Private backups are covered too. |
| Spam-check token, IP address, browser details | Not stored with your submission. | Only the country Cloudflare reports is kept. |
Copies other services keep
Twilio, Lob, Stripe, our mail relay, and a sender's own Gmail or Google Calendar keep their own copies under their own rules. CMS keeps its own records of a beneficiary's connected apps. Our code sets no deletion schedule for database backups yet.
Deletion requests
Email privacy@s2olutions.com. Clients and prospects should start with the agency that holds their information; we help the agency answer. We confirm who you are, answer within 45 days, and handle each request as the law requires. Records the law requires us or the agency to keep, such as consent proof and signed Scope of Appointment forms, stay for their period.
Related: Privacy policy · Terms of use