Trust

Context is only useful if people can trust where it came from.

GREPHT's trust model is built around provenance, least-necessary access, clear uncertainty, and keeping sensitive credential material out of the product whenever references are sufficient.

Credentials: Recorded by name and location. Never by value — GREPHT is not a secret store.
Where we run: A control plane. GREPHT never runs your workloads or holds your files.
Your record: Stays readable to you permanently, including after you stop paying.
Certifications: None yet. When there is one, it will be named here with its scope and date.

Provenance

Show the source.

Facts and relationships carry source, observation time, and whether they were explicit or inferred.

Credentials

Reference secrets. Don't copy them.

Understand credential relationships without becoming a plaintext secret store.

Unknowns

Incomplete stays incomplete.

Unknown data is surfaced as unknown instead of converted into false certainty.

Builder respect

Advisory, not surveillance.

Trust is undermined if the product becomes a hidden monitoring layer or approval gate. There is no per-builder activity feed.

Coverage

Never imply completeness.

GREPHT knows what has been recorded. It says what it has not seen rather than presenting a partial picture as the whole one.

Billing

Stripe handles payment data.

GREPHT uses Stripe-hosted Checkout and Customer Portal instead of storing raw card details.

What we don't claim

This page stays shorter than it could be.

Security pages tend to list every certification a company hopes to hold. Anything not listed here is not something GREPHT does yet.

If you stop paying: Your record stays readable — tools, findings, the Map, runbooks and history. What stops is GREPHT adding to it, and monitoring stops with it. That is stated at signup, again before a lapse, and on every monitoring surface the day it happens, rather than left to be discovered.
Certifications: GREPHT does not currently hold a published security certification. When that changes, it will be stated here with its scope and date.
Access: Connections request the narrowest access that still lets GREPHT derive useful context, and what was accessed stays inspectable.
Questions: Security review requests are answered directly by the people who built the thing, rather than routed through a portal.

Write to hello@grepht.com.

Judge the context by the evidence attached to it.

Start free trial See how GREPHT works

Builder · 7 days free, then $29/month. Cancel any time before it ends.