Data Retention

Data Retention

Draft / pending legal review. This page is provided for transparency while PulseMark prepares final legal documentation. Final terms may change before public launch.

Draft status date: June 2026

This draft data retention overview distinguishes the different kinds of data PulseMark Field Diagnostic handles and how each is retained. It is grounded in how the product actually works today, including its archive and purge behavior.

Active project evidence, trashed or archived content, support attachments, contact inquiries, billing records, and audit history are each handled differently. Where this page states a concrete timeline, it reflects current app behavior; where it does not, cautious language is used pending review. Questions can be directed through the contact page.

1. Active project evidence

Evidence uploaded to a project is available for that project’s workflow while the project and account remain active, subject to the app’s retention, purge, account, and billing controls. Active project evidence retention is included in Evidence Credit pricing, as described on the pricing page.

Active project evidence is not permanent storage, and it is not unlimited. It is also different from support attachments, which are described separately below.

2. Trash and purge-timer content

When projects or evidence are deleted or archived, they move out of active use and follow a purge timer rather than remaining available. For standard archived projects, the project is scheduled to be purged 30 days from archive.

A retention extension can extend retention by an additional 6 months from the time the extension is applied. Before a scheduled purge, the app sends a retention warning for archived standard-retention projects during the period shortly before the scheduled purge date. When a project is permanently purged, the project record and its associated data are permanently removed according to the purge workflow.

3. Support attachments

Files attached to a support request belong to that support request. Support attachments have their own retention window and purge handling and are removed after their retention window according to the support workflow.

Support attachments are not the same as active project evidence, and they are not a long-term diagnostic evidence store. Diagnostic evidence belongs in a project, not in a support request.

4. Contact and sales inquiry submissions

A public contact or sales inquiry is delivered to PulseMark’s team as an operational notification so the team can respond. A contact inquiry is not stored as an account or project record. How contact inquiries are handled is also described on the privacy page.

5. Billing and subscription records

Billing and subscription records are retained as needed to operate plans and for accounting and record-keeping. Payment records are also held by Stripe, the payment processor, as part of processing payments. PulseMark retains the billing status it needs to run your plan without storing full payment card numbers.

6. Audit and history records

The Service keeps audit and project history records that support traceability of the project record, including history of key actions. These records are retained to support a defensible diagnostic workflow. PulseMark does not state a fixed retention period for audit and history records on this draft page; the final retention period remains subject to review.

7. Certified Decision (future capability)

Certified Decision is a future capability that is not currently available. Any retention associated with Certified Decision would apply only if and when that capability is released. This page makes no active retention promise for Certified Decision, because the capability is not part of the current Service.

8. Backups, logs, and operational records

PulseMark and its providers keep backups, logs, and operational records to support security, reliability, and recovery of the Service. These are retained for a limited period as part of normal operations. PulseMark does not state a fixed retention period for backups and operational logs on this draft page; the final approach remains subject to review.

Questions about this draft policy can be directed to PulseMark through the contact page. This page is a draft prepared for transparency and remains subject to legal review before public launch.

Data Retention | PulseMark Field Diagnostic