Launch policy draft

Poventi Privacy Notice

This is a launch-stage product draft and should receive legal review before broad commercial use.

Information collected

Poventi may collect account details, profile information, questions, responses, transaction references, quality/reputation signals, device/session analytics, support or safety reports, video-session scheduling/attendance metadata, and verification evidence/status information needed to operate the marketplace.

Live video

Poventi may use an embedded video provider to create private, time-bounded rooms for selected customers and helpers. Poventi may store session scheduling, participant-consent, provider-room reference, join/leave timing, attendance duration, and payment/payout status. Direct participant contact information should not be required for the in-platform meeting experience.

Recording and transcription are off in the B9 launch flow. Poventi does not intentionally request or store a recording or transcript through that flow. Any future recording/transcription capability must have an explicit consent and legal/privacy design before activation, including consideration of jurisdiction-specific recording laws.

Executive Board context

Executive Board customers may provide a persistent context brief about their organization, goals, products, markets, and recurring decision needs. That context is stored so the same curated advisors can learn the customer over time and may be included with later Board questions. Customers should not place passwords, payment credentials, highly sensitive personal information, or information they are not authorized to share into Board context.

Poventi should disclose Board context only to the recurring advisors and service providers reasonably necessary to operate the Board relationship, subject to marketplace, safety, and confidentiality controls. If a Board advisor is replaced, the qualified replacement may receive the current Board context needed to continue the advisory relationship.

Verification data

Verification may involve third-party identity or professional-verification providers, corporate-email challenges, institution or issuer confirmation, approved documentary review, and consistency checks. Poventi should store only the verification status, provider/reference metadata, non-sensitive evidence summary, and audit history needed to support a badge. Raw government-ID images and biometric identity data should remain with the configured identity provider rather than being copied into Poventi verification tables.

Customers may see whether relevant qualifications are independently verified and a non-sensitive verification summary. Customers should not receive helpers’ raw identity documents, private verification codes, or other sensitive underlying evidence.

Why it is used

Information is used to operate the marketplace, match customers and helpers, substantiate qualification requirements, process payments, schedule secure live sessions, maintain recurring Executive Board context, prevent fraud and circumvention, evaluate response quality, improve the product, and meet legal obligations.

Private ratings

Two-sided ratings and comments are private to Poventi administrators at launch and may be used in internal reputation and matching systems.

Service providers

Poventi may use infrastructure, database, payment, embedded-video, identity, professional-verification, analytics, and email providers to operate the service. Only information reasonably needed for those services should be shared.

Retention and controls

Verification evidence can expire, be rejected, or be revoked, and a badge should stop being displayed when its evidence no longer supports it. Exact retention/deletion periods for video metadata, persistent Board context, and other marketplace data, consent language, and procedures for access, correction, redaction, or deletion must receive final legal review before broad launch.