Terms of Service
Effective July 30, 2026.
This interim policy applies only to the informational ProgramMetrics website, visitor email inquiries, and the current inactive product presentation.
ProgramMetrics describes eight fixed automated One-Time Analytics tiers, planned private Studio subscriptions, and separately licensed templates and workflow apps. Current availability is stated on each product page.
Current availability
Checkout, payment processing, customer file uploads, paid outputs, and Studio access are not active. Published descriptions and prices are for review and planning only.
The product lines remain separate. No described offer currently provides customer access or authorizes data submission.
Initial-launch data eligibility
ProgramMetrics will accept only properly de-identified, structured data that the customer is legally authorized to analyze. Customers must de-identify their data before any future submission and confirm they have the necessary legal authority to use it.
ProgramMetrics does not perform legal de-identification or certify that customer data meets HIPAA, FERPA, or another regulatory standard.
Prohibited data
Names, street addresses, email addresses, phone numbers, Social Security numbers, medical-record numbers, student-identification numbers, full dates of birth, payment-card or banking data, passwords, credentials, authentication tokens, security secrets, identifiable health information including Protected Health Information (PHI), FERPA-protected identifiable education records, and other legally restricted or regulated identifiable data are prohibited.
Open-ended narrative fields, case notes, comments, and other free-text fields that may contain identifying information are prohibited during the initial launch.
De-identification boundaries
Removing names alone may not properly de-identify a dataset. Customers must assess indirect identification risks from dates, geographic information, small groups, rare characteristics, and combinations of fields.
Anonymous record identifiers are permitted only when ProgramMetrics cannot use them to identify or contact an individual. Customers must retain every re-identification key outside ProgramMetrics and must not provide that key to ProgramMetrics.
The private Studio design uses browser-local processing by default, but browser-local processing does not eliminate privacy risk. Any future automated screening or checkbox will be supplemental only and will not replace customer responsibility.
Customers will remain responsible for reviewing and validating future outputs before relying on them.
This policy may be updated before checkout, uploads, paid services, or customer access are activated.
Questions can be sent to hello@programmetrics.io.