Privacy Policy

PulseMark collects information needed to provide the Service to OEMs and battery-service operations. At a high level, this includes account and organization details, user profile and role information, project and workflow information, uploaded evidence and its metadata, billing and subscription information handled through our payment processor, contact and sales inquiry information, support communications, and operational logs.

The sections below describe each category in more detail. This is draft copy and remains subject to legal review.

When an organization registers, PulseMark collects organization details and the information needed to set up and operate the account, such as the organization name and the configuration your administrators choose. This information identifies your organization and supports access management for your users.

For each authorized user, PulseMark collects basic profile information and the role assigned within your organization. Roles determine what a user can see and do, including Company Admin, Supervisor, Technician, and outside provider access. Role information is used to enforce access boundaries inside the Service.

PulseMark collects the project and workflow information your team enters, including diagnostic projects, review records, triage and discovery activity, diagnostic outcomes, and related notes. This information is the core of the diagnostic workflow your organization uses the Service to perform.

PulseMark processes the evidence files your team uploads to a project, along with metadata about those files such as file type and size. Supported evidence uploads include images, PDF, TXT, XML, CSV, and XLSX files. PulseMark does not support video or audio uploads as diagnostic evidence. Uploaded evidence is stored and processed to support the diagnostic workflow.

Billing and subscription information is handled through Stripe, our payment processor. PulseMark receives the subscription and billing status it needs to operate your plan, but full payment card numbers are entered into Stripe-hosted checkout and are not collected or stored by PulseMark outside of Stripe’s systems.

When you submit a public contact or sales inquiry, PulseMark collects the details you provide so its team can respond. A contact inquiry is delivered to PulseMark’s team as an operational notification to respond to your request; it is not stored as an account or project record. You should not include sensitive diagnostic evidence in a public inquiry.

When you contact support, PulseMark collects the content of your support communications and any files you attach to a support request. Support attachments belong to the support request, follow their own retention and purge handling, and are separate from project evidence. They are not a long-term diagnostic evidence store.

PulseMark collects operational logs and technical information such as device and browser details, access activity, and security and operational telemetry. This information supports security, troubleshooting, and reliable operation of the Service. PulseMark aims to keep operational logs free of sensitive evidence content.

PulseMark uses the information it collects to:

• provide, operate, and maintain the Service;
• manage accounts, users, roles, and access;
• process evidence and support the diagnostic workflow;
• handle plans, Evidence Credit usage, and billing;
• respond to contact, sales, and support requests;
• secure the Service and investigate misuse; and
• meet operational and legal obligations.

PulseMark shares information with the service providers that help operate the Service, such as payment processing, hosting, and storage providers, and only as needed for them to provide their service. PulseMark does not provide your organization’s evidence to other customers. PulseMark does not intend to sell personal information. Final privacy language remains pending legal review.

Payments are processed by Stripe through Stripe-hosted checkout and Stripe’s billing systems. Stripe handles payment card details directly. PulseMark relies on Stripe for payment processing and receives the billing status needed to operate your plan, without collecting or storing full card numbers itself.

The Service is hosted on cloud infrastructure, including Vercel for application hosting. Hosting providers process information as part of delivering the Service. PulseMark relies on these providers’ infrastructure and operational practices for the hosting layer of the Service.

PulseMark uses managed database and object storage providers to store project data and uploaded evidence. These providers store and serve data as part of operating the Service. Where applicable, evidence files are held in object storage and project records are held in a managed database.

To respond promptly, PulseMark may use an internal operations notification channel to alert its team when a new contact, sales, or support request is received. These are operational notifications used to prompt a response. They are not a customer-facing data store and are not used as a long-term record of account or project data.

PulseMark and its providers may use cookies or similar technologies that are needed to operate the Service, such as keeping you signed in and supporting basic site functionality. This draft describes cookie use at a high level, and final cookie and tracking disclosures remain subject to legal review.

Different categories of data are retained for different periods. How active project evidence, trashed or archived content, support attachments, contact inquiries, billing records, and audit history are retained is described on the data retention page.

Your administrators can manage much of your organization’s information directly in the Service, including users, roles, and project data. For access, update, or deletion requests that cannot be handled in the app, you can reach PulseMark through the contact page. How PulseMark responds to such requests, and any applicable limits, remains subject to legal review.

PulseMark uses reasonable technical and organizational measures intended to protect information, including authentication, role-based access, and organization scoping. No system can be completely secure, and PulseMark does not promise that the Service is immune from all risk. More detail is provided on the security page.

The Service is a business tool intended for OEMs and battery-service operations and is not directed to children. PulseMark does not intend to collect personal information from children, and the Service should not be used by anyone who is not an authorized user of a business account.

Depending on where you are located, you may have privacy rights under applicable state, national, or international law. PulseMark’s approach to these rights is being prepared, and this placeholder section will be finalized as part of legal review. This page does not yet state a final compliance program for any specific privacy law.

PulseMark may update this draft privacy policy as the product and its legal review progress. Material changes intended for the final policy will be reflected on this page. The draft status date above indicates the current draft.

Questions about this draft privacy policy can be directed to PulseMark through the contact page.