Source visibility
Every surfaced signal should carry source category, freshness, confidence, and reason code.
Security and data practices
This staging trust center states what is true now and labels what still needs owner, security, operations, or counsel approval. It does not borrow badges, uptime promises, or legal language from a future product.
Current control matrix
Unknown production facts are not omitted. They are marked as approval-needed items so the next reviewer can close them deliberately.
Data-practice disclosure worklist
Before public product launch, Pursenda should publish data categories, sources, purpose, identity level, update/freshness, retention, customer controls, correction/deletion route, suppression/opt-out route, geography limits, subprocessors, and whether product data trains models.
Every surfaced signal should carry source category, freshness, confidence, and reason code.
Anonymous account activity must not be described as a named person's private search history.
Correction, suppression, opt-out, deletion, and export routes need approved process language.
Security questionnaires can be requested by email during staging; a formal process needs approval.
Learn moreTrust documents
Each route says what is approved versus pending so review does not hide inside the footer.
Static-site behavior, future product data gates, contact path, and counsel review status.
Learn moreNo self-serve access, no approved commercial terms yet, and owner/legal approval notes.
Learn moreNo analytics, trackers, pixels, embeds, chat widgets, or form cookies on this staging site.
Learn moreData-processing addendum route and the approval items needed before customer processing.
Learn moreStaging register for future vendors, purposes, data categories, and notice process.
Learn moreOutreach and data-use boundaries that need approval before users send from the product.
Learn more